ORA-00600: internal error code, arguments: [kdourp_inorder2]

网友贴图求助，在recover database的时候出现ORA-600错误，具体信息如下：

SQL> recover database;
ORA-10562: Error occurred while applying redo to data block (file# 4, block#
94060)
ORA-10564: tablespace USERS
ORA-01110: data file 4: 'E:\APP\ORADATA\ORCL\USERS01.DBF'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 73747
ORA-00600: internal error code, arguments: [kdourp_inorder2], [4], [1], [0],
[44], [], [], [], [], [], [], [] 

搜索MOS：

ORA-600 [kdourp_inorder2] (文档 ID 809274.1)

Note: For additional ORA-600 related information please read Note:146580.1

PURPOSE:
  This article represents a partially published OERI note.

  It has been published because the ORA-600 error has been 
  reported in at least one confirmed bug.

  Therefore, the SUGGESTIONS section of this article may help
  in terms of identifying the cause of the error.

  This specific ORA-600 error may be considered for full publication
  at a later date. If/when fully published, additional information 
  will be available here on the nature of this error.



SUGGESTIONS:

  If the Known Issues section below does not help in terms of identifying
  a solution, please submit the trace files and alert.log to Oracle 
  Support Services for further analysis.

  Known Issues:

You can restrict the list below to issues likely to affect one of the following versions by clicking the relevant button: 
                 

NB	Bug	Fixed	Description
+	9724970	11.2.0.1.BP08, 11.2.0.2.2, 11.2.0.2.BP02, 11.2.0.3, 12.1.0.1	Block Corruption with PDML UPDATE. ORA_600 [4511] OERI[kdblkcheckerror] by block check
*	7662491	10.2.0.4.2, 10.2.0.5, 11.1.0.7.4, 11.2.0.1	Array Update can corrupt a row. Errors OERI[kghstack_free1] or OERI[kddummy_blkchk][6110]

• '*' indicates that an alert exists for that issue.
• '+' indicates a particularly notable issue / bug.
• 'I' indicates an install issue / bug included for completeness.
• 'P' indicates a port specific bug.
• 'E' indicates an "Enhancement" (as opposed to a bug fix).
• 'D' indicates that the bug fix is disabled by default.
• "OERI:xxxx" may be used as shorthand for ORA-600 [xxxx].

maclean也提供了相关文档信息：

 Bug 7662491

影响程度 Corruption(MEM/Block/Dictionary/Index) 

有无补丁 可用 

Bug描述： 在使用Forall .... update对行进行更新时可能会报

Workaround： 如果发现问题，请使用ROWID跳过损坏数据来重建问题表，或使用dbms_repair。

ORA-600 [kghstack_free1]

ORA-600 [kcbzpbuf_1] 

ORA-600 [kcbbvr_verify_disk_blk_1]

ORA-600 [kdourp_inorder2]

跳过问题数据。

具体的操作方式可参考文档580561.1

ORA-600 [kddummy_blkchk][][][18038] during extent operations like TRUNCATE on ASSM tablespaces (文档 ID 580561.1)

In this Document
  Description
  Likelihood of Occurrence
  Possible Symptoms
  Workaround or Resolution
  Patches
  Modification History
  References

DESCRIPTION

This alert describes the problem in Bug 5386204 / Note 5386204.8.

