My Oracle Support Banner

ORA-00600 [17287] After Restore / Recovery (Doc ID 2606522.1)

Last updated on DECEMBER 18, 2020

Applies to:

Oracle Database - Standard Edition - Version 12.2.0.1 and later
Oracle Cloud Infrastructure - Database Service - Version N/A to N/A [Release 1.0]
Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Linux x86-64

Symptoms


Database won't startup after restore / recovery.

Startup was failing with following errors.

ORA-00603: ORACLE server session terminated by fatal error
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [17287], [0x7FA0AADC2B60], [], [], [], [], [], [], [], [], [], []

On OCI DB Current SQL reported in traces is :

begin gsmadmin_internal.dbms_gsm_cloudadmin.syncParameters; end;

Note : This document applies to on-premise as well, different SQL can be reported in trace file.

Call stack was identified as below:

 kgiinb <- pfri7_inst_body_common <- pfri3_inst_body <- pfrrun <- plsql_run <- peicnt
  <- kkxexe <- opiexe <- kpoal8 <- opiodr <- kpoodrc <- rpiswu2 <- kpoodr <- upirtrc <- kpurcsc
   <- kpuexec <- OCIStmtExecute <- gwm_refresh_params <- gwm_init <- gwm_notifier
    <- gwm_pdb_notifier <- kscdnfy <- kpdbaSwitchOpenClose <- kpdbSwitchRunAsSysCbk
     <- rpiswu2 <- kpdbSwitch <- kpdbaOpenPdb <- kpdbaOpenClose <- kpdbaSwitchStateFromRoot
      <- kpdbRestorePdbStates <- kpdbCDBOpen <- adbdrv_options <- opiexe <- opiosq0 <- kpooprx
       <- kpoal8 <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr

Changes

 Customer restored the database instance from its own backup.

Cause

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
Symptoms
Changes
Cause
Solution
References


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