IBM Support

Manual bind is needed for replication when CUR_COMMIT is set ON in DB2

Flashes (Alerts)


Abstract

When the CUR_COMMIT configuration parameter is set to ON in DB2 for Linux, UNIX, and Windows Version 9.7 and later, you must issue the bind command manually with a new bind parameter to run the replication process without any issue.

Content

When CUR_COMMIT is set to ON, a query returns the currently committed value of the data at the time when the query was submitted. The query does not wait for the outcome of other insert/update/delete operations that have not yet committed, and instead returns the result immediately.

Because of this behavior, the replication packages must be bound with CONCURRENTACCESSRESOLUTION WAIT_FOR_OUTCOME.

Examples of bind:

Q Apply
db2 bind @qapply.lst isolation ur blocking all grant public concurrentaccessresolution wait_for_outcome

Q Capture
db2 bind @qcapture.lst isolation ur blocking all concurrentaccessresolution wait_for_outcome

SQL Apply
db2 bind @applycs.lst isolation cs blocking all grant public concurrentaccessresolution wait_for_outcome
db2 bind @applyur.lst isolation ur blocking all grant public concurrentaccessresolution wait_for_outcome

SQL Capture
db2 bind @capture.lst isolation ur blocking all concurrentaccessresolution wait_for_outcome

[{"Product":{"code":"SSDP5R","label":"InfoSphere Replication Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"10.1;9.7;10.2.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
25 September 2022

UID

swg21457826

Page Feedback