联系：手机/微信(+86 17813235971) QQ(107644445)
标题：快速处理 ORA-01210: data file header is media corrupt 故障
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
客户反馈硬件故障之后,数据库无法正常启动，尝试recover操作报ORA-01122错误
SQL> recover database; ORA-00283: 恢复会话因错误而取消 ORA-01122: 数据库文件 1 验证失败 ORA-01110: 数据文件 1: 'H:\BAIDUNETDISK\ORACLEDATA\ORCL\SYSTEM01.DBF' ORA-01207: 文件比控制文件更新 - 旧的控制文件
这个错误比较明显，由于数据文件的checkpoint信息比数据文件 file# 1新，通过重建ctl可以进行解决
SQL> @rectl.sql CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS FORCE LOGGING ARCHIVELOG * 第 1 行出现错误: ORA-01503: CREATE CONTROLFILE failed ORA-01210: data file header is media corrupt ORA-01110: data file 42: 'H:\BAIDUNETDISK\ORACLEDATA\ORCL\XFF.DBF'
但是这里遭遇到ORA-01210错误
[oracle@iZbp11c0qyuuo1gr7j98upZ ~]$ oerr ora 1210 01210, 00000, "data file header is media corrupt" // *Cause: The file header block is internally inconsistent. The beginning // of the block has a header with a checksum and other data for // insuring the consistancy of the block. It is possible that // the last disk write did not operate correctly. The most likely // problem is that this is not a datafile for any database. // *Action: Have operating system make correct file available to database. // If the trace file dump indicates that only the checksum is wrong, // restore from a backup and do media recovery.
这个错误比较明显，官方解释可能是由于文件头的写丢失导致checksum异常,对于这样的故障，可以考虑使用bbed进行修复，但是obet更加方便（Oracle数据块编辑工具( Oracle Block Editor Tool)-obet），直接使用这个工具进行处理
OBET> tailchk Check tailchk for File H:\BaiduNetdisk\oracledata\orcl\XFF.DBF, Block 1: current = 0x6E743122, required = 0x010B0000 OBET> d File: H:\BaiduNetdisk\oracledata\orcl\HD_DATAPMS01.DBF Block: 1 Offsets: 0 to 31 -------------------------------------------------------------------------------- 00002000 0BA20000 0100800A 00000000 00000104 02870000 00000000 0004200B 2F2E315E <32 bytes read> OBET> set mode edit mode set to: edit OBET> tailchk apply Confirm applying tailchk: File: H:\BaiduNetdisk\oracledata\orcl\XFF.DBF Block: 1 Offset in block: 8188 (file offset: 0x00003FFC) Original value: 0x6E743122 New value: 0x010B0000 Confirm? (Y/YES to proceed): y Verification successful: Stored tailchk matches calculated value (0x010B0000). Tailchk applied successfully. OBET> sum apply Confirm applying checksum: File: H:\BaiduNetdisk\oracledata\orcl\XFF.DBF Block: 1 Offset in block: 16 (file offset: 0x00002010) Original value: 0x0287 New value: 0x38ED Confirm? (Y/YES to proceed): y Verification successful: Stored checksum matches calculated value (0x38ED). Checksum applied successfully.
然后直接重建ctl成功，并顺利打开数据库
Thu Jul 23 12:11:39 2026
Successful mount of redo thread 1, with mount id 1767178232
Completed: CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS FORCE LOGGING ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 18688
LOGFILE
GROUP 1 'H:\BAIDUNETDISK\ORACLEDATA\ORCL\REDO01.LOG' SIZE 50M BLOCKSIZE 512,
GROUP 2 'H:\BAIDUNETDISK\ORACLEDATA\ORCL\REDO02.LOG' SIZE 50M BLOCKSIZE 512,
GROUP 3 'H:\BAIDUNETDISK\ORACLEDATA\ORCL\REDO03.LOG' SIZE 50M BLOCKSIZE 512
DATAFILE
'H:\BAIDUNETDISK\ORACLEDATA\ORCL\SYSTEM01.DBF',
'H:\BAIDUNETDISK\ORACLEDATA\ORCL\SYSAUX01.DBF',
'H:\BAIDUNETDISK\ORACLEDATA\ORCL\UNDOTBS01.DBF',
………………
CHARACTER SET ZHS16GBK
Thu Jul 23 12:12:21 2026
ALTER DATABASE RECOVER database
Media Recovery Start
started logmerger process
Parallel Media Recovery started with 20 slaves
Thu Jul 23 12:12:21 2026
Recovery of Online Redo Log: Thread 1 Group 3 Seq 104748 Reading mem 0
Mem# 0: H:\BAIDUNETDISK\ORACLEDATA\ORCL\REDO03.LOG
Recovery of Online Redo Log: Thread 1 Group 1 Seq 104749 Reading mem 0
Mem# 0: H:\BAIDUNETDISK\ORACLEDATA\ORCL\REDO01.LOG
Completed: ALTER DATABASE RECOVER database
alter database open upgrade
Beginning crash recovery of 1 threads
parallel recovery started with 19 processes
Started redo scan
Completed redo scan
read 8331 KB redo, 0 data blocks need recovery
Started redo application at
Thread 1: logseq 104749, block 2, scn 788671390
Recovery of Online Redo Log: Thread 1 Group 1 Seq 104749 Reading mem 0
Mem# 0: H:\BAIDUNETDISK\ORACLEDATA\ORCL\REDO01.LOG
Completed redo application of 0.00MB
Completed crash recovery at
Thread 1: logseq 104749, block 16665, scn 788695898
0 data blocks read, 0 data blocks written, 8331 redo k-bytes read
Initializing SCN for created control file
Database SCN compatibility initialized to 3
Thu Jul 23 12:12:27 2026
LGWR: STARTING ARCH PROCESSES
Thu Jul 23 12:12:27 2026
ARC0 started with pid=40, OS id=20580
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Thu Jul 23 12:12:28 2026
ARC1 started with pid=41, OS id=12396
Thu Jul 23 12:12:28 2026
ARC2 started with pid=42, OS id=18888
Thu Jul 23 12:12:28 2026
ARC3 started with pid=43, OS id=16552
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
Archived Log entry 1 added for thread 1 sequence 104747 ID 0x5e30f62f dest 1:
Thread 1 advanced to log sequence 104750 (thread open)
Thread 1 opened at log sequence 104750
Current log# 2 seq# 104750 mem# 0: H:\BAIDUNETDISK\ORACLEDATA\ORCL\REDO02.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Jul 23 12:12:29 2026
SMON: enabling cache recovery
Archived Log entry 2 added for thread 1 sequence 104749 ID 0x5e30f62f dest 1:
Archived Log entry 3 added for thread 1 sequence 104748 ID 0x5e30f62f dest 1:
[19300] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:15968843 end:15968859 diff:16 (0 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
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
*********************************************************************
Database Characterset is ZHS16GBK
Stopping background process MMNL
Errors in file C:\APP\XFF\diag\rdbms\orcl\orcl\trace\orcl_smon_18084.trc (incident=7313):
ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: C:\APP\XFF\diag\rdbms\orcl\orcl\incident\incdir_7313\orcl_smon_18084_i7313.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Block recovery from logseq 104750, block 74 to scn 906345854
Recovery of Online Redo Log: Thread 1 Group 2 Seq 104750 Reading mem 0
Mem# 0: H:\BAIDUNETDISK\ORACLEDATA\ORCL\REDO02.LOG
Block recovery completed at rba 104750.75.16, scn 0.906345855
Block recovery from logseq 104750, block 74 to scn 906345854
Recovery of Online Redo Log: Thread 1 Group 2 Seq 104750 Reading mem 0
Mem# 0: H:\BAIDUNETDISK\ORACLEDATA\ORCL\REDO02.LOG
Block recovery completed at rba 104750.75.16, scn 0.906345855
Errors in file C:\APP\XFF\diag\rdbms\orcl\orcl\trace\orcl_smon_18084.trc:
ORA-01595: 释放区 (2) 回退段 (4) 时出错
ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], []
这里有一个ORA-600 4194错误,由于undo回滚段异常，对异常回滚段进行处理，然后导出数据完成本次恢复工作
