Lock request conflict with an established lock (SDE.DEFAULT)(STATE_ID=xxxx)

[HiteshJilka]

Hello,

Within a day many times we encountered lock conflict error in our Oracle GDB several times. Those who try to connect to database fails and those who try to SAVE Edit their work gets the same error.

Lock request conflict with an established lock (SDE.DEFAULT)(STATE_ID=xxxx)

For solution , we close the ArcMap application of user whose STATE_ID is shows in error message. Once the user close his application, error resolves but after sometime some other user acquires lock and thus result in same error. Also this error comes for any user as we get STATE_ID of different users in error message.

Sometimes, even after closing ArcMap and its background processes (cache & Connection manager), the error still exist.  

I use to query Oracle DB to find out user who acquired state lock using STATE_LOCKS table. 

I couldn't find any solution from ESRI support,  Is there some kind of bug in ArcSDE 10.3 for this issue?  Also, Is there a way to find why this error occurs and how we can resolve this instead of closing arcmap application everytime.

[HiteshJilka]

No response yet 

This error comes daily and only have workaround to close the blocking session. User complaints for login issue and unable to save edits because of lock error.

ESRI Staff: Would you please give some idea why exclusive locks are held on STATE_ID of DEFAULT version. Any troubleshooting steps or any patch to fix this issue.

[JoshuaBixby]

Sharing with https://community.esri.com/groups/geodatabase?sr=search&searchId=ec559260-2e25-42fb-86e5-480f041e3c2...‌ to expand visibility.