联系：手机/微信(+86 17813235971) QQ(107644445)
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
有朋友数据库被文件系统勒索病毒加密,付费进行解密之后,发现所有的文本文件解密成功,但是Oracle数据库无法正常open,通过分析,虽然所有的文件名都已经恢复正常
但是文件内容没有被正常恢复成功
对于这次的情况,我们通过底层分析,发现是由于解密bug,导致文件没有被解密完成,通过对文件进行二次修复,实现数据库直接open,并导出数据
联系：手机/微信(+86 17813235971) QQ(107644445)
标题：ORA-600 kkdlcob-objn-exist 40
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
有客户晚上对数据库进行正常的重启维护,结果去遭遇数据库无法正常启动故障,报ORA-600 kkdlcob-objn-exist 40错误.
alert日志信息
Sat Jul 06 12:05:50 2019 alter database open Sat Jul 06 12:05:51 2019 LGWR: STARTING ARCH PROCESSES Sat Jul 06 12:05:51 2019 ARC0 started with pid=19, OS id=7056 ARC0: Archival started LGWR: STARTING ARCH PROCESSES COMPLETE ARC0: STARTING ARCH PROCESSES Thread 1 opened at log sequence 12 Current log# 3 seq# 12 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Sat Jul 06 12:05:52 2019 SMON: enabling cache recovery Sat Jul 06 12:05:52 2019 ARC1 started with pid=21, OS id=7948 Sat Jul 06 12:05:52 2019 ARC2 started with pid=22, OS id=11552 Sat Jul 06 12:05:52 2019 ARC3 started with pid=23, OS id=5504 ARC1: Archival started ARC2: Archival started ARC1: Becoming the 'no FAL' ARCH ARC1: Becoming the 'no SRL' ARCH ARC2: Becoming the heartbeat ARCH ARC3: Archival started ARC0: STARTING ARCH PROCESSES COMPLETE Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_ora_3092.trc (incident=20562): ORA-00600: internal error code, arguments: [kkdlcob-objn-exists], [40], [], [], [], [], [], [], [], [], [], [] Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\incident\incdir_20562\orcl_ora_3092_i20562.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 D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_ora_3092.trc: ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kkdlcob-objn-exists], [40], [], [], [], [], [], [], [], [], [], [] Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_ora_3092.trc: ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kkdlcob-objn-exists], [40], [], [], [], [], [], [], [], [], [], [] Error 704 happened during db open, shutting down database USER (ospid: 3092): terminating the instance due to error 704 Instance terminated by USER, pid = 3092 ORA-1092 signalled during: alter database open... opiodr aborting process unknown ospid (3092) as a result of ORA-1092 Sat Jul 06 12:05:56 2019 ORA-1092 : opitsk aborting process
ORA-600 kkdlcob-objn-exists官方解释，一般是由于ddl操作时dataobj#不合适引起,最大的可能是_NEXT_OBJECT值不对
对数据库启动过程进行跟踪
CREATE UNIQUE INDEX I_OBJ5 ON OBJ$(SPARE3,NAME,NAMESPACE,TYPE#,OWNER#,REMOTEOWNER,LINKNAME,SUBNAME,OBJ#) PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K NEXT 1024K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 OBJNO 40 EXTENTS (FILE 1 BLOCK 368)) END OF STMT PARSE #299964504:c=0,e=368,p=0,cr=0,cu=0,mis=1,r=0,dep=1,og=4,plh=440321312,tim=8823997737 ORA-00600: internal error code, arguments: [kkdlcob-objn-exists], [40], [], [], [], [], [], [], [], [], [], [] EXEC #299964504:c=875000,e=1213391,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=4,plh=440321312,tim=8825211183 ERROR #299964504:err=600 tim=8825211203 ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kkdlcob-objn-exists], [40], [], [], [], [], [], [], [], [], [], [] ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kkdlcob-objn-exists], [40], [], [], [], [], [], [], [], [], [], []
发现是I_OBJ5无法正常创建,导致数据库无法正常启动,由于这个是obj$对象的一个index(而且是11.2之后版本才引进),不是数据库启动必须的对象,通过bbed修改相关基表,让数据库启动不在跳过该index,数据库启动成功.因为进行了非常规的方法恢复,建议客户导出数据,导入到新库,数据库恢复工作完成.
联系：手机/微信(+86 17813235971) QQ(107644445)
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
11.2.0.4数据库启动报ORA-600 kcratr_scan_rc错误
ORA-600 kcratr_scan_rc错误相关alert日志
Thu May 09 01:56:01 2019 alter database open Beginning crash recovery of 1 threads parallel recovery started with 23 processes Started redo scan Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_ora_9975.trc (incident=171): ORA-00600: internal error code, arguments: [kcratr_scan_rc], [4], [1], [39821], [190063], [], [], [], [], [], [], [] Incident details in: /home/u01/diag/rdbms/orcl/orcl/incident/incdir_171/orcl_ora_9975_i171.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Aborting crash recovery due to error 600 Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_ora_9975.trc: ORA-00600: internal error code, arguments: [kcratr_scan_rc], [4], [1], [39821], [190063], [], [], [], [], [], [], [] Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_ora_9975.trc: ORA-00600: internal error code, arguments: [kcratr_scan_rc], [4], [1], [39821], [190063], [], [], [], [], [], [], [] ORA-600 signalled during: alter database open...
从这里看是由于数据库在做实例恢复的时候无法正确的应用日志导致.通过屏蔽数据库前滚恢复,强制open库
SQL> startup mount pfile='/tmp/pfile' ORACLE instance started. Total System Global Area 6998261760 bytes Fixed Size 2266624 bytes Variable Size 2684357120 bytes Database Buffers 4294967296 bytes Redo Buffers 16670720 bytes Database mounted. SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01092: ORACLE instance terminated. Disconnection forced 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 91 with name "_SYSSMU91_1360910548$" too small Process ID: 15929 Session ID: 5272 Serial number: 3
数据库报出来比较熟悉的ORA-01092 ORA-00704 ORA-00604 ORA-01555错误,分析trace文件
Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Thu May 09 02:10:27 2019 SMON: enabling cache recovery ORA-01555 caused by SQL statement below (SQL ID: bqbdby3c400p7, SCN: 0x0000.3e785fc7): select rowcnt,blkcnt,empcnt,avgspc,chncnt,avgrln,nvl(degree,1), nvl(instances,1) from tab$ where obj# = :1 Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_ora_15929.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 91 with name "_SYSSMU91_1360910548$" too small Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_ora_15929.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 91 with name "_SYSSMU91_1360910548$" too small Error 704 happened during db open, shutting down database USER (ospid: 15929): terminating the instance due to error 704 Instance terminated by USER, pid = 15929 ORA-1092 signalled during: alter database open resetlogs... opiodr aborting process unknown ospid (15929) as a result of ORA-1092 Thu May 09 02:10:28 2019 ORA-1092 : opitsk aborting process
这次的是比较少见的ORA-1555的错误语句select rowcnt,blkcnt,empcnt,avgspc,chncnt,avgrln,nvl(degree,1), nvl(instances,1) from tab$ where obj# = :1,通过bbed进行处理之后
SQL> alter database open; alter database open * ERROR at line 1: ORA-03113: end-of-file on communication channel Process ID: 17776 Session ID: 5272 Serial number: 3
数据库出现ORA-03113错误,通过分析alert日志
ORA-00600: internal error code, arguments: [4198], [], [], [], [], [], [], [], [], [], [], [] Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_smon_17739.trc (incident=128132): ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [], [], [], [], [] Incident details in: /home/u01/diag/rdbms/orcl/orcl/incident/incdir_128132/orcl_smon_17739_i128132.trc Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_mmon_17743.trc (incident=128151): ORA-00600: internal error code, arguments: [4412], [0x1E6BC4DF8], [0x000000000], [1], [6283], [], [], [], [], [], [], [] Incident details in: /home/u01/diag/rdbms/orcl/orcl/incident/incdir_128151/orcl_mmon_17743_i128151.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. SMON: Parallel transaction recovery slave got internal error SMON: Downgrading transaction recovery to serial Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_smon_17739.trc (incident=128133): ORA-00600: internal error code, arguments: [4137], [10.4.1100583], [0], [0], [], [], [], [], [], [], [], [] Incident details in: /home/u01/diag/rdbms/orcl/orcl/incident/incdir_128133/orcl_smon_17739_i128133.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 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 /home/u01/diag/rdbms/orcl/orcl/trace/orcl_mmon_17743.trc (incident=128152): ORA-00600: internal error code, arguments: [4406], [0x1E6BC4DF8], [0x000000000], [2], [6289], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [4412], [0x1E6BC4DF8], [0x000000000], [1], [6283], [], [], [], [], [], [], [] Incident details in: /home/u01/diag/rdbms/orcl/orcl/incident/incdir_128152/orcl_mmon_17743_i128152.trc ORACLE Instance orcl (pid = 15) - Error 600 encountered while recovering transaction (10, 4). Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_smon_17739.trc (incident=128134): ORA-00600: internal error code, arguments: [4137], [98.33.13158], [0], [0], [], [], [], [], [], [], [], [] Incident details in: /home/u01/diag/rdbms/orcl/orcl/incident/incdir_128134/orcl_smon_17739_i128134.trc Starting background process SMCO Thu May 09 02:16:25 2019 SMCO started with pid=21, OS id=18119 Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_smon_17739.trc (incident=128135): ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], [] Incident details in: /home/u01/diag/rdbms/orcl/orcl/incident/incdir_128135/orcl_smon_17739_i128135.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Non-fatal internal error happenned while SMON was doing non-existent object cleanup. SMON encountered 1 out of maximum 100 non-fatal internal errors. Thu May 09 02:16:27 2019 Thu May 09 02:16:32 2019 Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_ora_18168.trc (incident=128620): ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-28000: the account is locked Incident details in: /home/u01/diag/rdbms/orcl/orcl/incident/incdir_128620/orcl_ora_18168_i128620.trc ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-28000: the account is locked Block recovery from logseq 3, block 239 to scn 2147483855 Recovery of Online Redo Log: Thread 1 Group 3 Seq 3 Reading mem 0 Mem# 0: /home/u01/oradata/orcl/redo03.log Block recovery stopped at EOT rba 3.241.16 Block recovery completed at rba 3.241.16, scn 0.2147483854 Block recovery from logseq 3, block 239 to scn 2147483853 Recovery of Online Redo Log: Thread 1 Group 3 Seq 3 Reading mem 0 Mem# 0: /home/u01/oradata/orcl/redo03.log Block recovery completed at rba 3.241.16, scn 0.2147483854 Thu May 09 02:16:33 2019 Errors in file /home/u01/diag/rdbms/orcl/orcl/trace/orcl_ora_18170.trc (incident=128621): ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], [] ORA-28000: the account is locked Incident details in: /home/u01/diag/rdbms/orcl/orcl/incident/incdir_128621/orcl_ora_18170_i128621.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Thu May 09 02:16:34 2019 PMON (ospid: 17710): terminating the instance due to error 474 Instance terminated by PMON, pid = 17710
大量的ORA-600 4198,ORA-600 6006,ORA-600 4412,ORA-600 4137,ORA-600 4406,ORA-600 kdsgrp1等错误,根据以往经验,主要是undo异常导致,通过相关处理之后,数据库open正常,数据逻辑导出.
联系：手机/微信(+86 17813235971) QQ(107644445)
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
关于tab$异常的问题,我们在10G(10g数据库遭遇ORA-600 16703),11G(警告：互联网中有oracle介质被注入恶意程序导致—ORA-600 16703)中有发现,近期在12C版本中也发现该问题.再次提醒请注意检查安装介质的md5值和现在运行的库中是否有相关恶意程序
数据库版本
alert日志报错
************************************************************ Warning: The SCN headroom for this database is only 45 days! ************************************************************ ************************************************************ Warning: The SCN headroom for this database is only 45 days! ************************************************************ Picked broadcast on commit scheme to generate SCNs Fri Jan 25 11:34:55 2019 Starting background process TMON Fri Jan 25 11:34:55 2019 TMON started with pid=104, OS id=47282 Fri Jan 25 11:34:55 2019 Thread 1 advanced to log sequence 11942 (thread open) Thread 1 opened at log sequence 11942 Current log# 5 seq# 11942 mem# 0: +DATA/xifenfei/ONLINELOG/redo01_01.log Successful open of redo thread 1 Fri Jan 25 11:34:55 2019 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Fri Jan 25 11:34:55 2019 Network Resource Management enabled for Process LG00 (pid 451491) for Exadata I/O Fri Jan 25 11:34:55 2019 SMON: enabling cache recovery Errors in file /u01/oracle/app/oracle/diag/rdbms/xifenfei/xifenfei1/trace/xifenfei1_ora_46443.trc (incident=394486): ORA-00600: internal error code, arguments: [16703], [1403], [20], [], [], [], [], [], [], [], [], [] Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Fri Jan 25 11:34:56 2019 Errors in file /u01/oracle/app/oracle/diag/rdbms/xifenfei/xifenfei1/trace/xifenfei1_ora_46443.trc: ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [16703], [1403], [20], [], [], [], [], [], [], [], [], [] Fri Jan 25 11:34:56 2019 Errors in file /u01/oracle/app/oracle/diag/rdbms/xifenfei/xifenfei1/trace/xifenfei1_ora_46443.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [16703], [1403], [20], [], [], [], [], [], [], [], [], [] Fri Jan 25 11:34:56 2019 Errors in file /u01/oracle/app/oracle/diag/rdbms/xifenfei/xifenfei1/trace/xifenfei1_ora_46443.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [16703], [1403], [20], [], [], [], [], [], [], [], [], [] Fri Jan 25 11:34:56 2019 Error 704 happened during db open, shutting down database USER (ospid: 46443): terminating the instance due to error 704 Fri Jan 25 11:34:57 2019 Instance terminated by USER, pid = 46443
处理思路基本上和其他两个版本一样,都是对tab$进行修复,然后直接open数据库,但是在这次的恢复中遇到ORA-00600 kdfReserveSingle_1错误
ORA-600 kdfReserveSingle_1
SQL> alter database open ; alter database open * ERROR at line 1: ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00600: internal error code, arguments: [kdfReserveSingle_1], [0], [65280], [], [], [], [], [], [], [], [], [] Process ID: 319852 Session ID: 2401 Serial number: 24555 ---alert日志 Starting background process TMON Fri Jan 25 20:51:41 2019 TMON started with pid=94, OS id=322554 Fri Jan 25 20:51:41 2019 Thread 1 advanced to log sequence 11943 (thread open) Thread 1 opened at log sequence 11943 Current log# 6 seq# 11943 mem# 0: +DATA/xifenfei/ONLINELOG/redo02_01.log Successful open of redo thread 1 Fri Jan 25 20:51:41 2019 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Fri Jan 25 20:51:41 2019 Network Resource Management enabled for Process LG00 (pid 319754) for Exadata I/O Fri Jan 25 20:51:41 2019 SMON: enabling cache recovery Fri Jan 25 20:51:41 2019 [319852] Successfully onlined Undo Tablespace 2. Undo initialization finished serial:0 start:88159754 end:88160264 diff:510 ms (0.5 seconds) Verifying minimum file header compatibility (11g) for tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed Fri Jan 25 20:51:41 2019 SMON: enabling tx recovery Fri Jan 25 20:51:41 2019 Database Characterset is ZHS16GBK Errors in file /u01/oracle/app/oracle/diag/rdbms/xifenfei/xifenfei1/trace/xifenfei1_ora_319852.trc (incident=466446): ORA-00600: internal error code, arguments: [kdfReserveSingle_1], [0], [65280], [], [], [], [], [], [], [], [], [] Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Fri Jan 25 20:51:42 2019 Errors in file /u01/oracle/app/oracle/diag/rdbms/xifenfei/xifenfei1/trace/xifenfei1_ora_319852.trc: ORA-00600: internal error code, arguments: [kdfReserveSingle_1], [0], [65280], [], [], [], [], [], [], [], [], [] Fri Jan 25 20:51:42 2019 Errors in file /u01/oracle/app/oracle/diag/rdbms/xifenfei/xifenfei1/trace/xifenfei1_ora_319852.trc: ORA-00600: internal error code, arguments: [kdfReserveSingle_1], [0], [65280], [], [], [], [], [], [], [], [], [] Error 600 happened during db open, shutting down database USER (ospid: 319852): terminating the instance due to error 600 Fri Jan 25 20:51:43 2019 Instance terminated by USER, pid = 319852 ORA-1092 signalled during: alter database open… opiodr aborting process unknown ospid (319852) as a result of ORA-1092 Fri Jan 25 20:51:49 2019 ORA-1092 : opitsk aborting process
这个错误主要是由于12c的tab$和以前版本比有一些特殊,导致开始恢复不全,通过继续修复tab$之后数据库正常open.
相关文章汇总
tab$恢复错误汇总
12C数据库遭遇ORA-600 16703
10G数据库遭遇ORA-600 16703
ORA-600 16703故障解析—tab$表被清空
警告：互联网中有oracle介质被注入恶意程序导致—ORA-600 16703
联系：手机/微信(+86 17813235971) QQ(107644445)
标题：SCN Compatibility问题汇总-2019年6月23日
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
最近有不少朋友咨询关于2019年6月23日之前数据库scn，数据库是否要升级或者打补丁等问题，这里对相关问题做一个汇总。
1. 是否一定要升级或者打补丁
不一定，以下几种情况可以不用处理
1) 数据库版本11.1.0.7.20+ /11.2.0.3.9+ /11.2.0.4+版本已经包含了该补丁，无需处理
2) 数据库版本全部低于1)中数据库版本
3) 你的数据库环境中不存在1和2中数据库dblink访问
4) 你的数据库环境中有1和2中的数据库dblink访问,但是通过通过dbms_scn设置,不让1中的数据库版本scn compatibility改变(都保持为1)
2. 到了2019年6月23日之后,数据库的scn发生什么改变
简单的说就是数据库每秒可以使用的scn变大了,距离天花板的scn更加大,出现数据库scn用完的概率大大降低
--compat -- SCN compatibility value
--headroom_in_scn -- Difference between current SCN and RSL
--headroom_in_sec -- number of seconds it would take to reachRSL
SQL> set serveroutput on ;
SQL> declare
2 rsl number;
3 headroom_in_scn number;
4 headroom_in_sec number;
5 cur_scn_compat number;
6 max_scn_compat number;
7 begin
8 dbms_scn.GetCurrentSCNParams(rsl,headroom_in_scn,headroom_in_sec,cur_scn_compat,max_scn_compat);
9 dbms_output.put_line('rsl=' || rsl);
10 dbms_output.put_line('headroom_in_scn=' || headroom_in_scn);
11 dbms_output.put_line('headroom_in_sec=' || headroom_in_sec);
12 dbms_output.put_line('cur_scn_compat=' || cur_scn_compat);
13 dbms_output.put_line('max_scn_compat=' || max_scn_compat);
14 end;
15 /
rsl=16424869609472
headroom_in_scn=16424867538319
headroom_in_sec=1002494356
cur_scn_compat=1
max_scn_compat=3
PL/SQL procedure successfully completed.
SQL> Alter Database Set SCN Compatibility 2;
Database altered.
SQL> declare
2 rsl number;
3 headroom_in_scn number;
4 headroom_in_sec number;
5 cur_scn_compat number;
6 max_scn_compat number;
7 begin
8 dbms_scn.GetCurrentSCNParams(rsl,headroom_in_scn,headroom_in_sec,cur_scn_compat,max_scn_compat);
9 dbms_output.put_line('rsl=' || rsl);
10 dbms_output.put_line('headroom_in_scn=' || headroom_in_scn);
11 dbms_output.put_line('headroom_in_sec=' || headroom_in_sec);
12 dbms_output.put_line('cur_scn_compat=' || cur_scn_compat);
13 dbms_output.put_line('max_scn_compat=' || max_scn_compat);
14 end;
15 /
rsl=21792299122688
headroom_in_scn=21792297051479
headroom_in_sec=665048127
cur_scn_compat=2
max_scn_compat=3
PL/SQL procedure successfully completed.
SQL> Alter Database Set SCN Compatibility 3;
Database altered.
SQL> declare
2 rsl number;
3 headroom_in_scn number;
4 headroom_in_sec number;
5 cur_scn_compat number;
6 max_scn_compat number;
7 begin
8 dbms_scn.GetCurrentSCNParams(rsl,headroom_in_scn,headroom_in_sec,cur_scn_compat,max_scn_compat);
9 dbms_output.put_line('rsl=' || rsl);
10 dbms_output.put_line('headroom_in_scn=' || headroom_in_scn);
11 dbms_output.put_line('headroom_in_sec=' || headroom_in_sec);
12 dbms_output.put_line('cur_scn_compat=' || cur_scn_compat);
13 dbms_output.put_line('max_scn_compat=' || max_scn_compat);
14 end;
15 /
rsl=34585263898624
headroom_in_scn=34585261822622
headroom_in_sec=351819476
cur_scn_compat=3
max_scn_compat=3
PL/SQL procedure successfully completed.
这里大概演示了数据库scn compatibility变化带来的相关变化,这里可以看出来每秒
3. 如何禁用/启用scn compatibility自动升级
SQL> begin dbms_scn.DisableAutoRollover; end;
2 /
PL/SQL procedure successfully completed.
SQL> declare
2 EFFECTIVE_AUTO_ROLLOVER_TS date;
3 TARGET_COMPAT number;
4 IS_ENABLED boolean;
5 begin
6 dbms_scn.GETSCNAUTOROLLOVERPARAMS(EFFECTIVE_AUTO_ROLLOVER_TS,TARGET_COMPAT,IS_ENABLED);
7 dbms_output.put_line('EFFECTIVE_AUTO_ROLLOVER_TS='||to_char(EFFECTIVE_AUTO_ROLLOVER_TS,'yyyy-mm-dd hh24:mi:ss'));
8 dbms_output.put_line('TARGET_COMPAT=' || TARGET_COMPAT);
9 if(IS_ENABLED)then
10 dbms_output.put_line('IS_ENABLED IS TURE');
11 else
12 dbms_output.put_line('IS_ENABLED IS FALSE');
13 end if;
14 end;
15 /
EFFECTIVE_AUTO_ROLLOVER_TS=2019-06-23 00:00:00
TARGET_COMPAT=3
IS_ENABLED IS FALSE
PL/SQL procedure successfully completed.
SQL>
4. scn compatibility手工调整
SQL> Alter Database Set SCN Compatibility 2;
Database altered.
SQL> Alter Database Set SCN Compatibility 3;
Database altered.
SQL> Alter Database Set SCN Compatibility 1;
Alter Database Set SCN Compatibility 1
*
ERROR at line 1:
ORA-01126: database must be mounted in this instance and not open in any instance
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 4999609080 bytes
Fixed Size 9145080 bytes
Variable Size 1040187392 bytes
Database Buffers 3942645760 bytes
Redo Buffers 7630848 bytes
Database mounted.
SQL> Alter Database Set SCN Compatibility 1;
Database altered.
SQL> alter database open;
Database altered.
SQL> set serveroutput on ;
SQL> declare
2 rsl number;
3 headroom_in_scn number;
4 headroom_in_sec number;
5 cur_scn_compat number;
max_scn_compat number;
6 7 begin
8 dbms_scn.GetCurrentSCNParams(rsl,headroom_in_scn,headroom_in_sec,cur_scn_compat,max_scn_compat);
9 dbms_output.put_line('rsl=' || rsl);
dbms_output.put_line('headroom_in_scn=' || headroom_in_scn);
10 11 dbms_output.put_line('headroom_in_sec=' || headroom_in_sec);
12 dbms_output.put_line('cur_scn_compat=' || cur_scn_compat);
13 dbms_output.put_line('max_scn_compat=' || max_scn_compat);
end;
/ 14 15
rsl=16425127591936
headroom_in_scn=16425125502261
headroom_in_sec=1002510101
cur_scn_compat=1
max_scn_compat=3
PL/SQL procedure successfully completed.
参考文档：
Recommended patching and actions for Oracle database versions 12.1.0.1, 11.2.0.3 and earlier-before June 2019(Doc ID 2335265.1)
Recommended patches and actions for Oracle databases versions 12.1.0.1, 11.2.0.3 and earlier–before June 2019(Doc ID 2361478.1)
联系：手机/微信(+86 17813235971) QQ(107644445)
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
客户由于硬件故障，导致数据文件出现io错误
oracle@linux1:~> dd if=/oradata/orcl/system01.dbf of=/oradata/orcl/system01.dbf_bak bs=8192 dd: reading `/oradata/orcl/system01.dbf': Input/output error 83871+0 records in 83871+0 records out 687071232 bytes (687 MB) copied, 1.07177 s, 641 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 83871+0 records in 83871+0 records out 687071232 bytes (687 MB) copied, 1.0731 s, 640 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 83871+0 records in 83871+0 records out 687071232 bytes (687 MB) copied, 1.07431 s, 640 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 85158+1 records in 85158+1 records out 697618432 bytes (698 MB) copied, 4.11649 s, 169 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 85158+1 records in 85158+1 records out 697618432 bytes (698 MB) copied, 5.64775 s, 124 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 85158+1 records in 85158+1 records out 697618432 bytes (698 MB) copied, 7.1791 s, 97.2 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 85158+1 records in 85158+1 records out 697618432 bytes (698 MB) copied, 8.70247 s, 80.2 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 85158+1 records in 85158+1 records out 697618432 bytes (698 MB) copied, 10.2258 s, 68.2 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 85158+1 records in 85158+1 records out 697618432 bytes (698 MB) copied, 10.2272 s, 68.2 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 85158+1 records in 85158+1 records out 697618432 bytes (698 MB) copied, 10.2284 s, 68.2 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 85158+1 records in 85158+1 records out 697618432 bytes (698 MB) copied, 10.2296 s, 68.2 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 85158+1 records in 85158+1 records out 697618432 bytes (698 MB) copied, 10.2309 s, 68.2 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 85170+1 records in 85170+1 records out 697716736 bytes (698 MB) copied, 11.7563 s, 59.3 MB/s dd: reading `/oradata/orcl/system01.dbf': Input/output error 85170+1 records in 85170+1 records out 697716736 bytes (698 MB) copied, 13.3038 s, 52.4 MB/s 93431+1 records in 93431+1 records out 765390848 bytes (765 MB) copied, 18.2578 s, 41.9 MB/s
这个明显io错误比较多,无法直接使用以前的dd方法较好的恢复数据,只能通过linux平台的一些io工具修复文件(或者直接把磁盘挂载到win上通过工具处理),然后下载到win机器之后效果不错,只有17个坏块
C:\Users\XIFENFEI>dbv file=f:/11.2.0.1/system01.dbf DBVERIFY: Release 10.2.0.3.0 - Production on 星期日 2月 24 22:46:59 2019 Copyright (c) 1982, 2005, Oracle. All rights reserved. DBVERIFY - 开始验证: FILE = f:/11.2.0.1/system01.dbf 页 83871 标记为损坏 Corrupt block relative dba: 0x0041479f (file 1, block 83871) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 83872 标记为损坏 Corrupt block relative dba: 0x004147a0 (file 1, block 83872) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 83873 标记为损坏 Corrupt block relative dba: 0x004147a1 (file 1, block 83873) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0x759c0601 check value in block header: 0xe5e5 computed block checksum: 0xddc6 页 85161 流入 - 很可能是介质损坏 Corrupt block relative dba: 0x00414ca9 (file 1, block 85161) Fractured block found during dbv: Data in bad block: type: 6 format: 2 rdba: 0x00414ca9 last change scn: 0x0000.0ce20ac2 seq: 0x2 flg: 0x04 spare1: 0x0 spare2: 0x0 spare3: 0x0 consistency value in tail: 0xe5e5e5e5 check value in block header: 0x47f0 computed block checksum: 0xc3ab 页 85162 标记为损坏 Corrupt block relative dba: 0x00414caa (file 1, block 85162) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 85163 标记为损坏 Corrupt block relative dba: 0x00414cab (file 1, block 85163) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 85164 标记为损坏 Corrupt block relative dba: 0x00414cac (file 1, block 85164) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 85165 标记为损坏 Corrupt block relative dba: 0x00414cad (file 1, block 85165) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 85166 标记为损坏 Corrupt block relative dba: 0x00414cae (file 1, block 85166) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 85167 标记为损坏 Corrupt block relative dba: 0x00414caf (file 1, block 85167) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 85177 流入 - 很可能是介质损坏 Corrupt block relative dba: 0x00414cb9 (file 1, block 85177) Fractured block found during dbv: Data in bad block: type: 6 format: 2 rdba: 0x00414cb9 last change scn: 0x0000.0ce55ebf seq: 0x1 flg: 0x06 spare1: 0x0 spare2: 0x0 spare3: 0x0 consistency value in tail: 0xe5e5e5e5 check value in block header: 0x54c9 computed block checksum: 0x5ce5 页 85178 标记为损坏 Corrupt block relative dba: 0x00414cba (file 1, block 85178) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 85179 标记为损坏 Corrupt block relative dba: 0x00414cbb (file 1, block 85179) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 85180 标记为损坏 Corrupt block relative dba: 0x00414cbc (file 1, block 85180) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 85181 标记为损坏 Corrupt block relative dba: 0x00414cbd (file 1, block 85181) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 85182 标记为损坏 Corrupt block relative dba: 0x00414cbe (file 1, block 85182) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 页 85183 标记为损坏 Corrupt block relative dba: 0x00414cbf (file 1, block 85183) Bad header found during dbv: Data in bad block: type: 229 format: 5 rdba: 0xe5e5e5e5 last change scn: 0xe5e5.e5e5e5e5 seq: 0xe5 flg: 0xe5 spare1: 0xe5 spare2: 0xe5 spare3: 0xe5e5 consistency value in tail: 0xe5e5e5e5 check value in block header: 0xe5e5 computed block checksum: 0x0 DBVERIFY - 验证完成 检查的页总数: 93440 处理的页总数 (数据): 64294 失败的页总数 (数据): 0 处理的页总数 (索引): 12616 失败的页总数 (索引): 0 处理的页总数 (其它): 3111 处理的总页数 (段) : 0 失败的总页数 (段) : 0 空的页总数: 13402 标记为损坏的总页数: 17 流入的页总数: 2 最高块 SCN : 1073748415 (0.1073748415) C:\Users\XIFENFEI>
经过一系列恢复,数据库强制打开,数据库后台报ORA-7445 kkogbro
Completed: alter database open resetlogs upgrade Sun Feb 24 18:06:36 2019 MMON started with pid=15, OS id=9032 Sun Feb 24 18:07:50 2019 Errors in file d:\app\diag\rdbms\orcl\orcl\trace\orcl_ora_8336.trc: Sun Feb 24 18:07:52 2019 Trace dumping is performing id=[cdmp_20190224180752] Sun Feb 24 18:09:42 2019 alter tablespace temp add tempfile 'f:/11.2.0.1/temp01.dbf' size 128m autoextend on Completed: alter tablespace temp add tempfile 'f:/11.2.0.1/temp01.dbf' size 128m autoextend on Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x166] [PC:0x38E41AD, kkogbro()+497] ERROR: Unable to normalize symbol name for the following short stack (at offset 199): dbgexProcessError()+193<-dbgeExecuteForError()+65<-dbgePostErrorKGE()+1726<-dbkePostKGE_kgsf()+ 75<-kgeade()+560<-kgerev()+125<-kgerec5()+60<-sss_xcpt_EvalFilterEx()+1869<- sss_xcpt_EvalFilter()+174<-.1.6_8+59<-0000000077207388<-000000007721BF7D<- 00000000771F043A<-000000007721B61E<-kkogbro()+497<-kkogjro()+99<-kkojnp() +10299<-kkocnp()+78<-kkooqb()+1549<-kkoqbc()+2474<-apakkoqb()+200<- apaqbdDescendents()+496<-apaqbdList()+79<-apaqbdDescendents()+795<- apaqbdList()+79<-apaqbd()+17<-apadrv()+818<-opitca()+2518<-kksLoadChild()+9008 <-kxsGetRuntimeLock()+2320<-kksfbc()+15225<-kkspbd0()+669<-kksParseCursor()+741 <-opiosq0()+2538<-opipls()+12841<-opiodr()+1662<-rpidrus()+862<-rpidru()+154 <-rpiswu2()+2757<-rpidrv()+6105<-psddr0()+614<-psdnal()+510<-pevm_EXECC()+365 <-pfrinstr_EXECC()+90<-pfrrun_no_tool()+65<-pfrrun()+1241<-plsql_run()+875 <-peicnt()+329<-kkxexe()+616<-opiexe()+20006 Errors in file d:\app\diag\rdbms\orcl\orcl\trace\orcl_ora_8336.trc (incident=2540): ORA-07445: 出现异常错误: 核心转储 [kkogbro()+497] [ACCESS_VIOLATION] [ADDR:0x166] [PC:0x38E41AD] [UNABLE_TO_READ] [] Incident details in: d:\app\diag\rdbms\orcl\orcl\incident\incdir_2540\orcl_ora_8336_i2540.trc
通过分析trace文件,确认是和坏块有关系,对于上述坏块进行处理之后,数据正常导出.
联系：手机/微信(+86 17813235971) QQ(107644445)
标题：DBV-00600: 致命错误 – [21] [5] [0] [0] 错误原因
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
11.2.0.4 dbv检查
C:\Users\Administrator>dbv file=D:\TEMP\example01.dbf blocksize=8192 DBVERIFY: Release 11.2.0.4.0 - Production on 星期三 7月 4 18:04:34 2018 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. DBV-00600: 致命错误 - [21] [5] [0] [0]
12.2 dbv检查
oracle@localhost ~]$ dbv file=/tmp/example01.dbf DBVERIFY: Release 12.2.0.1.0 - Production on Wed Jul 4 06:28:51 2018 Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved. DBV-00113: FILE (/tmp/example01.dbf) file size is not a multiple of block size
OS文件大小
---linux
[oracle@localhost ~]$ ls -l /tmp/example01.dbf
-rwxrwxrwx 1 root root 104865793 Jul 3 11:46 /tmp/example01.dbf
---win
C:\Users\Administrator>dir D:\TEMP\example01.dbf
驱动器 D 中的卷是 本地硬盘
卷的序列号是 EECC-4D96
D:\TEMP 的目录
2018-07-03 23:46 104,865,793 example01.dbf
1 个文件 104,865,793 字节
0 个目录 2,192,213,327,872 可用字节
数据库记录文件大小
DUL> dump datafile 5 block 1 Block Header: block type=0x0b (file header) block format=0xa2 (oracle 10) block rdba=0x01400001 (file#=5, block#=1) scn=0x0000.00000000, seq=1, tail=0x00000b01 block checksum value=0xebd0=60368, flag=4 File Header: Db Id=0x58a78964=1487374692, Db Name=ORCL, Root Dba=0x0 Software vsn=0x0, Compatibility Vsn=0xb200000, File Size=0x3200=12800 Blocks File Type=0x3 (data file), File Number=5, Block Size=8192 Tablespace #6 - EXAMPLE rel_fn:5
比较明显数据文件头记录文件大小为12800*8192+8192(block 0)=104865792,而文件系统中显示的文件大小为104865793,不是8192的整数倍。因此出现相关错误DBV-00600: 致命错误 – [21] [5] [0] [0] 或者 DBV-00113(通过mos确认Bug 18232647 – DBVerify reports DBV-600 [21] [5] [0] [0] when datafile size is beyond expected – produce a more meaningful error (Doc ID 18232647.8))
联系：手机/微信(+86 17813235971) QQ(107644445)
标题：ORA-00600: internal error code, arguments: [1301]
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
有网友数据库报ORA-00600: internal error code, arguments: [1301]错误,然后就crash.简单查mos发现是bug引起
数据库版本
Sun Jul 01 17:48:09 2018 ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0 vsnsql=14 vsnxtr=3 Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options Windows NT Version V5.2 Service Pack 2 CPU : 32 - type 8664, 2 Physical Cores
alert日志报错
Sun Jul 01 17:48:09 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_pmon_98792.trc: ORA-00600: internal error code, arguments: [1301], [0x15CAEAF5C8], [11], [], [], [], [], [] Sun Jul 01 17:48:14 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_pmon_98792.trc: ORA-00600: internal error code, arguments: [1301], [0x15CAEAF5C8], [11], [], [], [], [], [] Sun Jul 01 17:48:14 2018 PMON: terminating instance due to error 472 Sun Jul 01 17:48:14 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_lgwr_98004.trc: ORA-00472: PMON process terminated with error Sun Jul 01 17:48:14 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_psp0_97900.trc: ORA-00472: PMON process terminated with error Sun Jul 01 17:48:15 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_dbw3_79724.trc: ORA-00472: PMON process terminated with error Sun Jul 01 17:48:16 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_dbw0_89896.trc: ORA-00472: PMON process terminated with error Sun Jul 01 17:48:16 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_ckpt_98468.trc: ORA-00472: PMON process terminated with error Sun Jul 01 17:48:16 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_dbw2_98348.trc: ORA-00472: PMON process terminated with error Sun Jul 01 17:48:17 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_j000_109140.trc: ORA-00472: PMON 进程因错误而终止 Sun Jul 01 17:48:17 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_dbw1_99112.trc: ORA-00472: PMON process terminated with error Sun Jul 01 17:48:17 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_mman_91488.trc: ORA-00472: PMON process terminated with error Sun Jul 01 17:48:53 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_q001_81352.trc: ORA-00472: PMON process terminated with error Sun Jul 01 17:50:59 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_reco_91716.trc: ORA-00472: PMON process terminated with error Sun Jul 01 17:50:59 2018 Errors in file d:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_smon_98428.trc: ORA-00472: PMON process terminated with error Sun Jul 01 17:51:02 2018 Instance terminated by PMON, pid = 98792
trace文件信息中的call stack信息
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [1301], [0x15CAEAF5C8], [11], [], [], [], [], []
check trace file d:\oracle\product\10.2.0\db_1\rdbms\trace\xifenfei_ora_0.trc for preloading .sym file messages
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedmp+663 CALL??? ksedst+55 003C878B8 000000000 00C18CE58
000000000
ksfdmp+19 CALL??? ksedmp+663 000000003 009BE3650 00BD10040
003CACC80
kgeriv+184 CALL??? ksfdmp+19 000000001 000000037
15CAEAF5C8 13CA54BB60
kgesiv+102 CALL??? kgeriv+184 003C8735C 000000001 0000003BC
15CA0562E0
ksesic2+125 CALL??? kgesiv+102 00000000A 15CAEAF5C8
15CF809B88 00042965C
ksuxdp+652 CALL??? ksesic2+125 000000515 000000002
15CAEAF5C8 000000000
ksuxdpg+114 CALL??? ksuxdp+652 000000000 0080D5698
76CCBF8BD519 009BE3010
ksucln+2458 CALL??? ksuxdpg+114 000000003 000000000 00BD3DC60
000000048
ksbrdp+903 CALL??? ksucln+2458 0049B7760 0049B777C 000000002
000000005
opirip+700 CALL??? ksbrdp+903 726F77740000001E 003C8B000
00C18FA50 000000000
opidrv+860 CALL??? opirip+700 000000032 000000004 00C18FD70
000000000
sou2o+52 CALL??? opidrv+860 000000032 000000004 00C18FD70
000000003
opimai_real+272 CALL??? sou2o+52 000000000 0076C0000 000040000
000000000
opimai+96 CALL??? opimai_real+272 000000000 000000000 000000000
000000000
BackgroundThreadSta CALL??? opimai+96 00C18FEC8 000000001 000000000
rt+633 000000000
0000000078D3B71A CALL??? BackgroundThreadSta D65F12CF0 000000000 000000000
rt+633 00C18FFA8
基本上可以定位因为Bug 7294679 – ORA-600 [1301] – INSTANCE TERMINATED BY PMON 原因导致pmon无法完全正常清理被kill掉的session而引起pmon异常从而使得数据库crash.在10.2.0.5和11.2.0.1版本之前alter system kill session 请谨慎,还有类似因为kill session导致 ORA-00600 [1113]的错误.
参考文档:ORA-00600 [1301] – Instance Terminated by PMON After Killing Sessions (Doc ID 737561.1)
ORA-00600 [1113] Instance Termination When Killing Sessions (Doc ID 561322.1)
联系：手机/微信(+86 17813235971) QQ(107644445)
标题：KFED – ERROR!!! could not initialize the diag context
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
grid用户执行kfed报ERROR!!! could not initialize the diag context错误
[grid@xifenfei ~]$ kfed ERROR!!! could not initialize the diag context
asmtool权限/所有者不对
通过分析是由于kfed在执行的时候需要在$ORACLE_BASE/diag目录下面创建asmtool文件夹以及相关文件,当grid用户无法创建之时，就会出现此类错误
[grid@xifenfei ~]$ cd $ORACLE_BASE/diag [grid@xifenfei diag]$ ls asm asmtool rdbms tnslsnr [grid@xifenfei diag]$ ls -ltr total 16 drwxr-xr-x. 3 grid oinstall 4096 Jul 31 2014 tnslsnr drwxr-xr-x. 3 root root 4096 Apr 21 10:11 asmtool drwxr-x---. 4 grid oinstall 4096 Apr 29 2018 rdbms drwxr-xr-x. 3 grid oinstall 4096 Jun 19 2018 asm
修改asmtool所有者
[root@xifenfei ~]# cd /u01/app/grid/diag/ [root@xifenfei diag]# chown grid:oinstall asmtool/
grid用户执行kfed正常
[grid@xifenfei diag]$ kfed as/mlib ASM Library [asmlib='lib'] aun/um AU number to examine or update [AUNUM=number] aus/z Allocation Unit size in bytes [AUSZ=number] blkn/um Block number to examine or update [BLKNUM=number] blks/z Metadata block size in bytes [BLKSZ=number] ch/ksum Update checksum before each write [CHKSUM=YES/NO] cn/t Count of AUs to process [CNT=number] de/v ASM device to examine or update [DEV=string] dm/pall Don't suppress repeated lines when dumping corrupt blocks [DMPALL=YES/NO] o/p KFED operation type [OP=READ/WRITE/MERGE/REPAIR/NEW/FORM/FIND/STRUCT] p/rovnm Name for provisioning purposes [PROVNM=string] s/eek AU number to seek to [SEEK=number] te/xt File name for translated block text [TEXT=string] ty/pe ASM metadata block type number [TYPE=number]
kfed创建对应目录
[grid@xifenfei asmtool]$ ls -ltr total 8 drwxr-xr-x. 3 root root 4096 Apr 21 10:23 user_root drwxr-xr-x. 3 grid oinstall 4096 Apr 21 10:24 user_grid
联系：手机/微信(+86 17813235971) QQ(107644445)
标题：OERR: ALL 600 Ora 600 Layers
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
** 0000 ** Service Layer
========================
KIESCBAS (1) Component notifier component
KIESDBAS (100) Debug component
KIESEBAS (300) Error component
KIESLBAS (500) Lock component
KIESMBAS (700) Memory component
KIESPBAS (900) System Parameters component
KIESSBAS (1100) System State object component
KIESGBAS (1110) Generic Linked List management component
KIESQBAS (1140) Enqueue component
KIESIBAS (1180) Instance Locks component
KIESUBAS (1200) User State object component
KIESABAS (1400) Async Msgs component
KIESKBAS (1700) license Key component
KIESRBAS (1800) Instance Registration component
KIESOBAS (1850) I/O Services component
** 2000 ** Cache Layer Component Base internal error values
===========================================================
KIECOBAS (2000) Cache Op component
KIECCBAS (2100) Control File mgmt component
KIECMBAS (2200) Misc (SCN etc.)
KIECHBAS (2400) Buffer Instance Hash Table
KIECRBAS (2600) Redo file component
KIECFBAS (2800) Db file component
KIECABAS (3000) Redo Application component
KIECBBAS (3200) Buffer manager base
KIECZBAS (3400) Archival & media recovery component base
KIECLBAS (3500) direct Loader component base
KIECVBAS (3600) recoVery component base
KIECKBAS (3700) Thread component base
KIECKBAS (3800) Compatibility segment component base
KIECBBAS (3900) Buffer working set manager component base
** 4000 ** Transaction Layer
============================
Transaction Layer Component Base internal error values:
KIETUBAS (4000) Transaction Undo Component
internal errors 4100-4199 used by transaction undo component as well
KIETPBAS (4210) Transaction Parallel
KIETLBAS (4250) Transaction List
KIETSBAS (4300) Transaction Segment
KIETCBAS (4400) Transaction Control Component
internal errors 4450-4499 used by transaction distributed component
KIETBBAS (4500) Transaction Block Component
KIETABAS (4600) Transaction Table Component
KIETRBAS (4800) Query Row Cache Component
KIETMBAS (4900) Transaction Monitor Component
KIETSBAS (4950) Query Bootstrap Component
KIETEBAS (5000) Transaction Extent
** 6000 ** Data Layer
=====================
** 8000 ** Access Layer
=======================
Data Layer Component Base internal error values:
8000...8199 reserved for data layer
8100...8149 reserved for index component
8100 - 8109 used in KAU
8110 - 8124 used in KKRI, KDIC (create index)
** 9000 ** Parallel Server
==========================
KIECLBAS (9000) KCL component: 9000 .. 9100
** 10000 ** Control Layer
=========================
** 12000 ** User/Oracle Interface Layer
=======================================
User/Oracle Interface & SQL Layer "components" (in a loose sense)
KIEUTBAS (12000) TAC* component: 12000 .. 12009
KIEURBAS (12010) SORT component: 12010 .. 12199
KIEUPBAS (12200) OPI* component: 12200 .. 12299
KIEUSBAS (12300) PRS, APA, EVA, EXP, QBA component: 12300 .. 12399
KIEUWBAS (12400) QKA, MSQ, and row source components: 12400 .. 12499
reserved for rix: 12480 .. 12499
KIEUVBAS (12600) *DRV component: 12600 .. 12799
KIEUDBAS (12800) KKDL, KKDC and KKM components: 12800 .. 12999
KIEUXBAS (13000 DELEXE, UPDEXE, CRI: 13000 .. 13079
REF : 13080 .. 13089
WSM : 13090 .. 13099
KIEUABAS (13100) OPIAMR: 13100 .. 13149
KIEULBAS (13200) ACL and ATB: 13200 .. 13230
KIEUZBAS (13250) AUD, AUSDRV, AOP: 13250 .. 13300
KIEUOBAS (13301) KOK* and object extensions: 13301 .. 13499
KIELCBAS (16000) loader column array builder
** 14000 ** System-dependent "Layer"
====================================
System Dependent Layer Component Base internal error values:
KIESFBAS (14000) File component
KIESCBAS (14100) Concurrency component
KIESPBAS (14200) Process component
KIESXBAS (14300) Exception-handler component
KIESMBAS (14500) Memory component
** Note that multiple ports can use the same internal error numbers.
We allow this because we don't want to waste numbers on port internal
errors, something which is very rarely used. In addition it is
likely that any bug that is reporting a port internal error to the
generic (portable) coding group is going to have to supply a lot of
documentation - so if two ports use the same number, it should never
confuse anybody.
** 15000 ** Security Layer
==========================
15000 - 15079 reserved for KZ*, SEC, and GRA;
15080 - 15099 reserved for KZL;
15100 - 15159 reserved for KKP;
15160 - 15199 reserved for KKO and KKE;
15190 .. 15199 reserved for KKOCRI
15200 - 15229 reserved for KKS;
15230 - 15259 reserved for KKT;
15260 - 15399 reserved for KKD;
15400 - 15409 reserved for KKY;
15410 - 15499 reserved for KKX (and PSD);
15500 - 15549 reserved for KKM;
15550 - 15599 reserved for KKR; (and KXH)
15600 - 15619 reserved for KKF; (parallel query)
15620 - 15639 reserved for KKZ (snapshots);
15640 - 15659 reserved for KKXA;
15660 - 15669 reserved for KKJ (job queue);
15670 - 15679 reserved for KKFS (parallel query)
15680 - 15689 reserved for KKRT;
15690 - 15699 reserved for other KK*;
15700 - 15799 reserved for KXFP; (parallel query)
15800 - 15809 reserved for KXFX; (parallel query)
15810 - 15819 reserved for KXFQ; (parallel query)
15820 - 15849 reserved for other KXF*; (parallel query)
15850 - 15859 reserved for KSX*;
15860 - 15999 reserved for other KX*;
** 16000 ** Loader "Layer"
==========================
16000 - 16149 reserved for the direct loader;
16150 - 16199 reserved for the c level call interface to direct loader;
16200 - 16229 reserved for KQL;
16230 - 16249 reserved for KQLR;
16250 - 16299 reserved for KQA;
16300 - 16399 reserved for KM*;
16400 - 16449 reserved for KKB;
16450 - 16499 reserved for KQLM;
16500 - 16549 reserved for KQD;
16550 - 16559 reserved for KQF;
16600 - 16650 reserved for KQLS;
16651 - 16700 reserved for KQLD;
16701 - 16750 reserved for KQLB;
** 17000 ** Generic "Layer"
===========================
17000 - 17089 reserved for KGL;
17090 - 17099 reserved for KGE;
17100 - 17199 reserved for KGH;
17200 - 17249 reserved for KGLR/KGLRO;
17250 - 17269 reserved for KGP;
17270 - 17299 reserved for KGI;
17300 - 17399 reserved for KGHX;
17500 - 17624 reserved for I/O subsystem KG components (KGFD, KGFF, KGK)
17625 - 17639 reserved for KGL3;
17640 - 17989 reserved for other KG*;
17990 - 17999 reserved for PL/SQL;
** 18000 ** K2 (2-phase commit),subdiv'd in k2.h: 18000 .. 18499
==================================================================
18000 - 18999 reserved for K2*;
** 19000 ** Object Layer
========================
19000 - 19999 reserved for KO*;
20000 - 20399 reserved for bitmap index KDIB*;
20400 - 20499 reserved for KKPO;;
20500 - 20999 reserved for SMR;
** 21000 ** Replication Layer
=============================
21000 - 21999 reserved for KN*;
** 23000 ** OLTP Layer
======================
23000 - 23999 reserved for KW*;
24000 - 24049 reserved for QOL;