Path: utzoo!attcan!uunet!jarthur!nntp-server.caltech.edu!mustang!topgun!lll-winken!sun-barr!cs.utexas.edu!hellgate.utah.edu!cc.utah.edu!inel.gov!gem-hy!cdm
From: cdm@gem-hy.Berkeley.EDU (Dale Cook)
Newsgroups: comp.databases
Subject: Re: Oracle crashes
Keywords: help oracle startup shutdown
Message-ID: <1990Oct9.223927.10795@inel.gov>
Date: 9 Oct 90 22:39:27 GMT
References: <25244@sequoia.execu.com> <19503@frog.UUCP>
Sender: news@inel.gov
Reply-To: cdm@gem-hy.Berkeley.EDU (Dale Cook)
Organization: Idaho National Engineering Laboratory, Idaho Falls, Idaho
Lines: 52

In article <19503@frog.UUCP>, barr@frog.UUCP (Chris Barr) writes:
|> In article <25244@sequoia.execu.com>, bob@sequoia.execu.com (Bob
Kieras) writes:
|> > 
|> >     We are running Ultrix-32 V3.1 (Rev. 9) on a Microvax 3600 and
|> >     ORACLE RDBMS V6.0.27.9.1 and we have encountered a problem.
|> >     If the machine is shutdouwn using the shutdown command without
|> >     shutting oracle down first, the database cannot be restarted. 
|> > 	 Unexpected oracle server termination by signal 6
|> >     ( Core is dumped and oracle crashed.)
|> 
|> Under Unix, a different message appears at restart, but the solution is
|> to first delete the ORACLE_HOME/dbs/sgadef{SID}.dbf file, then startup
|> will recover.  This might work for VMS - it works under Unix even when
|> the plug was pulled.
|> 
|> >     I have traced the problem to the database control file, 
|> >     /usr/oracle/dbs/cntrlora6.dbf where "ora6" is the instance name.
|> >     This file is either broken or left in a state incompatible with 
|> >     restarting the database. 
|> 
|> Use at least 2 controlfiles, specified at create time and in init.ora.
|> They are kept identical - except in case of disk crash or, perhaps, your
|> poweroff, in which case you'll have two to explore ...
|> 
|> Chris Barr
|> !frog!barr


This is a serious problem, folks.  When we had the problem (we use ULTRIX) and 
called Oracle support, the analyst was suprised we were able to bring the 
database back up.  I would highly recommend getting the fix from Oracle to 
bring yourself up to V6.0.27.9.2 - or you may find yourself rebuilding the
database next time it happens.

--- Dale Cook (EG&G Idaho)


Neither the United States Government nor the Idaho National
Engineering Laboratory nor any of their employees, makes any warranty,
expressed or implied, or assumes any legal liability or responsibility
for the accuracy, completeness, or usefulness of any information,
product, or process disclosed, or represents that its use would not
infringe privately owned rights.  Reference herein to any specific
commercial products, process, or service by trade name, trademark
manufacturer, or otherwise, does not necessarily constitute or imply
its endorsement, recommendation, or favoring by the United States
Government or the Idaho National Engineering Laboratory.  The views and
opinions of authors expressed herein do not necessarily state or reflect
those of the United States Government nor the Idaho National Engineering
Laboratory, and shall not be used for advertising or product endorsement
purposes.