Database - RAC/Scalability (MOSC)

MOSC Banner

Global Enqueue Services Deadlock detected

in Database - RAC/Scalability (MOSC) 3 commentsAnswered

Hello,

I was wondering if I could seek some guidance whether there is any action or anything I need to look at and possibly make changes to when this event happens.

Before I received this event in the alert log, we had a blocking session. The blocker was inactive and waiting on sqlnet to/from client, though I also saw a "gc cr block busy" attributed to the session when I ran a sql trace against it in OEM.

The applications people disconnected the application which killed the blocking session, but an hour later I received the GES deadlock.

It created a trace file which I have attached:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center