标签云
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 2131 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)
- 操作系统 (102)
- 数据库 (1,670)
- DB2 (22)
- MySQL (73)
- Oracle (1,532)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (21)
- ORA-xxxxx (159)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (14)
- ORACLE 21C (3)
- Oracle 23ai (7)
- Oracle ASM (65)
- Oracle Bug (8)
- Oracle RAC (52)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (560)
- Oracle安装升级 (91)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (78)
- PostgreSQL (18)
- PostgreSQL恢复 (6)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (37)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (20)
-
最近发表
- ORA-600 krse_arc_complete.4
- Oracle 19c 202410补丁(RUs+OJVM)
- ntfs MFT损坏(ntfs文件系统故障)导致oracle异常恢复
- .mkp扩展名oracle数据文件加密恢复
- 清空redo,导致ORA-27048: skgfifi: file header information is invalid
- A_H_README_TO_RECOVER勒索恢复
- 通过alert日志分析客户自行对一个数据库恢复的来龙去脉和点评
- ORA-12514: TNS: 监听进程不能解析在连接描述符中给出的SERVICE_NAME
- ORA-01092 ORA-00604 ORA-01558故障处理
- ORA-65088: database open should be retried
- Oracle 19c异常恢复—ORA-01209/ORA-65088
- ORA-600 16703故障再现
- 数据库启动报ORA-27102 OSD-00026 O/S-Error: (OS 1455)
- .[metro777@cock.li].Elbie勒索病毒加密数据库恢复
- 应用连接错误,初始化mysql数据库恢复
- RAC默认服务配置优先节点
- Oracle 19c RAC 替换私网操作
- 监听报TNS-12541 TNS-12560 TNS-00511错误
- drop tablespace xxx including contents恢复
- Linux 8 修改网卡名称
标签归档:ORA-03113
ORA-03113: 通信通道的文件结尾
数据库启动报:ORA-03113: 通信通道的文件结尾
PS C:\Users\Administrator> sqlplus / as sysdba SQL*Plus: Release 11.2.0.1.0 Production on 星期六 8月 3 11:05:03 2024 Copyright (c) 1982, 2010, Oracle. All rights reserved. 已连接到空闲例程。 SQL> startup nomount ORACLE 例程已经启动。 Total System Global Area 2.0510E+10 bytes Fixed Size 2184632 bytes Variable Size 1.1476E+10 bytes Database Buffers 8992587776 bytes Redo Buffers 40046592 bytes SQL> shutdown immediate ORA-01507: ?????? ORACLE 例程已经关闭。 SQL> startup ORACLE 例程已经启动。 Total System Global Area 2.0510E+10 bytes Fixed Size 2184632 bytes Variable Size 1.1476E+10 bytes Database Buffers 8992587776 bytes Redo Buffers 40046592 bytes 数据库装载完毕。 ORA-03113: 通信通道的文件结尾 进程 ID: 4040 会话 ID: 1018 序列号: 7
这类错误,一般真正错误原因在alert日志中,查看alert日志
Sat Aug 03 08:15:12 2024 alter database mount exclusive Successful mount of redo thread 1, with mount id 3557233552 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads parallel recovery started with 11 processes Started redo scan Completed redo scan read 0 KB redo, 0 data blocks need recovery Started redo application at Thread 1: logseq 745, block 80599, scn 7100295 Recovery of Online Redo Log: Thread 1 Group 1 Seq 745 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\XFF\REDO01.LOG Completed redo application of 0.00MB Completed crash recovery at Thread 1: logseq 745, block 80599, scn 7120296 0 data blocks read, 0 data blocks written, 0 redo k-bytes read LGWR: STARTING ARCH PROCESSES Sat Aug 03 08:15:19 2024 ARC0 started with pid=32, OS id=5496 ARC0: Archival started LGWR: STARTING ARCH PROCESSES COMPLETE ARC0: STARTING ARCH PROCESSES Sat Aug 03 08:15:20 2024 ARC1 started with pid=33, OS id=3873072 Sat Aug 03 08:15:20 2024 ARC2 started with pid=34, OS id=3873644 ARC1: Archival started ARC2: Archival started ARC2: Becoming the 'no FAL' ARCH ARC2: Becoming the 'no SRL' ARCH ARC1: Becoming the heartbeat ARCH sksasmowrt WriteConsole error 6 Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_arc2_3873644.trc: ORA-19815: 警告: db_recovery_file_dest_size 字节 (共 10737418240 字节) 已使用 100.00%, 尚有 0 字节可用。 ************************************************************************ You have following choices to free up space from recovery area: 1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard, then consider changing RMAN ARCHIVELOG DELETION POLICY. 2. Back up files to tertiary device such as tape using RMAN BACKUP RECOVERY AREA command. 3. Add disk space and increase db_recovery_file_dest_size parameter to reflect the new space. 4. Delete unnecessary files using RMAN DELETE command. If an operating system command was used to delete files, then use RMAN CROSSCHECK and DELETE EXPIRED commands. ************************************************************************ Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_arc2_3873644.trc: ORA-19809: 超出了恢复文件数的限制 ORA-19804: 无法回收 13760000 字节磁盘空间 (从 10737418240 限制中) ARC2: Error 19809 Creating archive log file to 'D:\FRA\XFF\ARCHIVELOG\2024_08_03\O1_MF_1_744_%U_.ARC' Sat Aug 03 08:15:20 2024 ARC3 started with pid=35, OS id=3873424 ARC3: Archival started ARC0: STARTING ARCH PROCESSES COMPLETE Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_ora_3873352.trc: ORA-19815: ??: db_recovery_file_dest_size ?? (? 10737418240 ??) ??? 100.00%, ?? 0 ????? ************************************************************************ You have following choices to free up space from recovery area: 1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard, then consider changing RMAN ARCHIVELOG DELETION POLICY. 2. Back up files to tertiary device such as tape using RMAN BACKUP RECOVERY AREA command. 3. Add disk space and increase db_recovery_file_dest_size parameter to reflect the new space. 4. Delete unnecessary files using RMAN DELETE command. If an operating system command was used to delete files, then use RMAN CROSSCHECK and DELETE EXPIRED commands. ************************************************************************ Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_ora_3873352.trc: ORA-19809: ??????????? ORA-19804: ???? 12296704 ?????? (? 10737418240 ???) ARCH: Error 19809 Creating archive log file to 'D:\FRA\XFF\ARCHIVELOG\2024_08_03\O1_MF_1_743_%U_.ARC' ARCH: Archival stopped, error occurred. Will continue retrying Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_arc2_3873644.trc: ORA-16038: 日志 3 sequence# 744 无法归档 ORA-19809: 超出了恢复文件数的限制 ORA-00312: 联机日志 3 线程 1: 'D:\ORACLE\ORADATA\XFF\REDO03.LOG' Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_ora_3873352.trc: ORA-16038: ?? 2 sequence# 743 ???? ORA-19809: ??????????? ORA-00312: ???? 2 ?? 1: 'D:\ORACLE\ORADATA\XFF\REDO02.LOG' USER (ospid: 3873352): terminating the instance due to error 16038 Sat Aug 03 08:15:27 2024 Instance terminated by USER, pid = 3873352
是由于闪回区满了,导致redo无法归档,从而使得数据库无法正常open,解决办法:
1. 清理以前归档日志
2. 把闪回区调大一些
由于bootstrap$异常导致数据库启动报ORA-03113 ORA-07445 lmebucp
数据库无法正常启动,报ORA-03113
SQL> startup ORACLE 例程已经启动。 Total System Global Area 5016387584 bytes Fixed Size 2011136 bytes Variable Size 905969664 bytes Database Buffers 4093640704 bytes Redo Buffers 14766080 bytes 数据库装载完毕。 ORA-03113: 通信通道的文件结束
alert日志报错ORA-07445 lmebucp
Mon Aug 27 15:31:37 2018 Thread 1 advanced to log sequence 21691 Thread 1 opened at log sequence 21691 Current log# 2 seq# 21691 mem# 0: /data/oracle/orcl/redo02.log Successful open of redo thread 1 Mon Aug 27 15:31:37 2018 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Mon Aug 27 15:31:37 2018 SMON: enabling cache recovery Mon Aug 27 15:31:37 2018 Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/orcl/udump/orcl_ora_5827.trc: ORA-07445: exception encountered: core dump [lmebucp()+24] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []
跟踪启动10046 trace
WAIT #1: nam='instance state change' ela= 822 layer=2 value=1 waited=1 obj#=-1 tim=1499370211971345 WAIT #1: nam='db file sequential read' ela= 29 file#=1 block#=257 blocks=1 obj#=-1 tim=1499370211971896 ===================== PARSING IN CURSOR #2 len=188 dep=1 uid=0 oct=1 lid=0 tim=1499370211972625 hv=2809067040 ad='b5fe2d00' create table bootstrap$ ( line# number not null, obj# number not null, sql_text varchar2(4000) not null) storage (initial 50K objno 41 extents (file 1 block 257)) END OF STMT PARSE #2:c=0,e=598,p=0,cr=0,cu=0,mis=1,r=0,dep=1,og=4,tim=1499370211972621 BINDS #2: EXEC #2:c=1000,e=195,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=4,tim=1499370211972873 ===================== PARSING IN CURSOR #2 len=55 dep=1 uid=0 oct=3 lid=0 tim=1499370211973429 hv=2111436465 ad='b7bd0530' select line#, sql_text from bootstrap$ where obj# != :1 END OF STMT PARSE #2:c=0,e=472,p=0,cr=0,cu=0,mis=1,r=0,dep=1,og=4,tim=1499370211973426 BINDS #2: kkscoacd Bind#0 oacdty=02 mxl=22(22) mxlc=00 mal=00 scl=00 pre=00 oacflg=08 fl2=0001 frm=00 csi=00 siz=24 off=0 kxsbbbfp=2b8c5d50a4d0 bln=22 avl=02 flg=05 value=41 EXEC #2:c=1000,e=838,p=0,cr=0,cu=0,mis=1,r=0,dep=1,og=4,tim=1499370211974375 WAIT #2: nam='db file sequential read' ela= 27 file#=1 block#=257 blocks=1 obj#=-1 tim=1499370211974522 WAIT #2: nam='db file sequential read' ela= 21 file#=1 block#=258 blocks=1 obj#=-1 tim=1499370211974855 FETCH #2:c=1000,e=479,p=2,cr=3,cu=0,mis=0,r=0,dep=1,og=4,tim=1499370211974908 Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x0, PC: [0x348772c, lmebucp()+24] *** 2018-08-27 15:31:37.074 ksedmp: internal or fatal error ORA-07445: exception encountered: core dump [lmebucp()+24] [SIGSEGV] [Address not mapped to object] [0x000000000] [] [] Current SQL statement for this session: alter database open ----- Call Stack Trace ----- calling call entry argument values in hex location type point (? means dubious value) -------------------- -------- -------------------- ---------------------------- Cannot find symbol Cannot find symbol Cannot find symbol ksedst()+31 call ksedst1() 000000001 ? 000000001 ? 000000000 ? 000000000 ? 000000000 ? 000000001 ? ksedmp()+610 call ksedst() 000000001 ? 000000001 ? 000000000 ? 000000000 ? 000000000 ? 000000001 ? ssexhd()+630 call ksedmp() 000000003 ? 000000001 ? 000000000 ? 000000000 ? 000000000 ? 000000001 ? <0x336800eca0> call ssexhd() 00000000B ? 2B8C5D238D70 ? 2B8C5D238C40 ? 000000000 ? 000000000 ? 000000001 ? --------------------- Binary Stack Dump ---------------------
通过这里发现,数据库启动执行select line#, sql_text from bootstrap$ where obj# != :1然后报ORA-07445 lmebucp错误。这样的错误比较诡异,一般可能是由于bootstrap异常导致,但是这里再往上跟踪发现 create bootstrap$表指定的记录为file 1 block 257,根据经验知道数据库的bootstrap$表记录一般是377 或者520比较常见.通过工具对于file 1进行分析
DUL> dump datafile 1 block 257 Block Header: block type=0x10 (data segment header block (unlimited extents)) block format=0xa2 (oracle 10) block rdba=0x00400101 (file#=1, block#=257) scn=0x0000.0000007e, seq=1, tail=0x007e1001 block checksum value=0xe75c=59228, flag=4 Data Segment Header: Extent Control Header ------------------------------------------------------------- Extent Header:: extents: 1 blocks: 7 last map: 0x00000000 #maps: 0 offset: 4128 Highwater:: 0x00400103 (rfile#=1,block#=259) ext#: 0 blk#: 1 ext size:7 #blocks in seg. hdr's freelists: 0 #blocks below: 1 mapblk: 0x00000000 offset: 0 Map Header:: next: 0x00000000 #extents: 1 obj#: 41 flag: 0x40000000 Extent Control Header ------------------------------------------------------------- 0x00400102 length: 7 nfl = 1, nfb = 1, typ = 2, nxf = 0, ccnt = 0 SEG LST:: flg:UNUSED lhd: 0x00000000 ltl: 0x00000000
发现异常比较明显,block 257为data_object_id=41,也就是
41|41|CREATE UNIQUE INDEX I_FILE1 ON FILE$(FILE#) PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K NEXT 1024K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 OBJNO 41 EXTENTS (FILE 1 BLOCK 257))
这里看数据库的引导异常或者bootstrap$表中记录异常.通过修复bootstrap相关内容,数据库完美启动
ora-600 2037 ORA-7445 kcbs_dump_adv_state解决
有客户系统断电,导致数据库无法启动,让我们帮忙解决,通过分析主要是ORA-600 2037和ORA-7445 _kcbs_dump_adv_state等错误,通过人工recover解决.
数据库报ORA-03113,无法启动成功
C:\Documents and Settings\Administrator>sqlplus / as sysdba SQL*Plus: Release 10.2.0.1.0 - Production on 星期五 5月 12 09:50:36 2017 Copyright (c) 1982, 2005, Oracle. All rights reserved. 已连接到空闲例程。 SQL> startup ORACLE 例程已经启动。 Total System Global Area 1258291200 bytes Fixed Size 1250548 bytes Variable Size 218106636 bytes Database Buffers 1031798784 bytes Redo Buffers 7135232 bytes 数据库装载完毕。 ORA-03113: 通信通道的文件结束
分析alert日志
Fri May 12 09:50:43 2017 ALTER DATABASE OPEN Fri May 12 09:50:43 2017 Beginning crash recovery of 1 threads parallel recovery started with 15 processes Fri May 12 09:50:43 2017 Started redo scan Fri May 12 09:50:43 2017 Completed redo scan 1240 redo blocks read, 277 data blocks need recovery Fri May 12 09:50:44 2017 Started redo application at Thread 1: logseq 5881, block 41179 Fri May 12 09:50:44 2017 Recovery of Online Redo Log: Thread 1 Group 1 Seq 5881 Reading mem 0 Mem# 0 errs 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\xff\REDO01.LOG Fri May 12 09:50:44 2017 Completed redo application Fri May 12 09:50:44 2017 Errors in file e:\oracle\product\10.2.0\admin\xff\bdump\xff_p006_6072.trc: ORA-00600: internal error code, arguments: [6110], [193], [3], [], [], [], [], [] Fri May 12 09:50:44 2017 Hex dump of (file 3, block 14004) in trace file e:\oracle\product\10.2.0\admin\xff\bdump\xff_p000_6024.trc Corrupt block relative dba: 0x00c036b4 (file 3, block 14004) Bad header found during crash/instance recovery Data in bad block: type: 255 format: 7 rdba: 0x06010601 last change scn: 0xa206.a2060601 seq: 0xb4 flg: 0x36 spare1: 0x1 spare2: 0x6 spare3: 0x673 consistency value in tail: 0x1b0a0708 check value in block header: 0x36b4 computed block checksum: 0xe4f5 Fri May 12 09:50:44 2017 Hex dump of (file 9, block 65507) in trace file e:\oracle\product\10.2.0\admin\xff\bdump\xff_p003_6056.trc Corrupt block relative dba: 0x0240ffe3 (file 9, block 65507) Bad header found during crash/instance recovery Data in bad block: type: 3 format: 6 rdba: 0x06020601 last change scn: 0xa206.a2060602 seq: 0xe3 flg: 0xff spare1: 0x1 spare2: 0x6 spare3: 0x6dc consistency value in tail: 0xc1028001 check value in block header: 0xffe3 computed block checksum: 0xff01 Fri May 12 09:50:44 2017 Reread of rdba: 0x00c036b4 (file 3, block 14004) found different data Fri May 12 09:50:44 2017 Reread of rdba: 0x0240ffe3 (file 9, block 65507) found different data Fri May 12 09:50:44 2017 Errors in file e:\oracle\product\10.2.0\admin\xff\bdump\xff_p005_6060.trc: ORA-00600: internal error code,arguments:[2037],[17442602],[2718302723],[255],[9],[203],[657105414],[2147549568] Fri May 12 09:50:44 2017 Errors in file e:\oracle\product\10.2.0\admin\xff\bdump\xff_p000_6024.trc: ORA-07445:exception encountered:core dump[ACCESS_VIOLATION][_kclcomplete+79][PC:0x72B0C7][ADDR:0x220][UNABLE_TO_READ][] Fri May 12 09:50:44 2017 Errors in file e:\oracle\product\10.2.0\admin\xff\bdump\xff_p006_6072.trc: ORA-07445: exception encountered:core dump[ACCESS_VIOLATION][_kcbzdh+2496][PC:0x4A4928][ADDR:0xB][UNABLE_TO_READ][] ORA-00600: internal error code, arguments: [6110], [193], [3], [], [], [], [], [] Errors in file e:\oracle\product\10.2.0\admin\xff\bdump\xff_p012_6128.trc: ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kcbs_dump_adv_state+723] [PC:0x5975A3] [ADDR:0xCBC0CBB2] [UNABLE_TO_READ] [] ORA-00600:internal error code,arguments:[2037],[17430318],[2718303745],[128],[1],[203],[4147028486],[2147549568]
错误比较明显由于坏块导致应用日志恢复异常,主要错误集中在ORA-600 2037,ORA-7445 _kcbs_dump_adv_state,ORA-7445_kcbzdh,ORA-7445 _kclcomplete等
dbv检查数据文件
E:\>dbv file=E:\ORACLE\PRODUCT\10.2.0\ORADATA\xff\SYSAUX01.DBF DBVERIFY: Release 10.2.0.1.0 - Production on 星期五 5月 12 09:57:39 2017 Copyright (c) 1982, 2005, Oracle. All rights reserved. DBVERIFY - 开始验证: FILE = E:\ORACLE\PRODUCT\10.2.0\ORADATA\xff\SYSAUX01.DBF 页 13353 标记为损坏 Corrupt block relative dba: 0x00c03429 (file 3, block 13353) Bad header found during dbv: Data in bad block: type: 1 format: 6 rdba: 0x3429a206 last change scn: 0x066f.066f3429 seq: 0x0 flg: 0x00 spare1: 0x6 spare2: 0xa2 spare3: 0x8c96 consistency value in tail: 0x06018001 check value in block header: 0x0 block checksum disabled 页 14004 标记为损坏 Corrupt block relative dba: 0x00c036b4 (file 3, block 14004) Bad header found during dbv: Data in bad block: type: 1 format: 6 rdba: 0x36b4a206 last change scn: 0x0673.067336b4 seq: 0x0 flg: 0x00 spare1: 0x6 spare2: 0xa2 spare3: 0xfb97 consistency value in tail: 0x06010210 check value in block header: 0x0 block checksum disabled 页 15261 标记为损坏 Corrupt block relative dba: 0x00c03b9d (file 3, block 15261) Bad header found during dbv: Data in bad block: type: 2 format: 6 rdba: 0x3b9da206 last change scn: 0x0673.06733b9d seq: 0x0 flg: 0x00 spare1: 0x6 spare2: 0xa2 spare3: 0x0 consistency value in tail: 0x06018001 check value in block header: 0x5549 block checksum disabled DBVERIFY - 验证完成 检查的页总数: 58880 处理的页总数 (数据): 19318 失败的页总数 (数据): 0 处理的页总数 (索引): 18610 失败的页总数 (索引): 0 处理的页总数 (其它): 13747 处理的总页数 (段) : 0 失败的总页数 (段) : 0 空的页总数: 7202 标记为损坏的总页数: 3 流入的页总数: 0 最高块 SCN : 178325323 (0.178325323) E:\>dbv file=E:\ORACLE\PRODUCT\10.2.0\ORADATA\xff\xff_BSE02 DBVERIFY: Release 10.2.0.1.0 - Production on 星期五 5月 12 10:10:24 2017 Copyright (c) 1982, 2005, Oracle. All rights reserved. DBVERIFY - 开始验证: FILE = E:\ORACLE\PRODUCT\10.2.0\ORADATA\xff\xff_BSE02 页 65507 标记为损坏 Corrupt block relative dba: 0x0240ffe3 (file 9, block 65507) Bad header found during dbv: Data in bad block: type: 2 format: 6 rdba: 0xffe3a206 last change scn: 0x06dc.06dcffe3 seq: 0x0 flg: 0x00 spare1: 0x6 spare2: 0xa2 spare3: 0xb32 consistency value in tail: 0x060102ff check value in block header: 0x0 block checksum disabled DBVERIFY - 验证完成 检查的页总数: 1310720 处理的页总数 (数据): 34102 失败的页总数 (数据): 0 处理的页总数 (索引): 30270 失败的页总数 (索引): 0 处理的页总数 (其它): 10850 处理的总页数 (段) : 0 失败的总页数 (段) : 0 空的页总数: 1235497 标记为损坏的总页数: 1 流入的页总数: 0 最高块 SCN : 178325221 (0.178325221)
确实如alert日志报错,file 3和9 都出现坏块导致实例恢复无法进行。根据错误ORA-600 2037和ORA-7445 _kcbs_dump_adv_state,初步判断和During Startup (Open Database) Alert Log Shows ORA-600[2037] and ORA-7445[kcbs_dump_adv_state] (Doc ID 551993.1)文章描述相符(而且版本也相符)
尝试recover datafile部分file
E:\>sqlplus / as sysdba SQL*Plus: Release 10.2.0.1.0 - Production on 星期五 5月 12 10:16:00 2017 Copyright (c) 1982, 2005, Oracle. All rights reserved. 连接到: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options SQL> recover datafile 1; 完成介质恢复。 SQL> recover datafile 2; 完成介质恢复。 SQL> recover datafile 3; 完成介质恢复。 SQL> recover datafile 4; 完成介质恢复。 SQL> recover datafile 9; 完成介质恢复。 SQL> alter database open; alter database open * 第 1 行出现错误: ORA-00600: 内部错误代码, 参数: [kcratr1_lastbwr], [], [], [], [], [], [], []
ORA-00600 kcratr1_lastbwr错误比较明显,见ORA-00600:[Kcratr1_lastbwr] During Database Startup after a Crash (Doc ID 393984.1)
通过recover database处理
SQL> recover database; 完成介质恢复。 SQL> alter database open; 数据库已更改。
然后通过查询dba_extents 处理坏块对象
补充ORA-600 2037错误
Format: ORA-600 [2037] [a] [b] 1 [d] [e] [f] [g] VERSIONS: versions 8.0 and above DESCRIPTION: During recovery we are examining a block to ensure that it is not corrupt prior to applying any change vectors. The block has failed this check and this exception is raised. ARGUMENTS: Arg [a] Relative Data Block Address (RDBA) that the redo vector is for Arg [b] The Block format Arg {c} RDBA in the block itself Arg [d] The block type Arg [e] The sequence number Arg [f] Flags, if set Arg [g] The return value from the block head/tail checker.