Oracle Recovery Tools 解决ORA-600 3020故障

尝试recover datafile,部分文件报ORA-600 3020，其他文件recover成功

ALTER DATABASE RECOVER  datafile 1 

Media Recovery Start

Serial Media Recovery started

Recovery of Online Redo Log: Thread 1 Group 3 Seq 24972 Reading mem 0

  Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG

Errors in file d:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_72232.trc  (incident=749532):

ORA-00600: 内部错误代码, 参数: [3020], [1], [272255], [4466559], [], [], [], [], [], [], [], []

ORA-10567: Redo is inconsistent with data block (file# 1, block# 272255, file offset is 2230312960 bytes)

ORA-10564: tablespace SYSTEM

ORA-01110: 数据文件 1: 'D:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01.DBF'

ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 383

Media Recovery failed with error 600

ORA-283 signalled during: ALTER DATABASE RECOVER  datafile 1  ...

Tue Aug 02 10:28:24 2022

Trace dumping is performing id=[cdmp_20220802102824]

Tue Aug 02 10:28:31 2022

ALTER DATABASE RECOVER  datafile 2 

Media Recovery Start

Serial Media Recovery started

Recovery of Online Redo Log: Thread 1 Group 3 Seq 24972 Reading mem 0

  Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG

Errors in file d:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_72232.trc  (incident=749533):

ORA-00600: 内部错误代码, 参数: [3020], [2], [92323], [8480931], [], [], [], [], [], [], [], []

ORA-10567: Redo is inconsistent with data block (file# 2, block# 92323, file offset is 756310016 bytes)

ORA-10564: tablespace SYSAUX

ORA-01110: 数据文件 2: 'D:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSAUX01.DBF'

ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 12330

Media Recovery failed with error 600

ORA-283 signalled during: ALTER DATABASE RECOVER  datafile 2  ...

利用Oracle数据库异常恢复检查脚本(Oracle Database Recovery Check)检查文件头相关信息，发现recover 失败的两个文件异常

---

通过Oracle Recovery Tools工具进行修复

---

数据库recover 成功，并顺利open

 

Tue Aug 02 10:56:13 2022

ALTER DATABASE RECOVER  datafile 1 

Media Recovery Start

Serial Media Recovery started

Recovery of Online Redo Log: Thread 1 Group 3 Seq 24972 Reading mem 0

  Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG

Completed: ALTER DATABASE RECOVER  datafile 1 

ALTER DATABASE RECOVER  datafile 2 

Media Recovery Start

Serial Media Recovery started

Recovery of Online Redo Log: Thread 1 Group 3 Seq 24972 Reading mem 0

  Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG

Completed: ALTER DATABASE RECOVER  datafile 2 

Tue Aug 02 10:56:34 2022

alter database open

Beginning crash recovery of 1 threads

 parallel recovery started with 7 processes

Started redo scan

Completed redo scan

 read 8504 KB redo, 0 data blocks need recovery

Started redo application at

 Thread 1: logseq 24972, block 2, scn 177712270

Recovery of Online Redo Log: Thread 1 Group 3 Seq 24972 Reading mem 0

  Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG

Completed redo application of 0.00MB

Completed crash recovery at

 Thread 1: logseq 24972, block 17011, scn 177734679

 0 data blocks read, 0 data blocks written, 8504 redo k-bytes read

Tue Aug 02 10:56:35 2022

Thread 1 advanced to log sequence 24973 (thread open)

Thread 1 opened at log sequence 24973

  Current log# 1 seq# 24973 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO01.LOG

Successful open of redo thread 1

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Tue Aug 02 10:56:35 2022

SMON: enabling cache recovery

Successfully onlined Undo Tablespace 2.

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

SMON: enabling tx recovery

*********************************************************************

WARNING: The following temporary tablespaces contain no files.

         This condition can occur when a backup controlfile has

         been restored.  It may be necessary to add files to these

         tablespaces.  That can be done using the SQL statement:

  

         ALTER TABLESPACE <tablespace_name> ADD TEMPFILE

  

         Alternatively, if these temporary tablespaces are no longer

         needed, then they can be dropped.

           Empty temporary tablespace: TEMP

**********************************************************

WARNING: Files may exists in db_recovery_file_dest

that are not known to the database. Use the RMAN command

CATALOG RECOVERY AREA to re-catalog any such files.

If files cannot be cataloged, then manually delete them

using OS command.

One of the following events caused this:

1. A backup controlfile was restored.

2. A standby controlfile was restored.

3. The controlfile was re-created.

4. db_recovery_file_dest had previously been enabled and

   then disabled.

**********************************************************

replication_dependency_tracking turned off (no async multimaster replication found)

LOGSTDBY: Validating controlfile with logical metadata

LOGSTDBY: Validation complete

Completed: alter database open

增加tempfile,导出数据该库恢复完成

• ORA-00742 ORA-00312故障恢复
• ORA-600 3600恢复—-resetlogs scn异常
• ORA-00322 ORA-00312恢复
• ORA-00333 ORA-01595 恢复
• 又一例ORA-600 kcratr_nab_less_than_odr
• commit_wait和commit_logging设置不当导致数据库无法正常启动
• ora-600 kcratr_scan_lastbwr
• ORA-00600 [2662]和ORA-00600 [4194]恢复
• 一起ORA-600 3020故障恢复的大体思路
• File #xxx found in data dictionary but not in controlfile. Creating OFFLINE file ‘MISSING00XXX’ in the controlfile
• 硬件故障数据库异常恢复
• 分享一次ORA-01113 ORA-01110故障处理过程