标签云
asm mount 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 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 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 勒索恢复 比特币 oracle 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (93)
- 数据库 (1,498)
- DB2 (22)
- MySQL (64)
- Oracle (1,374)
- Data Guard (42)
- EXADATA (7)
- GoldenGate (21)
- ORA-xxxxx (154)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (12)
- ORACLE 21C (3)
- Oracle ASM (63)
- Oracle Bug (7)
- Oracle RAC (44)
- Oracle 安全 (6)
- Oracle 开发 (26)
- Oracle 监听 (26)
- Oracle备份恢复 (478)
- Oracle安装升级 (76)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (71)
- PostgreSQL (13)
- PostgreSQL恢复 (3)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (32)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (15)
-
最近发表
- Oracle 启动后一会儿就挂掉故障处理—ORA-600 17182
- 断电引起的oracle数据库异常恢复
- 等保修改oracle SYS用户名要求的请注意—ORA-00600 kokasgi1
- ORA-07445 opiaba—绑定变量超过65535导致实例crash
- Buffer I/O error on dev故障数据库恢复
- 12.1.0.2最新patch—202301
- 11.2.0.4最新patch信息—202301
- 网卡异常导致数据库实例启动异常
- 最新版oracle dul工具
- 误删除asm disk导致磁盘组无法mount数据库恢复
- .eight加密数据库恢复
- win强制修改盘符导致oracle异常恢复
- 再一例asm disk被误加入vg并且扩容lv恢复
- 重建control遗漏数据文件,reseltogs报ORA-1555错误处理
- InnoDB: Database page corruption on disk or a failed file read of page恢复
- _locked加密数据库恢复
- 部分oracle数据文件被加密完美恢复
- ORA-600 kcbzpbuf_1故障恢复
- Oracle 19c 断电异常恢复
- Oracle Recovery Tools快速恢复ORA-19909
友情链接
标签归档:ORA-600 16703
tab$异常被处理之后报ORA-600 13304故障处理
又一例数据库启动报ORA-600 16703 1403 20错误故障
Sun Jun 13 14:00:56 2021 NOTE: dependency between database xff and diskgroup resource ora.DG_ARCH_xff.dg is established Errors in file /opt/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_56340.trc (incident=348265): ORA-00600: internal error code, arguments: [16703], [1403], [20], [], [], [], [], [], [], [], [], [] Incident details in: /opt/oracle/diag/rdbms/xff/xff1/incident/incdir_348265/xff1_ora_56340_i348265.trc ARC3: Archival started ARC0: STARTING ARCH PROCESSES COMPLETE Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Errors in file /opt/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_56340.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [16703], [1403], [20], [], [], [], [], [], [], [], [], [] Errors in file /opt/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_56340.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [16703], [1403], [20], [], [], [], [], [], [], [], [], [] Error 704 happened during db open, shutting down database USER (ospid: 56340): terminating the instance due to error 704 Instance terminated by USER, pid = 56340
这个故障比较明显,根据我们之前的分析经验(警告:互联网中有oracle介质被注入恶意程序导致—ORA-600 16703),应该是tab$被恶意破坏导致,通过分析安装程序,确认是该问题,客户通过互联网上的相关文章,dd方式进行处理,结果数据库报ORA-600 13304错误,无法继续,让我们提供技术支持
SMON: enabling tx recovery Database Characterset is AL32UTF8 Errors in file /opt/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_83843.trc (incident=396265): ORA-00600: internal error code, arguments: [13304], [], [], [], [], [], [], [], [], [], [], [] Incident details in: /opt/oracle/diag/rdbms/xff/xff1/incident/incdir_396265/xff1_ora_83843_i396265.trc ARC3: Archival started ARC0: STARTING ARCH PROCESSES COMPLETE Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Errors in file /opt/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_83843.trc: ORA-00600: internal error code, arguments: [13304], [], [], [], [], [], [], [], [], [], [], [] Errors in file /opt/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_83843.trc: ORA-00600: internal error code, arguments: [13304], [], [], [], [], [], [], [], [], [], [], [] Error 600 happened during db open, shutting down database USER (ospid: 83843): terminating the instance due to error 600 Instance terminated by USER, pid = 83843
通过我们的技术对数据库进行一系列恢复之后,open过程报错
SQL> alter database open; alter database open * ERROR at line 1: ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00704: bootstrap process failure ORA-00604: error occurred at recursive SQL level 1 ORA-00904: "NAME": invalid identifier Process ID: 23346 Session ID: 680 Serial number: 51933
通过跟踪启动过程分析
PARSE ERROR #140574232044112:len=45 dep=1 uid=0 oct=3 lid=0 tim=1623621695884944 err=904 select value$ from sys.props$ where name = :1 ORA-00604: error occurred at recursive SQL level 1 ORA-00904: "NAME": invalid identifier ORA-00604: error occurred at recursive SQL level 1 ORA-00904: "NAME": invalid identifier
基本上可以确定是由于客户自行恢复导致props$表异常.通过进一步分析,确认是由于在对tab$处理不合适导致,进一步对tab$进行处理,数据库恢复正常,实现数据0丢失
ORA-00600: internal error code, arguments: [16703], [1403], [4] 故障处理
有一个客户数据库遭遇ORA-600 16703错误,故障原因见:警告:互联网中有oracle介质被注入恶意程序导致—ORA-600 16703,这种故障已经恢复比较多,在这次的恢复中遇到一个新错误,进行记录
接手给客户报错情况ORA-00600: internal error code, arguments: [16703], [1403], [20]
Thu May 13 22:36:11 2021 SMON: enabling cache recovery Thu May 13 22:36:11 2021 NSA2 started with pid=61, OS id=6261 Archived Log entry 90224 added for thread 1 sequence 50454 ID 0x19ae1c6c dest 1: Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_5931.trc (incident=741052): ORA-00600: internal error code, arguments: [16703], [1403], [20], [], [], [], [], [], [], [], [], [] Incident details in: /oracle/diag/rdbms/xff/xff/incident/incdir_741052/xff_ora_5931_i741052.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_5931.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [16703], [1403], [20], [], [], [], [], [], [], [], [], [] Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_5931.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [16703], [1403], [20], [], [], [], [], [], [], [], [], [] Error 704 happened during db open, shutting down database USER (ospid: 5931): terminating the instance due to error 704 Instance terminated by USER, pid = 5931 ORA-1092 signalled during: alter database open... opiodr aborting process unknown ospid (5931) as a result of ORA-1092 Thu May 13 22:36:13 2021 ORA-1092 : opitsk aborting process
这种故障,由于是恶意脚本在数据库启动的时候清空tab$所致,使用bbed对tab$进行反向删除操作,实现数据库打开.
在这次的恢复过程中遇到ORA-600 16703 1403 4的错误
SQL> startup mount pfile='/tmp/pfile'; ORACLE instance started. Total System Global Area 7.0818E+10 bytes Fixed Size 2260448 bytes Variable Size 1.3422E+10 bytes Database Buffers 5.7177E+10 bytes Redo Buffers 217030656 bytes Database mounted. SQL> alter database open ; alter database open * ERROR at line 1: ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [16703], [1403], [4], [], [], [], [], [], [], [], [], [] Process ID: 51886 Session ID: 3497 Serial number: 3
根据ora-600 16703 1403 4基本上可以判断是由于tab$这个表中缺少obj#=4的对象导致,通过查询正常库,确认是该对象为tab$,也就是说由于tab$对象中少了tab$记录.通过bbed分析确认
SQL> SELECT a.OBJ# 2 ,TAB# 3 ,a.DATAOBJ# 4 ,BOBJ# 5 ,NAME 6 ,DBMS_ROWID.ROWID_RELATIVE_FNO (a.ROWID) FILE_ID 7 ,DBMS_ROWID.ROWID_BLOCK_NUMBER (a.ROWID) BLOCK_ID 8 FROM TAB$ a, obj$ b 9 WHERE a.obj# = b.obj# 10 AND A.OBJ# IN (4); OBJ# TAB# DATAOBJ# BOBJ# NAME ---------- ---------- ---------- ---------- ------------------------------ FILE_ID BLOCK_ID ---------- ---------- 4 1 2 2 TAB$ 1 147 BBED> set dba 1,147 DBA 0x00400093 (4194451 1,147) BBED> x /rnnnnnnnnnnnnncnnnnnnnntnnnnnnnnnncct *kdbr[14] rowdata[6848] @7349 ------------- flag@7349: 0x20 (KDRHFH) lock@7350: 0x02 cols@7351: 0 nrid@7352:0x00407b09.1 BBED> set dba 0x00407b09 DBA 0x00407b09 (4225801 1,31497) BBED> p kdbt[1] struct kdbt[1], 4 bytes @110 sb2 kdbtoffs @110 10 sb2 kdbtnrow @112 2 BBED> x /rnnnnnnnnnnnnncnnnnnnnntnnnnnnnnnncct *kdbr[11] rowdata[815] @4436 ------------ flag@4436: 0x5c (KDRHFL, KDRHFF, KDRHFD, KDRHFC) lock@4437: 0x02 cols@4438: 0 ckix@4439: 8 BBED> x /rn *kdbr[8] rowdata[950] @4571 ------------ flag@4571: 0xac (KDRHFL, KDRHFF, KDRHFH, KDRHFK) lock@4572: 0x00 cols@4573: 1 kref@4574: 1 hrid@4576:0x00400093.8 nrid@4582:0x00400094.0 col 0[2] @4590: 4
确认该记录发生了行迁移导致该问题,对其对应的block进行修复,数据库正常打开.
发表在 非常规恢复
标签为 arguments: [16703], ORA-00600: internal error code, ORA-600 16703, oracle tab$恢复, tab$恢复, [1403], [4]
评论关闭
ORA-600 16703直接把orachk备份表插入到tab$恢复
有一个朋友和我说,他们数据库出现了以下错误ORA-600 16703 错误
他们是在虚拟化环境中,可以恢复到上一个快照点,但是主机启动之后,数据库依旧异常,让我们进行处理
C:\Users\Administrator>sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Wed Mar 24 17:04:01 2021 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> select open_mode from v$database; OPEN_MODE -------------------- READ WRITE SQL> select count(1) from tab$; COUNT(1) ---------- 0
很明显tab$已经被清空,数据库无法正常使用.因为库没有crash,尝试把备份的orachk表插入进来
SQL> insert into tab$ select * from ORACHKB514061BDCB10EBA9CF58F3; 6318 rows created. SQL> commit; Commit complete. SQL> select 'DROP TRIGGER '||owner||'."'||TRIGGER_NAME||'";' from dba_triggers w here TRIGGER_NAME like 'DBMS_%_INTERNAL% ' 2 union all 3 select 'DROP PROCEDURE '||owner||'."'||a.object_name||'";' from dba_procedu res a where a.object_name like 'DBMS_%_INTERNAL% ' 4 union all 5 select 'drop '||object_type||' '||owner||'.'||object_name||';' from dba_obj ects where object_name in('DBMS_SUPPORT_DBMONITOR','DBMS_SUPPORT_DBMONITORP'); 'DROPTRIGGER'||OWNER||'."'||TRIGGER_NAME||'";' -------------------------------------------------------------------------------- drop PROCEDURE SYS.DBMS_SUPPORT_DBMONITORP; drop TRIGGER SYS.DBMS_SUPPORT_DBMONITOR; SQL> drop PROCEDURE SYS.DBMS_SUPPORT_DBMONITORP; Procedure dropped. SQL> drop TRIGGER SYS.DBMS_SUPPORT_DBMONITOR; Trigger dropped. SQL> commit; Commit complete. SQL>
重启数据库,该故障恢复完成,数据完美恢复0丢失.