Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps

Tuesday, July 15, 2008

ORA-00600: internal error code, arguments: [kcbz_check_objd_typ_3], [0], [0], [1], [], [], [], []

After the upgrade from 11.5.9 / to we are getting errors in DB alert logs:

ORA-00600: internal error code, arguments: [kcbz_check_objd_typ_3], [0], [0], [1], [], [], [], []

A search through ORA-600 lookup tool turns up this note:

Subject: ORA-600 [kcbz_check_objd_typ_3]
Doc ID: Note:406787.1 Type: REFERENCE
Last Revision Date: 10-JUL-2008 Status: PUBLISHED

Note: For additional ORA-600 related information please read Note 146580.1

This article represents a partially published OERI note.

It has been published because the ORA-600 error has been
reported in at least one confirmed bug.

Therefore, the SUGGESTIONS section of this article may help
in terms of identifying the cause of the error.

This specific ORA-600 error may be considered for full publication
at a later date. If/when fully published, additional information
will be available here on the nature of this error.


If the Known Issues section below does not help in terms of identifying
a solution, please submit the trace files and alert.log to Oracle
Support Services for further analysis.

Known Issues:
Bug# 6405339 See Note 6405339.8
Corruption / OERI[kcbz_check_objd_typ_3] / OERI:5400 from PQ
Fixed:,, 11.2

Bug# 5689412 See Note 5689412.8
ORA-600 [kcbz_check_objd_typ_3] after SCN based recovery

Bug# 4592596 See Note 4592596.8
Corruption (ORA-1410) from multi-table insert with direct load

Bug# 4430244 + See Note 4430244.8
Segment advisor can load blocks of dropped objects into buffer cache (KCB OERI errors)

Metalink Note 466049.1 describes summary of Bugs Containing ORA - 00600[kcbz_check_objd_typ_3]


This article is intended to

1. Help the reader to understand ORA-600 [kcbz_check_objd_typ_3] error and how is this caused.

2. List the most common bugs of the aforesaid error and their fixes.


This is a consolidated article based upon various bugs logged for the error
ORA-600 [kcbz_check_objd_typ_3] and gives the reader an overview about the most frequent bugs which the customers are affected with.

The error ORA-600 [kcbz_check_objd_typ_3] is raised because we see different object id in bufffer cache (BH) and on disk .

Summary of Bugs Containing ORA - 00600[kcbz_check_objd_typ_3]

Bug 5466416---Closed as Duplicate of Unpublished Bug 4430244


Versions affected : 10.2

Fixed releases :,

Details : Segment advisor code (eg: DBMS_SPACE.OBJECT_GROWTH_TREND)

can load blocks into the cache for Dropped objects as CURRENT leading

to subsequent operations seeing an incorrect (old) version of a block.

This can lead to various internal buffer cache related errors such as

ORA-600 [kcbnew_3] / ORA-600 [kcbz_check_objd_typ_3].

The exact error depends on which code sees the block.

Backportable : yes to 10.2

Symptoms :

1. ORA-600 [kcbnew_3] internal error reported in the alert.log

2. May occur if segment advisor and DROP operation are being run
concurrently on the same object.

Workaround :

sql>alter system flush buffer cache' to flush the buffer in the cache.

Patch Details:

Check Metalink for Patch 4430244 availability.

Bug 5859511 -----> Closed as Duplicate of Unpublished Bug 4592596


Fixed releases :,

Corruption can occur using a multi-table insert SQL with
direct load operations. Eg: If the SQL goes parallel.
This can result in subsequent ORA-1410 type errors on selects
from the target table/s.

Symptoms :

1.Select on table fails with ORA-600 [kcbz_check_objd_typ_3] after multi-table insert with direct load was done.

2.Analyze on the table fails with ORA-1410

3.Call Stack :- kcbassertbd3 kcbz_check_objd_typ kcbzib kcbgtcr ktrget kdst_fetch kdstf0010101km
kdsttgr qertbFetch qergiFetch qertqoFetch

Workaround: -
Do not use direct path (APPEND or PQ) in a multi-table insert SQL

Check Metalink for Patch 4592596 availability.

Unpublished Bug 5754708 ----> Closed as Duplicate of Unpublished Bug 4996133


Symptoms : -

1. Running in RAC mode
2. Reading the overflow segment of an IOT
3. Call Stack :- kdsgnp kafger qerixGetNonKeyCol qerixFetchByLogicalRowid
Call Stack :- kcbassertbd3 kcbz_check_objd_typ kcbzib kcbgtcr ktrget kdsgrp kdsfbr qertbFetchByRowID

Flush the buffer cache (10g onwards)
Restart the instance to clear its buffer cache.

Check Metalink for Patch 4996133 availability.

Bug 5348204


Fixed In Ver:

Symptoms :-

1.Cross Platform tablespace Import using Transportable tablespace option fails with following error message

ORA-39083: Object type TABLE failed to create with error
ORA-600: internal error code, arguments: [kcbz_check_objd_type_3]

2.Call Stack :- kcbz_check_objd_typ kcbzib kcbgtcr ktecgsc ktecgetsh ktecgshx ktsscd_segment ktsscf_segment kdicpsc kdicrws

I am still investigating this one. Will update once I get more information.


Anonymous said...

Stop cut/paste job from Metalink ..this technique of blog posting will not take u anywhere

Vikram Das said...

Hi Anonymous,

Most of my posts which are cut paste from metalink are work in progress. Usually I update them with my experiences about the problem. Metalink cut paste is done so that a reader doesn't have to go to metalink to refer to the note. Sometimes it is a pointer that Oracle is already aware of an issue. Some other readers have also raised objection about this. However I feel it is better to have the complete text about an issue in the post itself.

- Vikram

Anonymous said...

Not sure if you read or understand metalink user agreement. It is a violation of Oracle copyright and they can come after you if they want to.