ORA-00600 [kkbogdp1] Running Preupgrade_fixups.sql

(Doc ID 2290473.1)

Last updated on SEPTEMBER 01, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

 When running the preupgrade_fixups.sql script, before Upgrading From 12.1.0.2 To 12.2.0.1, it gives an ORA-00600: internal error code, arguments: [kkbogdp1] error.

For example:

SQL*Plus: Release 12.1.0.2.0 Production on Mon Jul 17 12:50:32 2017

Copyright (c) 1982, 2014, Oracle. All rights reserved.

Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics
and Real Application Testing options

12:50:32 sys@1234.example.qa.schedu1> set echo on;
12:50:36 sys@1234.example.qa.schedu1> @/export/home/oracle/preupgrade/preupgrade_fixups.sql
12:50:38 sys@1234.example.qa.schedu1> REM
12:50:38 sys@1234.example.qa.schedu1> REM Oracle PRE-Upgrade Fixup Script
12:50:38 sys@1234.example.qa.schedu1> REM
12:50:38 sys@1234.example.qa.schedu1> REM Auto-Generated by: Oracle Preupgrade Script
12:50:38 sys@1234.example.qa.schedu1> REM Version: 12.2.0.1.0 Build: 1
12:50:38 sys@1234.example.qa.schedu1> REM Generated on: 2017-07-17 12:50:15
12:50:38 sys@1234.example.qa.schedu1> REM
12:50:38 sys@1234.example.qa.schedu1> REM Source Database: SCHEDU1
12:50:38 sys@1234.example.qa.schedu1> REM Source Database Version: 12.1.0.2.0
12:50:38 sys@1234.example.qa.schedu1> REM For Upgrade to Version: 12.2.0.1.0
12:50:38 sys@1234.example.qa.schedu1> REM
12:50:38 sys@1234.example.qa.schedu1>
12:50:38 sys@1234.example.qa.schedu1> REM
12:50:38 sys@1234.example.qa.schedu1> REM Setup Environment
12:50:38 sys@1234.example.qa.schedu1> REM
12:50:38 sys@1234.example.qa.schedu1> SET ECHO OFF SERVEROUTPUT ON FORMAT WRAPPED TAB OFF LINESIZE 200;
Executing Oracle PRE-Upgrade Fixup Script

Auto-Generated by: Oracle Preupgrade Script
Version: 12.2.0.1.0 Build: 1
Generated on: 2017-07-17 12:50:15

For Source Database: SCHEDU1
Source Database Version: 12.1.0.2.0
For Upgrade to Version: 12.2.0.1.0

Fixup
Check Name Status Further DBA Action
---------- ------ ------------------
DECLARE
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [kkbogdp1], [], [], [], [], [], [], [], [], [], [], []

Changes

The argument kkbogdp1 indicates that there are invalid synonym dependencies or mismatched objects.

Actions that should be taken include:

Find Dependencies by running a Health Check:

hcheck.sql - Script to Check for Known Problems in Oracle 12c (Doc ID 136697.1)
How to Perform a Health Check on the Database (Doc ID 122669.1)
Script to Install the "hOut" Helper Package ("hout.sql") (Doc ID 101468.1)

   Output Example:

   HCKW-0016: Dependency$ p_timestamp mismatch for VALID objects (Doc ID 1361045.1)
   [W] - P_OBJ#=38006 D_OBJ#=38605
   [W] - P_OBJ#=38007 D_OBJ#=38606
   [W] - P_OBJ#=38008 D_OBJ#=38607... continued.

Complete the Queries and Actions here if dependencies are found:

HCKW-0016: Dependency$ p_timestamp mismatch for VALID objects (Doc ID 1361045.1)
Dependency$ P_timestamp Mismatch For VALID Public Synonyms Owned By MDSYS (Doc ID 1541636.1)
Health Check Reports Problem: Dependency$ p_timestamp mismatch for VALID objects (Doc ID 781959.1)

However, the ORA-00600 and same [kkbogdp1] argument persists even after resolving all of the problems reported in the hcheck.

You'll notice that rerunning the pre-upgrade script does not cause the dependency issue to return.

So then, what is the cause of the ORA-00600 [kkbogdp1]?

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