Unlocking the MUTEX Table

A MUTEX table could result in lock and unlock situations.

When you publish data, the data is set in the table and the status is also set to N. When an application node is running, the MUTEX table fetches data with status as N and acquires a lock. When the status changes from N to S, the MUTEX table releases the lock from the table. If you try to forcefully shutdown the application node, the MUTEX table gets locked and the configurations associated with MUTEX table do not work. To release a lock on a MUTEX table, manual intervention is required.

Note: Only Database Administrators can execute the scripts to unlock the MUTEX table. The administrators must fetch the ID and serial number of the locked session and then terminate the particular session that has acquired the lock. See the examples for Oracle and Microsoft SQL Server databases for details.

Unlocking the MUTEX Table: Example for Oracle Database

To fetch the ID and serial number of the locked session, execute the following query: 
select s.sid, s.serial#, p.spid From v$session s, v$process p
where s.paddr = p.addr AND s.sid in (select SESSION_ID from
v$locked_object);

To terminate the session that has acquired the lock, execute the following query: 

alter system kill session '<id>, <serial number>';

Unlocking the MUTEX Table: Microsoft SQL Server Database

To fetch the ID and serial number of the locked session, execute the following query: 

SELECT OBJECT_NAME(P.object_id)
 
ASTableName,Resource_type,request_session_id
FROM sys.dm_tran_locks L
JOIN sys.partitions P
ON L.resource_associated_entity_id=p.hobt_id
WHERE OBJECT_NAME(P.object_id)
='P1Chronolog_IncidentActivityUpdates'

To terminate the session that has acquired the lock, execute the following query: 

Kill session_ID