ORA-600:[KDDUMMY_BLKCHK][][][18021] After ALTER TABLE ALLOCATE EXTENT (Doc ID 564788.1)

Last updated on JULY 11, 2012

Applies to:

Oracle Server - Enterprise Edition - Version 10.2.0.1 to 11.1.0.6 [Release 10.2 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on DD-Mon-YYYY***


Symptoms

 

Database report ORA-00600[kddummy_blkchk] with error code 18021
This can affect a user session that failed to allocate an extent. Subsequent, 
PMON can report the same error while trying to recover the block and
SMON can receive the same exception while recover a transaction and crash the instance.

Wed Jan 23 05:59:02 2008
Errors in file /opt/oracle/admin/ORCL/udump/ORCL_ora_1089.trc:
ORA-00600: internal error code, arguments: [kddummy_blkchk], [130], [1105221], [18021], [], [], [], []
ORA-01653: unable to extend table SCOTT.EMP by 64 in tablespace USERS

Wed Jan 23 06:12:22 2008
Errors in file /opt/oracle/admin/ORCL/bdump/adw1d1_pmon_16865.trc:
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kddummy_blkchk], [130], [1105221], [18021], [], [], [], []
Wed Jan 23 06:12:24 2008
Doing block recovery for file 130 block 1105221
Wed Jan 23 06:12:24 2008
Trace dumping is performing id=[cdmp_20080123061224]
Wed Jan 23 06:12:24 2008
Block recovery from logseq 50259, block 344239 to scn 8635114735616
Wed Jan 23 06:12:24 2008
Recovery of Online Redo Log: Thread 1 Group 11 Seq 50259 Reading mem 0
  Mem# 0 errs 0: +DGDATA01/ORCL/onlinelog/group_11.265.628109791
  Mem# 1 errs 0: +DGFLASH01/adw1d/onlinelog/group_11.259.628109799
Block recovery completed at rba 50259.344880.16, scn 2010.2230470658

Wed Jan 23 22:36:24 2008
Errors in file /opt/oracle/admin/ORCL/bdump/ORCL_smon_13180.trc:
ORA-00600: internal error code, arguments: [kddummy_blkchk], [130], [1105221], [18021], [], [], [], []
Wed Jan 23 22:38:50 2008
ORACLE Instance adw1d1 (pid = 14) - Error 607 encountered while recovering transaction (9, 21) on object 14127361.

The database is restarted but it crashes minutes later due to SMON exception.

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