标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-00742 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,697)
- DB2 (22)
- MySQL (74)
- Oracle (1,558)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (159)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (68)
- Oracle Bug (8)
- Oracle RAC (53)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (571)
- Oracle安装升级 (93)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (81)
- 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 ktuPopDictI_1恢复
- impdp导入数据丢失sys授权问题分析
- impdp 创建index提示ORA-00942: table or view does not exist
- 数据泵导出 (expdp) 和导入 (impdp)工具性能降低分析参考
- 19c非归档数据库断电导致ORA-00742故障恢复
- Oracle 19c – 手动升级到 Non-CDB Oracle Database 19c 的完整核对清单
- sqlite数据库简单操作
- Oracle 暂定和恢复功能
- .pzpq扩展名勒索恢复
- Oracle read only用户—23ai新特性:只读用户
- 迁移awr快照数据到自定义表空间
- .hmallox加密mariadb/mysql数据库恢复
- 2025年首个故障恢复—ORA-600 kcbzib_kcrsds_1
- 第一例Oracle 21c恢复咨询
- 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扩展名勒索数据库恢复
标签归档:ORA-600 4194
ORA-00600 [2662]和ORA-00600 [4194]恢复
Sat Dec 26 19:34:05 2020 alter database open Beginning crash recovery of 1 threads parallel recovery started with 7 processes Started redo scan Completed redo scan read 0 KB redo, 0 data blocks need recovery Started redo application at Thread 1: logseq 24, block 2, scn 2621149392 Recovery of Online Redo Log: Thread 1 Group 3 Seq 24 Reading mem 0 Mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO03.LOG Completed redo application of 0.00MB Completed crash recovery at Thread 1: logseq 24, block 3, scn 2621169394 0 data blocks read, 0 data blocks written, 0 redo k-bytes read Sat Dec 26 19:34:06 2020 Thread 1 advanced to log sequence 25 (thread open) Thread 1 opened at log sequence 25 Current log# 1 seq# 25 mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO01.LOG Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Sat Dec 26 19:34:06 2020 SMON: enabling cache recovery Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_ora_5812.trc (incident=110636): ORA-00600: 内部错误代码, 参数: [2662], [0], [2621169401], [0], [2621591939], [4194545], [], [], [], [], [], [] Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_ora_5812.trc: ORA-00704: 引导程序进程失败 ORA-00704: 引导程序进程失败 ORA-00600: 内部错误代码, 参数: [2662], [0], [2621169401], [0], [2621591939], [4194545], [], [], [], [], [], [] Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_ora_5812.trc: ORA-00704: 引导程序进程失败 ORA-00704: 引导程序进程失败 ORA-00600: 内部错误代码, 参数: [2662], [0], [2621169401], [0], [2621591939], [4194545], [], [], [], [], [], [] Error 704 happened during db open, shutting down database USER (ospid: 5812): terminating the instance due to error 704 Instance terminated by USER, pid = 5812 ORA-1092 signalled during: alter database open... opiodr aborting process unknown ospid (5812) as a result of ORA-1092 Sat Dec 26 19:34:10 2020 ORA-1092 : opitsk aborting process
对应的trace文件内容,主要在查询undo$表触发ORA-600 2662错误
通过修改scn,解决ORA-600 2662错误之后,数据库启动报ORA-600 4194
Sat Dec 26 20:13:28 2020 SMON: enabling tx recovery Database Characterset is ZHS16GBK Trace dumping is performing id=[cdmp_20201226201328] No Resource Manager plan active Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_smon_8104.trc (incident=114188): ORA-00600: internal error code, arguments: [4194], [], [ Incident details in: e:\oracle\app\administrator\diag\rdbms\xff\xff\incident\incdir_114188\xff_smon_8104_i114188.trc Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x470E9BAC] [PC:0x6F21343, ___dyn_tls_init_callback()+111576860] Sat Dec 26 20:13:29 2020 Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\cdump\xffcore.log ORA-07445: caught exception [ACCESS_VIOLATION] at [___dyn_tls_init_callback()+111576860] [0x06F21343] Doing block recovery for file 3 block 3121 Resuming block recovery (PMON) for file 3 block 3121 Block recovery from logseq 12, block 73 to scn 3221225727 Recovery of Online Redo Log: Thread 1 Group 3 Seq 12 Reading mem 0 Mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO03.LOG Block recovery stopped at EOT rba 12.75.16 Block recovery completed at rba 12.75.16, scn 0.3221225724 Doing block recovery for file 3 block 176 Resuming block recovery (PMON) for file 3 block 176 Block recovery from logseq 12, block 73 to scn 3221225721 Recovery of Online Redo Log: Thread 1 Group 3 Seq 12 Reading mem 0 Mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO03.LOG Block recovery completed at rba 12.73.16, scn 0.3221225722 Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_smon_8104.trc: ORA-01595: error freeing extent (3) of rollback segment (4)) ORA-00600: internal error code, arguments: [4194], [], [ Trace dumping is performing id=[cdmp_20201226201331] Sat Dec 26 20:13:31 2020 PMON (ospid: 5200): terminating the instance due to error 397 Instance terminated by PMON, pid = 5200
解决异常undo,数据库启动正常,导出数据
oracle 8.1.6因断电无法启动恢复
接到一个oralce 8.1.6的数据库恢复请求,由于断电之后,系统无法正常恢复,通过尝试recover datafile报错如下
SQL> select * from v$version; BANNER ---------------------------------------------------------------- Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production PL/SQL Release 8.1.6.0.0 - Production CORE 8.1.6.0.0 Production TNS for 32-bit Windows: Version 8.1.6.0.0 - Production NLSRTL Version 3.4.1.0.0 - Production
Tue Oct 16 14:17:01 2018 Media Recovery Datafile: 1 Media Recovery Start Media Recovery Log Recovery of Online Redo Log: Thread 1 Group 1 Seq 146597 Reading mem 0 Mem# 0 errs 0: D:\ORACLE\ORADATA\ORCL\REDO01.LOG Tue Oct 16 14:17:02 2018 Errors in file D:\Oracle\admin\orcl\udump\ORA03040.TRC: ORA-00600: internal error code, arguments: [kcoapl_blkchk], [1], [30547], [6101], [], [], [], [] Tue Oct 16 14:17:03 2018 Errors in file D:\Oracle\admin\orcl\udump\ORA03040.TRC: ORA-01578: ORACLE data block corrupted (file # 1, block # 30547) ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF' ORA-00607: Internal error occurred while making a change to a data block ORA-00600: internal error code, arguments: [kcoapl_blkchk], [1], [30547], [6101], [], [], [], [] Tue Oct 16 14:17:03 2018 Errors in file D:\Oracle\admin\orcl\udump\ORA03040.TRC: ORA-00314: log 2 of thread 1, expected sequence# 146598 doesn't match 146415 ORA-00312: online log 2 thread 1: 'D:\ORACLE\ORADATA\ORCL\REDO02.LOG'
这里可以获取到两个信息:1)system文件可能有坏块,导致数据库recover的时候报ORA-600 kcoapl_blkchk错误,2)数据库的redo可能异常了,由于8i数据库默认redo 10m,在业务繁忙时候切换较为频繁,而文件系统的cache导致redo信息比较老,而数据文件需要redo比较新,从而无法正常恢复成功。比较明显对于当前这样的情况只能是屏蔽数据一致性,强制拉库
ARC0: media recovery disabled Tue Oct 16 14:17:39 2018 SMON: enabling cache recovery Tue Oct 16 14:17:39 2018 Errors in file D:\Oracle\admin\orcl\udump\ORA02256.TRC: ORA-00600: internal error code, arguments: [2662], [1], [1712082681], [1], [1712107587], [8388610], [], [] Tue Oct 16 14:17:41 2018 Errors in file D:\Oracle\admin\orcl\udump\ORA02256.TRC: ORA-00600: internal error code, arguments: [2662], [1], [1712082682], [1], [1712107587], [8388610], [], [] ORA-00600: internal error code, arguments: [2662], [1], [1712082681], [1], [1712107587], [8388610], [], [] Tue Oct 16 14:17:43 2018 Errors in file D:\Oracle\admin\orcl\udump\ORA02256.TRC: ORA-00600: internal error code, arguments: [2662], [1], [1712082682], [1], [1712107587], [8388610], [], [] ORA-00600: internal error code, arguments: [2662], [1], [1712082681], [1], [1712107587], [8388610], [], [] Tue Oct 16 14:17:45 2018 Errors in file D:\Oracle\admin\orcl\udump\ORA02256.TRC: ORA-00603: ORACLE server session terminated by fatal error ORA-00600: internal error code, arguments: [2662], [1], [1712082682], [1], [1712107587], [8388610], [], [] ORA-00600: internal error code, arguments: [2662], [1], [1712082681], [1], [1712107587], [8388610], [], []
ORA-600 2662这个错误比较常见,直接推数据库scn,启动库
Tue Oct 16 16:09:11 2018 Errors in file D:\Oracle\admin\orcl\bdump\orclSMON.TRC: ORA-00600: internal error code, arguments: [4193], [29469], [29477], [], [], [], [], [] Recovery of Online Redo Log: Thread 1 Group 3 Seq 1 Reading mem 0 Mem# 0 errs 0: D:\ORACLE\ORADATA\ORCL\REDO03.LOG Tue Oct 16 16:09:12 2018 Errors in file D:\Oracle\admin\orcl\bdump\orclSMON.TRC: ORA-01595: error freeing extent (3) of rollback segment (2)) ORA-00600: internal error code, arguments: [4193], [29469], [29477], [], [], [], [], [] Tue Oct 16 16:09:13 2018 Completed: ALTER DATABASE OPEN Tue Oct 16 16:12:06 2018 CREATE ROLLBACK SEGMENT nrbs1 TABLESPACE rbs Tue Oct 16 16:12:06 2018 Errors in file D:\Oracle\admin\orcl\udump\ORA02252.TRC: ORA-00600: internal error code, arguments: [4194], [79], [38], [], [], [], [], []
错误比较明显ORA-600 4194,而且已经告知是由于rollback segment 2异常,通过屏蔽回滚段,open数据库,删除老回滚段,创建新回滚段(8i无undo自动管理)
SQL> startup ORACLE instance started. Total System Global Area 1549432076 bytes Fixed Size 70924 bytes Variable Size 500707328 bytes Database Buffers 1048576000 bytes Redo Buffers 77824 bytes Database mounted. Database opened. SQL> drop rollback segment "RBS1"; Rollback segment dropped. SQL> drop rollback segment "RBS2"; Rollback segment dropped. SQL> drop rollback segment "RBS3"; Rollback segment dropped. SQL> drop rollback segment "RBS4"; Rollback segment dropped. SQL> drop rollback segment "RBS5"; Rollback segment dropped. SQL> drop rollback segment "RBS6"; Rollback segment dropped. SQL> CREATE ROLLBACK SEGMENT nrbs1 TABLESPACE rbs; Rollback segment created. SQL> CREATE ROLLBACK SEGMENT nrbs2 TABLESPACE rbs; Rollback segment created. SQL> CREATE ROLLBACK SEGMENT nrbs3 TABLESPACE rbs; Rollback segment created. SQL> CREATE ROLLBACK SEGMENT nrbs4 TABLESPACE rbs; Rollback segment created. SQL> CREATE ROLLBACK SEGMENT nrbs5 TABLESPACE rbs; Rollback segment created. SQL> CREATE ROLLBACK SEGMENT nrbs6 TABLESPACE rbs; Rollback segment created. SQL> CREATE ROLLBACK SEGMENT nrbs7 TABLESPACE rbs; Rollback segment created.
客户安排导出导入,至此该库恢复完成
ORA-604 ORA-607 ORA-600
有客户数据库经过一系列恢复之后,出现ORA-604 ORA-607 ORA-600的错误,尝试各种方法无法打开,希望我们介入处理
Sat May 12 21:18:56 2018 SMON: enabling cache recovery Sat May 12 21:18:57 2018 Errors in file d:\oracle\admin\xifenfei\udump\xifenfei_ora_3448.trc: ORA-00600: 内部错误代码,参数: [4194], [34], [28], [], [], [], [], [] Sat May 12 21:19:00 2018 Recovery of Online Redo Log: Thread 1 Group 1 Seq 644 Reading mem 0 Mem# 0 errs 0: D:\ORACLE\ORADATA\xifenfei\REDO01.LOG Recovery of Online Redo Log: Thread 1 Group 1 Seq 644 Reading mem 0 Mem# 0 errs 0: D:\ORACLE\ORADATA\xifenfei\REDO01.LOG Sat May 12 21:19:01 2018 Errors in file d:\oracle\admin\xifenfei\udump\xifenfei_ora_3448.trc: ORA-00604: 递归 SQL 层 1 出现错误 ORA-00607: 当更改数据块时出现内部错误 ORA-00600: 内部错误代码,参数: [4194], [34], [28], [], [], [], [], [] Error 604 happened during db open, shutting down database USER: terminating instance due to error 604 Sat May 12 21:19:02 2018 Errors in file d:\oracle\admin\xifenfei\bdump\xifenfei_pmon_1840.trc: ORA-00604: error occurred at recursive SQL level Instance terminated by USER, pid = 3448 ORA-1092 signalled during: alter database open...
ORA-600 4194 trace文件
分析trace文件,确定ORA-600 4194对应的sql语句为update undo$ set name=:2……
*** 2018-05-12 21:18:57.000 ksedmp: internal or fatal error ORA-00600: 内部错误代码,参数: [4194], [34], [28], [], [], [], [], [] Current SQL statement for this session: update undo$ set name=:2,file#=:3,block#=:4,status$=:5,user#=:6,undosqn=:7, xactsqn=:8,scnbas=:9,scnwrp=:10,inst#=:11,ts#=:12,spare1=:13 where us#=:1 ----- Call Stack Trace ----- calling call entry argument values in hex location type point (? means dubious value) -------------------- -------- -------------------- ---------------------------- _ksedmp+147 CALLrel _ksedst+0 _ksfdmp.108+e CALLrel _ksedmp+0 3 _kgeriv+89 CALLreg 00000000 212778 3 _kseipre.107+3f CALLrel _kgeriv+0 _ksesic2+24 CALLrel _kseipre.107+0 __VInfreq__kturdb+8 CALLrel _ksesic2+0 1062 0 22 0 1C b _kcoapl+1df CALLreg 00000000 30A0F94 30A100A 11 6BB7E014 _kcbapl+71 CALLrel _kcoapl+0 30A0F90 6BB7E000 1 0 2000 _kcrfwr+734 CALLrel _kcbapl+0 30A0F90 6BBFC844 3014F9C _kcbchg1+7ec CALLrel _kcrfwr+0 _ktuchg+630 CALLrel _kcbchg1+0 0 4 3015224 301523C 0 0 _ktbchg2+75 CALLrel _ktuchg+0 2 672D50F4 1 310DCD8 310DCE0 30A0F90 310D2F0 30A0ED0 0 0 _kddchg+18f CALLrel _ktbchg2+0 0 672D50F4 310DCD8 310DCE0 30A0F90 310D2E8 30A0ED0 0 0 _kduovw.53+6e3 CALLrel _kddchg+0 310D2AC 310DCD8 310DCE0 30A0F90 30A0ED0 0 0 _kduurp.53+61a CALLrel _kduovw.53+0 310D2AC _kdusru+aa5 CALLrel _kduurp.53+0 310D2AC 672D514C _kauupd+12e CALLrel _kdusru+0 310D6E0 672D514C 310D2AC 0 _updrow+729 CALLrel _kauupd+0 310D6DC 672D514C 310D2AC 0 672D539C E F 672E4E48 12 301BBA0 301BBA4 _qerupFetch+107 CALLrel _updrow+0 _updaul+202 CALL??? 00000000 672DE9C4 0 672EC040 7FFF _updThreePhaseExe+b CALLrel _updaul+0 672EBDD4 301BD30 0 6 _updexe+105 CALLrel _updThreePhaseExe+0 672EBDD4 0 310D2AC 301BE0C 672EBDD4 1 301BE0C 0 _opiexe+f97 CALLrel _updexe+0 672EBDD4 301BF48 _opiodr+4cd CALLreg 00000000 4 3 301C894 _rpidrus.43+99 CALLrel _opiodr+0 4 3 301C894 B _skgmstack+71 CALLreg 00000000 301C484 _rpidru+6d CALLrel _skgmstack+0 301C49C 212600 F618 778198 301C484 _rpiswu2+17e CALLreg 00000000 301C7BC _rpidrv+109 CALLrel _rpiswu2+0 _rpiexe+33 CALLrel _rpidrv+0 B 4 301C894 8 _ktuscu+2a8 CALLrel _rpiexe+0 B _kqrcmt+2c2 CALL??? 00000000 672EA898 3 ..1.18_2.filter.95+ CALLrel _kqrcmt+0 67B9C5F4 1 0 212778 212778 FF 159 0 0 0 ..1.23_5.filter.99+ CALLrel _ktcrcm+0 67B9C5F4 0 0 0 0 1 0 0 14d _ktuini+64 CALLrel _ktuiup.99+0 301D990 _adbdrv+2665 CALLrel _ktuini+0 301D990 ..1.5_1.filter.29+2 CALLrel _adbdrv+0 9d _opiosq0+9a4 CALLrel _opiexe+0 4 0 301DDD8 _kpooprx+c6 CALLrel _opiosq0+0 3 E 301DE70 24 _kpoal8+225 CALLrel _kpooprx+0 301E738 301E680 13 1 0 24 _opiodr+4cd CALLreg 00000000 5E 14 301E734 _ttcpip+a86 CALLreg 00000000 5E 14 301E734 0 _opitsk+2f4 CALLrel _ttcpip+0 _opiino+5fc CALLrel _opitsk+0 0 0 2188C8 30CF020 E6 0 _opiodr+4cd CALLreg 00000000 3C 4 301FBD4 _opidrv+233 CALLrel _opiodr+0 3C 4 301FBD4 0 _sou2o+19 CALLrel _opidrv+0 _opimai+10a CALLrel _sou2o+0 _OracleThreadStart@ CALLrel _opimai+0 4+35c 7C80B726 CALLreg 00000000 --------------------- Binary Stack Dump ---------------------
进一步分析确定为system rollback segment header 异常
Block image after block recovery: buffer tsn: 0 rdba: 0x00400009 (1/9) scn: 0x0000.d794070f seq: 0x01 flg: 0x04 tail: 0x070f0e01 frmt: 0x02 chkval: 0x2320 type: 0x0e=KTU UNDO HEADER W/UNLIMITED EXTENTS Extent Control Header ----------------------------------------------------------------- Extent Header:: spare1: 0 spare2: 0 #extents: 6 #blocks: 47 last map 0x00000000 #maps: 0 offset: 4128 Highwater:: 0x00400183 ext#: 2 blk#: 2 ext size: 8 #blocks in seg. hdr's freelists: 0 #blocks below: 0 mapblk 0x00000000 offset: 2 Unlocked Map Header:: next 0x00000000 #extents: 6 obj#: 0 flag: 0x40000000 Extent Map ----------------------------------------------------------------- 0x0040000a length: 7 0x00400011 length: 8 0x00400181 length: 8 0x00400189 length: 8 0x00400191 length: 8 0x00400199 length: 8 TRN CTL:: seq: 0x0056 chd: 0x0054 ctl: 0x0052 inc: 0x00000000 nfb: 0x0001 mgc: 0x8002 xts: 0x0068 flg: 0x0001 opt: 2147483646 (0x7ffffffe) uba: 0x00400183.0056.1b scn: 0x0000.d77996ab Version: 0x01 FREE BLOCK POOL:: uba: 0x00400183.0056.1b ext: 0x2 spc: 0x794 uba: 0x00000000.002f.21 ext: 0x5 spc: 0x1334 uba: 0x00000000.002e.37 ext: 0x4 spc: 0x788 uba: 0x00000000.0000.00 ext: 0x0 spc: 0x0 uba: 0x00000000.0000.00 ext: 0x0 spc: 0x0 ………… ORA-00604: 递归 SQL 层 1 出现错误 ORA-00607: 当更改数据块时出现内部错误 ORA-00600: 内部错误代码,参数: [4194], [34], [28], [], [], [], [], []
这种问题需要通过通过bbed/ue修改ktuxc的相关内容,实现数据库open成功,可以参考另外几篇文章:
使用bbed解决ORA-00607/ORA-00600[4194]故障
通过bbed模拟ORA-00607/ORA-00600 4194 故障
ORA-607/ORA-600[4194]不一定是重大灾难
数据库报ORA-00607/ORA-00600[4194]错误