topic Re: Error trying to view locks in Geodatabase Questions

Error trying to view locks

MichaelStranovsky — Tue, 19 Dec 2017 18:29:56 GMT

I am receiving this error while clicking on the lock tab in Geodatabase Administration using ArcCatalog 10.5.1. Has anyone else experienced this?

Re: Error trying to view locks

RexRobichaux2 — Thu, 28 Dec 2017 19:42:57 GMT

Hello Michael,

What type DBMS is your geodatabase stored in? Also can you provide the version of geodatabase (Right click gdb admin connection < Properties)? Is this a sde or DBO (if SQL Server) owned geodatabase schema? Lastly- and just to verify- you are connected as the geodatabase administrative user when attempting to view current locks correct?

From my experience, this error can sometimes be indicative of orphaned records in the locks tables within the geodatabase. This typical workflow to diagnose and fix this issue would be to use (for a SQL Server DBMS):

Take a full backup of the database (.bak for example), then disconnect all users using the ArcCatalog interface. Check the following tables and remove any remaining / orphaned entries through SQL from the geodatabase.

SELECT * FROM sde.SDE_table_locks;
SELECT * FROM sde.SDE_layer_locks;
SELECT * FROM sde.SDE_object_locks;
SELECT * FROM sde.SDE_state_locks;
SELECT * FROM sde.sde_process_information;

If you need assistance or would like further clarification I'd recommend contacting Esri Technical Support to assist with this workflow and confirm that this is what is causing the issue. I hope this is helpful!

Re: Error trying to view locks

BillFox — Tue, 02 Jan 2018 18:40:10 GMT

Yes, I had this exact issue a few months ago.

Rex is correct to clean out any orphan locks

Re: Error trying to view locks

RexRobichaux2 — Thu, 04 Jan 2018 21:46:59 GMT

To follow up further- a recent defect was logged for 10.5.1 regarding this behavior surrounding orphaned locks. I encourage anyone experiencing this to reference this defect if you contact Esri Support Services. It appears that this behavior is currently specific to 10.5.1 and is not reproducible at 10.6.

BUG-000110574: Error “Column value is null” is encountered while accessing the locks information in geodatabase administration window.

Re: Error trying to view locks

BillFox — Fri, 09 Feb 2018 00:56:05 GMT

That same error is back after updating ArcMap from 10.5.1 to 10.6

Re: Error trying to view locks

RexRobichaux2 — Wed, 14 Feb 2018 15:10:31 GMT

Hello Bill- Thanks for bringing this behavior to light at 10.6. Thus far the BUG-000110574 hasn't been reproducible at 10.6 so this is interesting. Are you able to open a ticket with Esri Support Services so that evaluate this further at 10.6 and update that defect if necessary? Thanks!

Re: Error trying to view locks

BillFox — Thu, 15 Feb 2018 18:10:44 GMT

Strange, but It's not having the error today

Re: Error trying to view locks

AlinaTaus — Wed, 07 Mar 2018 15:36:17 GMT

