Re: Debate on rc commands Solaris and Oracle

I'll echo that sentiment.

'shutdown abort', 'startup restrict' was a regular part of my shutdown scripts beginning in 1994 with 7.0.16, as 'shutdown immediate' wasn't all that reliable, even in situations where it should have worked.

Jared

On Wednesday 29 January 2003 15:53, John Kanagaraj wrote:
> Rao,
>
> And where did you read that 'shutdown abort' is not recommended? This is
> another myth that has been busted a while ago. A shutdown abort followed by
> a startup restrict and a normal shutdown is the way to go when dealing with
> rogue sessions that open a connection and never shutdown. In such cases, a
> shutdown immediate will _never_ return (certainly not within your 5 to 10
> minutes). I have been using this method for more than 8 years now -
> starting at 7.0.16 fyi. The trick in this case is to script it into the rc
> commands.
>
> John Kanagaraj
> Oracle Applications DBA
> DBSoft Inc
> (W): 408-970-7002
>
> I don't know what the future holds for me, but I do know who holds my
> future!
>
> ** The opinions and statements above are entirely my own and not those of
> my employer or clients **
>
>
> -----Original Message-----
> Sent: Wednesday, January 29, 2003 11:49 AM
> To: Multiple recipients of list ORACLE-L
>
>
> Paula,
>
> Shutdown abort is not recommended as the file checkpointing is not done
> during shutdown abort. If you need to perform shutdown abort, then, it is
> preferred to bring up the db with startup restrict (so that the users
> wouldn't connect) and then, cleanly shutdown the db and bring it up again.
>
> Tell to your sys admins. that shutdown immediate would take some time
> (about 5 to 10 minutes) depending on the activity on your db. They would
> have to wait for that much time before calling a DBA during system boots.
>
> Rao
>
> -----Original Message-----
> Sent: Wednesday, January 29, 2003 11:30 AM
> To: Multiple recipients of list ORACLE-L
>
>
>
> System Administrator says he doesn't trust that the rc commands will stop
> if the database doesn't want to shutdown and even if it does would want to
> shutdown with scripts beforehand so that a DBA could connect and resolve
> the issue. Other DBA says this is all wrong and rc commands should include
> shutdown immediate of database. In the past I had setup 2 processes in the
> system scripts for the sys admin - shutdown immediate - wait .... shutdown
> abort - on a read-only DSS system which of course allows some room for this
> type of activity. I kind of would want to know if a database was going to
> be shutdown with an abort esp. in OLTP system and do it myself.
>
>
>
> - any ideas

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jared Still
  INET: jkstill_at_cybcon.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).