标签云
asm 恢复 asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 kfed MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 ORACLE恢复 Oracle 恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (100)
- 数据库 (1,598)
- DB2 (22)
- MySQL (70)
- Oracle (1,463)
- Data Guard (49)
- EXADATA (7)
- GoldenGate (21)
- ORA-xxxxx (158)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (13)
- ORACLE 21C (3)
- Oracle ASM (65)
- Oracle Bug (7)
- Oracle RAC (47)
- Oracle 安全 (6)
- Oracle 开发 (27)
- Oracle 监听 (27)
- Oracle备份恢复 (530)
- Oracle安装升级 (84)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (75)
- PostgreSQL (18)
- PostgreSQL恢复 (6)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (36)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (19)
-
最近发表
- PostgreSQL解析wal日志之—walminer
- Oracle 19c/21c最新patch信息-202404
- PostgreSQL恢复系列:pg_filedump批量处理
- PostgreSQL部分主要字典信息
- PostgreSQL恢复系列:pg_filedump恢复字典构造
- PostgreSQL 16 源码安装
- ORA-00742 ORA-00312 恢复
- 数据库open成功后报ORA-00353 ORA-00354错误引起的一系列问题(本质ntfs文件系统异常)
- ORA-600 ktsiseginfo1故障
- ORA-00600: internal error code, arguments: [16703], [1403], [4] 原因
- 最近遇到几起ORA-600 16703故障(tab$被清空),请引起重视
- ORA-600 2662快速恢复之Patch scn工具
- TNS-12518: TNS:listener could not hand off client connection
- ora.storage无法启动报ORA-12514故障处理
- 断电引起文件scn异常数据库恢复
- ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
- .[hudsonL@cock.li].mkp勒索加密数据库完美恢复
- 模拟带库实现rman远程备份
- 又一例:ORA-600 kclchkblk_4和2662故障
- Oracle误删除数据文件恢复
标签归档:OSD-04016
又一例asm格式化文件系统恢复
又一个客户把win rac中的asm disk给格式化为ntfs了(data磁盘组由三个500G的磁盘组成,被格式化掉前面两个还剩下一个),而且格式化之后,还进行了一系列恢复(比如修复磁盘头,又进行分区等一些磁盘操作),导致恢复难度增加,也增加了一些数据覆盖
asm alert日志报错
Thu Aug 23 11:20:14 2018 NOTE: ASM client orcl1:orcl disconnected unexpectedly. NOTE: check client alert log. NOTE: Process state recorded in trace file d:\app\administrator\diag\asm\+asm\+asm1\trace\+asm1_ora_2260.trc Thu Aug 23 11:20:28 2018 Errors in file d:\app\administrator\diag\asm\+asm\+asm1\trace\+asm1_lgwr_3820.trc: ORA-27070: async read/write failed OSD-04016: 异步 I/O 请求排队时出错。 O/S-Error: (OS 87) 参数错误。 WARNING: IO Failed. group:2 disk(number.incarnation):1.0xf0f0a1cb disk_path:\\.\ORCLDISKDATA1 AU:26 disk_offset(bytes):27566080 io_size:4096 operation:Write type:synchronous result:I/O error process_id:3820 NOTE: unable to write any mirror side for diskgroup DATA NOTE: cache initiating offline of disk 1 group DATA NOTE: process 3268:3820 initiating offline of disk 1.4042301899 (DATA_0001) with mask 0x7e in group 2 WARNING: Disk DATA_0001 in mode 0x7f is now being taken offline NOTE: initiating PST update: grp = 2, dsk = 1/0xf0f0a1cb, mode = 0x15 kfdp_updateDsk(): 22 Thu Aug 23 11:20:28 2018 kfdp_updateDskBg(): 22 ERROR: too many offline disks in PST (grp 2) WARNING: Disk DATA_0001 in mode 0x7f offline aborted
数据库alert日志报错
WARNING: IO Failed. group:2 disk(number.incarnation):1.0xf0f0a1cb disk_path:\\.\ORCLDISKDATA1 AU:422 disk_offset(bytes):442515456 io_size:16384 operation:Read type:synchronous result:I/O error process_id:11992 WARNING: failed to read mirror side 1 of virtual extent 5 logical extent 0 of file 260 in group [2.1859146063] from disk DATA_0001 allocation unit 422 reason error; if possible,will try another mirror side Errors in file d:\app\administrator\diag\rdbms\orcl\orcl1\trace\orcl1_ora_11992.trc: ORA-15080: 与磁盘的同步 I/O 操作失败 WARNING: failed to write mirror side 1 of virtual extent 5 logical extent 0 of file 260 in group 2 on disk 1 allocation unit 422 Errors in file d:\app\administrator\diag\rdbms\orcl\orcl1\trace\orcl1_ora_11992.trc: ORA-00202: 控制文件: ''+DATA/orcl/controlfile/current.260.944422981'' ORA-15081: 无法将 I/O 操作提交到磁盘 Thu Aug 23 11:20:13 2018 Errors in file d:\app\administrator\diag\rdbms\orcl\orcl1\trace\orcl1_dbw1_3224.trc: ORA-27070: 异步读取/写入失败 WARNING: IO Failed. group:2 disk(number.incarnation):1.0xf0f0a1cb disk_path:\\.\ORCLDISKDATA1 AU:841 disk_offset(bytes):882532352 io_size:131072 operation:Write type:asynchronous result:I/O error process_id:3224 Errors in file d:\app\administrator\diag\rdbms\orcl\orcl1\trace\orcl1_dbw1_3224.trc: ORA-15080: 与磁盘的同步 I/O 操作失败 WARNING: failed to write mirror side 1 of virtual extent 240 logical extent 0 of file 259 in group 2 on disk 1 allocation unit 841 KCF: read, write or open error, block=0x7853 online=1 file=4 '+DATA/orcl/datafile/users.259.944422883' error=15081 txt: '' Errors in file d:\app\administrator\diag\rdbms\orcl\orcl1\trace\orcl1_dbw1_3224.trc: ORA-27070: 异步读取/写入失败 OSD-04006: ReadFile() 失败, 无法读取文件 O/S-Error: (OS 87) 参数错误。 WARNING: IO Failed. group:2 disk(number.incarnation):1.0xf0f0a1cb disk_path:\\.\ORCLDISKDATA1 AU:422 disk_offset(bytes):442515456 io_size:16384 operation:Read type:synchronous result:I/O error process_id:3224 WARNING: failed to read mirror side 1 of virtual extent 5 logical extent 0 of file 260 in group [2.1859146063] from disk DATA_0001 allocation unit 422 reason error; if possible,will try another mirror side Errors in file d:\app\administrator\diag\rdbms\orcl\orcl1\trace\orcl1_dbw1_3224.trc: ORA-15080: 与磁盘的同步 I/O 操作失败 WARNING: failed to write mirror side 1 of virtual extent 5 logical extent 0 of file 260 in group 2 on disk 1 allocation unit 422 Errors in file d:\app\administrator\diag\rdbms\orcl\orcl1\trace\orcl1_dbw1_3224.trc: ORA-00202: 控制文件: ''+DATA/orcl/controlfile/current.260.944422981'' ORA-15081: 无法将 I/O 操作提交到磁盘 Errors in file d:\app\administrator\diag\rdbms\orcl\orcl1\trace\orcl1_dbw1_3224.trc: ORA-00204: 读取控制文件时出错 (块 41, # 块 1) ORA-00202: 控制文件: ''+DATA/orcl/controlfile/current.260.944422981'' ORA-15081: 无法将 I/O 操作提交到磁盘 DBW1 (ospid: 3224): terminating the instance due to error 204
由于客户进行了一系列恢复恢复操作导致查看磁盘都不全
D:\>asmtool -list NTFS \Device\Harddisk0\Partition1 100M NTFS \Device\Harddisk0\Partition2 102298M NTFS \Device\Harddisk1\Partition1 102397M NTFS \Device\Harddisk2\Partition1 204797M ---这里还有一个磁盘没有正常显示 ORCLDISKDATA10 \Device\Harddisk4\Partition1 511997M--客户尝试修复的磁盘 ORCLDISKDATA2 \Device\Harddisk5\Partition1 511997M ORCLDISKRECOVERY0 \Device\Harddisk6\Partition1 51197M ORCLDISKRECOVERY1 \Device\Harddisk7\Partition1 51197M ORCLDISKRECOVERY2 \Device\Harddisk8\Partition1 51197M ORCLDISKCRS0 \Device\Harddisk9\Partition1 10237M ORCLDISKCRS1 \Device\Harddisk10\Partition1 10237M ORCLDISKCRS2 \Device\Harddisk11\Partition1 10237M NTFS \Device\Harddisk12\Partition2 4194174M
通过主机层面激活卷,删除分区等一系列操作,然后通过kfed构造磁盘头,让这些磁盘在os层面可以正常显示
C:\Users\Administrator>asmtool -list NTFS \Device\Harddisk0\Partition1 100M NTFS \Device\Harddisk0\Partition2 102298M NTFS \Device\Harddisk1\Partition1 102397M NTFS \Device\Harddisk2\Partition1 204797M ------需要处理的磁盘------ ORCLDISKDATA0 \Device\Harddisk3\Partition1 511997M ORCLDISKDATA1 \Device\Harddisk4\Partition1 511997M ORCLDISKDATA2 \Device\Harddisk5\Partition1 511997M ----------------------- ORCLDISKRECOVERY0 \Device\Harddisk6\Partition1 51197M ORCLDISKRECOVERY1 \Device\Harddisk7\Partition1 51197M ORCLDISKRECOVERY2 \Device\Harddisk8\Partition1 51197M ORCLDISKCRS0 \Device\Harddisk9\Partition1 10237M ORCLDISKCRS1 \Device\Harddisk10\Partition1 10237M ORCLDISKCRS2 \Device\Harddisk11\Partition1 10237M NTFS \Device\Harddisk12\Partition2 4194174M
由于asm磁盘组内部目录au被彻底损坏,导致无法通过asm直接拷贝出来数据,通过底层扫描,按照au恢复出来相关数据,由于格式化ntfs和后续的误操作导致部分数据au被覆盖.其余数据均恢复,抢救了绝大部分数据.
数据文件恢复参考:asm disk header 彻底损坏恢复
另外有一次win平台类似恢复经历:asm disk格式化为ntfs恢复
如果您遇到此类情况,无法解决请联系我们,提供专业ORACLE数据库恢复技术支持
Phone:17813235971 Q Q:107644445 E-Mail:dba@xifenfei.com
Automatic datafile offline due to write error on
由于存储突然掉线导致数据文件无法访问,导致部分数据文件被自动offline
Thu May 17 14:49:03 2018 KCF: read, write or open error, block=0xe93b8 online=1 Thu May 17 14:49:03 2018 KCF: read, write or open error, block=0x24eb65 online=1 file=25 'F:\ORACLE\ORADATA\ORCL\QYSCZH12.ORA' file=28 'F:\ORACLE\ORADATA\ORCL\QYSCZH15.ORA' error=27070 txt: 'OSD-04016: 异步 I/O 请求排队时出错。 O/S-Error: (OS 2) 系统找不到指定的文件。' Automatic datafile offline due to write error on file 25: F:\ORACLE\ORADATA\ORCL\QYSCZH12.ORA Thu May 17 14:49:03 2018 KCF: read, write or open error, block=0x22b0a1 online=1 file=28 'F:\ORACLE\ORADATA\ORCL\QYSCZH15.ORA' error=27070 txt: 'OSD-04016: 异步 I/O 请求排队时出错。 O/S-Error: (OS 2) 系统找不到指定的文件。' Automatic datafile offline due to write error on file 28: F:\ORACLE\ORADATA\ORCL\QYSCZH15.ORA Thu May 17 14:49:03 2018 KCF: read, write or open error, block=0x138def online=1 file=11 'F:\ORACLE\ORADATA\ORCL\QYSCZH4' error=27070 txt: 'OSD-04016: 异步 I/O 请求排队时出错。 O/S-Error: (OS 2) 系统找不到指定的文件。' file=30 'F:\ORACLE\ORADATA\ORCL\QYSCZH17.ORA' file=11 'F:\ORACLE\ORADATA\ORCL\QYSCZH4' error=27070 txt: 'OSD-04016: 异步 I/O 请求排队时出错。 error=27070 txt: 'OSD-04016: 异步 I/O 请求排队时出错。 O/S-Error: (OS 2) 系统找不到指定的文件。' O/S-Error: (OS 2) 系统找不到指定的文件。' …… file=15 'F:\ORACLE\ORADATA\ORCL\QYSCZH6.ORA' error=27072 txt: 'OSD-04008: WriteFile() 失败, 无法写入文件 O/S-Error: (OS 21) 设备未就绪。' Automatic datafile offline due to write error on file 15: F:\ORACLE\ORADATA\ORCL\QYSCZH6.ORA KCF: read, write or open error, block=0xade96 online=1 file=9 'F:\ORACLE\ORADATA\ORCL\QYSCZH2' error=27072 txt: 'OSD-04008: WriteFile() 失败, 无法写入文件 O/S-Error: (OS 21) 设备未就绪。' Automatic datafile offline due to write error on file 9: F:\ORACLE\ORADATA\ORCL\QYSCZH2 Thu May 17 14:49:28 2018 KCF: read, write or open error, block=0x378c66 online=1 file=15 'F:\ORACLE\ORADATA\ORCL\QYSCZH6.ORA' error=27072 txt: 'OSD-04008: WriteFile() 失败, 无法写入文件 O/S-Error: (OS 21) 设备未就绪。' Automatic datafile offline due to write error on file 15: F:\ORACLE\ORADATA\ORCL\QYSCZH6.ORA KCF: read, write or open error, block=0x35f6de online=1 ……
存储掉线是悲剧的起点,按理说数据库是归档模式,存储恢复之后,继续recover datafile,然后online应该问题不大,但是由于客户没有及时处理这个问题(也许业务实时性要求不高,可能挂几个小时也没人知道),导致第二个悲剧发生,删除归档的定时任务把数据库的归档日志给删除了.导致后面存储挂载上来之后,数据文件也无法正常online成功
Tue May 22 16:28:13 2018 ALTER DATABASE RECOVER datafile 'F:\ORACLE\ORADATA\ORCL\QYSCZH' Media Recovery Start Serial Media Recovery started ORA-279 signalled during: ALTER DATABASE RECOVER datafile 'F:\ORACLE\ORADATA\ORCL\QYSCZH' ... Tue May 22 16:28:42 2018 ALTER DATABASE RECOVER CONTINUE DEFAULT Media Recovery Log D:\ORALCE\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2018_05_22\O1_MF_1_267346_%U_.ARC Errors with log D:\ORALCE\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2018_05_22\O1_MF_1_267346_%U_.ARC ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ... ALTER DATABASE RECOVER CONTINUE DEFAULT Media Recovery Log D:\ORALCE\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2018_05_22\O1_MF_1_267346_%U_.ARC Errors with log D:\ORALCE\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2018_05_22\O1_MF_1_267346_%U_.ARC ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
通过Oracle数据库异常恢复检查脚本(Oracle Database Recovery Check)脚本检测发现结果如下:
遭遇这种情况,常规方法无法恢复,考虑使用bbed或者其他方法强制online文件,由于存储突然掉线,这样恢复的库可能后续还有大量工作需要处理,最常见的可能有表和index不一致,表的segment header信息和extent实际信息不匹配等
OSD-04016: 异步 I/O 请求排队时出错
有某客户由于硬件故障,导致数据库无法启动,让我们介入处理
数据库启动报错
Mon Feb 26 17:28:24 2018 ALTER DATABASE OPEN Beginning crash recovery of 1 threads parallel recovery started with 3 processes Started redo scan Completed redo scan read 2054 KB redo, 509 data blocks need recovery Started redo application at Thread 1: logseq 41341, block 54 Recovery of Online Redo Log: Thread 1 Group 1 Seq 41341 Reading mem 0 Mem# 0: E:\ORADATA\ORCL\REDO01.LOG Completed redo application of 1.77MB KCF: read, write or open error, block=0x16439 online=1 file=1 'E:\ORADATA\ORCL\SYSTEM01.DBF' error=27070 txt: 'OSD-04016: 异步 I/O 请求排队时出错。 O/S-Error: (OS 1) 函数不正确。' Errors in file d:\oracle\diag\rdbms\orcl\orcl\trace\orcl_dbw0_4928.trc: ORA-01243: system tablespace file suffered media failure ORA-01114: IO error writing block to file 1 (block # 91193) ORA-01110: data file 1: 'E:\ORADATA\ORCL\SYSTEM01.DBF' ORA-27070: async read/write failed OSD-04016: 异步 I/O 请求排队时出错。 O/S-Error: (OS 1) 函数不正确。 DBW0 (ospid: 4928): terminating the instance due to error 1243 Mon Feb 26 17:28:29 2018 Instance terminated by DBW0, pid = 4928
这里错误比较明显,由于io错误,在数据库实例恢复之时,写回block正好在该损坏位置从而使得数据库无法正常实例恢复,进而无法open.
dbv验证文件
通过专业工具对system文件进行了重构system文件,然后dbv检查结果如下
DBVERIFY: Release 11.2.0.1.0 - Production on 星期二 2月 27 17:20:14 2018 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. DBVERIFY - 开始验证: FILE = D:\OK\SYSTEM01.DBF 页 91156 标记为损坏 Corrupt block relative dba: 0x00416414 (file 1, block 91156) Bad header found during dbv: Data in bad block: type: 229 format: 6 rdba: 0xe1d9e3e7 last change scn: 0xd682.ffc8c7cb seq: 0x8c flg: 0x8c spare1: 0xc0 spare2: 0xf6 spare3: 0x70b3 consistency value in tail: 0x71f50602 check value in block header: 0x8195 computed block checksum: 0x8689 DBVERIFY - 验证完成 检查的页总数: 215040 处理的页总数 (数据): 178112 失败的页总数 (数据): 0 处理的页总数 (索引): 19070 失败的页总数 (索引): 0 处理的页总数 (其他): 3118 处理的总页数 (段) : 1 失败的总页数 (段) : 0 空的页总数: 14739 标记为损坏的总页数: 1 流入的页总数: 0 加密的总页数 : 0 最高块 SCN : 1638554501 (0.1638554501)
这里比较明显重构出来的system文件只有block 91156坏块,这里注意和没有处理之前的坏块不一样
通过dump分析坏块所属对象
Start dump data block from file D:\OK\SYSTEM01.DBF minblk 91156 maxblk 91156 V10 STYLE FILE HEADER: Compatibility Vsn = 186646528=0xb200000 Db ID=1383974140=0x527dc4fc, Db Name='ORCL' Activation ID=0=0x0 Control Seq=806694=0xc4f26, File size=215040=0x34800 File Number=1, Blksiz=8192, File Type=3 DATA Dump all the blocks in range: buffer tsn: 0 rdba: 0xe1d9e3e7 (903/1696743) scn: 0xd682.ffc8c7cb seq: 0x8c flg: 0x8c tail: 0x71f50602 frmt: 0x06 chkval: 0x8195 type: 0xe5=unknown Hex dump of corrupt header 4 = CORRUPT Start dump data block from file D:\OK\SYSTEM01.DBF minblk 91155 maxblk 91155 V10 STYLE FILE HEADER: Compatibility Vsn = 186646528=0xb200000 Db ID=1383974140=0x527dc4fc, Db Name='ORCL' Activation ID=0=0x0 Control Seq=806694=0xc4f26, File size=215040=0x34800 File Number=1, Blksiz=8192, File Type=3 DATA Dump all the blocks in range: buffer tsn: 0 rdba: 0x00416413 (1/91155) scn: 0x0000.613ad8d6 seq: 0x01 flg: 0x06 tail: 0xd8d60601 frmt: 0x02 chkval: 0xcc5f type: 0x06=trans data Hex dump of block: st=0, typ_found=1 Block header dump: 0x00416413 Object id on Block? Y seg/obj: 0x25 csc: 0x00.613ad8ce itc: 2 flg: - typ: 2 - INDEX fsl: 0 fnx: 0x0 ver: 0x01 Itl Xid Uba Flag Lck Scn/Fsc 0x01 0x0009.000.0016fda0 0x00c0130e.6f38.01 CB-- 0 scn 0x0000.3e6ed294 0x02 0x0009.008.0023e862 0x00c002cf.a217.13 --U- 1 fsc 0x0000.613ad8d6 Start dump data block from file D:\OK\SYSTEM01.DBF minblk 91157 maxblk 91157 V10 STYLE FILE HEADER: Compatibility Vsn = 186646528=0xb200000 Db ID=1383974140=0x527dc4fc, Db Name='ORCL' Activation ID=0=0x0 Control Seq=806694=0xc4f26, File size=215040=0x34800 File Number=1, Blksiz=8192, File Type=3 DATA Dump all the blocks in range: buffer tsn: 0 rdba: 0x00416415 (1/91157) scn: 0x0000.6193dc0c seq: 0x01 flg: 0x06 tail: 0xdc0c0601 frmt: 0x02 chkval: 0x8c21 type: 0x06=trans data Hex dump of block: st=0, typ_found=1 Block header dump: 0x00416415 Object id on Block? Y seg/obj: 0x25 csc: 0x00.6193dc04 itc: 2 flg: - typ: 2 - INDEX fsl: 0 fnx: 0x0 ver: 0x01 Itl Xid Uba Flag Lck Scn/Fsc 0x01 0x0006.00c.001ee103 0x00c008a5.8dbd.02 C--- 0 scn 0x0000.57303e03 0x02 0x000b.00f.00053100 0x00c008af.1563.09 --U- 1 fsc 0x0000.6193dc0c
这里比较明显,可以确定坏块为index,object_id=0×25=37,通过查询其他库,确定为i_obj2(obj$的index)
使用该文件启动数据库
SQL> alter database rename file 'E:\ORADATA\ORCL\SYSTEM01.DBF' to 'd:\orcl\SYSTEM01.DBF'; 数据库已更改。 SQL> recover database; 完成介质恢复。 SQL> alter database open; 数据库已更改。
检查alert日志
发现smon进程由于坏块的存储,出现大量报错,需要处理,不然数据库一段时间后就会crash.
Tue Feb 27 20:31:23 2018 QMNC started with pid=27, OS id=4652 Completed: alter database open Tue Feb 27 20:31:25 2018 Starting background process CJQ0 Tue Feb 27 20:31:25 2018 CJQ0 started with pid=30, OS id=2172 Tue Feb 27 20:31:25 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Hex dump of (file 1, block 91156) in trace file d:\oracle\diag\rdbms\orcl\orcl\trace\orcl_cjq0_2172.trc Corrupt block relative dba: 0x00416414 (file 1, block 91156) Bad header found during multiblock buffer read Data in bad block: type: 229 format: 6 rdba: 0xe1d9e3e7 last change scn: 0xd682.ffc8c7cb seq: 0x8c flg: 0x8c spare1: 0xc0 spare2: 0xf6 spare3: 0x70b3 consistency value in tail: 0x71f50602 check value in block header: 0x8195 computed block checksum: 0x8689 Reading datafile 'D:\ORCL\SYSTEM01.DBF' for corruption at rdba: 0x00416414 (file 1, block 91156) Reread (file 1, block 91156) found same corrupt data Errors in file d:\oracle\diag\rdbms\orcl\orcl\trace\orcl_smon_3992.trc (incident=77085): ORA-01578: ORACLE data block corrupted (file # 1, block # 91156) ORA-01110: data file 1: 'D:\ORCL\SYSTEM01.DBF' Incident details in: d:\oracle\diag\rdbms\orcl\orcl\incident\incdir_77085\orcl_smon_3992_i77085.trc Errors in file d:\oracle\diag\rdbms\orcl\orcl\trace\orcl_cjq0_2172.trc (incident=77221): ORA-01578: ORACLE data block corrupted (file # 1, block # 91156) ORA-01110: data file 1: 'D:\ORCL\SYSTEM01.DBF' Incident details in: d:\oracle\diag\rdbms\orcl\orcl\incident\incdir_77221\orcl_cjq0_2172_i77221.trc
重建i_obj2 index,参考://www.xifenfei.com/?p=5566