I am having the same error at 10.5.1. I am also getting an error message when trying to compress the database ("Failed to compress the database. Operation Failed [dbo.DEFAULT). I had 10.6 installed on another machine so I tried to access the locks or compress and I am getting the same exact error messages. I uninstalled 10.6 and went back to 10.3.1 and I am no longer getting either of those error message. It's been a very frustrating week. I upgraded from 10.3.1 to 10.6 and spent two days trying to figure out why I could no longer edit a versioned database. After calling tech support I was told there's a bug that affects 10.6 on Windows 7 so I downgraded to 10.5.1, went through the trouble of having to save all my .mxds to be compatible with an older version only to find out there's another bug at 10.5.1. I guess I'll be stuck at 10.3.1 until ESRI no longer supports it....

Re: Error trying to view locks

BillFox — Fri, 16 Mar 2018 16:44:43 GMT

Hi Alina,

I have the same NULL error popup in ArcMap today.

And the same compress FAIL errors

And ArcGIS Pro v2.1.2 will show connections but just crashes when clicking the "Show connected users and locks..." button > Locks tab

Unable to get lock list

A database connection exception has occurred

Column value is NULL

RRobichaux-esristaff‌

Re: Error trying to view locks

RexRobichaux2 — Fri, 16 Mar 2018 16:57:05 GMT

Thank you Bill and Alina for following up on this. I can provide you with an update- it appears the "not reproducible in 10.6" has been expunged from the defect and further testing is still ongoing. Therefore this looks to be (currently) an ongoing issue at 10.5.1 and 10.6 (and Pro 2.0+) that will hopefully be addressed soon. I'll ensure to update you when I have more information and/or there are developments with the BUG-000110574 defect. For anyone else experiencing this issue- if you have not already, I would suggest logging a case with Esri Support Services and reference the above defect as well as your system configuration. This will better assist Esri in gauging the number of users being affected by this behavior.

I hope this has been helpful and to have more information soon!

Re: Error trying to view locks

BillFox — Fri, 16 Mar 2018 20:41:01 GMT

I tried compress from 10.3.1 and it fails too.

It grows the SQL Server transaction log until it fills the hard drive - which has now stoped the geodatabase working for users.

SQL Server 2014

Geodatabase v10.4.1

Windows Server 2008 R2

RRobichaux-esristaff‌

Re: Error trying to view locks

RexRobichaux2 — Thu, 22 Mar 2018 12:41:24 GMT

Hi Bill- sorry to hear you are still having issues with this compress / locks. The filling of the transaction log could well be due to existing / orphaned locks still existing. Did you ensure the following tables were completely empty in SQL before attempting the compress?

sde.SDE_object_locks
sde.SDE_layer_locks
sde.SDE_table_locks
sde.SDE_state_locks
sde.SDE_project_information

Additionally, I'd recommend truncating or deleting a large amount of the current transaction log to free up space in SQL. Further- ensure the 'Recovery Model' of the geodatabase is set to 'Simple' before running compress. You can change it back to 'FULL' after the compress if you want, or just leave it set to simple and change it to FULL when you want to take a manual or scheduled full backup of the database.

Please feel free to give the above suggestions a try and hopefully, this gets your GDB back up, running, and accessible / compressed.

Re: Error trying to view locks

BillFox — Mon, 26 Mar 2018 18:50:17 GMT

Rex,

Thanks for the detail.

The compress problem is just like the view locks problem - both are fixed after following each of the steps you listed.

Including a required change from full to simple in order to successfully get it to work without filling up the disk with a run-away transaction log.

Once the orphan records are clear, compress is fast (a couple seconds) again.

If a user happens to crash an ArcMap session or have to kill a non-responsive session a new orphan record will cause the same problems.

With ESRI support we also found that with the update to 10.5 requiring geocoding locators to be removed from inside the geodatabase and placed in a file folder they were not successfully rebuilding from usual nightly windows task scheduler running python script due to ArcGIS Server placing locks on them as a web service.

We think those failed rebuilds were creating the orphan records.

Notes:

Stop ArcGIS Server address locator services
Rebuild address locators
Overwrite address locator services

Re: Error trying to view locks

Arlington_CoGISMC — Thu, 06 Sep 2018 12:00:38 GMT

I am on 10.6.1 and still having this annoying problem... has it ever been resolved?

Re: Error trying to view locks

KevinDunlop — Thu, 13 Sep 2018 18:24:34 GMT

I am also experience this with 10.6.1. If we delete all the records out the tables listed above, then it solves the issue. Would be great to know the cause of the problem so we can try to prevent it.

Re: Error trying to view locks

MichaelVolz — Thu, 13 Sep 2018 18:33:09 GMT

Is this issue occurring with all enterprise db versions or just specific types of enterprise dbs (SQL Server)? My org utilizes Oracle so I am curious if I will encounter this bug.

Re: Error trying to view locks

KevinDunlop — Thu, 13 Sep 2018 18:42:01 GMT

For us, we run SQL Server 2016 Enterprise and SDE 10.6.1. This has never happened in our Oracle or Postgres databases.

Re: Error trying to view locks

ErnestoCarreras4 — Tue, 18 Sep 2018 22:02:27 GMT

Re: Error trying to view locks

BillFox — Tue, 02 Oct 2018 22:44:38 GMT

The status for BUG-000110574 has been updated to Implemented.

Reproducible at ArcMap 10.6.0, 10.6.1 and Pro 2.2.0

Fix implemented in 2.3

Re: Error trying to view locks

SteveHossack — Fri, 26 Oct 2018 17:08:29 GMT

Your query worked great. I was able to determine the orphaned records and fix the problem. Thank you for sharing!