RE: ORA-00600: internal error code, arguments: [4000], [6],
- From: "Jeremiah Wilton" <jwilton@xxxxxxxxxxxxx>
- To: <anelson77388@xxxxxxxxx>, <Arvind.Kumar@xxxxxxxxxxxxx>
- Date: Thu, 12 Mar 2009 11:41:25 -0700
On Thu, Mar 12, 2009 at 6:43 AM Allan Nelson <anelson77388@xxxxxxxxx> wrote:
> Metalink Doc Id 47456.1 says this is a very serious error and to contact
Oracle
> if the database won't start
>
> On Thu, Mar 12, 2009 at 4:29 AM, Arvind Kumar <Arvind.Kumar@xxxxxxxxxxxxx>
wrote:
> >
> > 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], [], [], [], [],
[], []
This is indeed a serious error (not all ORA-600 errors are). I encountered
this error back on 7.3.2.3 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.
http://www.bluegecko.net
Remote Database Administration
--
//www.freelists.org/webpage/oracle-l
Other related posts:
