Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Shutdown of one instance takes about 1hr
On Jan 31, 8:08 am, 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
A normal shutdown waits for all connected sessions to exit. You will probably get much faster results if you use a shutdown immediate.
# set Oracle environment
sqlplus /nolog <<EOF
connect / as sysdba
shutdown immediate
exit
EOF
HTH -- Mark D Powell --
Received on Wed Jan 31 2007 - 07:24:22 CST