Hosted Customer Record Lock Self Service Overview

Hosted Customer Record Lock Self Service Overview

GOAL: To provide a wholistic overview of the self-service process for hosted users with the RO and MODIFY SQL accounts to empower boards to quickly clear record locks internally to facilitate more efficient turnaround on tasks. 

Hosted customers typically will typically have Read Only and Modify SQL Accounts that are available to personnel of their internal IT team. 

These individuals would be able to help leverage the Modify Account to clear these locks in an efficient manner. 

IT personnel from hosted boards will have SQL Accounts with usernames that roughly follow the composition below which can be leveraged; 

[Board Name][Product][Environment][RO/MOD]

• RO = Read Only
• MOD = Modify

CMD RECORD LOCK SCRIPT:

select * from CMD_RECORD_LOCKS

delete CMD_RECORD_LOCKS

CMD Record Lock Notes:

Record locks can occur whenever someone is running a process, meaning that they come and go as users run and complete processes.

Note: It is okay to delete record locks if they are old and you are sure they are no longer relevant.

You don’t want to go and delete record locks as this could end another person’s session and cause them to have to restart.

However, if you see a record lock from a while ago, and you are sure it is no longer relevant, then it is fine to delete them.  

PROCESS OVERVIEW:

select * from CMD_RECORD_LOCKS

**See the below current record locks using SELECT statement**

Note: When various users are running different processes, each process and its associated locks will have its own Process ID. 

delete CMD_RECORD_LOCKS

IMPORTANT NOTE: If user’s wish to only delete certain Record Locks, so as not to disturb certain process run by others – you can utilize a WHERE clause in the SQL delete statement to choose certain PROCESS_ID values. 

delete CMD_RECORD_LOCKS

where PROCESS_ID = '12345'