Block corruption with error ORA-600 [kddummy_blkchk] [file#] [block#] [18038]
may be reported during a DROP/TRUNCATE

The corruption shows as a PAGETABLE SEGMENT HEADER having blocks in the
"Auxillary Map" outside of the "Extent Map" range. 

The same operation terminated without any error in previous RDBMS versions 
like Oracle9i. 

LIKELIHOOD OF OCCURRENCE

The object is populated by direct path operations such as SQL*Loader using DIRECT=Y for example.  
The object is stored in a Locally Managed Tablespace (LMT) that is using ASSM (dba_tablespaces.segment_space_management='AUTO').
Bug 5386204 is mostly hit when db_block_size=16384.

POSSIBLE SYMPTOMS

One evidence of hitting this bug might be the value 18038 in the third argument of 
ORA-600 [kddummy_blkchk] where [18038] is a check error code. 

@ Error check code 18038 means that the "Data dba" stored in "Auxiliary Map" is out of range 


  
 
 

  
  @TYP:0 CLS: 4 AFN:234 DBA:0x3a801554 OBJ:0 SCN:0x000b.290f5e0d SEQ:  1 OP:14.2

 
 
  
@ In this case "Data dba: 0x3a801555" stored in the "Auxiliary Map" is equal to 0x3a801551 + 4 which is out of the extent 0, hence the error. 

WORKAROUND OR RESOLUTION

In order to identify objects that are affected by the corruption, use the procedure 
DBMS_SPACE_ADMIN.ASSM_TABLESPACE_VERIFY 
  
DBMS_SPACE_ADMIN.ASSM_SEGMENT_VERIFY is also an option but it requires patch for Bug 6760697
  
How to execute DBMS_SPACE_ADMIN.ASSM_TABLESPACE_VERIFY:
    
    
    
  
  

   
   alter system set DB_BLOCK_CHECKSUM = OFF;
-- open a new session and run :
exec DBMS_SPACE_ADMIN.assm_tablespace_verify('<Tablespace Name>', DBMS_SPACE_ADMIN.TS_VERIFY_DEEP, DBMS_SPACE_ADMIN.SEGMENT_VERIFY_DEEP);

See if any trace file is generated in the directory defined by user_dump_dest. 
The absence of a trace file means that no corrupt segments were found.

  
  
Note: DB_BLOCK_CHECKSUM has to be disabled; otherwise the same ORA-600 error may be produced        
 
  
  
  
    
    
    
  
  

   
   Oracle check block type 0x23=PAGETABLE SEGMENT HEADER even if DB_BLOCK_CHECKING is not set.
Starting in Oracle 10g, block verifycation will always be performed for meta data blocks. 


  
  
Example of output from DBMS_SPACE_ADMIN.ASSM_TABLESPACE_VERIFY      
  
  
  
  
 
 
    
  
  
Segment header [dba: 0x003a801554, (file 234,block 5460)] 
Segment object id: 7825838; inc. no.: 0 
********* 
    
  
  
verifying extent map and tablespace bitmap consistency 
--------- 
Verifying extent map and  auxilliary extent map   consistency in   the segment 
Block Corruption in seg hdr / ext map block:                rdba: 0x3a801554, err code: 18038 
  
 
 
  
Identifying the object using the segment header information.
  
 
  
 
 

  
  Segment header [dba: 0x003a801554, (file 234,block 5460)] 

select * 
from DBA_EXTENTS 
where FILE_ID = 234 
and 5460 between block_id and block_id + blocks - 1; 
  
  

  
  

 
 
  
Identifying the object using the Segment object id information. 
  
 
 

  
  Segment object id: 7825838; inc. no.: 0  

select *  
from DBA_OBJECTS  
where DATA_OBJECT_ID = 7825838;
 
 
  
@ How to execute DBMS_SPACE_ADMIN.ASSM_SEGMENT_VERIFY  


  
  
  

   
   @ alter system set DB_BLOCK_CHECKSUM = OFF;



 
  
  

  
WORKAROUNDs:

Disable DB_BLOCK_CHECKSUM for any action taken.

Note: DB_BLOCK_CHECKSUM has to be disabled; otherwise the same ORA-600 error may be produced
  
alter system set DB_BLOCK_CHECKSUM = OFF;
-- open a new session

	DROP TABLE .. PURGE;
	ALTER TABLE .. MOVE ..; 
	Create table as select (CTAS)
	export/import, etc   

PATCHES

The patch prevents the corruption from taking place. Affected objects will have to be recreated.
  
This bug was previously incorrectly listed as fixed in 10.2.0.4.
  
This problem is fixed in the 10.2.0.5 Patch Set
This problem is fixed in the 11.1.0.6 rdbms release.

One off patches for this issue are available for some platforms / versions.
 
 
    
  
  
See Patch 5386204 for patch availability.
 
 

MODIFICATION HISTORY

03-JUN-2008 - Initial Alert version
04-JUN-2008 - Implemented correction
11-JUN-2008 - Added info about DB_BLOCK_CHECKSUM
13-JUN-2008 - Published 
04-OCT-2010 - Checked from relevancy.

REFERENCES

BUG:5386204 - ORA-600 [KDDUMMY_BLKCHK] ERRORS WITH CODE 18038

NOTE:1088018.1 - Master Note for Handling Oracle Database Corruption Issues

NOTE:5386204.8 - Bug 5386204 - Block corruption / OERI[kddummy_blkchk] after direct load of ASSM segment