Database Can Not Startup With Error "Control file sequence number mismatch!"

(Doc ID 2411155.1)

Last updated on JULY 02, 2018

Applies to:

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

Symptoms

1. Instance startup failed at OPEN phase, but no obvious errors in alert log:

 

Thu May 31 15:23:20 2018
Starting ORACLE instance (normal)
****************** Large Pages Information *****************

......
......

Thu May 31 15:23:37 2018
ARC3 started with pid=41, OS id=15059
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
System state dump requested by (instance=1, osid=15002), summary=[abnormal instance termination].
System State dumped to trace file /oracle/app/oracle/diag/rdbms/xpbd/xpbd1/trace/xpbd1_diag_14925.trc
USER (ospid: 15002): terminating the instance <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 15002 terminate the instance...
Dumping diagnostic data in directory=[cdmp_20180531152337], requested by (instance=1, osid=15002), summary=[abnormal instance termination].
Instance terminated by USER, pid = 15002

 

2. Find the related trace file and find following error in the trace file:

 

Error: kccpb_sanity_check_2
Control file sequence number mismatch! <<<<<<<<< Control file sequence number mismatch!
fhcsq: 25038565 bhcsq: 3481437667 cfn 8
kjzduptcctx: Notifying DIAG for crash event
----- Abridged Call Stack Trace -----
ksedsts()+461<-kjzdssdmp()+267<-kjzduptcctx()+232<-kjzdicrshnfy()+53<-ksuitm()+1332<-kccpb_sanity_check()+341<-kccrec_rbl()+433<-kccext_ugg()+294<-kccrec_read_write()+356<-kccrrc()+456<-krse_arc_source_init()+548<-krse_arc_driver_core()+797<-krse_arc_driver()+338
<-krsq_arch_to_force_switch()+189<-kcttsc()+352<-kcfopd()+1560<-adbdrv()+51834<-opiexe()+18384<-opiosq0()+3870<-kpooprx()+274
----- End of Abridged Call Stack Trace -----

*** 2018-05-31 15:23:37.560
USER (ospid: 15002): terminating the instance  <<<<<<<<<<<<<<<  Instance was terminated by ospid:15002
ksuitm: waiting up to [5] seconds before killing DIAG(14925) 

 

Changes

 

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