Skip to main content

Editor's Picks

Remove Geodatabase Locks Preventing Schema Editing of Feature Class or Table

Published Date

This tutorial is for Enterprise Geodatabase Administrators tasked with ensuring schema locks are released from GIS datasets whose schemas need to be edited from time to time.

The syntax used in the video is below.  Examples are for SQL Server and Oracle.

SQL Server
SELECT A.SERVER_ID, B.OWNER + '.' + B.TABLE_NAME "TABLE", A.NODENAME, L.LOCK_TYPE FROM SDE.SDE_PROCESS_INFORMATION A, SDE.SDE_TABLE_REGISTRY B, SDE.SDE_TABLE_LOCKS L
WHERE A.SDE_ID = L.SDE_ID AND L.REGISTRATION_ID = B.REGISTRATION_ID AND B.TABLE_NAME = 'LAKES'
ORDER BY NODENAME, SERVER_ID;
 
Oracle
SELECT A.SERVER_ID, B.OWNER||'.'||B.TABLE_NAME "TABLE", A.NODENAME,
L.LOCK_TYPE FROM SDE.PROCESS_INFORMATION A, SDE.TABLE_REGISTRY B, SDE.TABLE_LOCKS L
WHERE A.SDE_ID = L.SDE_ID AND L.REGISTRATION_ID = B.REGISTRATION_ID AND B.TABLE_NAME = 'LAKES'
ORDER BY NODENAME, SERVER_ID;

To learn more, contact us: https://esri.ca/contact.