Re: Shutdown of one instance takes about 1hr

On Feb 2, 12:20 pm, "gazzag" <gar..._at_jamms.org> wrote:
> On 31 Jan, 13:08, Alexander Skwar <alexan..._at_skwar.name> wrote:
>
>
>
>
>
> > Hello!
>
> > Each night, we shutdown the Oracle 9.2.0.4.0 databases on our
> > Solaris 9 host. I now noticed, that it takes about 1 hour for
> > a certain instance to shutdown:
>
> > SQL*Plus: Release 9.2.0.4.0 - Production on Wed Jan 31 02:55:56 2007
>
> > Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
>
> > SQL> Connected.
> > SQL> ORA-01013: user requested cancel of current operation
> > SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
> > JServer Release 9.2.0.4.0 - Production
> > Database "RACEREF1" shut down.
>
> > SQL*Plus: Release 9.2.0.4.0 - Production on Wed Jan 31 03:57:44 2007
>
> > To shutdown, I use the Oracle supplied dbshut script, which simply
> > does a "shutdown" after having connected with "connect / as sysdba".
> > Obviously, I don't run those commands manually, but have a cron
> > job setup, which runs dbshut and 15 seconds after it finishes, it
> > runs dbshut again. Actually, it does:
>
> > su - oracle -c "ORACLE_HOME=$ORACLE_HOME $ORACLE_HOME/bin/lsnrctl stop
> > ORACLE_HOME=$ORACLE_HOME $ORACLE_HOME/bin/dbshut"
>
> > Anyway, when it shuts down the databases for the 2nd time, it again
> > takes about 1 hour to do the shutdown.
>
> > But is the shutdown actually successful? I wonder because of the
> > message
>
> > ORA-01013: user requested cancel of current operation
>
> > Further, when I startup the databases again, I see this in the logs:
>
> > SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
> > JServer Release 9.2.0.4.0 - Production
>
> > Database "RACEP1" warm started.
> > Database "RACEREF1" already started.
>
> > Database "RACEREF1" possibly left running when system went down (system crash?).
> > Notify Database Administrator.
>
> > SQL*Plus: Release 9.2.0.4.0 - Production on Wed Jan 31 05:00:58 2007
>
> > The system did not go down. At noon today, I manually shutdown the
> > database, and that was very fast (a few seconds). It also came up just
> > fine (ie. no message).
>
> > What's happening there?
>
> > Alexander Skwar
>
> To my knowledge, Oracle recommends that the dbstart and dbshut scripts
> are only used by the system boot procedure. As a matter of interest,
> why do you need to shut the database every night?- Hide quoted text -
>
> - Show quoted text -

It doesn't matter what recommends. Automating the system so that the database starts and stop automatically is a dangerous practice.

Did up Nuno Soto's feelings on that subject if necessary.

Anyone ever see a storage administrator go a little crazy re-booting systems multiple times when faced with storage problems.

What's the impact on a ( formerly ) operational database if that happens. Received on Fri Feb 02 2007 - 17:55:35 CST