False Deadlock Detected While Creating An Index (Doc ID 557658.1)

Last updated on SEPTEMBER 01, 2010

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.4 to 9.2.0.5 - Release: 9.2 to 9.2
Information in this document applies to any platform.

Symptoms

A false deadlock occurs while creating an index.

DEADLOCK DETECTED
No current SQL statement being executed.
----- PL/SQL Call Stack -----
object line object
handle number name
53ea27e8 244 package body CTXSYS.DRIDISP
53ea27e8 412 package body CTXSYS.DRIDISP
53ea27e8 369 package body CTXSYS.DRIDISP
51eecb74 750 package body CTXSYS.DRIDDL
57d6f908 170 CTXSYS.TEXTINDEXMETHODS
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-0005002c-000dc9d7 13 758 X 13 758 S
session 758: DID 0001-000D-0000000A session 758: DID 0001-000D-0000000A
Rows waited on:
Session 758: obj - rowid = 0004F931 - AABPkxAArAAAAAAAAA
(dictionary objn - 325937, file - 43, block - 0, slot - 0)

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms