Troubleshooting
Problem
I get a "Lock Busy for item" or "Lock Busy for category" sometimes from the UI or as an exception in application logs. I am unable to make changes to the item or category because of this error.
Symptom
The database recognizes that objects are still locked when they are not in use.
Cause
This issue can occur due to an abnormal end of a program or abrupt database issue. In Product Master and InfoSphere Master Data Management Collaboration Server, the application contains a locking mechanism to prevent concurrency of multiple transactions to modify an update at the same time. The locking mechanism prevents corruption or lost updates from concurrency. When an application transaction or external transaction modifies a Product Master object, the application obtains a lock specific to that object and updates the LCK database table. The locking mechanism contains two types of locks in the LCK database table: shared and master. A master lock prevents any other process to read or write that locked object. A shared lock allows another process to read, but not allow a write operation on that locked object.
Diagnosing The Problem
Back up the database.
It is required to shut down InfoSphere Master Data Management Collaborative Server or Product Master with stop_local.sh. The shutdown releases any existing transaction against our locking mechanism in our product. The first SQL statement (A) checks for any shared locks:
SELECT *
FROM lck
WHERE lck_type = 'S';
This second SQL statement (B) checks for master locks for all of the product objects:
SELECT *
FROM lck
WHERE lck_type='M'
AND (
lck_thread_id != '-1'
OR lck_jvm_id != '-1');
Resolving The Problem
If the first SQL statement (A) returns any rows while Product Master is shut down, you must remove all shared locks by running the following SQL statement:
DELETE FROM lck WHERE lck_type = 'S';
If the second SQL statement (B) returns any rows, you must reset the LCK_THREAD_ID or LCK_JVM_ID IDs of any master lock on all objects by running the following SQL statements:
UPDATE lck
SET lck_thread_id = '-1' ,
lck_jvm_id = '-1'
WHERE (
lck_thread_id != '-1'
OR lck_jvm_id != '-1')
AND lck_type='M';
Commit;
After the resolution is applied, you can start Product Master application with start_local.sh shell script.
Note: If you are running Product Master under a Kubernetes or Red Hat OpenShift architecture, it is required to shut down the Product Master application. Before the resolution is applied on the database, you need to shut down pods with an oc (ks) scale --replicas=0 command and ensure all pods are 0/1 running
[{"Type":"MASTER","Line of Business":{"code":"","label":""},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS2U2U","label":"InfoSphere Master Data Management Collaboration Server"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9PZ7","label":"IBM Product Master"},"ARM Category":[{"code":"a8m0z000000cvp2AAA","label":"Error or Warning Messages"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSADN3","label":"IBM Product Master Modernization"},"ARM Category":[{"code":"a8m0z000000GoylAAC","label":"Troubleshooting"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Product Synonym
MDMCS;Infosphere Master Data Management Collaboration Server;WPC ;WebSphere Product Center;MDMPIM;MDM Server for PIM;InfoSphere MDM Server for PIM;InfoSphere Master Data Management Server for Product Information Management; Product Master; IPM
Was this topic helpful?
Document Information
Modified date:
15 September 2022
UID
swg21307221