联系：手机/微信(+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正常,数据逻辑导出.
