Troubleshooting
Problem
During database upgrade from DB2 V9.5 or earlier, the CUR_COMMIT configuration parameter is set to DISABLED to maintain the same behavior as in previous releases.
For the proper functioning of Workload Automation and to prevent possible internal deadlocks, this parameter must be set to ON.
Symptom
If CUR_COMMIT is not set to ON, some internal operations might be delayed due to multiple transactions insisting to the same DB table. For example, executing composer validate command on a User definition takes longer than expected, specifically up to 3 minutes due to internal timeout expiration.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS8GJD","label":"IBM Workload Automation"},"ARM Category":[{"code":"a8m50000000L33tAAC","label":"Product Operations-\u003EDB2"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
18 December 2023
UID
ibm17099289