Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see High-speed Apply Engine 13.1.

Format of conflict resolution rules

A conflict resolution rule in any [xxxConflict] section consists of a Code parameter and one or more Action parameters, as shown in the following figure:

Code=code
Action=action01
Action=action02

The code value defines an Oracle message number, a Db2 SQL code, or a conflict type (for more information, see Code parameter values). The action value defines the action that the High-speed Apply Engine takes when it encounters the conflict type that is defined by the code value (for more information, see Code parameter values).

If you specify more than one action for a code, the actions must be valid in the specified sequence. For example, ifaction01 in the preceding figure was specified as Abort, then action02 could never be performed. The following sections describe the codes and actions that you can define for these parameters.

Several actions cause High-speed Apply Engine to perform a commit action or a rollback action. For more information, see Actions for conflict resolution. The value of the DistributionType parameter or the CommitOnDemand parameter can limit commit or rollback actions to the COMMIT or ROLLBACK statements in your input. High-speed Apply Engine might perform additional commit or rollback actions in response to certain Action parameters of a conflict resolution rule or to resource shortages.

Related topic

Conflict-resolution

 

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