My Oracle Support Banner

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

Last updated on AUGUST 04, 2018

Applies to:

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


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.


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.