RIRecursionLimit
Usage
Use this parameter to control how much processing High-speed Apply Engine performs to determine the RI relationships of the target tables in the apply request. With this parameter, you can avoid unnecessary RI-related processing when your target database contains many generations of RI relationships, but your target tables are related to only a few generations of RI relationships. Select one of the following values:
- Specify 0 to disable RI-related processing. (Alternately, you can set the value of the RIClustering parameter to No).
- Specify a number between 1 and 32767 to define the number of generations in the chain of RI parent relationships.
- Specify Max to direct High-speed Apply Engine to determine all of the 'parent' RI relationships beginning with the target tables of the apply request. For compatibility with earlier versions, the default value is Max.
Be aware of the following points about this parameter:
- If either the RIClustering parameter or the URCheckRI parameter is set to No, High-speed Apply Engine ignores the value of the RIRecusionLimit parameter
High-speed Apply Engine looks at only the parent tables in RI relationships. High-speed Apply Engine starts with the first target table it encounters. If the RIClustering parameter is Yes and this parameter is greater than zero, High-speed Apply Engine interrogates the target DBMS to find the immediate parent tables of the target table. Then it determines the parents of the parents and so forth, depending on the number of generations that you specify. When High-speed Apply Engine encounters a new target table, it follows the chain of RI parent relationships again, up to the number of generations you specify.
For example, if you know that your input includes only child tables and their immediate RI parents, specify 1 to prevent High-speed Apply Engine from acquiring RI information for any grandparent tables. Match the scope of RI-related processing to the scope of the RI relationships in your input data.