Re: Problem in shutting down database

The SHUTDOWN NORMAL command will work well (and quickly) as long as
all of the other sessions
have (through some means) disconnected.  Otherwise, I always go with
SHUTDOWN NORMAL.

Now, there was a time (back in the 7.2 or 8.0 days?) where there was a
bug with SHUTDOWN
IMMEDIATE (on some platforms).  As I recall, the workaround was to do:

SHUTDOWN ABORT
STARTUP
SHUTDOWN NORMAL

That bug hasn't been around for some time (although that procedure has
become standard practice
in some shops as a result).

Personally, SHUTDOWN IMMEDIATE has almost always been the way to go.
Note that IMMEDIATE
DOES wait for pending transactions to complete (commit or rollback).
It just doesn't expect that all of
the sessions will "kindly leave the room".

-- James
----------------------------------------------------------------------
James J. Morrow | Senior Oracle Applications DBA | TriOra Group, LLC
morrow.james <at> gmail <dot> com
james.morrow <at> trioragroup <dot> com




On Mon, Feb 16, 2009 at 11:20 AM, Tipton, Josh
<Josh.Tipton@xxxxxxxxxxxxxx> wrote:
> Preclone do a shutdown immediate, startup restrict, shutdown.
>
>
>
> ________________________________
>
> From: ora-apps-dba-bounce@xxxxxxxxxxxxx
> [mailto:ora-apps-dba-bounce@xxxxxxxxxxxxx] On Behalf Of Mostafa Eletriby
> Sent: Monday, February 16, 2009 11:19 AM
> To: ora-apps-dba@xxxxxxxxxxxxx
> Subject: Re: Problem in shutting down database
>
>
>
> Dear James,
>
>
>
> Thanks for your quick reply. this is excellent clarification.
>
> I used to use only shutdown normal when performing a pre-clone phase which I
> have to shutdown the database by this way.
>
> Thanks alot.
>
>
>
> Good Day
>
> Regards,
>
> Mostafa
>
>
>
>
>
>
>
>
>
>
>
>
>
> --- On Mon, 2/16/09, James Morrow <morrow.james@xxxxxxxxx> wrote:
>
> From: James Morrow <morrow.james@xxxxxxxxx>
> Subject: Re: Problem in shutting down database
> To: ora-apps-dba@xxxxxxxxxxxxx
> Date: Monday, February 16, 2009, 12:05 PM
>
> It appears that there is still a session connected to the database.
>
> This is the normal behavior for SHUTDOWN NORMAL.
>
>
>
> While shutting down the various E-Business Suite services (concurrent
>
> managers, forms,
>
> apache, etc.) does actually kill off user sessions, merely shutting
>
> down the SQL*Net (Net8) listener
>
> doesn't terminate any active [network] connections. It merely prevents
>
> new [network] ones from being created.
>
>
>
> NOTE:  I pretty much always use "SHUTDOWN IMMEDIATE" instead of
>
> "SHUTDOWN NORMAL".  The
>
> "SHUTDOWN NORMAL" command not only waits for all transactions to
>
> complete, but it waits for all users
>
> to be nice enough to log out on their own.  The "SHUTDOWN IMMEDIATE"
>
> command will wait for transactions
>
> to complete and then kick the users out.  "SHUTDOWN IMMEDIATE" is a
>
> normal "graceful" shutdown procecdure
>
> (not something to be afraid of).  (This isn't to be confused with
>
> "SHUTDOWN ABORT" which basically "crashes"
>
> the instance).
>
>
>
> -- James
>
> ----------------------------------------------------------------------
>
> James J. Morrow | Senior Oracle Applications DBA | TriOra Group, LLC
>
> morrow.james <at> gmail <dot> com
>
> james.morrow <at> trioragroup <dot> com
>
>
>
>
>
>
>
>
>
> On Mon, Feb 16, 2009 at 10:29 AM, Mostafa Eletriby <m_etrib@xxxxxxxxx>
>
> wrote:
>
>> Hi DBAs,
>
>>
>
>> Please I need a clarification and a solution for this current status.
>
>> many times when I shutdown the database normal shutdown after connecting
>
> as
>
>> sysdba & executing shutdown to be normal shutdown, the the session
>
> hangs and
>
>> waiting for active processes to be completed, this can be for hours then
>
>> fail to shutdown normal  then I have to shutdown immediate then
>
> performing
>
>> normal shutdown and it ends cleanly Or I restart the server.
>
>>
>
>> Also there is no active connection running and no user logging into
>
>> application, coz the middle tier is down.
>
>>
>
>> Operating system: Win 2000
>
>> Instance:  11.5.10.2
>
>> Database: 9.2.0.8
>
>> Is this a bug?
>
>>
>
>> this is the current status. Anyone has idea, permanet solution?
>
>>
>
>> Mon Feb 16 17:29:18 2009
>
>> Beginning log switch checkpoint up to RBA [0x291a9.2.10], SCN:
>
>> 0x0000.d5d338b1
>
>> Thread 1 advanced to log sequence 168361
>
>>   Current log# 3 seq# 168361 mem# 0:
>
> F:\ORACLE\PRODDATA\LOG03A.DBF
>
>>   Current log# 3 seq# 168361 mem# 1:
>
> F:\ORACLE\PRODDATA\LOG03B.DBF
>
>> Mon Feb 16 17:56:55 2009
>
>> Completed checkpoint up to RBA [0x291a9.2.10], SCN: 0x0000.d5d338b1
>
>> Mon Feb 16 17:57:58 2009
>
>> Shutting down instance: further logons disabled
>
>> Shutting down instance (normal)
>
>> License high water mark = 304
>
>> Mon Feb 16 18:02:58 2009
>
>> Active process 4680 user 'exora' program 'ORACLE.EXE'
>
>> Active process 5068 user 'exora' program 'ORACLE.EXE'
>
>> Active process 5556 user 'exora' program 'ORACLE.EXE'
>
>> Active process 5576 user 'exora' program 'ORACLE.EXE'
>
>> Active process 6208 user 'exora' program 'ORACLE.EXE'
>
>> Active process 5760 user 'exora' program 'ORACLE.EXE'
>
>> Active process 812 user 'exora' program 'ORACLE.EXE'
>
>> Active process 5168 user 'exora' program 'ORACLE.EXE'
>
>> SHUTDOWN: waiting for logins to complete.
>
>>
>
>> Thanks alot
>
>> Good Day
>
>> Regards,
>
>>
>
>>
>
>>
>
>
>
>
>
> ******************************************************************************
> This email contains confidential and proprietary information and is not to
> be used or disclosed to anyone other than the named recipient of this email,
> and is to be used only for the intended purpose of this communication.
> ******************************************************************************

Other related posts: