标签云
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,683)
- DB2 (22)
- MySQL (73)
- Oracle (1,545)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (159)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (7)
- Oracle ASM (68)
- Oracle Bug (8)
- Oracle RAC (53)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (565)
- Oracle安装升级 (92)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (79)
- 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-15411: Failure groups in disk group DATA have different number of disks.
- 断电引起的ORA-08102: 未找到索引关键字, 对象号 39故障处理
- ORA-00227: corrupt block detected in control file
- 手工删除19c rac
- 解决oracle数据文件路径有回车故障
- .wstop扩展名勒索数据库恢复
- Oracle Recovery Tools工具一键解决ORA-00376 ORA-01110故障(文件offline)
- OGG-02771 Input trail file format RELEASE 19.1 is different from previous trail file form at RELEASE 11.2.
- OGG-02246 Source redo compatibility level 19.0.0 requires trail FORMAT 12.2 or higher
- GoldenGate 19安装和打patch
- dd破坏asm磁盘头恢复
- 删除asmlib磁盘导致磁盘组故障恢复
- Kylin Linux 安装19c
- 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-01595
记录一次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表空间解决,至此本数据库恢复完成,建议对其进行逻辑方式重建
undo异常总结和恢复思路
UNDO异常报错千奇百怪,针对本人遇到的比较常见的undo异常报错进行汇总,仅供参考,数据库恢复过程是千奇百怪的,不能照搬硬套.
ORA-00704/ORA-00376
ORA-00704: bootstrap process failure
ORA-00604: error occurred at recursive SQL level 2
ORA-00376: file 3 cannot be read at this time
ORA-01110: data file 3: ‘/u01/oracle/oradata/ora11g/undotbs01.dbf’
Error 704 happened during db open, shutting down database
USER (ospid: 17864): terminating the instance due to error 704
Instance terminated by USER, pid = 17864
ORA-1092 signalled during: alter database open…
opiodr aborting process unknown ospid (17864) as a result of ORA-1092
ORA-00600[4097]
Fri Aug 31 23:14:10 2012
Errors in file /u01/oradata/orcl/bdump/orcl_smon_15589.trc:
ORA-00600: internal error code, arguments: [4097], [], [], [], [], [], [], []
Fri Aug 31 23:14:12 2012
Non-fatal internal error happenned while SMON was doing logging scn->time mapping.
SMON encountered 1 out of maximum 100 non-fatal internal errors.
ORA-01595/ORA-00600[4194]
Fri Aug 31 23:14:14 2012
Errors in file /u01/oradata/orcl/bdump/orcl_smon_15589.trc:
ORA-01595: error freeing extent (2) of rollback segment (4))
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4194], [48], [34], [], [], [], [], []
0RA-00600[4193]
Tue Feb 14 09:35:34 2012
Errors in file d:\oracle\product\10.2.0\admin\interlib\udump\interlib_ora_2824.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [4193], [2005], [2008], [], [], [], [], []
ORA-00600[kcfrbd_3]
Wed Dec 05 10:26:35 2012
SMON: enabling tx recovery
Wed Dec 05 10:26:35 2012
Database Characterset is ZHS16GBK
Wed Dec 05 10:26:35 2012
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_548.trc:
ORA-00600: internal error code, arguments: [kcfrbd_3], [2], [2279045], [1], [2277120], [2277120], [], []
SMON: terminating instance due to error 474
ORA-00600[4137]
Fri Jul 6 18:00:40 2012
SMON: ignoring slave err,downgrading to serial rollback
Fri Jul 6 18:00:41 2012
Errors in file /usr/local/oracle/admin/techdb/bdump/techdb_smon_16636.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
ORACLE Instance techdb (pid = 8) – Error 600 encountered while recovering transaction (3, 17).
ORA-01595/ORA-01594
Sat May 12 21:54:17 2012
Errors in file /oracle/app/admin/prmdb/bdump/prmdb2_smon_483522.trc:
ORA-01595: error freeing extent (2) of rollback segment (19))
ORA-01594: attempt to wrap into rollback segment (19) extent (2) which is being freed
ORA-00704/ORA-01555
Fri May 4 21:04:21 2012
select ctime, mtime, stime from obj$ where obj# = :1
Fri May 4 21:04:21 2012
Errors in file /oracle/admin/standdb/udump/perfdb_ora_1286288.trc:
ORA-00704: bootstrap process failure
ORA-00704: bootstrap process failure
ORA-00604: error occurred at recursive SQL level 1
ORA-01555: snapshot too old: rollback segment number 40 with name “_SYSSMU40$” too small
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 1286288
ORA-1092 signalled during: alter database open resetlogs…
ORA-00607/ORA-00600[4194]
Block recovery completed at rba 3994.5.16, scn 0.89979533
Thu Jul 26 13:21:11 2012
Errors in file /orasvr/admin/mispdata/udump/mispdata_ora_2865.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4194], [31], [2], [], [], [], [], []
Error 604 happened during db open, shutting down database
USER: terminating instance due to error 604
Instance terminated by USER, pid = 2865
ORA-1092 signalled during: ALTER DATABASE OPEN…
ORA-00704/ORA-00600[4000]
Thu Feb 28 19:29:13 2013
Errors in file /u1/PROD/prodora/db/tech_st/10.2.0/admin/PROD_oracle/udump/prod_ora_20989.trc:
ORA-00704: bootstrap process failure
ORA-00704: bootstrap process failure
ORA-00600: internal error code, arguments: [4000], [50], [], [], [], [], [], []
Thu Feb 28 19:29:13 2013
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 20989
ORA-1092 signalled during: ALTER DATABASE OPEN RESETLOGS…
undo异常恢复处理思路
除了极少数undo坏块,undo文件丢失外,大部分undo异常是因为redo未被正常进行前滚,从而导致undo回滚异常数据库无法open,解决此类问题,需要结合一般需要结合redo异常处理技巧在其中,一般undo异常处理思路
1.切换undo_management= MANUAL尝试启动数据库,如果不成功进入2
2.设置10513 等event尝试启动数据库,如果不成功进入3
3.使用_offline_rollback_segments/_corrupted_rollback_segments屏蔽回滚段
4.如果依然不能open数据库,考虑使用bbed工具提交事务,修改回滚段状态等操作
5.如果依然还不能open数据库,考虑使用dul
如果您按照上述步骤还不能解决,请联系我们,将为您提供专业数据库技术支持
Phone:17813235971 Q Q:107644445 E-Mail:dba@xifenfei.com
姊妹篇
ORACLE REDO各种异常恢复
ORACLE丢失各种文件导致数据库不能OPEN恢复
发表在 Oracle备份恢复
标签为 ORA-00376, ORA-00704, ORA-01595, ORA-600 4000, ORA-600 4097, ORA-600 4193, ORA-600 4194, ORA-6004137, oracle异常恢复, ORACLE恢复, undo异常
评论关闭