sitemap

RSS地图

收藏本站

设为首页

Oracle研究中心

当前位置:Oracle研究中心 > 故障案例 >

【案例】Oracle报错ORA-00600 13013的产生原因和解决办法

时间:2016-10-23 10:05   来源:Oracle研究中心   作者:HTZ   点击:

天萃荷净 Oracle研究中心案例分析:运维DBA反映测试Oracle数据库alert日志中报错ORA-00600 [13013], [5001],结合MOS官方分析解决办法为Doc ID 816784.1。
Oralce数据库ORA-00600 13013的错误,其实在MOS中已经说得比较清楚了,解决方案也给了,不过只限是普通的一些表,如果是一些核心的底层的表就麻烦了。以后面我们会模拟一些UNDO$表上面的13013错误

How to resolve ORA-00600 [13013], [5001] (Doc ID 816784.1)

Modified:22-Apr-2013

Type:HOWTO

clip_image001
In this Document

Goal
Solution
Section 1> What information needs to be Collected
Section 2 >How to resolve if a Index is corrupted
Section 3> How to resolve if table is corrupted
How to resolve when Smon terminates the instance due to Ora-00600[13013]
How to resolve the issue if the object involved belongs to system tablespace
Identifying the row having issue when the table is having corruption.
Are there any Known Bug
References

APPLIES TO:
Oracle Database – Enterprise Edition – Version 10.1.0.2 to 11.2.0.0 [Release 10.1 to 11.2]
Oracle Database – Enterprise Edition – Version 10.2.0.4 and later
Information in this document applies to any platform.
***Checked for relevance on 22-Apr-2013***

GOAL
The Goal of this article is to resolve Ora-00600[13013] and check if there are any known bugs associated with this error to prevent future occurence of this issue

SOLUTION

Section 1> What information needs to be Collected
ORA-600 [13013] [a] [b] [c] [d] [e] [f]


This format relates to Oracle Server 8.0.3 to 10.1

Arg [a] Passcount
Arg [b] Data Object number
Arg [c] Tablespace Relative DBA of block containing the row to be updated
Arg [d] Row Slot number
Arg [e] Relative DBA of block being updated (should be same as [c])
Arg [f] Code
The Second argument would give the information about the data object id.
This would give information about the object involved.
SQL>Select object_name,object_type,owner from dba_objects where data_object_id=
Once the Object is identified run the following :
The below command check if the table has corruption or not .

注意这里必须加上online,不然对在表上持有4的TM锁的,影响所有的DML
SQL> Analyze table . validate structure online ;
If this goes fine table doesnot have corruption. For next command.
If the above command fails with ORA-1498 go to Section 3
The below command check if table/index has corruption or not
SQL>Analyze table . validate structure cascade online ;
If the above command errors out with ora-1499 it indicates a corruption in index.

Go to section 2 for resolution
Run dbverify on the datafile reported in the error

Arg [c] in the ora-0600[13013] would give the Relative DBA

For example
ORA-00600: internal error code, arguments: [13013], [5001], [57353], [155254965], [261],
[155254965], [17], []

Arg [c] –> rdba–>155254965

Use this value and find the file and block number for this dba
select dbms_utility.data_block_address_file(155254965) Rfile# ,dbms_utility.data_block_address_block(155254965) "Block#" from dual;

RFILE# Block#
———- ———-
37 65717

不过如果是index/table中的记录不匹配,dbv是不能认识的,但是如果是因为块中的某些值不对导致的,DBV会识别的

You an run dbveirfy on datafile with rfile#=37
SQL>Select name from v$datafile where rfile#=37
dbv file= blocksize=

