SMON Fails With ORA-600 [kdiulk:kcbz_objdchk] (Doc ID 1339492.1)

Last updated on FEBRUARY 07, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.1 [Release 11.2]
Information in this document applies to any platform.
***Checked for relevance on 22-Feb-2013***

Symptoms

After a session was killed SMON fails with:


ORA-600 [kdiulk:kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], [] when trying to recover transaction 3, 7.



The trace file reports a mismatch in the data_object_id:


OBJD MISMATCH typ=6, seg.obj=-2, diskobj=4034895, dsflg=0, dsobj=3995327, tid=3995327, cls=1.



The undo block written to the trace file shows undo for an index block with data_object_id 3995327. However the same block is also dumped from the buffer cache, with a more recent scn, as a data object with data_object_id 4034895.

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