There are 2 scenarios that can cause this to occur.
-When a user explicitly locks an element and selects the Keep lock after the session closes option when locking.
The element remains unlocked after the user logs off or session expires.
-Another scenario can occur that the user did not check the option to Keep lock after the session closes
but inadvertently the lock remains in effect. This can sometimes occur (in error) when the user clicks the browser back button from within the lock element screen, rather than the ok or cancel button within the lock element screen.
https://www.ibm.com/support/knowledgecenter/en/SSQP76_8.10.x/com.ibm.odm.dcenter.bu.econsole/topics/tsk_dc_explore_lock.html
For either scenario, any user lock can be removed by removing the database records in the LOCKTBL table.
Each of the rows in this table represents a user lock for an element.
By removing all rows and committing the change to the DB, removes all locks for all users in the project.
#OperationalDecisionManager(ODM)#Support#SupportMigration