Text Query Deadlock With GATHER_STATS Job and ORA-07445 [drexumcx()+64] or [drumcmf()+184] in Alert Logfile on 10.2.0.4.0 (Doc ID 797041.1)

Last updated on MAY 13, 2013

Applies to:

Oracle Text - Version: 10.2.0.4 to 10.2.0.4 - Release: 10.2 to 10.2
Information in this document applies to any platform.
***Checked for relevance on 19-Jan-2012***

Symptoms

While running Text query sessions during statistic maintenance windows, using gather_stats_jobr or  gather_[Table|Schema|Database]_stats procedures, a deadlock with one of the Text query sessions occurs and eventually query session core dump with ORA-7445 [drexumcx], visible in alert logfile.

*** 2009-03-20 22:06:12.821
A deadlock among DDL and parse locks is detected.
This deadlock is usually due to user errors in
the design of an application or from issuing a set
of concurrent statements which can cause a deadlock.
This should not be reported to Oracle Support.
The following information may aid in finding
the errors which cause the deadlock:
ORA-04020: deadlock detected while trying to lock object TEXT.XML_IDX
--------------------------------------------------------
  object   waiting  waiting       blocking blocking
  handle   session     lock mode   session     lock mode
--------  -------- -------- ----  -------- -------- ----
0xa87376d8  0xa71a8868 0x98789f54    X  0xa719d5d0 0x9834ace4    S
0xa0caa1f4  0xa719d5d0 0x9834e894    S  0xa71a8868 0x9823e3d0    X
--------------------------------------------------------
---------- DUMP OF WAITING AND BLOCKING LOCKS ----------
--------------------------------------------------------
------------- WAITING LOCK -------------
----------------------------------------
SO: 0x98789f54, type: 53, owner: 0xa6f2576c, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=98789f54 handle=a87376d8 request=X
call pin=(nil) session pin=(nil) hpc=0000 hlc=0000
htl=0x98789fa0[0xa3d44088,0xa3e7ffac] htb=0xa3e7ffac ssga=0xa3e7fd20
user=a71a8868 session=a71a8868 count=0 flags=[0000] savepoint=0xc99f1
LIBRARY OBJECT HANDLE: handle=a87376d8 mtx=0xa873778c(0) cdp=0
name=TEXT.ITEM 
hash=6cbb78e269f641642b2dca531feed73a timestamp=01-10-2009 07:05:50
namespace=TABL flags=KGHP/TIM/SML/[02000000]
kkkk-dddd-llll=0000-0749-074d lock=S pin=S latch#=2 hpc=31ae hlc=31ae
lwt=0xa8737734[0x98789f70,0x98789f70] ltm=0xa873773c[0xa873773c,0xa873773c]
pwt=0xa8737718[0xa8737718,0xa8737718] ptm=0xa8737720[0xa8737720,0xa8737720]
ref=0xa8737754[0xa8737754,0xa8737754] lnd=0xa8737760[0xa8947b30,0xa86f4e4c]
  LIBRARY OBJECT: object=a23b8328
  type=TABL flags=EXS/LOC[0005] pflags=[0000] status=VALD load=0
...
------------- BLOCKING LOCK ------------
----------------------------------------
SO: 0x9823e3d0, type: 53, owner: 0xa6f261c4, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=9823e3d0 handle=a0caa1f4 mode=X
call pin=(nil) session pin=(nil) hpc=0000 hlc=0000
htl=0x9823e41c[0xa3e7ffdc,0xa3e7ffdc] htb=0xa3e7ffdc ssga=0xa3e7fd20
user=a71a8868 session=a71a8868 count=1 flags=[0000] savepoint=0xc962e
LIBRARY OBJECT HANDLE: handle=a0caa1f4 mtx=0xa0caa2a8(0) cdp=0
name=TEXT.XML_IDX DR$STATS$OBJ
hash=c59fefefa06ced5e681f46e4cfbe5a40 timestamp=NULL
namespace=CPOB flags=KGHP/TIM/FUL/FUP/SML/[0e000000]
kkkk-dddd-llll=0000-0001-0001 lock=X pin=X latch#=1 hpc=21f8 hlc=21f6
lwt=0xa0caa250[0x9834e8b0,0x9834e8b0] ltm=0xa0caa258[0xa0caa258,0xa0caa258]
pwt=0xa0caa234[0xa0caa234,0xa0caa234] ptm=0xa0caa23c[0xa0caa23c,0xa0caa23c]
ref=0xa0caa270[0xa0caa270,0xa0caa270] lnd=0xa0caa27c[0xa0caa27c,0xa0caa27c]
  LIBRARY OBJECT: object=8f873988
  type=CPOB flags=EXS/LOC/PRG[0085] pflags=[0000] status=VALD load=0
  DATA BLOCKS:
  data#     heap  pointer    status pins change whr
  ----- -------- -------- --------- ---- ------ ---
      0 a0bff808 8f873a20 I/P/A/-/-    0 NONE   00 
--------------------------------------------------------
This lock request was aborted.
A deadlock among DDL and parse locks is detected.
This deadlock is usually due to user errors in
the design of an application or from issuing a set
of concurrent statements which can cause a deadlock.
This should not be reported to Oracle Support.
The following information may aid in finding
the errors which cause the deadlock:
ORA-04020: deadlock detected while trying to lock object TEXT.XML_IDX
--------------------------------------------------------
  object   waiting  waiting       blocking blocking
  handle   session     lock mode   session     lock mode
--------  -------- -------- ----  -------- -------- ----
0xa87376d8  0xa71a8868 0x98518bac    X  0xa719d5d0 0x9834ace4    S
0xa0caa1f4  0xa719d5d0 0x983583a0    S  0xa71a8868 0x9823e3d0    X
--------------------------------------------------------
*** 2009-03-20 22:06:25.021
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [drexumcx()+64] [SIGSEGV] [Address 
not mapped to object] [0x4] [] []
Current SQL statement for this session:
  declare 
     cost sys.ODCICost := sys.ODCICost(NULL, NULL, NULL, NULL); 
     arg0 CLOB := null;
 
    begin 
      :1 := "CTXSYS"."TEXTOPTSTATS".ODCIStatsIndexCost(
                     sys.ODCIINDEXINFO('TEXT','XML_IDX', ...
...

or

----- PL/SQL Call Stack -----
  object                 line    object
  handle         number    name
0xa059345c           106    CTXSYS.TEXTOPTSTATS
0xa8900cd8              6     anonymous block
----- Call Stack Trace -----
... <- drexumcx <- drexoicost <- spefcpfa < ...

or

... <- drexumcx <- drexofcost <- spefcpfa < ...

or

... <- drumcmf <- drurnew <- draccbi <- drexumcx <- drexostatscoll <- spefcpfa < ...



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