Database Administration (MOSC)

MOSC Banner

Resolve Deadlock

edited Oct 20, 2009 3:45AM in Database Administration (MOSC) 5 commentsAnswered
I found the following deadlock entry in one of the trace file.

==============================================

DEADLOCK DETECTED ( ORA-00060 )
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
                       ---------Blocker(s)--------  ---------Waiter(s)---------
Resource Name          process session holds waits  process session holds waits
TX-00230001-00051171       119      10     X            131     320           X
TX-00220027-000574aa       131     320     X            119      10           X
session 10: DID 0001-0077-000002EB session 320: DID 0001-0083-00000256
session 320: DID 0001-0083-00000256 session 10: DID 0001-0077-000002EB
Rows waited on:

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