URCheckRI
The URCheckRI parameter determines whether the High-speed Apply Engine accommodates dependencies between units of recovery (transactions) based on database-defined referential integrity (RI) relationships. High-speed Apply Engine uses this parameter only when it distributes work between multiple agents based on transactions (when the DistributionType parameter is UR).
Attributes
This parameter has the following attributes:
Attribute | Value |
---|---|
Section | [DistributionTuning] |
Abbreviation | None |
DBMS | Db2, Db2 LUW, Oracle |
Required? | No |
Valid values | Yes or No |
Default value | Yes |
Usage
When you select distribution by UR, High-speed Apply Engine can direct multiple agents to wait as needed when statements in two different transactions update tables that are part of a database-defined RI relationship. (High-speed Apply Engine directs the agent processing the later transaction to wait until the agent processing the earlier transaction finishes and performs a commit action.) For more information about distribution by UR, see Distribution by unit of recovery or DistributionType. Select one of the following values:
- Specify Yes to accommodate transaction dependencies based on database-defined RI relationships. This value is the default.
- Specify No to ignore transaction dependencies based on database-defined RI relationships. High-speed Apply Engine does not examine the RI relationships of the target tables in your input data. Use this value to avoid RI-related processing when you know that 1) your input data does not contain any RI dependencies or that 2) you can safely ignore the RI dependencies in your input data.
Be aware of the following points regarding the URCheckRI parameter:
- This parameter does not apply under distribution by object (when the DistributionType parameter is Object). To control RI processing under distribution by object, use the RIClustering parameter.
- Set this parameter to Yes when your input contains a larger number of RI dependencies. If the input contains fewer RI dependencies, consider setting this parameter to No and using a conflict resolution rule with an Code parameter of RIConflict and an Action parameter of Retry.
Related topics