topic Re: sde locks in ArcGIS Enterprise Questions

sde locks

Anonymous User — Wed, 01 Apr 2020 13:49:20 GMT

SDE Feature classes continue to get schema locks put on them even when no one is in them or have ever even opened them. It's driving me a bit nuts. Has anyone else seen this?

SDE 10.6.1 SQL 2012.

Re: sde locks

George_Thompson — Wed, 01 Apr 2020 13:59:04 GMT

Are they part of a feature dataset or related table?

Schema locking—ArcGIS Help | Documentation

Are you attempting to update the schema?

Are there any active map services using that feature class?

You are going to need to provide some more information to get more responses .

Geodatabase‌

Re: sde locks

VinceAngelo — Wed, 01 Apr 2020 14:10:53 GMT

Locks, by their very nature, tell you who has obtained them (host and connection user). This will tell you why they exist. The biggest offenders are feature dataset use (lock one, lock them all) and ArcGIS Server map services, but simply having ArcCatalog and ArcMap open at the same time can suffice (which is why I only use the Catalog window of ArcMap, not ArcCatalog).

- V

Re: sde locks

Anonymous User — Wed, 01 Apr 2020 14:51:26 GMT

Hey Vince,

The locks are pretty much all over the place. I understand that Catalog or a service or just an ArcMap session can lock something.

The offending server is where Enterprise is installed. The lock owner is Enterpriseservername.10.6.1.9270

We are enterprise 10.6.1 so the first part makes sense. 9270 makes no sense to me though. I plan on booting the server tomorrow morning for Win updates and that may give me a way to target in on it.

Note that this is also happening on a new feature class that I just created for testing. NO one is in it. Some refresh process I suspect.

Doug Pare

GIS Programmer/Analyst

Summit County Government

970-668-4221

Re: sde locks

George_Thompson — Wed, 01 Apr 2020 15:22:54 GMT

The ".9270" part is the build number of the client that was used to upgrade / create the enterprise geodatabase.

Are the locks preventing you from doing any work or more just curious (or annoyed) about them?

Re: sde locks

Anonymous User — Wed, 01 Apr 2020 15:40:03 GMT

Thanks about info about build number.

The locks are not keeping us from updating data. There are only three of us and all is versioned.

What is so odd is that the general username for READERS with select privileges only will lock a feature class and I’m not able to modify schema such as add a field/column.

Not a big deal really, but –

Why is a reader locking the SDE feature class?

The locks are being put on at 1:02 am 1:03 am 1:05 am and then stops for a few hours. Then 5am. I can guarantee that no one is in this test feature class. Other feature classes get the same.

Thanks

Doug

Re: sde locks

George_Thompson — Wed, 01 Apr 2020 16:25:42 GMT

Ok, good to know that information. Any user (viewer, editor, data owner) when connected will place a lock on the tables they are looking at.

Based on your time stamps, my guess is that the locks are from map services that are being "recycled" at those times. Even if no one is looking / using the map service, I believe that there is a lock placed from the ArcGIS Server machine service name (ServerName) because the service is active. There is also an option to disable schema locks on the map service: https://enterprise.arcgis.com/en/server/latest/administer/windows/disabling-schema-locking-on-a-map-service.htm Now there are pros & cons to both ways.

Hope this helps!

Re: sde locks

MichaelVolz — Wed, 01 Apr 2020 16:53:22 GMT

Can you disable schema locks on all types of services or just specific types? I do not see this capability on a geocode service.

Re: sde locks

George_Thompson — Wed, 01 Apr 2020 18:57:20 GMT

I know that it is available for map services. My guess why is related to not having the ability to "change" data via a map service it is more a "reading" function.

I am not sure for other services but would guess it is not available.

Re: sde locks

Anonymous User — Wed, 01 Apr 2020 19:53:52 GMT

Thank you George. That might just be the ticket.

I will look into it later, as things are a bit insane a the moment.

Doug

Re: sde locks

George_Thompson — Wed, 01 Apr 2020 19:55:54 GMT

Understand and good luck!

Re: sde locks

Streltzer_Tracie — Thu, 02 Apr 2020 12:53:47 GMT

On 10.4.1 on 2016 sQL Server, I have the same issue. Recycling causes a lock on the dataset that never clears, so sometimes there will be multiple locks from the sam set of ArcGIS Servers. This seems to be a bigger problem when using a multi-server site.

Re: sde locks

Anonymous User — Thu, 02 Apr 2020 13:17:38 GMT

I’m still puzzling through this but it looks like any service that uses a feature class in a dataset puts a lock on every feature class in the dataset. Doesn’t even need to be in the service. Everything in the dataset gets a lock on it.

- Doug

Re: sde locks

George_Thompson — Thu, 02 Apr 2020 13:19:12 GMT

That is the expected behavior of feature datasets.

Re: sde locks

MichaelVolz — Thu, 02 Apr 2020 13:23:41 GMT

Doug:

Do you have a specific business requirement for having feature classes in feature datasets (topology maybe) as opposed to standalone feature classes?

Re: sde locks

Anonymous User — Thu, 02 Apr 2020 13:39:50 GMT

Thanks. I should have thought of this earlier. It really helps to have some confirmation.

I wonder if there is an easy way to discover just what services are using what feature classes in a dataset? Short of digging through the projects that are publishing services…

(Like many of us I’m working from home now. My only internet option is satellite and the latency makes things pretty tough).

Doug

Re: sde locks

VinceAngelo — Thu, 02 Apr 2020 13:51:23 GMT

Yup, "Lock one, lock them all." This is fundamental property of feature datasets.

Re: sde locks

ahagopian_coj — Thu, 29 Jul 2021 19:46:05 GMT

Hello! I know this post is over a year old but I came across it while searching for the answer to our problem. We have an sde setup that every dataset has a lock on it. I setup a test dataset that absolutely no one is using and has no map services on it. Yet it too has a schema lock on it. What we are finding is that every feature class in sde regardless of map services or not has a lock on it. This means that no one can add fields so I have people exporting the data in sde to shapefiles then working in the shapefiles causing the data in sde to become out of date. Is there a setting or something else I am missing causing every dataset to have a lock on it? We are at 10.6.1.