Encounter PSLOCKS When Running Search/Match/Post (SCC_SL_SMP), Which Impacts Performance (Doc ID 2270396.1)

Last updated on AUGUST 03, 2018

Applies to:

PeopleSoft Enterprise CS Campus Community - Version 9 to 9.2 [Release 9]
Information in this document applies to any platform.

Goal

PSLOCK is occurring when running Search/Match/Post (SCC_SL_SMP) process.

PSLOCK issue appears to be stemming from the 'save' call in app class SCC_SL_TRANSACTION:ACCESSORS:StagedUserPerzCategory, which issues the following SQL:

SQLExec("DELETE FROM PSUSERPRSNLOPTN WHERE OPRID = :1 and OPTN_CATEGORY_LVL=:2 and USEROPTN=:3", &userid, %This.OPTN_CATEGORY_LVL,
%This.USEROPTN);

This is a PeopleTools table, and tools internally serializes its updates via the PSLOCK table using object type names = 'UPM' and 'SYS'. Although PSLOCK is being updated when the rowsetcache objects are being refreshed, this only happens the first time they are used. After that, they
stay in the rowset cache, and this does not trigger updates to PSLOCK.

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

References

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

Encounter PSLOCKS When Running Search/Match/Post (SCC_SL_SMP), Which Impacts Performance (Doc ID 2270396.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!