Troubleshooting
Problem
Customer execute same process by several user at a time. Then process has rolled back due to lock contention even they using synchronized() to serialize processes.
Symptom
Enabling debug log for lock contention, observed following lock for Semaphore was released and acquired by other process.
11056 [f8d] DEBUG 2020-12-27 22:04:57.466 TM1.Lock.Exception Further explaining contention encountered by thread 13652 when attempting to acquire lock (0x00000099730FB010) on object [Semaphore "P1007", addr=0x000000995D620068, index=N-0]
Cause
They used CubeSaveData to save cube data to disk and this release the Semaphore, then other process acquire lock, then main process failed lock after CubeSaveData so rolled back occur.
Resolving The Problem
Do not use CubeSaveData on each process which are serialized as well as SaveDataAll.
Document Location
Worldwide
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD29G","label":"IBM Planning Analytics"},"ARM Category":[{"code":"a8m0z000000GoURAA0","label":"Troubleshooting->Lock Contention"}],"ARM Case Number":"TS004684574","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
25 January 2021
UID
ibm16407812