Applies to:
Oracle Server – Enterprise Edition – Version: 10.2.0.4 and later [Release: 10.2 and later ]
Symptoms
o Alter tablespace SYSAUX online fails with following error:
ORA-00600: internal error code, arguments: [kcbgcur_9], [4394910], [3],
[4294967262], [2], [], [], []
o Call stack trace is similar to:
ksedst <- ksedmp <- ksfdmp <- kgerinv <- kgeasnmierr
<- kcbgcur <- kcbchg1_main <- kcbchg <- ktuapundo <- ktbapundo
<- kdiulk <- kcoubk <- ktundo <- kttasu <- kttonl
<- atsdrv <- opiexe <- opiosq0 <- kpooprx <- kpoal8
o Alert log shows problem reading SYSAUX datafile:
o SYSAUX datafile is corrupt; datafile recovery has been successful
but still can not online the SYSAUX tablespace.
SQL> purge dba_recyclebin;
purge dba_recyclebin
*
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 2
ORA-00376: file 3 cannot be read at this time
ORA-01110: data file 3: ‘+FCCDG1/fc74/sysaux01.dbf’
ORA-06512: at line 19
Cause
This is similar to unpublished bug 7644703:
Abstract: LNX-32-10204: ORA-600: [KCBGCUR_9], [4273334], WHEN “ALTER TABLESPACE ONLINE”
Solution
This bug 7644703 is still being worked by development.
A possible workaround is to:
a) drop associated object(s)
b) disable primary key(s) and purge dba_recyclebin
c) bring the tablespace online.
For example:
a) From ORA-00600 [KCBGCUR_9] trace file, find the associated object(s):
BH (700000083f66240) file#: 3 rdba: 0×00c1476b (3/83819) class: 1 ba: 700000083b42000
set: 9 blksize: 8192 bsi: 0 set-flg: 0 pwbcnt: 0
dbwrid: 0 obj: 319335 objn: -1 tsn: 2 afn: 3
In this case, the object id is 319335.
select owner, object_name, subobject_name, object_type
from dba_objects where data_object_id = 319335;
data_object_id = 319335 is WRH$_LATCH_PK for table WRH$_LATCH
Drop the affected indexes (WRH$_LATCH_PK and WRH$_SYSTEM_EVENT_P).
b) alter table sys.WRH$_LATCH disable primary key;
purge dba_recyclebin;
c) alter tablespace sysaux online;
alter table sys.WRH$_LATCH_MISSES_SUMMARY enable primary key
using index local tablespace SYSAUX;
alter table sys.WRH$_LATCH enable primary key
using index local tablespace SYSAUX;
Note: By dropping the associated object the SAVE UNDO block will not be pinned
avoiding the error. The affected indexes were recreated by enabling the primary key(s) again.
References
SR 7275353.993
NOTE:183327.1 – Common Causes and Solutions on ORA-376 Error Found in
Backup & Recovery