Manage geodatabase locks

Available with Standard or Advanced license.

Locks are applied to geodatabase objects and services to help ensure data integrity. For example, if someone is editing the data in a table, a schema lock is placed on the table so the owner cannot change the table's schema while someone is editing the data. Similarly, when someone is editing a feature layer in a branch version, a lock is placed on the underlying web service to prevent multiple editors from making edits in the same child version simultaneously.

Which locks you can see from an ArcGIS Pro client depends on whether you are a dataset or version owner, or the geodatabase administrator. Dataset and version owners can view locks for the items they own; geodatabase administrators can view all locks, and disconnect users holding locks when necessary.

View locks on your datasets

If you need to see who is holding a lock that is preventing you from altering the schema of a dataset you own, you can view a list of the lock held on the dataset on the Geodatabase Administration dialog box.

1. Start ArcGIS Pro and connect to the geodatabase as the dataset owner.
2. Right-click the dataset in the Catalog pane and click Manage > Locks.

   The dataset is listed in the Object Name field, and connections made to the dataset are listed below that.

3. If you need the lock released, either contact the user or users identified in the list and ask them to close their connection to the dataset, or contact your geodatabase administrator.

View locks on your versions

If you need to see who is holding a lock that is preventing you from managing a version you own, you can view a list of these locks on the Geodatabase Administration dialog box.

1. Start ArcGIS Pro and connect to the geodatabase as the version owner.
2. Right-click the database connection in the Catalog pane and click Administration > Locks.

   The Locks list on the Geodatabase Administration dialog box opens, and you can see the locks for datasets and versions you own.

3. If you need the lock released, either contact the user or users identified in the list and ask them to close their connection to the version, or contact your geodatabase administrator.

Manage geodatabase locks

Geodatabase administrators can see who is holding schema, version, and state locks for all items in the geodatabase using the Locks tab of the Geodatabase Administration dialog box. The geodatabase administrator can also remove the connections that are holding locks to free the resource for use.

Note:

You cannot remove an individual lock; you can only disconnect the user, thereby removing all locks held by that user.

1. Start ArcGIS Pro and connect to the geodatabase as the geodatabase administrator.
2. Right-click the database connection in the Catalog pane and click Administration > Locks.

   The Locks list on the Geodatabase Administration dialog box opens.

3. Use the drop-down menus at the top to filter locks by object type, object name, lock type, or lock owner.
4. Contact the users who hold the locks that need to be released and ask them to finish their transactions and disconnect from the geodatabase. If someone holding a lock is gone for the day and the lock needs to be released immediately, you can disconnect them.

   Caution:

   Use caution when disconnecting users. Esri recommends that you avoid disconnecting active sessions, especially if the connected user is in the process of editing. You should only disconnect users to drop locks if a session was left open, even when not being used (for example, over the weekend), if a session crashed leaving a connection behind that locks an object, or if a deadlock situation occurs.

5. If necessary, right-click the lock and click Disconnect User.

   The geodatabase administrator requires elevated privileges to disconnect users.

   • In PostgreSQL, the sde user must have superuser status in the database cluster.
   • If your geodatabase in SQL Server is in the sde user's schema, the sde user must have elevated privileges to disconnect users. See Privileges for geodatabases in SQL Server for specific privileges.
   • See Privileges for geodatabases in Oracle for specific privileges needed in Oracle.
   • In SAP HANA, the sde user requires additional database permission. See Privileges for geodatabases in SAP HANA for more information.