Dynamic bind

The dynamic bind process uses packages instead of plans to optimize the DBRM bind process and allows SQL preparation to be completed during execution.

Based on the dynamic bind technology, BMC AMI Copy has the following behavior when it is retrying plan OPENs and BINDs:

• If the initial plan OPEN fails because the plan is not found, is invalid, or the user lacks authority and the plan is bound successfully, BMC AMI Copy retries the OPEN.

  Important

  If the reason code for the initial OPEN failure is lack of authority, the error may be due to the plan not existing or to insufficient user privilege. If GRANT EXECUTE to PUBLIC is supported, BMC AMI Copy attempts to BIND the plan even though the plan may already be bound.

  If the reason code for the initial OPEN failure is lack of authority and GRANT EXECUTE to PUBLIC is not supported, BMC AMI Copy will not allow the BIND attempt.

• If the initial plan OPEN fails for any other reason than the plan is not found, is invalid, or the user lacks authority, BMC AMI Copy retries the OPEN, but does not attempt a plan BIND.
• If the plan BIND is successful, but the following retry of the OPEN fails, BMC AMI Copy does not retry the plan BIND regardless of the reason for the OPEN failure.
• If the BIND fails because of a deadlock, BMC AMI Copy retries the OPEN, and if the OPEN fails for any of the reasons listed above, the BIND is retried. Otherwise, the BIND is not retried.
• If the BIND attempt is not allowed by BMC AMI Copy or fails for any reason, no retry of the OPEN or the BIND is done.

See also the description for the BINDQUALIFIER=ACP vvr and PUBLICPLAN=YES.