Master Note for Handling Oracle Database Corruption Issues (Doc ID 1088018.1)
APPLIES TO:
Oracle Database - Enterprise Edition - Version 9.2.0.8 to 11.2.0.2.0 [Release 9.2 to 11.2]Information in this document applies to any platform.
DETAILS
The goal of this article is to give a global picture about corruption errors and appropiate actions deppending where the corruption is found.
In addition to the Support Notes below, you can get additional information here: My Oracle Support Comunity
The information contained in this targets product administrators.
In the common errors is possible to show only the notes related with an specific error or with an specific kind of corruption by clicking the desired button.
In addition to the Support Notes below, you can get additional information here: My Oracle Support Comunity
The information contained in this targets product administrators.
In the common errors is possible to show only the notes related with an specific error or with an specific kind of corruption by clicking the desired button.
ACTIONS
CORRUPTION EXPLANATION | |
| What is a corruption? Note 840978.1 : Physical and Logical block corruption How to force reformat a corrupted block? Note 336133.1 : How to Format Corrupted Block Not Part of Any Segment | How to identify corruptions in a database? Note 472231.1 : How to identify all the Corrupted Objects in the Database reported by RMAN Note 819533.1 : How to identify the corrupt Object reported by ORA-1578 / RMAN / DBVERIFY Known corruptions caused by OS/HW Issues Note 1323649.1 : Known Corruption issues caused by 3rd party Software Provider |
KIND OF CORRUPTIONS | |
| SEGMENT CORRUPTED | How to handle Segment Corruptions (Table, Index, LOB, Long, IOT, Temporary) This section refers to BLOCK CORRUPTION affecting database segments. Note 428526.1 : Baddata Script To Check Database For Corrupt column data |
| CONTROLFILE CORRUPTION | Note 1072762.6 : ORA-00227, ORA-00202: BRING UP INSTANCE AFTER MACHINE CRASH |
| UNDO CORRUPTION | Note 281429.1 : Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter Note 39283.1 : ORA-600 [4194] "Undo Record Number Mismatch While Adding Undo Record" Note 431652.1 : How to Change the Existing Undo Tablespace to a New Undo Tablespace |
| DICTIONARY CORRUPTION | Note 136697.1 : "hcheck.sql" script to check for known problems in Oracle8i, Oracle9i, Oracle10g and Oracle 11g |
| REDO CORRUPTION | Note 1031381.6 : How to Dump Redo Log File Information. |
| ROW & COLUMN CORRUPTION | Note 976591.1 : HowTo validate a date/timestamp column Note 869305.1 : How To identify a 'corrupt' row when error is raised b |
| HOW TO IDENTIFY TABLE/INDEX INCOSISTENCY | Note 136620.1 : Sanity Check of Oracle NUMBERS, How to Find and Patch |
HOW TO HANDLE SEGMENT CORRUPTIONS | |
TABLE CORRUPTION
| Note 28814.1 : Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g/11g |
INDEX CORRUPTION
| Note 28814.1 : Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g/11g Note 438143.1 : Use of dbms_metadata.get_ddl() to extract Index DDL Note 394143.1 : How Could I Format The Output From Dbms_metadata.Get_ddl Utility? |
LOB
| Note 452341.1 : How to detect Lob Corruption Note 293515.1 : ORA-1578 ORA-26040 in a LOB segment - Script to solve the errors |
LONG
| ** Contact Oracle Support ** -->> Generic notes about these objects: * None Public* |
IOT
| ** Contact Oracle Support ** -->> Generic notes about these objects: * None Public* |
TEMPORARY
| Note 1332088.1 : How to clear corruption in temporary segment not in temp tablespace Note 422039.1 : Steps to drop a temporary segment while SMON is not able |
PACKAGE INFORMATION AND EXAMPLES | |
DBMS_REPAIR
| Note 556733.1 : DBMS_REPAIR script Note 68013.1: DBMS_REPAIR example |
DBMS_METADATA
| Note 438143.1 : Use of dbms_metadata.get_ddl() to extract Index DDL Note 394143.1 : Q How Could I Format The Output From Dbms_metadata.Get_ddl Utility? Note 332077.1 : Why Does DBMS_METADATA.GET_DDL Not Show All Lines? Note 188838.1 : Using DBMS_METADATA To Get The DDL For Objects |
TOOLS | |
DBV
| Note 35512.1 : DBVERIFY - Database file Verification Utility (7.3.2 - 10.2) Note 269028.1 : DBV Reports Corruption Even After Drop/Recreate Object Note 336133.1 : How to Format Corrupted Block Not Part of Any Segment |
EXPORT
| Note 214369.1 : Using The Export Utility To Check For Database Corruption |
RMAN
| Note 472231.1 : How to identify all the Corrupted Objects in the Database with RMAN Note 1266059.1 : ABMR: HOW TO TEST AUTOMATIC BLOCK RECOVERY FEATURE |
TRANSPORTABLE TABLESPACE
| Note 733824.1 : HowTo Recreate a database using TTS |
DATA RECOVERY ADVISOR
| note 1317849.1 : Data Recovery Advisor - Corruption Reference Guide |
ORA600/7445 Error Lockup tool
| Note 153788.1 : ORA-600/ORA-7445 Error Look-up Tool |
GENERIC LINKS | |
PATCHSET UPDATES (PSU) & CRITICAL PATCH UPDATES (CPU)
| Note 268895.1 : Oracle Database Server Patchset Information, Versions: 8.1.7 to 11.2.0 Note 1061295.1 : Patch Set Updates - One-off Patch Conflict Resolution Note 161549.1 : Oracle Database, Networking and Grid Agent Patches for Microsoft Platforms Note 756671.1 : Oracle Recommended Patches -- Oracle Database Note 742060.1 : Release Schedule of Current Database Releases Note 161818.1 : Oracle Database (RDBMS) Releases Support Status Summary |
COMMON ERRORS | |
| ORA-1578 is reported when a block is thought to be corrupt on read. | |
| This error is raised when an operation refers to a ROWID in a table for which there is no such row. The reference to a ROWID may be implicit from a WHERE CURRENT OF clause or directly from a WHERE ROWID=... clause. ORA 1410 indicates the ROWID is for a BLOCK that is not part of this table. | |
| The object has been deleted by another user since the operation began. If the error is reproducible, following may be the reasons:- a.) The header block has an invalid block type. b.) The data_object_id (seg/obj) stored in the block is different than the data_object_id stored in the segment header. See dba_objects.data_object_id and compare it to the decimal value stored in the block (field seg/obj). | |
| An ORA-08102 indicates that there is a mismatch between the key(s) stored in the index and the values stored in the table. What typically happens is the index is built and at some future time, some type of corruption occurs, either in the table or index, to cause the mismatch. | |
| Generally this is a result of an ANALYZE ... VALIDATE ... command. This error generally manifests itself when there is inconsistency in the data/Index block. Some of the block check errors that may be found:- a.) Row locked by a non-existent transaction b.) The amount of space used is not equal to block size c.) Transaction header lock count mismatch. While support are processing the tracefile it may be worth the re-running the ANALYZE after restarting the database to help show if the corruption is consistent or if it 'moves'. Send the tracefile to support for analysis. If the ANALYZE was against an index you should check the whole object. Eg: Find the tablename and execute: ANALYZE TABLE xxx VALIDATE STRUCTURE CASCADE; | |
| An error occurred when validating an index or a table using the ANALYZE command. One or more entries does not point to the appropriate cross-reference. | |
| Trying to access data in block that was loaded without redo generation using the NOLOGGING/UNRECOVERABLE option. This Error raises always together with ORA-1578 | |
| Oracle is trying to access a row using its ROWID, which has been obtained from an index. A mismatch was found between the index rowid and the data block it is pointing to. The rowid points to a non-existent row in the data block. The corruption can be in data and/or index blocks. ORA-600 [12700] can also be reported due to a consistent read (CR) problem. | |
| This is called a 'STUCK RECOVERY'. There is an inconsistency between the information stored in the redo and the information stored in a database block being recovered. | |
| A mismatch has been detected between Redo records and rollback (Undo) records. We are validating the Undo record number relating to the change being applied against the maximum undo record number recorded in the undo block. This error is reported when the validation fails. | |
| A mismatch has been detected between Redo records and Rollback (Undo) records. We are validating the Undo block sequence number in the undo block against the Redo block sequence number relating to the change being applied. This error is reported when this validation fails. | |
| While backing out an undo record (i.e. at the time of rollback) we found a transaction id mis-match indicating either a corruption in the rollback segment or corruption in an object which the rollback segment is trying to apply undo records on. This would indicate a corrupted rollback segment. | |
| Not enough free space was found when inserting a row into an index leaf block during the application of undo. | |
| Oracle is attempting to read or update a generic entry in the control file. If the entry number is invalid, ORA-600 [2130] is logged. | |
| Oracle is checking the status of transaction locks within a block. If the lock number is greater than the number of lock entries, ORA-600 [4512] is reported followed by a stack trace, process state and block dump. This error possibly indicates a block corruption. | |
| A data block SCN is ahead of the current SCN. The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN stored in a UGA variable. If the SCN is less than the dependent SCN then we signal the ORA-600 [2662] internal error. | |
| We are accessing a rollback segment header to see if a transaction has been committed. However, the xid given is in the future of the transaction table. This could be due to a rollback segment corruption issue OR you might be hitting the following known problem. | |
| It means that Oracle has tried to find an undo segment number in the dictionary cache and failed. | |
| Oracle is undoing an index leaf key operation. If the key is not found, ORA-00600 [6006] is logged. ORA-600[6006] is usually caused by a media corruption problem related to either a lost write to disk or a corruption on disk. | |
| This assertion is raised because we are trying to unlock the rows in a block, but receive an incorrect block type. The second argument is the block type received. | |
| Oracle is checking that the row slot we are about to free is not already on the free list. This internal error is raised when this check fails. | |
| During a delete operation we are deleting from a view via an instead-of trigger or an Index organized table and have exceeded a 5000 pass count when we raise this exception. | |
| During the execution of an UPDATE statement, after several attempts (Arg [a] passcount) we are unable to get a stable set of rows that conform to the WHERE clause. | |
| We are trying to generate the absolute file number given a tablespace number and relative file number and cannot find a matching file number or the file number is zero. | |
| Looking up/checking a tablespace invalid tablespace ID and/or rdba found | |
| Invalid tsn and/or rfn found | |
| An object block buffer in memory is checked and is found to have the wrong object id. This is most likely due to corruption. | |
| ORA-600[kddummy_blkchk] is for 10.1/10.2 and ORA-600[kdblkcheckerror] for 11 onwards. | |
| This exception occurs when there are problems obtaining the row cache information correctly from sys.seg$. In most cases there is no information in sys.seg$. | |
| This exception is raised when we are performing a sanity check on the dependent SCN and fail. The dependent scn is greater than the current scn. | |
Comments
Post a Comment
Oracle DBA Information