CommitOnDemand
The CommitOnDemand parameter specifies whether the High-speed Apply Engine processes or ignores any COMMIT or ROLLBACK statements included in SQL input (when the value of the DistributionType parameter is Object).
Attributes
This parameter has the following attributes:
Attribute | Value |
|---|---|
Section | [CommitTriggers] |
Abbreviation | None |
DBMS | Db2, Db2 LUW, Oracle |
Required? | No |
Valid values | Yes or No |
Default value | No |
Usage
Use this parameter as one method to make High-speed Apply Engine to honor the original COMMIT or ROLLBACK statements in your SQL input.
- Specify No to direct High-speed Apply Engine to ignore COMMIT or ROLLBACK statements in the SQL input and issue COMMIT statements at points determined by other parameters (such as StatementCount-parameter and Time). This value is the default.
- Specify Yes to direct High-speed Apply Engine to apply COMMIT or ROLLBACK statements to the target database at the same points where the COMMIT statements occur in the SQL input.
- If you specify Yes, you must set the value of the MaxAgents parameter to 1.
- You can specify Yes only for SQL input.
- If you specify Yes, High-speed Apply Engine honors the input COMMIT or ROLLBACK statements, but it might perform additional commit or rollback actions in response to certain Action parameters of a conflict resolution rule or to resource shortages.
This parameter causes High-speed Apply Engine to honor the original COMMIT or ROLLBACK statements with only one agent and for SQL input. To honor these statements with more than one agent or in logical log input, set the DistributionType parameter to UR. For more information, see DistributionType.
Related topics