Skip to Content

Restart parameters

Related topics

Command and syntax reference

Specifying restart parameters

Enabling restart processing

The [Restart] parameters control processing during a restart.

Parameter

Reference

CheckpointFrequency

RestartID

RestartType

RetainTime

Retry

TableName

 

The [Restart] section is optional, but we recommend that you record restart information for your apply requests, so that you can successfully complete apply processing in the event of an operating environment or DBMS failure.

Error
Warning

In general, do not modify the input file of an apply request between the initial run and restart. Modify the configuration file only to the extent required to resolve error conditions. Ensure that changes to the configuration do not alter the distribution of work between agents. For example, do not change the values of configuration parameters such as MaxAgents, DistributionType, PartitionClustering, or RIClustering.

For more information about restarting the High-speed Apply Engine, see  Restart and recovery. For more information about using these parameters, see  Specifying and using restart parameters.

The following figure shows an example of the [Restart] parameters:

[Restart]
  RestartType=New
  TableName=BMCAPT_APERSCL
  CheckpointFrequency=3
  RetainTime=20
  Retry=5

Restart restrictions

Warning
Important

When running High‑Speed Apply Engine in RESTART mode, the conflict file must not be allocated on a CDS (cloud‑based) device type such as UNIT=CLOUD9.

CDS device types don't support the data set access method used by High-speed Apply Engine when reopening an existing conflict file in a restart scenario. If the conflict file is defined with DISP=OLD or DISP=SHR on a CDS device, High-speed Apply Engine will fail during initialization with the following AMI CLOUD errors:

  • ZM9WJ003E Unsupported disposition
  • ZM9OX006E ExitPoint VOLUME_MOUNT failed with RC=0x00000008 and RSN=0x00000000
  • ZM9OX006E ExitPoint FILE_END failed with RC=0x0000000C and RSN=0x00004014

When using High-speed Apply Engine with RESTART, make sure that the conflict file is allocated on a supported, non‑CDS device type.

CDS device types must not be used for conflict files in restart scenarios.

For more information about Cloud Data Sets limitations, see Requirements and restrictions for integrating BMC AMI Data for Db2 with Cloud Data Sets.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

High-speed Apply Engine 13.1