今天就跟大家聊聊有关怎样分析ORA-600 [13013]报错的维护，可能很多人都不太了解，为了让大家更加了解，小编给大家总结了以下内容，希望大家根据这篇文章可以有所收获。
最近客户ORACLE数据库遇到断电，重新启动之后，反馈实例经常性自动关闭。
ORACLE环境为：ORACLE11.2.0.4 单机
OS版本为：centos6.7
通过查看ALTER 日志发现如下错误。
Errors in file /home/oracle/app/diag/rdbms/asd/asd/trace/asd_smon_24301.trc (incident=464751):
ORA-00600: internal error code, arguments: [13013], [5001], [268], [8457615], [5], [8457615], [17], [], [], [], [], []
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 9 out of maximum 100 non-fatal internal errors.
Sat Feb 24 11:26:09 2018
Sweep [inc][464751]: completed
MOS上描述：
Format: ORA-600 [13013] [a] [b] {c} [d] [e] [f]
Arg [a] Passcount
Arg [b] Data Object number
Arg {c} Tablespace Decimal Relative DBA (RDBA) of block containing the row to be updated
Arg [d] Row Slot number
Arg [e] Decimal RDBA of block being updated (Typically same as {c})
Arg [f] Code
参考一些技术文档，记录处理过程如下：
SQL> select dbms_utility.data_block_address_file(8457615) rfile,
2 dbms_utility.data_block_address_block(8457615) rblocks
3 from dual;
RFILE RBLOCKS
———- ———-
2 69007
SQL> set linesize 999 pagesize 9999
SQL> select owner,segment_name,segment_type,tablespace_name from dba_extents
2 where file_id =2
3 and 69007 between block_id and block_id + blocks -1;
OWNER SEGMENT_NAME SEGMENT_TYPE TABLESPACE_NAME
—————– —————– ——————– —————–
SYS SMON_SCN_TO_TIME_AUX CLUSTER SYSAUX
— 查询受影响表的索引信息
SQL> select owner,index_name from dba_indexes where table_name='SMON_SCN_TIME';
OWNERINDEX_NAME
——– ———————
SYSSMON_SCN_TIME_SCN_IDX
SYSSMON_SCN_TIME_TIM_IDX
— 在线重建索引
SQL> alter index SMON_SCN_TIME_SCN_IDX rebuild online;
索引已更改。
SQL> alter index SMON_SCN_TIME_TIM_IDX rebuild online;
索引已更改。
通过观察一段时间后，发现实例恢复正常并手动备份数据库。
看完上述内容，你们对怎样分析ORA-600 [13013]报错的维护有进一步的了解吗？如果还想了解更多知识或者相关内容，请关注云搜网行业资讯频道，感谢大家的支持。
