ORA-600 [KKPO_RCINFO_DEFSTG:OBJNOTFOUND] On 11.2 Databases After Upgrade (Doc ID 1308400.1)

Last updated on NOVEMBER 28, 2016

Applies to:

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

Symptoms

This article is specifically written for V11202 databases that are encountering
on basic operations :-

ORA-00600: internal error code, arguments: [kkpo_rcinfo_defstg:objnotfound],[xxxxx], []

The error will be reported at the user session level and within the alert log.

The argument [xxxxx] will represent an object_id that can be queried from dba_objects.

The article however might still be applicable for 11201 databases and we will report the
known circumstances.

The following symptoms can be attributed :-

a) ORA-00600: internal error code, arguments: [kkpo_rcinfo_defstg:objnotfound],[xxxxx], []
will be seen at session level and within alert log

b) The ORA-00600 will be seen on various basic DML/DDL operations e.g.

select /*+ all_rows */ count(1) from "A"."B" where sourceid=49;

select * from DBSNMP.AQ_MNTR_MSGS_QUEUE where rownum <=1;

c) The sessions seeing the error can vary e.g. SQLPLUS, Grid Control

d) Running hcheck.sql on the database it will show messages like :-

Problem: Orphaned IND$ (no SEG$)
ORPHAN IND$: OBJ=701427 DOBJ=701427 TS=13 RFILE/BLOCK=0 0 BO#=701321 SegType=

100's of objects are likely to be reported, the OBJ/DOBJ values will correlate to
the arguments reported in the ORA-00600 error

e) select count(*) from deferred_stg$;

This SQL will likely return zero rows

f) select to_char(action_time,'DD-MON-YYYY HH24:MI'),action, version, id, comments
from registry$history;

This will report an entry similar to :-

29-MAR-2011 09:16 UPGRADE 11.2.0.2.0
Upgraded from 11.2.0.2.0

Informing that CATUPGRD.SQL has been run

All of these symptoms would be expected to be present for the article to be applicable. If the error is seen without all symptoms being observed this article can still be considered and a SR raised to Support if assistance is needed.

Changes

The error is primarily associated with various SQL operations failing at session level after the incorrect running of CATUPGRD.SQL and is related to missing deferred segment references in the data dictionary.

The error can also be associated with upgrading an earlier <11.2 database to 11.2.0.1 and then subsequently to 11.2.0.2 but again the likely root cause is still linked to how CATUPGRD.SQL has been run.

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