标签云
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,603)
- DB2 (22)
- MySQL (70)
- Oracle (1,468)
- Data Guard (50)
- EXADATA (7)
- GoldenGate (21)
- ORA-xxxxx (158)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (13)
- ORACLE 21C (3)
- Oracle 23ai (3)
- Oracle ASM (65)
- Oracle Bug (7)
- Oracle RAC (47)
- Oracle 安全 (6)
- Oracle 开发 (27)
- Oracle 监听 (27)
- Oracle备份恢复 (532)
- 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)
-
最近发表
- WINDOWS 下用dg broker搭建ADG(单机to单机)
- 存储故障后oracle报—ORA-01122/ORA-01207故障处理
- Oracle 23ai rm redo*.log恢复
- Oracle 发布计划—包含Oracle 23ai版本
- Oracle 23ai 变化之—-默认数据文件变为bigfile
- 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-600 4193
ORACLE 8.1.7 数据库ORA-600 4000故障恢复
在数据库的恢复过程中遇到ORA-600 4000错误挺多的,但是在oracle 8i(8.1.7)中遇到此类问题,还是第一次,做个记忆,供参考:
数据库故障起因:因为存储异常,导致当前redo损坏,并_allow_resetlogs_corruption参数尝试打开数据库
Media Recovery Log kcrrga: Warning. Log sequence in archive filename wrapped to fix length as indicated by %S in LOG_ARCHIVE_FORMAT. Old log archive with same name might be overwritten. ORA-279 signalled during: ALTER DATABASE RECOVER database using backup cont... Wed Aug 20 23:01:43 2014 ALTER DATABASE RECOVER CANCEL Media Recovery Cancelled Completed: ALTER DATABASE RECOVER CANCEL Wed Aug 20 23:01:50 2014 alter database open resetlogs RESETLOGS is being done without consistancy checks. This may result in a corrupted database. The database should be recreated. RESETLOGS after incomplete recovery UNTIL CHANGE 262618871 Wed Aug 20 23:01:50 2014 Thread 1 opened at log sequence 1 Current log# 3 seq# 1 mem# 0: F:\REDO01.LOG Successful open of redo thread 1. Wed Aug 20 23:01:50 2014 SMON: enabling cache recovery Wed Aug 20 23:01:50 2014 Errors in file C:\oracle\admin\YCFD\udump\ORA00320.TRC: ORA-00600: ??????????: [4000], [3], [], [], [], [], [], [] SMON: disabling cache recovery Wed Aug 20 23:01:51 2014 ORA-704 signalled during: alter database open resetlogs
数据库遭遇ORA-600 4000错误,数据库无法打开,分析对应trace日志
Dump file C:\oracle\admin\YCFD\udump\ORA00320.TRC Wed Aug 20 23:01:50 2014 ORACLE V8.1.7.0.0 - Production vsnsta=0 vsnsql=e vsnxtr=3 Windows 2000 Version 5.2 Service Pack 2, CPU type 586 Oracle8i Release 8.1.7.0.0 - Production JServer Release 8.1.7.0.0 - Production Windows 2000 Version 5.2 Service Pack 2, CPU type 586 Instance name: ycfd Redo thread mounted by this instance: 1 Oracle process number: 8 Windows thread id: 320, image: ORACLE.EXE *** SESSION ID:(7.1) 2014-08-20 23:01:50.838 *** 2014-08-20 23:01:50.838 ksedmp: internal or fatal error ORA-00600: ??????????: [4000], [3], [], [], [], [], [], [] Current SQL statement for this session: select ctime, mtime, stime from obj$ where obj# = :1 ----- Call Stack Trace -----
这里可以看出来,是因为数据库在启动之时需要执行select ctime, mtime, stime from obj$ where obj# = :1语句,但是由于每种原因出现ORA-600 4000导致数据库无法正常启动,继续分析日志
lock header dump: 0x0040003e Object id on Block? Y seg/obj: 0x12 csc: 0x00.fb5c5c5 itc: 1 flg: - typ: 1 - DATA fsl: 0 fnx: 0x0 ver: 0x01 Itl Xid Uba Flag Lck Scn/Fsc 0x01 xid: 0x0003.012.0002ae94 uba: 0x00801f5b.5389.11 --U- 1 fsc 0x0000.0fb5c5c6 SQL> select checkpoint_change# from v$database; 263570122
此处比较明显,通过xid可以知道三号回滚段中对应一个事务出现问题:
1. 该block为file 1 bock 62,object_id为 18(obj$)上有一个事务
2. 该事务的scn为263,570,886>database scn(263570122)导致该故障发生
3. 当数据库访问到file 1 block 62的时候,发现有一个事务,而该事务的scn大于数据库scn,从而出现ORA-600[4000]
解决该问题有几种方法
1. 修改block 62,人工提交该事务
2. 修改数据库scn,让数据库scn大于itl scn
解决block 62 事务问题后出现如下错误
Wed Aug 20 23:03:55 2014 SMON: enabling cache recovery Wed Aug 20 23:03:55 2014 Dictionary check beginning Dictionary check complete Wed Aug 20 23:03:55 2014 SMON: enabling tx recovery Wed Aug 20 23:03:56 2014 Errors in file C:\oracle\admin\YCFD\bdump\ycfdSMON.TRC: ORA-00600: internal error code, arguments: [4193], [21173], [21181], [], [], [], [], [] Recovery of Online Redo Log: Thread 1 Group 1 Seq 2 Reading mem 0 Mem# 0 errs 0: F:\REDO03.LOG SMON: terminating instance due to error 600 Instance terminated by SMON, pid = 2468
数据库出现ORA-600 4193,这个是常见错误,因为redo记录和undo记录不匹配导致,可以直接使用_corrupted_rollback_segments/_offline_rollback_segments屏蔽回滚段跳过
Wed Aug 20 23:08:10 2014 SMON: enabling cache recovery SMON: enabling tx recovery SMON: about to recover undo segment 1 SMON: mark undo segment 1 as needs recovery SMON: about to recover undo segment 2 SMON: mark undo segment 2 as needs recovery SMON: about to recover undo segment 3 SMON: mark undo segment 3 as needs recovery SMON: about to recover undo segment 4 SMON: mark undo segment 4 as needs recovery SMON: about to recover undo segment 5 SMON: mark undo segment 5 as needs recovery SMON: about to recover undo segment 6 SMON: mark undo segment 6 as needs recovery SMON: about to recover undo segment 7 SMON: mark undo segment 7 as needs recovery SMON: about to recover undo segment 1 SMON: mark undo segment 1 as needs recovery SMON: about to recover undo segment 2 SMON: mark undo segment 2 as needs recovery SMON: about to recover undo segment 3 SMON: mark undo segment 3 as needs recovery SMON: about to recover undo segment 4 SMON: mark undo segment 4 as needs recovery SMON: about to recover undo segment 5 SMON: mark undo segment 5 as needs recovery SMON: about to recover undo segment 6 SMON: mark undo segment 6 as needs recovery SMON: about to recover undo segment 7 SMON: mark undo segment 7 as needs recovery Wed Aug 20 23:08:15 2014 Completed: alter database open
其他类似文章:
ORA-600[4194]/[4193]解决
通过bbed解决ORA-600 4000案例
通过bbed解决ORA-00600[4000]案例
记录一次ORA-600 4000数据库故障恢复
记录一次ORA-600 3004 恢复过程和处理思路
10.1.0.2数据库在启动的时候报ORA-00600[3004]错误
SQL> startup ORACLE 例程已经启动。 Total System Global Area 1042254360 bytes Fixed Size 743960 bytes Variable Size 503316480 bytes Database Buffers 536870912 bytes Redo Buffers 1323008 bytes 数据库装载完毕。 ORA-00600: 内部错误代码,参数: [3004], [1], [0], [0], [], [], [], []
alert日志信息
Tue Jul 15 10:57:11 2014 Database mounted in Exclusive Mode. Completed: ALTER DATABASE MOUNT Tue Jul 15 10:57:12 2014 ALTER DATABASE OPEN Tue Jul 15 10:57:12 2014 Beginning crash recovery of 1 threads attempting to start a parallel recovery with 3 processes parallel recovery started with 3 processes Tue Jul 15 10:57:12 2014 Started first pass scan Tue Jul 15 10:57:12 2014 Errors in file d:\oracle\product\10.1.0\admin\orcl\udump\orcl_ora_1084.trc: ORA-00600: 内部错误代码, 参数: [3004], [1], [0], [0], [], [], [], [] Tue Jul 15 10:57:13 2014 Errors in file d:\oracle\product\10.1.0\admin\orcl\bdump\orcl_p000_3780.trc: ORA-10388: parallel query server interrupt (failure) Tue Jul 15 10:57:13 2014 Errors in file d:\oracle\product\10.1.0\admin\orcl\bdump\orcl_p002_3420.trc: ORA-10388: parallel query server interrupt (failure) Tue Jul 15 10:57:14 2014 Errors in file d:\oracle\product\10.1.0\admin\orcl\bdump\orcl_p001_3784.trc: ORA-10388: parallel query server interrupt (failure) Tue Jul 15 10:57:14 2014 Aborting crash recovery due to error 600 Tue Jul 15 10:57:14 2014 Errors in file d:\oracle\product\10.1.0\admin\orcl\udump\orcl_ora_1084.trc: ORA-00600: 内部错误代码, 参数: [3004], [1], [0], [0], [], [], [], [] ORA-600 signalled during: ALTER DATABASE OPEN...
根据老杨的blog,出现该问题,很可能是crontrolfile异常导致,所以这里可以考虑通过重建控制文件或者把当前控制文件当作备份控制文件来使用
Tue Jul 15 13:42:31 2014 ALTER DATABASE RECOVER database using backup controlfile Tue Jul 15 13:42:31 2014 Media Recovery Start WARNING! Recovering data file 1 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 2 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 3 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 4 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 5 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 6 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 7 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 8 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 9 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 10 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 11 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. attempting to start a parallel recovery with 3 processes parallel recovery started with 3 processes Starting datafile 1 with incarnation depth 0 in thread 1 sequence 794 Datafile 1: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSTEM01.DBF' Starting datafile 2 with incarnation depth 0 in thread 1 sequence 794 Datafile 2: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\UNDOTBS01.DBF' Starting datafile 3 with incarnation depth 0 in thread 1 sequence 794 Datafile 3: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSAUX01.DBF' Starting datafile 4 with incarnation depth 0 in thread 1 sequence 794 Datafile 4: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\USERS01.DBF' Starting datafile 5 with incarnation depth 0 in thread 1 sequence 794 Datafile 5: 'E:\ORADB\USER1_1.ORA' Starting datafile 6 with incarnation depth 0 in thread 1 sequence 794 Datafile 6: 'E:\ORADB\USER1_2.ORA' Starting datafile 7 with incarnation depth 0 in thread 1 sequence 794 Datafile 7: 'E:\ORADB\USER1_3.ORA' Starting datafile 8 with incarnation depth 0 in thread 1 sequence 794 Datafile 8: 'E:\ORADB\USER1_4.ORA' Starting datafile 9 with incarnation depth 0 in thread 1 sequence 794 Datafile 9: 'E:\ORADB\INDEX1_1.ORA' Starting datafile 10 with incarnation depth 0 in thread 1 sequence 794 Datafile 10: 'E:\ORADB\INDEX1_2.ORA' Starting datafile 11 with incarnation depth 0 in thread 1 sequence 794 Datafile 11: 'E:\ORADB\TEMP1_1.ORA' Media Recovery Log ORA-279 signalled during: ALTER DATABASE RECOVER database using backup cont... Tue Jul 15 13:43:03 2014 ALTER DATABASE RECOVER LOGFILE 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\REDO01.LOG' Tue Jul 15 13:43:03 2014 Media Recovery Log D:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\REDO01.LOG Completed: ALTER DATABASE RECOVER LOGFILE 'D:\ORACLE\PRODU Tue Jul 15 13:43:17 2014 alter database open resetlogs RESETLOGS after complete recovery through change 3142208 Resetting resetlogs activation ID 1378452168 (0x522982c8) Setting recovery target incarnation to 3 Tue Jul 15 13:43:18 2014 Setting recovery target incarnation to 3 Tue Jul 15 13:43:18 2014 Flashback Database Disabled Tue Jul 15 13:43:19 2014 Assigning activation ID 1380750902 (0x524c9636) Maximum redo generation record size = 120832 bytes Maximum redo generation change vector size = 116476 bytes Private_strands 7 at log switch Thread 1 opened at log sequence 1 Current log# 1 seq# 1 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\REDO01.LOG Successful open of redo thread 1 Tue Jul 15 13:43:19 2014 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Tue Jul 15 13:43:19 2014 SMON: enabling cache recovery Tue Jul 15 13:43:20 2014 Errors in file d:\oracle\product\10.1.0\admin\orcl\udump\orcl_ora_1484.trc: ORA-00600: 内部错误代码, 参数: [2662], [0], [3142214], [0], [3142438], [8388617], [], [] Tue Jul 15 13:43:21 2014 Errors in file d:\oracle\product\10.1.0\admin\orcl\udump\orcl_ora_1484.trc: ORA-00600: 内部错误代码, 参数: [2662], [0], [3142214], [0], [3142438], [8388617], [], [] Tue Jul 15 13:43:21 2014 Error 600 happened during db open, shutting down database USER: terminating instance due to error 600
这里出现ORA-600[2662]因为scn相差较小,直接重启几次,然后数据库出现如下启动正常但是出现ORA-01595和ORA-00600[4194]错误
Tue Jul 15 13:48:26 2014 Starting background process MMON Starting background process MMNL MMON started with pid=17, OS id=2896 MMNL started with pid=18, OS id=3828 Tue Jul 15 13:48:26 2014 Block recovery completed at rba 2.90.16, scn 0.3162303 Tue Jul 15 13:48:26 2014 Errors in file d:\oracle\product\10.1.0\admin\orcl\bdump\orcl_smon_3724.trc: ORA-01595: error freeing extent (3) of rollback segment (1)) ORA-00607: Internal error occurred while making a change to a data block ORA-00600: internal error code, arguments: [4194], [57], [6], [], [], [], [], [] Tue Jul 15 13:48:26 2014 Completed: alter database open Tue Jul 15 13:48:27 2014 Errors in file d:\oracle\product\10.1.0\admin\orcl\bdump\orcl_j000_2956.trc: ORA-00600: internal error code, arguments: [4193], [1375], [1379], [], [], [], [], []
通过设置undo_management=manual,重建undo表空间解决,至此本数据库恢复完成,建议对其进行逻辑方式重建
记录一次ORA-00600[kdxlin:psno out of range]/ORA-00600[3020]/ORA-00600[4000]/ORA-00600[4193]的数据库恢复
尝试recover database,遭遇ORA-00600[kdxlin:psno out of range]/ORA-00600[3020]/ORA-00354错误
Media Recovery Log Recovery of Online Redo Log: Thread 1 Group 1 Seq 5645 Reading mem 0 Mem# 0 errs 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\GTGS\REDO01.LOG Mon Jun 09 15:36:10 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_p001_9604.trc: ORA-00600: internal error code, arguments: [kdxlin:psno out of range], [], [], [], [], [], [], [] Mon Jun 09 15:36:12 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_p002_9592.trc: ORA-00600: internal error code, arguments: [3020], [3], [23337], [12606249], [], [], [], [] ORA-10567: Redo is inconsistent with data block (file# 3, block# 23337) ORA-10564: tablespace SYSAUX ORA-01110: data file 3: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\GTGS\SYSAUX01.DBF' ORA-10560: block type 'FIRST LEVEL BITMAP BLOCK' Mon Jun 09 15:36:12 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_p001_9604.trc: ORA-10562: Error occurred while applying redo to data block (file# 3, block# 20142) ORA-10564: tablespace SYSAUX ORA-01110: data file 3: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\GTGS\SYSAUX01.DBF' ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 47841 ORA-00600: internal error code, arguments: [kdxlin:psno out of range], [], [], [], [], [], [], [] Mon Jun 09 15:36:13 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_p002_9592.trc: ORA-00600: internal error code, arguments: [3020], [3], [23337], [12606249], [], [], [], [] ORA-10567: Redo is inconsistent with data block (file# 3, block# 23337) ORA-10564: tablespace SYSAUX ORA-01110: data file 3: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\GTGS\SYSAUX01.DBF' ORA-10560: block type 'FIRST LEVEL BITMAP BLOCK' Errors with log Mon Jun 09 15:36:14 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_p000_9600.trc: ORA-00354: corrupt redo log block header ORA-00353: log corruption near block 2357 change 25400286 time 06/06/2014 04:00:41 ORA-00334: archived log: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\GTGS\REDO02.LOG' Mon Jun 09 15:36:14 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_p000_9600.trc: ORA-00600: internal error code, arguments: [kddummy_blkchk], [1], [1490], [6401], [], [], [], [] Mon Jun 09 15:36:16 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_p000_9600.trc: ORA-10562: Error occurred while applying redo to data block (file# 1, block# 1490) ORA-10564: tablespace SYSTEM ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\GTGS\SYSTEM01.DBF' ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 203 ORA-00600: internal error code, arguments: [kddummy_blkchk], [1], [1490], [6401], [], [], [], [] Media Recovery failed with error 12801 ORA-283 signalled during: ALTER DATABASE RECOVER database ...
因为数据库允许少量丢失数据,且redo文件发生损坏,直接使用隐含参数屏蔽redo前滚,尝试强制拉库,报ORA-00704,ORA-00600[4000]错误
Mon Jun 09 15:57:51 2014 SMON: enabling cache recovery Mon Jun 09 15:57:51 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\udump\gtgs_ora_8664.trc: ORA-00600: 内部错误代码, 参数: [4000], [1], [], [], [], [], [], [] Mon Jun 09 15:57:52 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\udump\gtgs_ora_8664.trc: ORA-00704: 引导程序进程失败 ORA-00704: 引导程序进程失败 ORA-00600: 内部错误代码, 参数: [4000], [1], [], [], [], [], [], [] Mon Jun 09 15:57:52 2014 Error 704 happened during db open, shutting down database USER: terminating instance due to error 704 Mon Jun 09 15:57:52 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_pmon_9760.trc: ORA-00704: bootstrap process failure Mon Jun 09 15:57:52 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_reco_5244.trc: ORA-00704: bootstrap process failure Mon Jun 09 15:57:52 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_smon_7096.trc: ORA-00704: bootstrap process failure Mon Jun 09 15:57:53 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_ckpt_7924.trc: ORA-00704: bootstrap process failure Mon Jun 09 15:57:53 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_lgwr_708.trc: ORA-00704: bootstrap process failure Mon Jun 09 15:57:53 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_dbw0_7400.trc: ORA-00704: bootstrap process failure Mon Jun 09 15:57:53 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_mman_9836.trc: ORA-00704: bootstrap process failure Instance terminated by USER, pid = 8664 ORA-1092 signalled during: alter database open resetlogs...
对数据库启动过程做10046,然后使用bbed修改scn绕过该错误,然后继续尝试打开数据库,报ORA-00604/ORA-00607/ORA-00600[4193]错误
Mon Jun 09 16:01:09 2014 SMON: enabling cache recovery Mon Jun 09 16:01:10 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\udump\gtgs_ora_7548.trc: ORA-00600: 内部错误代码, 参数: [4193], [57], [51], [], [], [], [], [] Mon Jun 09 16:01:10 2014 Doing block recovery for file 1 block 397 Block recovery range from rba 2.3.0 to scn 0.1073741830 Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0 Mem# 0 errs 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\GTGS\REDO02.LOG Block recovery stopped at EOT rba 2.5.16 Block recovery completed at rba 2.5.16, scn 0.1073741830 Doing block recovery for file 1 block 9 Block recovery range from rba 2.3.0 to scn 0.1073741829 Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0 Mem# 0 errs 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\GTGS\REDO02.LOG Block recovery completed at rba 2.5.16, scn 0.1073741830 Mon Jun 09 16:01:11 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\udump\gtgs_ora_7548.trc: ORA-00604: 递归 SQL 级别 1 出现错误 ORA-00607: 当更改数据块时出现内部错误 ORA-00600: 内部错误代码, 参数: [4193], [57], [51], [], [], [], [], [] Error 604 happened during db open, shutting down database USER: terminating instance due to error 604 Mon Jun 09 16:01:11 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_reco_9176.trc: ORA-00604: error occurred at recursive SQL level Mon Jun 09 16:01:11 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_smon_7932.trc: ORA-00604: error occurred at recursive SQL level Mon Jun 09 16:01:12 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_ckpt_7428.trc: ORA-00604: error occurred at recursive SQL level Mon Jun 09 16:01:12 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_lgwr_6936.trc: ORA-00604: error occurred at recursive SQL level Mon Jun 09 16:01:12 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_dbw0_404.trc: ORA-00604: error occurred at recursive SQL level Mon Jun 09 16:01:12 2014 Errors in file d:\oracle\product\10.1.0\admin\gtgs\bdump\gtgs_mman_7968.trc: ORA-00604: error occurred at recursive SQL level Instance terminated by USER, pid = 7548 ORA-1092 signalled during: ALTER DATABASE OPEN...
该错误的原因是因为数据库在启动的过程中,会事先利用上次数据库运行过程中system undo segment header指向的block,而该block异常,所以出现该错误,使用bbed/dul之类的工具清除掉undo seg header 指向block指针,然后数据库启动会重新分配一个block,从而实现数据库正常启动.