'ODF-0107:Object Definition is locked for updates, please retry' error message.

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

This error message indicates that a Clarity lock has been placed on one of the Studio Objects.
It may or may not be on the object that was currently being updated; it could be a different object.

Resolution

To find out which object has the lock, take a look at the data in the lock table.

For Oracle Database

 SELECT *
 FROM PRLOCK
 WHERE PRTABLENAME = 'ODF_OBJECTS'
 AND PRNAME = 'objectUpdate'
 AND PRLOCKEDSINCE < sysdate - .042

For Microsoft SQL Server Database

 SELECT *       
 FROM PRLOCK 
 WHERE PRTABLENAME = 'ODF_OBJECTS'
 AND PRNAME = 'objectUpdate'
 AND PRLOCKEDSINCE < getdate() - .042

For PostgreSQL Database

select * from prlock
where (prtablename = 'ODF_OBJECTS'
and prname = 'objectUpdate')
and prlockedsince < now()::DATE

If any records are returned, go to the UI and verify that these objects should not be locked.

If the records remain in the PRLOCK table, the next step is to delete the specific PRLOCK records found.  

It should only be used when the record cannot be released through standard application functionality.  

Go to the URL browser address field and modify the URL to reveal the locks page, e.g. https://server/niku/nu#action:security.locks

Select the lock type for Type = 'Object Update' only
and Click button (Clear Locks).

NOTE: Back up the PRLOCK table and test resolution in a non-production environment first.

FOR ON PREMISE IMPLEMENTATIONS ONLY.

For Oracle Database

 DELETE       
 FROM PRLOCK 
 WHERE PRTABLENAME = 'ODF_OBJECTS'
 AND PRNAME = 'objectUpdate'
 AND PRLOCKEDSINCE < sysdate - .042
 ;
 COMMIT
 ;

For Microsoft SQL Server Database

 DELETE       
 FROM PRLOCK 
 WHERE PRTABLENAME = 'ODF_OBJECTS'
 AND PRNAME = 'objectUpdate'
 AND PRLOCKEDSINCE < getdate() - .042
 ;
 COMMIT
 ;

 

Additional Information

Understanding Clarity PRLOCK Table

The PRLOCK table is used to prevent concurrent editing. The feature restricts 2 or more users from editing the same field in the database at one time.

All of them are legitimate locks, and should clear automatically, but the lock can not be released if the user transaction does not complete.

More information can be found at:
https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=744933#bm25d3d2b5-4918-46b2-b815-bfb665fde9b2