Database open Error ORA-01555 problem

The managed test library is out of order and cannot open, so let's take a look at the problem first:

Recovery of Online Redo log:thread 1 Group 4 Seq 4 Reading mem 0 mem# 0:/onlinelog/shr/redo04.log Completed Redo Application of 0.00MB Completed crash recovery at Thread 1:logseq 4, block 3, SCN 7755957 0 data blocks read, 0 d ATA blocks written, 0 redo k-bytes Read thread 1 advanced to log sequence 5 (thread open) Thread 1 opened at log Seque NCE 5 log# 5 seq# 5 mem# 0:/onlinelog/shr/redo05.log Successful open of Redo Thread 1 MTTR advisory is di Sabled because Fast_start_mttr_target is not set Thu June 13:31:35 2014 smon:enabling Cache recovery ORA-01555 CA Used by SQL statement below (SQL Id:4krwuz0ctqxdt, scn:0x0000.007658ba): Select CTime, Mtime, stime from obj$ where OB J # =: 1 Errors in file/oracle/diag/rdbms/shr/shr/trace/shr_ora_5262.trc:ora-00704:bootstrap process failure ORA-0 0704:bootstrap process Failure ora-00604:error occurred at recursive SQL level 1 ora-01555:snapshot too CK Segment Number 6 with Name "_syssmu6_1263032392$" too small Errors in File/oracle/diag/rdbms/shr/shr/trace/shr_ora_5262.trc:ora-00704:bo Otstrap process Failure Ora-00704:bootstrap process Failure ora-00604:error occurred at recursive SQL level 1 ora- 01555:snapshot too old:rollback segment number 6 with name "_syssmu6_1263032392$" too small Error 704 happened DB Open, shutting down database USER (ospid:5262): Terminating the instance due to error 704 instance terminated by U SER, PID = 5262 ORA-1092 signalled during:alter DATABASE OPEN ... opiodr aborting process unknown ospid (5262) as a re Sult of ORA-1092 Thu June 13:31:37 2014 Ora-1092:opitsk aborting process

From the above error, the database open failed because Oracle encountered a ora-01555 error executing recursive SQL during the bootstrap phase.
This bootstrap process cannot continue and causes the database to not open. We can see the following SQL statement for the error:
Select CTime, Mtime, stime from obj$ where obj# =: 1

This is a familiar SQL that you will find in the process of tracking Oracle open via 10046 Trace.

For this error, perhaps some people think that the problem is to roll back, in fact, this is not the case, the implementation of the SCN can be very smooth to the database open.

But here's the problem: the brother's database is Oracle 11.2.0.4 and has not supported the traditional 10015 event approach.

Here we solve the problem by Oradebug:

 sql> conn/as sysdba Connected to a idle instance.  
       
Sql> Startup Mount ORACLE instance started. Total System Global area 4275781632 bytes Fixed size 2260088 bytes Variable Size 98985664  
8 bytes Database buffers 3271557120 bytes Redo buffers 12107776 bytes database mounted. Sql> oradebug poke 0x06001ae70 4 0x859afa ora-00074:no process has been specified sql> oradebug setmy sql>  
PID Statement processed. sql> oradebug dumpvar SGA kcsgscn_ kcslf kcsgscn_ [06001ae70, 06001aea0) = 00000000 00000000 00000000 00000000 00000 00000000 00000000 00000000 00000000 00000000 6001ab50 00000000 sql> oradebug poke 0x06001ae70 4 0x859AFA BEFOR  
       
E: [06001ae70, 06001ae74) = 00000000 After: [06001ae70, 06001ae74] = 00859AFA sql> ALTER DATABASE open;  
       
Database altered. Sql> 

Here is a simple explanation, 4 for length, 0x859afa is 16, I am on the basis of the original v$datafile_header.checkpoint_change#
Add up to 1000000 to get the value.