Oracle Database Log File version inconsistency problem handling

The oracle Database Log File version is inconsistent. When the test database is started in the morning, the following problems are found: the database version is 11.2.0.3SQL> startupORACLE instance started. total System Global Area 1653518336 bytesFixed Size 2228904 bytesVariable Size 1140854104 bytesDatabase Buffers 503316480 bytesRedo Buffers 7118848 bytesDatabase mounted. ORA-03113: end-of-file on communication channelProcess ID: 8264 www.2cto.com Session ID: 191 Serial number: 3 check the alarm log file information as follows: Fri Aug 24 09:52:27 2012 Completed: alter database MOUNTFri Aug 24 09:52:27 2012 alter database OPENFri Aug 24 09:52:33 2012 Errors in file/u01/app/oracle/diag/rdbms/enmot2/enmot2/trace/enmot2_lgwr_8222.trc: ORA-00322: log 2 of thread 1 is not current copyORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02b. log'ora-00322: log 2 of thread 1 is not current copyORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02a. log 'errors in file/u01/app/oracle/diag/rdbms/enmot2/enmot2/trace/enmot2_lgwr_8222.trc: ORA-00322: log 2 of thread 1 is not current copyORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02b. log'ora-00322: log 2 of thread 1 is not current copyORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02a. log 'errors in file/u01/app/oracle/diag/rdbms/enmot2/enmot2/trace/enmot2_ora_8264.trc: ORA-00322: log 1 of thread is not current copy
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02a. log 'ora-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02b. log 'user (ospid: 8264): terminating the instance due to error 322Fri Aug 24 09:52:34 2012 www.2cto.com System state dump requested by (instance = 1, osid = 8264 ), summary = [abnormal instance termination]. system State dumped to trace file/u01/app/oracle/diag/rdbms/enmot2/enmot2/trace/enmot2_diag_8212.trcDumping diagnostic data in directory = [cdmp_20120824095234], requested by (instance = 1, osid = 8264), summary = [abnormal instance termination]. instance terminated by USER, pid = 8264
The problem is obvious. There is a problem with the log image, because the test database can be opened through resetlog: SQL> alter system set "_ allow_resetlogs_uption" = true scope = spfile; System altered. SQL> startup mountORACLE instance started. total System Global Area 1653518336 bytesFixed Size 2228904 bytesVariable Size 1140854104 bytesDatabase Buffers 503316480 bytesRedo Buffers 7118848 bytesDatabase mounted. SQL> recover database until cancel; Media recovery complete. SQL> alter database open resetlogs; Database altered.
The alarm log information is as follows: Fri Aug 24 09:53:56 2012 alter database open resetlogsORA-1139 signalled during: alter database open resetlogs... fri Aug 24 09:54:27 2012 www.2cto.com alter database recover database until cancel Media Recovery Start started logmerger processParallel Media Recovery started with 4 slavesMedia Recovery Not RequiredCompleted: alter database recover database until cancel alter database open resetlogsRESETLOGS is being done without consistancy checks. this may resultin a specified upted database. the database shoshould be recreated. RESETLOGS after incomplete recovery until change 1427077 Resetting resetlogs activation ID 1296798128 (0x4d4b91b0) Fri Aug 24 09:56:11 2012
Setting recovery target incarnation to 2Fri Aug 24 09:56:12 2012 Assigning activation ID 1297978010 (0x4d5d929a) Thread 1 opened at log sequence 1 Current log #1 seq #1 mem #0: /u01/app/oracle/oradata/enmot2/redo01a. log Current log #1 seq #1 mem #1:/u01/app/oracle/oradata/enmot2/redo01b. logSuccessful open of redo thread 1Fri Aug 24 09:56:15 2012 MTTR advisory is disabled because provided is not setFri Aug 24 09:56:15 2012 SMON: enabling cache recovery [8371] Successfully onlined Undo Tablespace 2. undo initialization finished serial: 0 start: 68627054 end: 68628914 diff: 1860 (18 seconds) Dictionary check beginningFri Aug 24 09:56:26 2012 Dictionary check completeVerifying file header compatibility for 11g tablespace encryption .. verifying 11g file header compatibility for tablespace encryption completedFri Aug 24 09:56:26 2012 www.2cto.com SMON: enabling tx recovery
Database Characterset is ZHS16GBKNo Resource Manager plan already turned off (no async multimaster replication found) Starting background process QMNCFri Aug 24 09:56:36 2012 QMNC started with pid = 20, OS id = 8383 LOGSTDBY: validating controlfile with logical metadataFri Aug 24 09:56:37 2012 LOGSTDBY: Validation completeFri Aug 24 09:56:47 2012 Completed: alter database open Resetlogs and above are the entire processing process.