ORA-600 [4000] trying to get dba of undo segment header block from usn-47456.1

rongshiyuan發表於2013-01-23
HeaderBloC
ORA-600 [4000] "trying to get dba of undo segment header block from usn" [ID 47456.1]
 
Note: For additional ORA-600 related information please read Note:146580.1 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:
Format: 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 Note 1371820.8, 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
You can restrict the list below to issues likely to affect one of the following versions by clicking the relevant button:



NBBugFixedDescription
1391019011.2.0.4, 12.1.0.0ORA-600 [4000] from plugged in tablespace in Exadata V11020001 V11020002 V11020003 EXADATA OERI TRANSPORT
*914554111.1.0.7.4, 11.2.0.1.2, 11.2.0.2, 12.1.0.0OERI[25027]/OERI[4097]/OERI[4000]/ORA-1555 in plugged datafile after CREATE CONTROLFILE in 11g V11010006 V11010007 V11020001 CORR/LOG ERROR OERI RMAN TRANSPORT
+1042501011.2.0.3, 12.1Stale data blocks may be returned by Exadata FlashCache V11020001 V11020002 CORR/PHY EXADATA OERI WRONGRES
M1474172712.1.0.0Fixes for bug 12326708 and 14624146 can cause problems - backout patch V11020002 CORR/PHY NEEDSUPDATE OERI OPS
12353983ORA-600 [4000] with XA in RAC V11010006 V11010007 OERI OPS XA
768785611.2.0.1ORA-600 [4000] from DML on transported ASSM tablespace V10020002 V10020003 V10020004 V10020005 V11010006 V11010007 BITSEG OERI TRANSPORT
291744111.1.0.6OERI [4000] during startup V09020008 V10010005 V10020002 V10020003 V10020004 V10020005 OERI STARTUP
31157339.2.0.5, 10.1.0.2OERI[4000] / index corruption can occur during index coalesce CORR/IND OERI
29595569.2.0.5, 10.1.0.2STARTUP after an ORA-701 fails with OERI[4000] OERI STARTUP
13718208.1.7.4, 9.0.1.4, 9.2.0.1OERI:4506 / OERI:4000 possible against transported tablespace OERI TRANSPORT
+4345967.3.4.2, 8.0.3.0ORA-600[4000] from altering storage of BOOTSTRAP$ ERROR OERI
  • '*' 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.
  • Fixed versions use "BPnn" to indicate Exadata bundle nn.
  • "OERI:xxxx" may be used as shorthand for ORA-600 [xxxx].





  Bug 1362499
      ORA-600 [4000] after migrating 7.3.4.3 to 8.0.6.1 on HP-UX 32-bit
      Specific to HP-UX, fixed in one-off patch









來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/17252115/viewspace-753113/，如需轉載，請註明出處，否則將追究法律責任。







相關文章