CA PPM Tuesday Tip: Understanding Clarity PRLOCK Table

Discussion created by Antonio_Arenas Employee on Mar 31, 2015
Latest reply on Apr 1, 2015 by John_George

Clarity uses a table named PRLOCK


PRLOCK table is used to prevent concurrent editing.  Which means that this feature restrict to have 2 or more users editing the same field on the database at the same time.


All of them are legitimate locks, and should clear when the reason why the lock

was created is cleared.


The most frequent Locks Types are: Import Export Lock , Job Scheduler Lock , Process Engine, Project Insert Lock.


a. Import Export Lock: are created when a project is opened with a

scheduler (OWB or MSP). It should be cleared when the project is saved and closed.


b. Job Scheduler Lock: are created when a job is scheduled, to prevent

concurrent job runs and race conditions, among other possible problematic situations.


c. Process Engine: locks appear when there's a process instance attached to

an object, such as an investment (projects, ideas, etc.)


d. Project Insert Lock: are created when there is a project creation or or convert an idea to project.


Sometimes, deadlocks may occur on the database, and as a result, some locks

are left behind. Usually that is the case when is an environmental disconnect (i.e. database service shutdown, deadlock) during the save operation.


This that is the case you will want to remove this lock, and the steps are the following.


You can see PRLOCK info on a clarity Unlisted page called System locks.


You can use the following example to show Unlisted page.





Then you can choose which lock do you want to clear.


Some processes cannot be removed through the UI using ‘security.locks’.

If the customer has an issue where the lock is not removed from the Unlisted page ; to gather all the details and open a support case for assistance in resolving the lock.