smon_scn_time ORA-00600 ktspfupdst-1

简介: 处理流程如下: 查看数据库日志报错: ORA-00600: internal error code, arguments: [ktspfupdst-1], [], [], [], [], [], [], [], [], [], [], [] Incid...


处理流程如下:


查看数据库日志报错:


ORA-00600: internal error code, arguments: [ktspfupdst-1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /home/oradba/oracle/diag/rdbms/yjfcdbp/yjfcdb/incident/incdir_192162/yjfcdb_smon_17351_i192162.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 logging scn->time mapping.
SMON encountered 2 out of maximum 100 non-fatal internal errors.
System state dump requested by (instance=1, osid=17307 (PMON)), summary=[abnormal instance termination].
System State dumped to trace file /home/oradba/oracle/diag/rdbms/yjfcdbp/yjfcdb/trace/yjfcdb_diag_17323.trc
Dumping diagnostic data in directory=[cdmp_20141030070534], requested by (instance=1, osid=17307 (PMON)), summary=[abnormal instance termination].
Instance terminated by PMON, pid = 17307


查看trace文件发现错误语句如下:


insert into smon_scn_time (thread, time_mp, time_dp, scn, scn_wrp, scn_bas, num_mappings, tim_scn_map) values (0, :1, :2, :3, :4, :5, :6, :7)


出现原因:


smon_scn_time表中的索引逻辑损坏




进行处理
首先对smon_scn_time进行结构验证,没有问题
SQL> conn / as sysdba
SQL> ANALYZE TABLE smon_scn_time VALIDATE STRUCTURE;


Table analyzed.


然后对涉及的索引进行验证报错:
SQL> ANALYZE TABLE smon_scn_time VALIDATE STRUCTURE CASCADE ONLINE; 


ERROR at line 1:
ORA-01499: table/index cross reference failure - see trace file


然后对涉及的索引进行重建


SQL> ALTER INDEX SMON_SCN_TIME_TIM_IDX REBUILD ONLINE;
SQL> ALTER INDEX SMON_SCN_TIME_SCN_IDX REBUILD  ONLINE;


重建后可以进行验证


SQL> ANALYZE TABLE smon_scn_time VALIDATE STRUCTURE CASCADE ONLINE; 


Table analyzed.


但是查看日志报错任然有ORA600错误,但是语句报错已经消失


然后处理如下:


SQL> conn / as sysdba
停止SMON 写入 smon_scn_time表
SQL> alter system set events '12500 trace name context forever, level 10';


SQL> truncate cluster SMON_SCN_TO_TIME_AUX;
 
Cluster truncated


启动SMON 写入 smon_scn_time表
SQL> alter system set events '12500 trace name context off';


再次查看日志没有报错。




SCN=(SCN_WRP * 4294967296) + SCN_BAS


参考文档
SMON Signals ORA-00600 [ktspfupdst-1] and Instance Terminates (文档 ID 1353076.1)
Instance Terminated With Error ORA-00474: SMON Process Terminated With Error (文档 ID 1361872.1)
LOCK ON SYS.SMON_SCN_TIME (文档 ID 747745.1)

相关文章
幾種重要的SCN
幾種重要的SCN  转自 http://www.cnblogs.com/gkl0818/archive/2009/02/11/1388011.html 1.
735 0
|
10月前
|
min restore scn of backup set file is greater than restore scn. can't use to restor
min restore scn of backup set file is greater than restore scn. can't use to restor
65 1
Goldengate:ERROR 180 encountered commit SCN that is not greater than the highest SCN already processed
How to recover from Extract ERROR 180 encountered commit SCN that is not greater than the highest SCN already processedThis is the summary of Metalink Doc:987379.
935 0
关于SCN HEADROOM 和_external_scn_rejection_threshold_hours 的说明
1、headroom 可以理解为一个时刻 SCN能够达到的最大值,其随时间的增加而增大 2、关于DBLINK SCN传播会选择更高的SCN进行同步 3、_external_scn_rejection_threshold_hours和HEADROOM的关...
1103 0
AI助理

你好,我是AI助理

可以解答问题、推荐解决方案等