标签云
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-01595 ORA-08103 ORA-600 2131 ORA-600 2662 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)
- 操作系统 (103)
- 数据库 (1,769)
- DB2 (22)
- MySQL (77)
- Oracle (1,610)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (166)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (69)
- Oracle Bug (8)
- Oracle RAC (54)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (592)
- Oracle安装升级 (97)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (86)
- PostgreSQL (30)
- pdu工具 (6)
- PostgreSQL恢复 (9)
- SQL Server (32)
- SQL Server恢复 (13)
- TimesTen (7)
- 达梦数据库 (3)
- 达梦恢复 (1)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (39)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (22)
-
最近发表
- 2025年的Oracle 8.0.5数据库恢复
- ORA-600 kokiasg1故障分析(obj$中核心字典序列全部被恶意删除)
- ORA-00756 ORA-10567故障数据0丢失恢复
- 数据库文件变成32k故障恢复
- tcp连接过多导致监听TNS-12532 TNS-12560 TNS-00502错误
- 文件系统格式化MySQL数据库恢复
- .sstop勒索加密数据库恢复
- 解决一次硬件恢复之后数据文件0kb的故障恢复case
- Error in invoking target ‘libasmclntsh19.ohso libasmperl19.ohso client_sharedlib’问题处理
- ORA-01171: datafile N going offline due to error advancing checkpoint
- linux环境oracle数据库被文件系统勒索加密为.babyk扩展名溯源
- ORA-600 ksvworkmsgalloc: bad reaper
- ORA-600 krccfl_chunk故障处理
- Oracle Recovery Tools恢复案例总结—202505
- ORA-600 kddummy_blkchk 数据库循环重启
- 记录一次asm disk加入到vg通过恢复直接open库的案例
- CHECKDB 发现了 N 个分配错误和 M 个一致性错误
- 达梦数据库dm.ctl文件异常恢复
- Oracle Recovery Tools修复ORA-00742、ORA-600 ktbair2: illegal inheritance故障
- 可能是 tempdb 空间用尽或某个系统表不一致故障处理
标签归档:ORA-600[3668]/ORA-600[4146]
记录8.0.5数据库恢复过程
某银行需要恢复2004年磁带备份数据库 8.0.5,当时因为开发商使用begin backup命令进行热备,然后压缩到磁带上.在硬盘紧张,rman不成熟的时代,使用这样的方法备份本身没有大问题,可是因为没有备份归档日志,给现在的恢复带来了很多的问题.
尝试不完全恢复启动库
SVRMGR> startup pfile='init.ora' mount ORACLE instance started. Total System Global Area 141826208 bytes Fixed Size 47264 bytes Variable Size 124829696 bytes Database Buffers 16777216 bytes Redo Buffers 172032 bytes Database mounted. SVRMGR> recover database using backup controlfile until cancel; ORA-00279: change 613561556 generated at 08/21/04 22:42:48 needed for thread 1 ORA-00289: suggestion : /oracle/product/8.0.5/dbs/arch1_55329.dbf ORA-00280: change 613561556 for thread 1 is in sequence #55329 Specify log: {<RET>=suggested | filename | AUTO | CANCEL} cancel Media recovery cancelled. SVRMGR> alter database open resetlogs; alter database open resetlogs * ORA-00600: internal error code, arguments: [4146], [31400], [31370], [], [], [], [], []
这个错误是因为回滚段corruption导致,客户已经没有了一致性要求,所以解决办法是通过一些手段找出回滚段并屏蔽
屏蔽回滚段重启库
SVRMGR> shutdown abort ORACLE instance shut down. SVRMGR> startup pfile='init.ora' mount ORACLE instance started. Total System Global Area 141826208 bytes Fixed Size 47264 bytes Variable Size 124829696 bytes Database Buffers 16777216 bytes Redo Buffers 172032 bytes Database mounted. SVRMGR> alter database open; alter database open * ORA-00600: internal error code, arguments: [3668], [1], [2], [55992], [55992], [4], [], []
根据ORA-00600[3668]错误的提示,因为重建控制文件,有一个数据文件因为在磁带恢复丢失,所以控制文件在上次重建的时候没有包含进去,根据经验在8.0中可以通过resetlogs解决
resetlogs重新打开数据库
SVRMGR> alter database open resetlogs; alter database open resetlogs * ORA-01139: RESETLOGS option only valid after an incomplete database recovery SVRMGR> recover datatabase using backup controlfile until cancel; ORA-00274: illegal recovery option DATATABASE SVRMGR> recover database using backup controlfile until cancel; ORA-00279: change 613561558 generated at 07/30/12 09:14:49 needed for thread 1 ORA-00289: suggestion : /oracle/product/8.0.5/dbs/arch1_1.dbf ORA-00280: change 613561558 for thread 1 is in sequence #1 Specify log: {<RET>=suggested | filename | AUTO | CANCEL} cancel Media recovery cancelled. SVRMGR> alter database open resetlogs; alter database open resetlogs * ORA-00604: error occurred at recursive SQL level 1 ORA-01555: snapshot too old: rollback segment number with name "" too small
根据经验可能是屏蔽了undo或者undo损坏,然后有事务可能需要读undo,无法读到对应记录,可能出现此错误,因为无trace文件,尝试推进scn解决.当然这个问题可以通过open时做10046然后深入分析也许可以找到原因.
open数据库成功
根据上面的分析,重启库,推进scn,resetlogs库解决问题
SVRMGR> shutdown immediate ORA-01109: database not open Database dismounted. ORACLE instance shut down. SVRMGR> startup pfile='init.ora' mount; ORACLE instance started. Total System Global Area 141826208 bytes Fixed Size 47264 bytes Variable Size 124829696 bytes Database Buffers 16777216 bytes Redo Buffers 172032 bytes Database mounted. SVRMGR> alter database open ; alter database open * ORA-00600: internal error code, arguments: [3668], [1], [2], [55994], [55994], [4], [], [] SVRMGR> recover database using backup controlfile until cancel; ORA-00279: change 613561560 generated at 07/30/12 09:17:11 needed for thread 1 ORA-00289: suggestion : /oracle/product/8.0.5/dbs/arch1_1.dbf ORA-00280: change 613561560 for thread 1 is in sequence #1 Specify log: {<RET>=suggested | filename | AUTO | CANCEL} cancel Media recovery cancelled. SVRMGR> alter database open resetlogs; Statement processed.
这次恢复比较幸运,在备份到磁带过程中被覆盖的一个同名的数据文件,因为是index,通过查询dba_extents,然后删除并重建相关index,s数据库算恢复完全.有些时候,对数据库多一份备份,可能成为最后的救命稻草,哪怕是一份不是十分完整的备份.再次重复:对dba而言,数据库备份重于一切