Database Tuning (MOSC)

MOSC Banner

Index locking

edited Apr 27, 2010 4:43PM in Database Tuning (MOSC) 7 commentsAnswered
Hi!

I have many deadlocks in alert-log file. 

Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-000d0016-0008823a 204 35 X 77 436 S
TX-00070015-00126947 77 436 X 204 35 S
session 35: DID 0001-00CC-00000D9B session 436: DID 0001-004D-00002D94
session 436: DID 0001-004D-00002D94 session 35: DID 0001-00CC-00000D9B

Session 436: obj - rowid = 00002C32 - AAACwyABXAABGjHAAA
(dictionary objn - 11314, file - 87, block - 288967, slot - 0)
Session 35: obj - rowid = 00001F16 - AAAB8WAAfAAAAAAAAA
(dictionary objn - 7958, file - 31, block - 0, slot - 0)

Objects 11314 and 7958 are simple indexes. No bitmap, no reference integrity. What does it mean? Why objects in deadlock graphs indexes rather than tables? How I can find source of deadlock?

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