标签云
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,589)
- DB2 (22)
- MySQL (70)
- Oracle (1,459)
- Data Guard (49)
- EXADATA (7)
- GoldenGate (21)
- ORA-xxxxx (158)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (13)
- ORACLE 21C (3)
- Oracle ASM (65)
- Oracle Bug (7)
- Oracle RAC (47)
- Oracle 安全 (6)
- Oracle 开发 (27)
- Oracle 监听 (27)
- Oracle备份恢复 (526)
- Oracle安装升级 (83)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (75)
- PostgreSQL (13)
- PostgreSQL恢复 (3)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (36)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (19)
-
最近发表
- 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-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
- .[hudsonL@cock.li].mkp勒索加密数据库完美恢复
- 模拟带库实现rman远程备份
- 又一例:ORA-600 kclchkblk_4和2662故障
- Oracle误删除数据文件恢复
- Oracle 19C 备库DML重定向—DML Redirection
- ORA-01595/ORA-600 4194处理
- 从ORA-00283 ORA-16433报错开始恢复
- 近期又遇到ORA-600 16703和ORA-702故障
- RECOVER_YOUR_DATA勒索恢复
- ORA-01033: ORACLE initialization or shutdown in progress 故障处理
- Oracle 19c/21c最新patch信息-202401
- 存储故障,强制拉库报ORA-600 kcbzib_kcrsds_1处理
- ORA-600 kcrf_resilver_log_1故障处理
分类目录归档:Oracle备份恢复
ORA-01595/ORA-600 4194处理
又一个客户由于服务器断电,导致oracle无法正常启动报ORA-600 4194错误
Sat Jan 20 13:45:22 2024 ALTER DATABASE OPEN Beginning crash recovery of 1 threads parallel recovery started with 32 processes Started redo scan Completed redo scan read 31 KB redo, 5 data blocks need recovery Started redo application at Thread 1: logseq 9, block 3 Recovery of Online Redo Log: Thread 1 Group 3 Seq 9 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO03.LOG Completed redo application of 0.02MB Completed crash recovery at Thread 1: logseq 9, block 66, scn 81924188 5 data blocks read, 5 data blocks written, 31 redo k-bytes read Thread 1 advanced to log sequence 10 (thread open) Thread 1 opened at log sequence 10 Current log# 1 seq# 10 mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set SMON: enabling cache recovery Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery Database Characterset is AL32UTF8 No Resource Manager plan active Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_smon_5164.trc (incident=384222): ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] Incident details in: d:\oracle\diag\rdbms\xff\xff\incident\incdir_384222\xff_smon_5164_i384222.trc Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_ora_6832.trc (incident=384270): ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] Incident details in: d:\oracle\diag\rdbms\xff\xff\incident\incdir_384270\xff_ora_6832_i384270.trc Doing block recovery for file 3 block 207 Resuming block recovery (PMON) for file 3 block 207 Block recovery from logseq 10, block 64 to scn 81924393 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery stopped at EOT rba 10.66.16 Block recovery completed at rba 10.66.16, scn 0.81924391 Doing block recovery for file 3 block 160 Resuming block recovery (PMON) for file 3 block 160 Block recovery from logseq 10, block 64 to scn 81924389 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery completed at rba 10.64.16, scn 0.81924390 Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_smon_5164.trc: ORA-01595: 释放区 (2) 回退段 (3) 时出错 ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] Trace dumping is performing id=[cdmp_20240120134525] Doing block recovery for file 3 block 3857 Resuming block recovery (PMON) for file 3 block 3857 Block recovery from logseq 10, block 64 to scn 81924396 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery stopped at EOT rba 10.66.16 Block recovery completed at rba 10.66.16, scn 0.81924391 Doing block recovery for file 3 block 272 Resuming block recovery (PMON) for file 3 block 272 Block recovery from logseq 10, block 64 to scn 81924390 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery completed at rba 10.66.16, scn 0.81924391 replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Sat Jan 20 13:45:26 2024 QMNC started with pid=56, OS id=8052 Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x66F8B134] [PC:0x93C7D88, kgegpa()+38] Dump file d:\oracle\diag\rdbms\xff\xff\trace\alert_xff.log Doing block recovery for file 3 block 3857 Resuming block recovery (PMON) for file 3 block 3857 Block recovery from logseq 10, block 64 to scn 81924396 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery completed at rba 10.66.16, scn 0.81924399 Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_mmon_7876.trc (incident=396089): ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-06512: 在 "SYS.DBMS_HA_ALERTS_PRVT", line 310 ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], Doing block recovery for file 3 block 3857 Resuming block recovery (PMON) for file 3 block 3857 Block recovery from logseq 10, block 64 to scn 81924396 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery completed at rba 10.66.16, scn 0.81924399 Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_pmon_8876.trc (incident=384102): ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] Sat Jan 20 13:45:39 2024 Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_pmon_8876.trc: ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] PMON (ospid: 8876): terminating the instance due to error 472 Instance terminated by PMON, pid = 8876
这个故障比较简单,由于undo回滚异常导致,对异常的undo进行处理,数据库正常open,重建undo表空间导出数据,完成本次恢复工作
从ORA-00283 ORA-16433报错开始恢复
接手一个客户无法正常启动的故障数据库,尝试recover 报ORA-00283 ORA-16433错误
[oracle@xff trace]$ sqlplus / as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Sat Jan 27 04:46:23 2024 Copyright (c) 1982, 2014, Oracle. All rights reserved. ???: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options SQL> show pdbs; SQL> select open_mode from v$database; OPEN_MODE -------------------- MOUNTED SQL> SQL> recover database; ORA-00283: recovery session canceled due to errors ORA-16433: The database must be opened in read/write mode
通过对控制文件进行处理,再次尝试recover库
SQL> recover database; ORA-00399: corrupt change description in redo log ORA-00353: log corruption near block 134877 change 3249721295 time 01/27/2024 00:21:05 ORA-00312: online log 1 thread 1:'/u01/app/oracle/oradata/xff/redo01.log'
由于redo和数据文件不匹配,无法正常recover库,尝试强制打开库报ORA-600 2662错误
SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-00603: ORACLE server session terminated by fatal error ORA-00600: internal error code, arguments: [2662], [0], [3249721308], [0],[3249730440], [16777344],[],[],[],[],[],[] ORA-00600: internal error code, arguments: [2662], [0], [3249721307], [0],[3249730440], [16777344],[],[],[],[],[],[] ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00600: internal error code, arguments: [2662], [0], [3249721303], [0],[3249730440], [16777344],[],[],[],[],[],[] Process ID: 117336 Session ID: 1146 Serial number: 11764
基于这种错误,尝试oradebug修改scn
SQL> oradebug setmypid oradebug DUMPvar SGA kcsgscn_ Statement processed. SQL> kcslf kcsgscn_ [06001FBB0, 06001FBE0) = 00000000 00000000 00000000 00000000 00000000 SQL> oradebug poke 0x06001FBB0 4 0x10000000 oradebug DUMPvar SGA kcsgscn_ ORA-32521: error parsing ORADEBUG command:
发现报ORA-32521错误,证明常规的oradebug方法无法修改scn,参考相关文章:
oradebug poke ORA-32521/ORA-32519故障解决
第一次通过其他方法处理,由于计算失误导致数据库启动报ORA-600 2252错误
SQL> ALTER DATABASE OPEN RESETLOGS; ALTER DATABASE OPEN RESETLOGS * ERROR at line 1: ORA-00600: internal error code, arguments: [2252], [45264], [0], [11641],[3340959744], [],[],[],[],[],[]
该错误是相关文章参考:
记录一次ORA-00600[2252]故障解决
ORA-00600: internal error code, arguments: [2252], [3987]
主机断电系统回到N年前数据库报ORA-600 kcm_headroom_warn_1错误
处理正确的scn值之后,数据库open成功,然后逻辑方式导出数据,恢复工作完成
SQL> alter database open ; Database altered.
近期又遇到ORA-600 16703和ORA-702故障
比较常见的由于软件注入恶意代码或者被人恶意破坏的常见故障ORA-600 16703和ORA-702故障
上面的故障是由于bootstrap$表被删除导致,以前处理过类似case:
恶意删除bootstrap$导致数据库无法正常启动-1
恶意删除bootstrap$导致数据库无法正常启动-2
2019恢复第一单—ORA-704-ORA-702恢复
ORA-00702: bootstrap verison ” inconsistent with version ’8.0.0.0.0′
该故障的原因是一般是由于在互联网上下载了带恶意脚本的oracle安装介质,300天之后数据库重启会导致tab$被删除,参见:
ORA-600 16703故障解析—tab$表被清空
警告:互联网中有oracle介质被注入恶意程序导致—ORA-600 16703
再次提醒oracle使用者:
1. 不要使用从第三方网站下载非官方的数据库访问软件(发生过被注入恶意脚本的plsql dev案例:plsql dev引起的数据库被黑勒索比特币实现原理分析和解决方案)
2. 从官方下载oracle 安装程序和补丁程序(防止被注入恶意脚本,参考:警告:互联网中有oracle介质被注入恶意程序导致—ORA-600 16703)