The controlfile header block returned by the OS has a sequence number that is...

刘泽宇

The controlfile header block returned by the OS has a sequence number that is too old. (Doc ID 1589355.1)

登录/注册后可看大图 To Bottom

登录/注册后可看大图

---

                               
登录/注册后可看大图

In this Document Symptoms Cause Solution References APPLIES TO: Oracle Database Cloud Schema Service - Version N/A and later Oracle Database Exadata Cloud Machine - Version N/A and later Oracle Database Exadata Express Cloud Service - Version N/A and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Oracle Database Cloud Exadata Service - Version N/A and later Information in this document applies to any platform. SYMPTOMS Database instance went down with following error message in alert log: --- Wed Sep 11 23:26:39 2013 ********************* ATTENTION: ******************** The controlfile header block returned by the OS has a sequence number that is too old. The controlfile might be corrupted. PLEASE DO NOT ATTEMPT TO START UP THE INSTANCE without following the steps below. RE-STARTING THE INSTANCE CAN CAUSE SERIOUS DAMAGE TO THE DATABASE, if the controlfile is truly corrupted. In order to re-start the instance safely, please do the following: (1) Save all copies of the controlfile for later analysis and contact your OS vendor and Oracle support. (2) Mount the instance and issue: ALTER DATABASE BACKUP CONTROLFILE TO TRACE; (3) Unmount the instance. (4) Use the script in the trace file to RE-CREATE THE CONTROLFILE and open the database. ***************************************************** USER (ospid: 24051722): terminating the instance --- CAUSE BUG 14281768 - CONTROL FILE GETS CORRUPTED Which was closed as Vendor OS/Software/Framework Problem SOLUTION Error is typically raised when the Controlfile is overwritten by an older copy of the Controlfile. Most likely this happened due to Storage OR I/o error. All copies of the control file must have the same internal sequence number for Oracle to start up the database or shut it down in normal or immediate mode. The solution is actually given with the accompained message :- (1) Save all copies of the controlfile for later analysis and contact your OS vendor and Oracle support. (2) Mount the instance and issue: ALTER DATABASE BACKUP CONTROLFILE TO TRACE; (3) Unmount the instance. (4) Use the script in the trace file to RE-CREATE THE CONTROLFILE and open the database. To make a sanity check in the future , please set the following parameter :- SQL> alter system set "_controlfile_update_check"='HIGH' scope=spfile; -- then bounce the database. Please check with your OS System/Storage admin regarding the issue. The precautions is to relocate the control file on a fast and direct I/O enabled disk , the main target is not letting the OS to write an old copy (cached copy of the controlfile to it). To reverse the parameter setting :- SQL> alter system set "_controlfile_update_check"='OFF' scope=spfile; -- then bounce the database.