Deadlocks with block - 0, slot - 0 during INSERT
Date: Thu, 10 Jul 2008 00:39:11 -0700 (PDT)
Message-ID: <cd6eaf79-63b3-4f2b-b9a0-6077843d9741@d77g2000hsb.googlegroups.com>
Hi
We are getting strange deadlocks in 9.2.0.7 database:
1. They occur during INSERT into range-partitioned table where all
indexes are local.
2. Both sessions were trying to execute the same SQL statement.
3. ObjectID point to table partition and index (primary key) partition
corresponding to this table partition. This is strange as I would
expect locking to occur in the same order in both sessions.
4. "Rows Waited On" section of trace file shows block - 0 and slot -
0:
- - - - - - - - - - - - - - - - - - - - - -
Rows waited on:
Session 65: obj - rowid = 00009B64 - AAAJtkABsAAAAAAAAA
(dictionary objn - 39780, file - 108, block - 0, slot - 0)
Session 90: obj - rowid = 00009B65 - AAAJtlAASAAAAAAAAA
(dictionary objn - 39781, file - 18, block - 0, slot - 0)
- - - - - - - - - - - - - - - - - - - - - -
Why are block/slot = 0?
In other databases we get something like that:
- - - - - - - - - - - - - - - - - - - - -
Rows waited on:
Session 513: obj - rowid = 000068C1 - AAAGjBAALAAAABHAA1
(dictionary objn - 26817, file - 11, block - 71, slot - 53)
Session 468: obj - rowid = 000068C1 - AAAGjBAALAAAAA9ABM
(dictionary objn - 26817, file - 11, block - 61, slot - 76)
- - - - - - - - - - - - - - - - - - - - -
Received on Thu Jul 10 2008 - 02:39:11 CDT