OWB: We have one project that opens fine in read-only mode, but when opened in read-write mode it does not open and you only see Project1, why?

Document ID : KB000055233
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

OWB: We have one project that opens fine in read-only mode, but when opened in read-write mode it does not open and you only see Project1, why?

Solution:

The project is listed in the PRLock table and the pruserid is set to '-99'.

SELECT * FROM PRLOCK WHERE PRTABLENAME = 'SRM_PROJECTS' AND PRUSERID = -99 ;  


Run the following update query to set the lock record to a valid user id value.

UPDATE PRLOCK SET PRUSERID = 1 WHERE PRTABLENAME = 'SRM_PROJECTS' AND PRRECORDID = ???????  ;  

Note: pruserid '1' is for admin, but can be replaced with the project manager's record ID from the CMN_SEC_USERS table.

Replace the question mark with the project's internal record ID from SRM_PROJECTS or from INV_INVESTMENTS table.

After the update query is executed, go to the project within the application and you should see the 'admin' user (or the project manager) has the lock . You can now drop the lock.

When the lock record has the -99 value in the lock table, the project is not listed as locked in the web interface, or in the list of projects in the Open dialog in OWB.

The error in the app-ca.log will look similar to this:

WARN 2015-02-17 13:11:50,176 [ApplicationServerThread] niku.xql2 (admin:76287893__17aa961:schedulers.getProject) Lock prImportExport held by user 0 requested by user 5071230