Ниже приведу собранный из разных источников перечень ошибок ORA-600 с кратким описанием проблемы и направлением, куда идти, чтобы их решить. Перечень буду править исправлением сообщения, так что лучше сохраните ссылку на него.
ORA-600 [12700]
ORA-00600 [12700]
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.
Resolving an ORA-600 [12700] error in Oracle 8 and above.
ORA-600 [12700] “Index entry Points to Missing ROWID”
ORA-600 [3020]
ORA-00600 [3020]
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.
ORA-600 [3020] “Stuck Recovery”
Information Required for Root Cause Analysis of ORA-600 [3020] (stuck recovery)
ORA-600 [4194]
ORA-00600 [4194]
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.
ORA-600 [4194] “Undo Record Number Mismatch While Adding Undo Record”
Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter
ORA-600 [4193]
ORA-00600 [4193]
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. Undo
ORA-600 [4193] “seq# mismatch while adding undo record”
Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter
Ora-600 [4193] When Opening Or Shutting Down A Database
ORA-600 [4193] When Trying To Open The Database
ORA-600 [4137]
ORA-00600 [4137]
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.
ORA-600 [4137] “XID in Undo and Redo Does Not Match”
ORA-600 [6101]
ORA-00600 [6101]
Not enough free space was found when inserting a row into an index leaf block during the application of undo.
ORA-600 [6101] “insert into leaf block (undo)”
ORA-600 [2103]
ORA-00600 [2103]
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.
ORA-600 [2130] “Attempt to access non-existent controlfile entry”
ORA-600 [4512]
ORA-00600 [4512]
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.
ORA-600 [4512] “Lock count mismatch”
ORA-600 [2662]
ORA-00600 [2662]
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.
ORA-600 [2662] “Block SCN is ahead of Current SCN”
ORA 600 [2662] DURING STARTUP
ORA-600 [4097]
ORA-00600 [4097]
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.
ORA-600 [4097] “Corruption”
ORA-600[4000]
ORA-00600[4000]
It means that Oracle has tried to find an undo segment number in the dictionary cache and failed.
ORA-600 [4000] “trying to get dba of undo segment header block from usn”
ORA-600 [6006]
ORA-00600 [6006]
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.
ORA-600 [6006]
ORA-600 [4552]
ORA-00600 [4552]
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.
ORA-600 [4555]
ORA-600[6856]
ORA-00600[6856]
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.
ORA-600 [6856] Corrupt Block When Freeing a Row Slot
ORA-600 [13011]
ORA-00600 [13011]
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.
ORA-600 [13011] “Problem occurred when trying to delete a row”
ORA-600 [13013]
ORA-00600 [13013]
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.
ORA-600 [13013] “Unable to get a Stable set of Records”
How to resolve ORA-00600 [13013], [5001]
ORA-600 [25012]
ORA-00600 [25012]
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. afn/rdba/tsn
ORA-600 [25012] “Relative to Absolute File Number Conversion Error”
ORA-600 [25026]
ORA-00600 [25026]
Looking up/checking a tablespace
invalid tablespace ID and/or rdba found
afn/rdba/tsn
ORA-600 [25027]
ORA-00600 [25027]
Invalid tsn and/or rfn found
afn/rdba/tsn
ORA-600 [kcbz_check_objd_typ]
ORA-00600 [kcbz_check_objd_typ]
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]
ORA-600[kdblkcheckerror]
ORA-00600[kddummy_blkchk]
ORA-00600[kdblkcheckerror]
ORA-600[kddummy_blkchk] is for 10.1/10.2 and ORA-600[kdblkcheckerror] for 11 onwards. Block
ORA-600 [kddummy_blkchk]
How to Resolve ORA-00600[kddummy_blkchk]
ORA-600 [kdblkcheckerror]
QREF – kddummy_blkchk / kdBlkCheckError – Check Codes Listing (Full) [This section is not visible to customers.]
QREF – kddummy_blkchk / kdBlkCheckError – Check Codes Definition && Return Values[This section is not visible to customers.]
ORA-600[ktadrprc-1]
ORA-00600[ktadrprc-1]
Dictionary problem
ORA-600 [ktsircinfo_num1]
ORA-00600 [ktsircinfo_num1]
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$.
ORA-600 [qertbfetchbyrowid]
ORA-00600 [qertbfetchbyrowid]
Row problem
ORA-600 [ktbdchk1-bad dscn]
ORA-00600 [ktbdchk1-bad dscn]
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.
ORA-600 [ktbdchk1: bad dscn]