Re: ORA-00600: internal error code, arguments: [4000], [6],

From: Allan Nelson <anelson77388_at_gmail.com>
Date: Thu, 12 Mar 2009 08:42:56 -0500
Message-ID: <ffb96860903120642s1572a491r52931f86d9aa07c7_at_mail.gmail.com>



Metalink Doc Id* 47456.1 says this is a very serious error and to contact Oracle if the database won't start

 ***Subject: *ORA-600 [4000] "trying to get dba of undo segment header block from usn"* Doc ID: *47456.1* Type: *REFERENCE* Modified Date: * 03-APR-2008* Status: *PUBLISHED*

Note: For additional ORA-600 related information please read Note 146580.1 <https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=146580.1&blackframe=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:
  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
<https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=1371820.8&blackframe=1>, 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:   Bug# 3115733 See Note 3115733.8
<https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=3115733.8&blackframe=1>

      OERI[4000] / index corruption can occur during index coalesce
      Fixed: 9.2.0.5, 10.1.0.2

  Bug# 2959556 See Note 2959556.8
<https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=2959556.8&blackframe=1>

      STARTUP after an ORA-701 fails with OERI[4000]
      Fixed: 9.2.0.5, 10.1.0.2

  Bug# 2917441 See Note 2917441.8
<https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=2917441.8&blackframe=1>

      OERI [4000] during startup
      Fixed: 11.1.0.6

  Bug# 1371820 See Note 1371820.8
<https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=1371820.8&blackframe=1>

      OERI:4506 / OERI:4000 possible against transported tablespace
      Fixed: 8.1.7.4, 9.0.1.4, 9.2.0.1

  Bug# 434596 + See Note 434596.8
<https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=434596.8&blackframe=1>

      ORA-600[4000] from altering storage of BOOTSTRAP$
      Fixed: 7.3.4.2, 8.0.3.0


  Bug 1362499 <https://metalink.oracle.com/metalink/plsql/showdoc?db=Bug&id=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

.

On Thu, Mar 12, 2009 at 4:29 AM, Arvind Kumar <Arvind.Kumar_at_labour.gov.za>wrote:

> Hi All,
>
>
>
> Trying to restore production database into a new box. While startup the
> database it returns following error in alert.log
>
>
>
> Errors in file /recov2/SIYPROD/admin/udump/siydev3_ora_4047.trc:
>
> ORA-00600: internal error code, arguments: [4000], [6], [], [], [], [], [],
> []
>
> Thu Mar 12 10:29:17 2009
>
> Errors in file /recov2/SIYPROD/admin/udump/siydev3_ora_4047.trc:
>
> ORA-00704: bootstrap process failure
>
> ORA-00704: bootstrap process failure
>
> ORA-00600: internal error code, arguments: [4000], [6], [], [], [], [], [],
> []
>
> Thu Mar 12 10:29:17 2009
>
> Error 704 happened during db open, shutting down database
>
> USER: terminating instance due to error 704
>
> Instance terminated by USER, pid = 23851
>
> ORA-1092 signalled during: alter database open...
>
>
>
> And trace in udump
>
>
>
> /recov2/SIYPROD/admin/udump/siydev3_ora_4074.trc
>
> Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
>
> With the Partitioning, OLAP and Oracle Data Mining options
>
> JServer Release 9.2.0.4.0 - Production
>
> ORACLE_HOME = /u300/app/oracle/product/9.2.0
>
> System name: SunOS
>
> Node name: p0
>
> Release: 5.9
>
> Version: Generic_117171-17
>
> Machine: sun4us
>
> Instance name: SIYDEV3
>
> Redo thread mounted by this instance: 1
>
> Oracle process number: 10
>
> Unix process pid: 4074, image: oracle_at_p0 (TNS V1-V3)
>
>
>
> *** SESSION ID:(7.3) 2009-03-12 10:29:17.374
>
> *** 2009-03-12 10:29:17.374
>
> *** 2009-03-12 10:32:15.354
>
> ksedmp: internal or fatal error
>
> ORA-00600: internal error code, arguments: [4000], [6], [], [], [], [], [],
> []
>
> Current SQL statement for this session:
>
> select ctime, mtime, stime from obj$ where obj# = :1
>
> ----- Call Stack Trace -----
>
> .
>
>
>
> Any pointer/help will be much appreciated.
>
>
>
> Thanks & Regards,
> Arvind Kumar
>
>
>
>
>
> Disclaimer
> This e-mail and any attachments transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom it is
> addressed. If you have received this e-mail in error please notify the
> sender and delete the original message. Any views or opinion expressed in
> this e-mail are those of the author and do not necessarily represent those
> of the Department of Labour. The recipient should check this e-mail and any
> attachments for the presence of viruses and other destructive codes. While
> all possible precautions have been taken, the Department accepts no
> liability whatsoever for loss or damage resulting from the opening of this
> message or attachments, or the use of the information contained in this
> message or attachment.
>

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Mar 12 2009 - 08:42:56 CDT

Original text of this message