Section 2 >How to resolve if a Index is corrupted
You would need to drop and recreate the index
Ensure before dropping the Index
SQL>Spool /tmp/createindex.sql
SQL>Set long 100000000
SQL>Select dbms_metadata.get_ddl(‘INDEX’,'’,<‘user name>’) from dual
SQL>Spool off

Refer the Following note to Identify the index
Note 563070.1

Title: ORA-1499. Table/Index row count mismatch
Please note if there is just one index in the table then you can use dbms_metadata.get_ddl to get the script of the index and drop and recreate it.

Section 3> How to resolve if table is corrupted

Option a> Backup is available
Ora-1498 would be reported on the table.
The trace file from Ora-1498 would contain following information
Example

Block Checking: DBA = 1066265208, Block Type = KTB-managed data block —>
file 254,block 911992
data header at 0xc00000010118e07c
kdbchk: avsp(816) > tosp(812)
Block header dump: 0x3f8dea78
Object id on Block Y
seg/obj: 0x155b452 csc: 0x05.7b2b4ee6 itc: 3 flg: E typ: 1 – DATA
brn: 0 bdba: 0x3f8dde0c ver: 0x01
inc: 0 exflg: 0

Note the DBA value reported in the trace file DBA = 1066265208
Convert this to find the file number anOracle oracleplus.netd block number having issue

Sql>Select dbms_utility.data_block_address_file(‘1066265208’) from dual ;

DBMS_UTILITY.DATA_BLOCK_ADDRESS_FILE(‘1066265208’)
————————————————–
254

Sql>Select dbms_utility.data_block_address_block(‘1066265208’) from dual ;

DBMS_UTILITY.DATA_BLOCK_ADDRESS_BLOCK(‘1066265208’)
—————————————————
911992


Run dbverify on the datafile containing the table
dbv file= blocksize=
Corruption would be reported on the block.
If you have an Rman backup do a Rman block recovery (Take the file number and block number affected from the trace file)
Rman> Blockrecover datafile block

Or
If you have a user managed backup you can do an restore and recovery from good copy of the problematic datafile

Option b> Backup is not available
If no backups are available then use event 10231 at session level to create a salvage table
SQL>alter session set events ‘10231 trace name context forever, level 10’
SQL> Create table .salvage_table as select * from ;

Rename the Original table to old.
Rename salvage table to Original table name
or
You can use dbms_repair script to mark the block soft corrupt.

Note 556733.1

DBMS_REPAIR SCRIPT


How to resolve when Smon terminates the instance due to Ora-00600[13013]

If Smon is terminating the instance then.
Set event 10513 and startup the database

event="10513 trace name context forever, level 2"
SQL>Startup mount ;
SQL>Show parameter event
SQL>Alter datatabase open ;

Identify the object involved using information from Section 1.

How to resolve the issue if the object involved belongs to system tablespace
System objects are very important.
Please open a Service request with Oracle support if system tables are involved.

Identifying the row having issue when the table is having corruption.

1>Once the error occurs, using the ORA-600 arguments, gather the following information :

ORA-00600: internal error code, arguments: [13013], [5001], [57353], [155254965], [261],
[155254965], [17], []


arg b : [57353] – it is the OBJECT_ID
arg c : [155254965] – it is the block address in Decimal
arg d : [261] – is it the slot number

2. Translate the the block address in Decimal to a file# and block #

select dbms_utility.data_block_address_file(155254965) Rfile# ,dbms_utility.data_block_address_block(155254965) "Block#" from dual;

RFILE# Block#
———- ———-
37 65717

The Relative file is 37
The block number is 65717

Find the data_object_id for this object

Argument b is Object_id–> 57353

SQL>Select data_object_id ,object_name,owner from dba_objects where object_id=57353 ;

3. Create the rowid using dbms_rowid.rowid_create(1,DATA_OBJECT_ID,FILE#,BLOCK#,SLOT#)

In this case :

select dbms_rowid.rowid_create(1,57353,37,65717,261) from dual;
DBMS_ROWID.ROWID_C
——————
AAAOAJAAlAAAQC1AEF

4. You can select from table and identify the record causing the issue

SQL> Select * from . where rowid=’AAAOAJAAlAAAQC1AEF’;

Are there any Known Bug
There is a internal bug number 5085288
fixed in 11.1
Details

ORA-600 [13013] [5001] error can occur on a MERGE command if the DELETE pass encounters a consistent read (CR) error due to the update pass having updated the same
row and column previously.
Check for availability of one off patch using patch 5085288

Bug 4549673
Abstract: ORA-30926 / OERI:13030 during update
Fixed-Releases: 9208 A204 B106

Details:
ORA-30926 (in Oracle 9i) or ORA-600 [13030] (in Oracle10g) can occur
during an update DML. This can occur if an internal ORA-1551 error
occurs and is trapped (1551 errors are not visible to client
code and are trapped and handled internally)

Fixed In Ver: 11.0
Check for availability of one off patch using patch 5085288


REFERENCES
BUG:4549673 – UPDATE FAILS WITH ORA-30926 ON A PARTITIONED TABLE HAVING UPDATE TRIGGER
NOTE:1088018.1 – Master Note for Handling Oracle Database Corruption Issues
NOTE:556733.1 – DBMS_REPAIR SCRIPT
NOTE:563070.1 – ORA-1499. Table/Index row count mismatch
本文固定链接: http://www.htz.pw/2014/05/30/how-to-resolve-ora-00600-13013-5001-doc-id-816784-1.html | 认真就输

--------------------------------------ORACLE-DBA----------------------------------------

最权威、专业的Oracle案例资源汇总之【案例】Oracle报错ORA-00600 13013的产生原因和解决办法

本文由大师惜分飞原创分享,网址:http://www.oracleplus.net/arch/1040.html

Oracle研究中心

关键词:

ORA-00600

Oracle报错ORA-00600 13013的解决办法

ORA-00600 13013官方MOS的解决办法