CRM: Deadlocks at Database Level on PSLOCK and/or PSVERSION Tables (Doc ID 653099.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

Deadlocks at the Database level on PSLOCK and or PSVERSION tables resulting in application server processes to collapse, on multi language installations.

• Users see deadlock errors or prolonged processing due to locks at the db level, when trying to open, update or save components
• SQL Statement causing the deadlock errors on PSLOCK Table seen at the DB level:
  • SELECT VERSION, OBJECTTYPENAME FROM PSLOCK WHERE OBJECTTYPENAME IN ('PDM', 'CRM') FOR UPDATE OF VERSION
• Multiple updates to PSLOCK and PSVERSION tables, along with inserts into PSCONTDEFN table are seen in the trace files.

The deadlocks occur usually on  Multilanguage installations with multiple users logging in and working to open, update or save components such as Case, Lead, Customer etc.
Even if majority of users log in through the base language and there is a sub set of users logging in non base language, the deadlocks occur consistently.

The Deadlock is always issued on the same transaction:
SELECT VERSION, OBJECTTYPENAME FROM PSLOCK WHERE OBJECTTYPENAME IN ('PDM', 'CRM') FOR UPDATE OF VERSION

The Deadlocks are coming out when 5-6 users are connected and the more users are connecting, the more locks are issued on the database.
Peopletools 8.45 allows to manage the cache via peoplecode. That's what is done out of the box by Peoplesoft CRM 8.9 and above to accelerate the display of all the meta-data dependant pages, such as display templates, AAF, BO Search adapter.
Cache management is done using CreateRowSetCache() or RowsetCache function calls.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.