All clarity projects are locked in the application.
One reason this can happen is if the Autoschedule Project job was run against the projects without the parameter PUBLISH AFTER SCHEDULING being checked. If this option isn't checked all projects will remain locked.
To verify this is the cause:
Note: The above is depended on whether job history retained from the date the projects were locked
Release : All supported Releases
Component : CA PPM SAAS PROJECT MANAGEMENT
1. Rerun the Autoschedule Project job against impacted projects with 'Publish After Scheduling' checked.
(IMPORTANT: this can impact task data as it will publish changes done by the tentative schedule created for the project(s))
2. If projects still remain locked, you can clear them from the Security Locks page in Clarity
IMPORTANT: Before unlocking, make sure that the projects are not intentionally checked out by a user (it can be locked if the user is working on the project in MSP, OWB, or created there own tentative schedule via the Gantt)
3. If you get an error trying to access the security.locks page (and have Administrative access) this could be due to a high # of projects being locked. In order to fix this, please contact Broadcom support.
To check for project locks from the DB side:
Select * from prlock where prtablename = 'SRM_PROJECTS'