bob@sequoia.execu.com (Bob Kieras) (10/02/90)
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.
When we attempt to restart the database, we get the following error
while using the SQLDBA program :
SQLDBA> startup
ORACLE instance started
Database mounted
Unexpected oracle server termination by signal 6
%
( Core is dumped and oracle crashed.)
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. Rebuilding the database and thereby replacing
the control file fixes the problem. Obviously, we can always have
"shutdown" shutdown the database first but if the machine ever crashes,
the databse will be creamed. Does anyone out there know of an oracle
utility that "fixes" control files ?
thanks in advance
Bob Kierassharnyo@.com (Suwandi Harnyo) (10/03/90)
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. > When we attempt to restart the database, we get the following error > while using the SQLDBA program : > > SQLDBA> startup > ORACLE instance started > Database mounted > Unexpected oracle server termination by signal 6 > % > ( Core is dumped and oracle crashed.) > > 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. Rebuilding the database and thereby replacing > the control file fixes the problem. Obviously, we can always have > "shutdown" shutdown the database first but if the machine ever crashes, > the databse will be creamed. Does anyone out there know of an oracle > utility that "fixes" control files ? > > thanks in advance > Bob Kieras Bob, This is a known problem and Oracle has a fix for it. Call the technical support line. -Andi
barr@frog.UUCP (Chris Barr) (10/04/90)
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
cdm@gem-hy.Berkeley.EDU (Dale Cook) (10/10/90)
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.