<\/HEAD>
Sometimes when reconciling and posting an Enterprise Geodatabase, the following error may occur:<\/P>
"Lock request conflict with an established lock (SDE.DEFAULT)(STATE_ID=xyz)"<\/P>
<\/P>
ArcGIS applies and releases locks on datasets in a geodatabase as people edit and query data. These locks are necessary to maintain data and version consistency but affect access to locked objects.<\/SPAN><\/P><\/P>The problem is due to a user locking the process on the states tables. This lock can be caused by:<\/P>1-A user is performing a bulk process on the versioned data.<\/P>2- A user is in the process of reconciliation or posting and the process is taking a long time.<\/P><\/P>Solution:<\/P>1-The user causing the lock on the tables can be found using the stored procedure "sp_who" in SQLServer:<\/P><\/P> USE master; <\/SPAN><\/SPAN>
GO <\/SPAN>
EXEC sp_who; <\/SPAN>
GO<\/SPAN><\/P>
As we observe, sp_who returns the following information after querying several system tables (syslocks, sysprocesses, etc.):<\/P>
- SPID<\/STRONG><\/SPAN> <\/SPAN>The system process ID.<\/LI>STATUS <\/SPAN><\/STRONG><\/SPAN>The status of the process (RUNNABLE, SLEEPING, SUSPENDED, etc.).<\/LI>LOGIN <\/SPAN><\/STRONG><\/SPAN>User's login name.<\/LI>HOSTNAME<\/STRONG><\/SPAN> <\/SPAN>User's machine name.<\/LI>BLK<\/STRONG><\/SPAN> If the process is blocked, this value is the SPID of the blocking process.<\/SPAN><\/LI>DBNAME<\/STRONG><\/SPAN> <\/SPAN>Name of the database being used by the process.<\/LI>CMD<\/STRONG><\/SPAN> <\/SPAN>The command currently being executed (for example, SELECT, INSERT)<\/LI><\/UL>Source: <A class="link-titled" href="https:\/\/sicuel.es\/2018\/12\/17\/sp_who\/\
