Identity Manager: Purging lock12_5 Table to Resolve Locking Contention
search cancel

Identity Manager: Purging lock12_5 Table to Resolve Locking Contention

book

Article ID: 10771

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Identity Suite

Issue/Introduction

The lock12_5 table is a critical component of the Task Persistence architecture within the Identity Manager object store. It tracks events currently in progress. While system cleanup processes remove many entries, common operational scenarios often result in leftover records. Over time, this causes the table to grow significantly, leading to database session locking, transaction contention, and performance degradation.

Environment

Identity Manager

Cause

Task Persistence tables, including lock12_5, do not automatically purge all entries after events are updated. Accumulation of these records over time causes database performance bottlenecks.

Resolution

Warning: The lock12_5 table must be purged only while the Identity Manager environment is completely stopped. Attempting to truncate or clear this table while the environment is active will result in data corruption and the loss of active transaction locks.

 

To clean up the lock12_5 table:

1. Stop the Identity Manager application on all nodes (or at least stop all IMEs on all nodes).

2. On the task persistence database, kill any locks or active sessions to the lock12_5 table, if any exist.

3. Drop all rows within the lock12_5 table using the below query:

TRUNCATE TABLE lock12_5 ;

4. Start the Identity Manager application.