nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Online Sevice Schema Lock?

ShaneHolt1

V.10.2.1, I'm attempting to edit feature classes, but cannot due to a schema lock. I have published a map viewed via ArcGIS online for our field crews' use, and believe this is the source of the lock even though I stopped the service and changed the 'schemaLockingEnabled' property to 'false'. When I connect to the default database and select administer geodatabase to view the current locks, the user id is ArcGIS, and the lock is always started at 12:02 AM. I've even attempted to disconnect the user, but to no avail.

Any insight would be appreciated.

Thank you,

Find more posts tagged with

Accepted answers

All comments

ShaneHolt1

Hi Rex, sorry for not clarifying earlier;

I am attempting to add fields to an existing feature class in this particular instance, and anticipate creating a few new feature classes in the near future as well.

RexRobichaux2

Hi Shane, thanks for the additional information and screenshot. One thing I should have asked earlier- when you say you are attempting to edit feature classes- do you mean edit in the normal sense (editor toolbar, adding deleting or modifying features/attributes of features) or are you attempting to make schema changes to the feature classes themselves (add fields, edit fields, delete fields, for example)? So far I still don't see anything that would prohibit feature edits- but what you are encountering would be expected (inability to obtain an exclusive schema lock when there are shared schema locks active) if making schema changes to feature classes. Thanks!

ShaneHolt1

Thanks for the info, I felt the map service shouldn't be causing a lock as well, but really didn't know where else to look. In the past, I've always tried to do my editing when I knew other users were not connected to the db. We've also created a child version of the default db for other users within the company to connect to (rather than a direct connection to the default db),but I believe that creates a schema lock when others are have our data in their mxd as well.

In the 'Lock Owner' info, FPB is an acronym for my company.

Although I have some admin rights, our db is ultimately managed by our IT Dept. I've assisted with db setup/management, but on a very limited basis. We use SQL 2012.

Thanks again, and if there's any other info you need, let me know and I will do my best to get it!

RexRobichaux2

Hello Shane,

A published hosted layer / map service shouldn't create any exclusive locks that would prohibit you from editing the underlying feature class. Therefore there is a chance the restrictive lock is coming from somewhere else. Would you be able to post a screenshot of the geodatabase admin / locks tab using the geodatabase administrative user so we can see all connections / locks?

Also what version and type DBMS is the data stored in? Thanks!

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.