Global Enqueue Services Deadlock Detected

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Global Enqueue Services Deadlock Detected

nauman
Dear Erman,

I am getting a flood of messages (Global Enqueue Services Deadlock Detected) in my database alert file. Please guide me how to resolve the issue.

Regards
Reply | Threaded
Open this post in threaded view
|

Re: Global Enqueue Services Deadlock Detected

nauman
DB EM is not configured and i need to find out the exact queries which is creating the problem.

Thanks & regards
Reply | Threaded
Open this post in threaded view
|

Re: Global Enqueue Services Deadlock Detected

ErmanArslansOracleBlog
Administrator
Please follow this note in the first place ->

Troubleshooting "Global Enqueue Services Deadlock detected" (Doc ID 1443482.1)
Reply | Threaded
Open this post in threaded view
|

Re: Global Enqueue Services Deadlock Detected

nauman
Hi Erman,

I have gone through the document referred by you and other document as well. I suppose global enqueue deadlock issue to be resolved by the Developer in application code and logic. Your comments are requested.

Thanks & regards
Reply | Threaded
Open this post in threaded view
|

Re: Global Enqueue Services Deadlock Detected

ErmanArslansOracleBlog
Administrator
Most of the time, yes.. It is an application issue. However; you need to follow the document and see what type of a deadlock you are facing..

For instance, in TX deadlock in Share(S) mode , the solution "may be" a different one->

in TX deadlock in Share(S) mode :

ITL contention, eg: INITRANS setting for the object is too small, it can not handle the number of concurrent transactions.

The solution is to increase INITRANS setting for the object involved in the deadlock using "alter table" or "alter index" command