No Lock Owner, Old Lock, Unable to Disconnect User

498
3
Jump to solution
12-22-2021 12:36 PM
ShannonPugh
Occasional Contributor

I want to turn on editor tracking but it seems that database schema locks are preventing it:

ShannonPugh_0-1640204390856.png

I can disconnect users, but not these that are blank in the "Lock Owner" field. When I try, I get this message:

ShannonPugh_1-1640204515817.png

The other thing to note about these locks is that the time acquired for the lock is very old.

 

How can I get rid of these locks that show no owner?

 

The database platform is SQL Server and I am trying to disconnect the users with locks from ArcGIS Pro 2.9 Catalog pane.

0 Kudos
1 Solution

Accepted Solutions
AzinSharaf
Occasional Contributor II

we had same issue with orphan lock and the following workaround from Esri Support fixed it. Make sure you have a full backup before applying any change.

First (if possible), we may just need to restart SQL Server and see if the orphan locks disappear. If you want to test restarting server, you will need to right click the Instance in SSMS > Restart. Please keep in mind restarting server may affect users who are connected and editing at the time.

Please capture a full back up in SSMS. It is important to have the backup created before attempting to truncate the 'table_locks' table.

After our first compression, we can verify if the the orphan records are still appearing in the 'SDE_table_locks' table. Additionally, the' SDE_layer_locks', 'SDE_obect_locks', and SDE_state_locks' should be empty.

Next, we can attempt to truncate the 'SDE_table_locks' table. After running the query in SSMS, we can verify if the orphan locks are still appearing within the ArcGIS Administration Dialog.

Please note: verify all services are stopped (if applicable) and that no users are connected or editing before running the query.

  • TRUNCATE TABLE sde.SDE_table_locks;

Afterwards, attempt to compress the geodatabase again and see if our end_state_count is now 1 within the Compress_Log table.

Reference Image:

AzinSharaf_0-1640206348789.png

 




 

View solution in original post

0 Kudos
3 Replies
AzinSharaf
Occasional Contributor II

we had same issue with orphan lock and the following workaround from Esri Support fixed it. Make sure you have a full backup before applying any change.

First (if possible), we may just need to restart SQL Server and see if the orphan locks disappear. If you want to test restarting server, you will need to right click the Instance in SSMS > Restart. Please keep in mind restarting server may affect users who are connected and editing at the time.

Please capture a full back up in SSMS. It is important to have the backup created before attempting to truncate the 'table_locks' table.

After our first compression, we can verify if the the orphan records are still appearing in the 'SDE_table_locks' table. Additionally, the' SDE_layer_locks', 'SDE_obect_locks', and SDE_state_locks' should be empty.

Next, we can attempt to truncate the 'SDE_table_locks' table. After running the query in SSMS, we can verify if the orphan locks are still appearing within the ArcGIS Administration Dialog.

Please note: verify all services are stopped (if applicable) and that no users are connected or editing before running the query.

  • TRUNCATE TABLE sde.SDE_table_locks;

Afterwards, attempt to compress the geodatabase again and see if our end_state_count is now 1 within the Compress_Log table.

Reference Image:

AzinSharaf_0-1640206348789.png

 




 

0 Kudos
ShannonPugh
Occasional Contributor

Thanks, worked beautifully!

ShannonPugh
Occasional Contributor

Thanks, we will give this a try and let you know how it goes.