Shulou(Shulou.com)05/31 Report--

Today, I will talk to you about how to analyze the maintenance of ORA-600 [13013] error reports. Many people may not know much about it. In order to make you understand better, the editor has summarized the following contents for you. I hope you can gain something according to this article.

Recently, the customer's ORACLE database suffered a power outage, and after restarting, the feedback instance was often shut down automatically.

ORACLE environment: ORACLE11.2.0.4 stand-alone

The OS version is: centos6.7

The following error is found by looking at the ALTER log.

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

The description on 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

Referring to some technical documentation, the recording process is as follows:

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

-query the index information of the affected table

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

-- re-indexing online

SQL > alter index SMON_SCN_TIME_SCN_IDX rebuild online

The index has changed.

SQL > alter index SMON_SCN_TIME_TIM_IDX rebuild online

The index has changed.

After observing for a period of time, it is found that the instance returns to normal and backs up the database manually.

After reading the above, do you have any further understanding of how to analyze the maintenance of ORA-600 [13013] error reports? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.