分类: Oracle
2010-03-31 17:16:03
ORA-600 [4000] "trying to get dba of undo segment header block from usn" [ID 47456.1] | |||||
| |||||
Modified 05-MAR-2010 Type REFERENCE Status PUBLISHED |
Note: For additional ORA-600 related information please read PURPOSE: This article discusses the internal error "ORA-600 [4000]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [4000] [a] VERSIONS: version 6.0 to 9.2 DESCRIPTION: This has the potential to be a very serious error. It means that Oracle has tried to find an undo segment number in the dictionary cache and failed. ARGUMENTS: Arg [a] Undo segment number FUNCTIONALITY: KERNEL TRANSACTION UNDO IMPACT: INSTANCE FAILURE - Instance will not restart STATEMENT FAILURE SUGGESTIONS: As per , this can be seen when executing DML on tables residing in tablespaces transported from another database. It is fixed in 8.1.7.4, 9.0.1.4 and 9.2.0.1 The workaround however is to create more rollback segments in the target database until the highest rollback segment number (select max(US#) from sys.undo$;) is at least as high as in equivalent max(US#) from the source database. It has also been seen where memory has been corrupted so try shutting down and restarting the instance. If the database will not start contact Oracle Support Services immediately, providing the alert.log and associated trace files. KNOWN ISSUES:
Known Bugs
NB Bug Fixed Description * 11.2.0.2, 12.1 OERI[25027]/OERI[4097]/OERI[4000] in plugged datafile after CREATE CONTROLFILE in 11g See 11.1.0.6 OERI [4000] during startup 9.2.0.5, 10.1.0.2 STARTUP after an ORA-701 fails with OERI[4000] 9.2.0.5, 10.1.0.2 OERI[4000] / index corruption can occur during index coalesce 8.1.7.4, 9.0.1.4, 9.2.0.1 OERI:4506 / OERI:4000 possible against transported tablespace + 7.3.4.2, 8.0.3.0 ORA-600[4000] from altering storage of BOOTSTRAP$