联系:手机/微信(+86 17813235971) QQ(107644445)
作者:惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
11.2.0.4版本数据库启动报ORA-00742 ORA-00312错误
Fri Feb 25 15:02:27 2022 ALTER DATABASE MOUNT Successful mount of redo thread 1, with mount id 2001521283 Database mounted in Exclusive Mode Lost write protection disabled Completed: ALTER DATABASE MOUNT Fri Feb 25 15:02:31 2022 ALTER DATABASE OPEN Beginning crash recovery of 1 threads parallel recovery started with 11 processes Started redo scan Aborting crash recovery due to error 742 Errors in file /u01/app/oracle/diag/rdbms/xifenfei/xifenfei/trace/xifenfei_ora_98720.trc: ORA-00742: Log read detects lost write in thread %d sequence %d block %d ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/xifenfei/redo01.log' Errors in file /u01/app/oracle/diag/rdbms/xifenfei/xifenfei/trace/xifenfei_ora_98720.trc: ORA-00742: Log read detects lost write in thread %d sequence %d block %d ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/xifenfei/redo01.log' ORA-742 signalled during: ALTER DATABASE OPEN...
现场人员进行错误恢复尝试
Fri Feb 25 15:17:17 2022 ALTER DATABASE RECOVER CANCEL Fri Feb 25 15:17:17 2022 Errors in file /u01/app/oracle/diag/rdbms/xifenfei/xifenfei/trace/xifenfei_pr00_130027.trc: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: '/u01/app/oracle/oradata/xifenfei/system01.dbf' ORA-1547 signalled during: ALTER DATABASE RECOVER CANCEL ... ALTER DATABASE RECOVER CANCEL ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...
通过一些人工修复异常redo之后,数据库顺利直接open成功
ALTER DATABASE RECOVER database Media Recovery Start started logmerger process Parallel Media Recovery started with 12 slaves Sat Feb 26 09:45:07 2022 Recovery of Online Redo Log: Thread 1 Group 1 Seq 5281 Reading mem 0 Mem# 0: /u01/app/oracle/oradata/xifenfei/redo01.log Sat Feb 26 09:45:08 2022 Media Recovery Complete (xifenfei) Completed: ALTER DATABASE RECOVER database Sat Feb 26 09:45:25 2022 alter database open Beginning crash recovery of 1 threads parallel recovery started with 11 processes Started redo scan Completed redo scan read 4861 KB redo, 0 data blocks need recovery Started redo application at Thread 1: logseq 5281, block 2, scn 262332375 Recovery of Online Redo Log: Thread 1 Group 1 Seq 5281 Reading mem 0 Mem# 0: /u01/app/oracle/oradata/xifenfei/redo01.log Completed redo application of 0.00MB Completed crash recovery at Thread 1: logseq 5281, block 9725, scn 262353916 0 data blocks read, 0 data blocks written, 4861 redo k-bytes read Initializing SCN for created control file Database SCN compatibility initialized to 3 Warning - High Database SCN: Current SCN value is 262353917, threshold SCN value is 0 If you have not previously reported this warning on this database, please notify Oracle Support so that additional diagnosis can be performed. Sat Feb 26 09:45:25 2022 Thread 1 advanced to log sequence 5282 (thread open) Thread 1 opened at log sequence 5282 Current log# 2 seq# 5282 mem# 0: /u01/app/oracle/oradata/xifenfei/redo02.log Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Sat Feb 26 09:45:25 2022 SMON: enabling cache recovery [111600] Successfully onlined Undo Tablespace 2. Undo initialization finished serial:0 start:69076924 end:69077284 diff:360 (3 seconds) Dictionary check beginning Tablespace 'TEMP' #3 found in data dictionary, but not in the controlfile. Adding to controlfile. Dictionary check complete Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed Database Characterset is ZHS16GBK No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Sat Feb 26 09:45:26 2022 QMNC started with pid=20, OS id=116832 LOGSTDBY: Validating controlfile with logical metadata LOGSTDBY: Validation complete Completed: alter database open
数据库正常open,数据0丢失,数据库可以直接使用