MaxFailedBinds
For Db2 and Db2 LUW, the MaxFailedBinds parameter specifies how many bind actions can fail before the High-speed Apply Engine stops processing the apply request.
Attributes
This parameter has the following attributes:
Attribute | Value |
|---|---|
Section | [BindTuning] |
Abbreviation | None |
DBMS | Db2, Db2 LUW |
Required? | No |
Valid values | An integer from 0 to 32767 |
Default value | 5 |
Usage
When a bind action fails for reasons other than unavailable Db2 resources (for more information, see MaxRetries), High-speed Apply Engine counts the action as a failed bind action and continues to process the apply request, using dynamic SQL or EXECUTE IMMEDIATE. The MaxFailedBinds parameter defines the point when High-speed Apply Engine stops processing because of failed bind actions. When High-speed Apply Engine exceeds this limit, it issues message BMCAPT0072 and terminates processing with an error.
Specify a number representing how many failed bind actions High-speed Apply Engine accepts before it terminates processing.
Consider these points regarding the MaxFailedBinds parameter:
- Use this parameter to stop High-speed Apply Engine from processing large amounts of input dynamically when a problem in your environment prevents bind actions from succeeding. Frequent failed bind actions can indicate a serious problem with the target DBMS.
- When a bind action fails because of an unavailable Db2 resource condition and High-speed Apply Engine exceeds the MaxRetries limit (MaxRetries), High-speed Apply Engine does not count the action as a failed bind for purposes of this parameter. High-speed Apply Engine continues processing with dynamic SQL or EXECUTE IMMEDIATE.
- High-speed Apply Engine does count a failed bind action for purposes of this parameter if the bind fails because of allocation errors, I/O errors, or any other conditions that are not related to unavailable Db2 resources.
Related topic