idea Identify Source of Schema Lock in ArcGIS Pro Ideas

Identify Source of Schema Lock

ChrisKahn — Fri, 22 Jan 2021 23:38:39 GMT

Instead of the generic "Schema Lock" message in ArcGIS, how about alerting the user as to which of the possilbe hundreds of MXD, Web, or Mobile services are actually causing the lock, so that everything does not have to be shut down to remove the lock?

Re: Identify Source of Schema Lock

MikePing — Thu, 21 Jun 2012 14:31:49 GMT

In version 10.1 there's a new schema lock manger. You'll be able to see a list of all schema locks and who the users are.

Re: Identify Source of Schema Lock

RayChilcote — Fri, 22 Jun 2012 16:57:25 GMT

Extremely painful if you don't know who has the lock. Shutting down the instance is a workaround (albeit, the best we have to guarantee an update!).

If you have access to the RDBMS (and some people don't, so a tool WOULD be better), here's a sql statement that will show what machine has the lock (useful for direct connect, really not useful for those utilizing an ArcSDE service or virtualized PCs):

select a.lock_type, b.table_name, c.owner, to_char(c.start_time, 'MON-DD-YY HH24:MI:SS') START_TIME, c.nodename
from sde.table_locks a, sde.table_registry b, sde.process_information c
where a.sde_id = c.sde_id
and a.registration_id = b.registration_id;

Re: Identify Source of Schema Lock

SimonNeville — Fri, 13 Jul 2012 01:22:14 GMT

In a single user environment, when its just another instance of ArcGIS that is causing the lock, how about the option to over-ride the lock??

Re: Identify Source of Schema Lock

MarcWeinshenker1 — Mon, 30 Jul 2012 18:58:33 GMT

mping wrote, "In version 10.1 there's a new schema lock manger. You'll be able to see a list of all schema locks and who the users are." While this is true, all (or multiple) ArcGIS Server services will have the same name, and that doesn't help. If I only want to stop the services holding the lock I need more granular identification.

Re: Identify Source of Schema Lock

RonnieRichards — Mon, 12 Nov 2012 16:52:49 GMT

Please also improve this situation in Arcpy. I wish would also report a schema lock but instead it reports it cannot create the output feature class or table. Even with overwriteoutput = true there are times when a single user environment creates schema locks and arcpy does not report the correct error.
Instead we start chasing down overwriteoutput options when it is not the real issue or cause of the error.

Re: Identify Source of Schema Lock

MartinRick — Tue, 22 Jun 2021 08:08:51 GMT

Re: Identify Source of Schema Lock

ZachSchmitt — Fri, 29 Jan 2016 20:23:04 GMT

I have so many services that it is very difficult to pin point what service is creating a lock. A tool that shows what service is causing the lock instead of the user would be extremely beneficial and a huge time saver

Re: Identify Source of Schema Lock

SianDoherty2 — Tue, 26 Sep 2017 21:10:07 GMT

Would be niceto be able to list what exactly has it locked, not just that it's locked.

Re: Identify Source of Schema Lock

JulieBrown — Tue, 26 Sep 2017 21:35:10 GMT

I use the following queries to find the 'culprit':

select registration_id from sde.table_registry where table_name ='<your table in question>'

select b.nodename connect_source, b.start_time from sde.table_registry a, sde.process_information b, sde.table_locks c where a.registration_id = c.registration_id and b.sde_id = c.sde_id and a.registration_id=<registration_id obtained in the previous query>

Re: Identify Source of Schema Lock

CarlosNantes — Thu, 05 Oct 2017 21:15:19 GMT

That worked for me, thank you.

Re: Identify Source of Schema Lock

TimLangner — Wed, 19 Jun 2019 13:33:16 GMT

This idea is showing as new but was created in 2012.

It is a good idea though.

Re: Identify Source of Schema Lock

JoshWhite — Wed, 19 Jun 2019 15:55:46 GMT

The only surefire way of eliminating all locks is to stop all services. I've tried time and time again to figure this issue out and every time I discover its easier to shut everything down, make the appropriate changes and then restart the services.

Re: Identify Source of Schema Lock

RobertBorchert — Thu, 20 Jun 2019 18:28:15 GMT

We actually solved the issue for us. We installed our own Portal. In the process we had to create services on the new database. We agreed as a whole to create Feature services that ONLY make use of ONE feature dataset. We created folders that match the Feature Datasets in which to keep the services.

This way we don't need to track which service is making use of a feature.

Re: Identify Source of Schema Lock

PeterKing — Wed, 26 Jun 2019 19:45:43 GMT

Just a thought for those still struggling with this, we too have hundreds of services running. When publishing services, you can disable schema locking of the service by changing "schemaLockingEnabled" to "false". It is under Parameters > Advanced. In ArcGIS Pro it is under Configuration > Configure Parameters > Advanced. This help keep the services from locking the data and allows schema changes while services are running.