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

From: Jeremiah Wilton <>
Date: Thu, 12 Mar 2009 11:41:25 -0700
Message-ID: <006901c9a342$26305300$7290f900$_at_net>

On Thu, Mar 12, 2009 at 6:43 AM Allan Nelson <> wrote:

> Metalink Doc Id 47456.1 says this is a very serious error and to contact
> if the database won't start
> On Thu, Mar 12, 2009 at 4:29 AM, Arvind Kumar <>
> > 
> > Trying to restore production database into a new box. While startup the
> > 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], [], [], [], [],
[], []

This is indeed a serious error (not all ORA-600 errors are). I encountered this error back on when someone changed MAXEXTENTS on SYS.BOOTSTRAP$. The change had been made several weeks back, so backups were not an option for repairing the problem. The eventual response from Oracle was to escalate to BDE, who logged in remotely manually patched data blocks in file 1.

At this point I would be concerned about the source (production) system you are cloning from. If the problem is also present in the source copy, it may not restart if you shut it down. You might want to export some data if you can before you try restarting.

This should be in the hands of Oracle Support.

Jeremiah Wilton
Blue Gecko, Inc.
Remote Database Administration

Received on Thu Mar 12 2009 - 13:41:25 CDT

Original text of this message