MaxRetries
For Db2 and Db2 LUW, the MaxRetries parameter specifies how many times the High-speed Apply Engine attempts to bind static SQL if the bind action fails due to unavailable Db2 resources (for example, Db2 catalog contention).
Attributes
This parameter has the following attributes:
Attribute | Value |
|---|---|
Section | [BindTuning] |
Abbreviation | None |
DBMS | Db2, Db2 LUW |
Required? | No |
Valid values | An integer from 1 to 32767 |
Default value | 5 |
Usage
When a bind action fails because of unavailable Db2 resources, High-speed Apply Engine tries the bind action again, in case the resource (such as the Db2 catalog) becomes available. When the number of retry attempts exceeds this value, High-speed Apply Engine stops attempting to bind static SQL and continues processing with dynamic SQL or EXECUTE IMMEDIATE.
Specify a number representing how many times High-speed Apply Engine retries the bind action before it stops attempting to bind static SQL.
Consider these points regarding the MaxRetries parameter:
- Use this parameter to adapt High-speed Apply Engine’s retry attempts to the amount of Db2 catalog contention in your environment. If you have high amounts of catalog contention, set this parameter to a higher value.
- The MaxRetries parameter handles only bind actions that fail because of unavailable Db2 resources. High-speed Apply Engine does not retry bind actions that fail because of other reasons.
- The MaxFailedBinds parameter handles bind actions that fail for other reasons (for example, allocation failures or I/O errors). High-speed Apply Engine does not count bind actions that fail because of unavailable resources as failed binds for purposes of the MaxFailedBinds parameter. For more information, see MaxFailedBinds).
Related topic