Re: suspicious standard Oracle Linux start/stop script

"Tanel Poder" <tanel@@peldik.com> wrote in message news:<3ed654c8$1_1_at_news.estpak.ee>...
> > If I'm worried about SHUTDOWN IMMEDIATE hanging, then my script does a
> > SHUTDOWN ABORT, followed by a STARTUP RESTRICT, and then a SHUTDOWN
> > IMMEDIATE. No problems...

Unless you are using something that requires a huge cleanup at startup... :-(

>
> Do you have an example of that script?
> What I'm saying (and you can't argue it) - you can't predict everything.
>
> And if something unpredicted happens, such sqlplus can't be started for some
> odd reason (someone has changed env for example), what will your script do
> then? Terminate, to allow shutdown to proceed? Or just hang there?
>
> Do whatever you want at home or in your test environment, but in production
> you should have so rare reboots anyway, that you can afford doing that one
> extra step to manually shut down db *and deal with any unexpected
> conditions*.

For unix, given my druthers, I like the concept of run levels - you have the application at a level, the db at a level, and so on. Then for each level, you have a shutdown script that handles most common situations (ie, kills off app/sqlnet processes, nicely shuts down lsnrctl and dbsnmp, etc). You manually switch levels. If you have a hang at any level, then you can deal with it without having locked yourself out. For the startup, you can assume a powerfailure/reboot or normal scenario to bring to a full run level, or manually switch levels (ie, if HW maintenance is repeatedly bouncing the system, you don't want dbstart running). If you've crashed because you've blown certain hardware, you're TSOL anyways and it won't make a difference.

The most important thing if you have more than one admin, is that everyone signs off on the procedures and sticks to them.

>
> A lot of people (including me) won't put db start up scripts to init.d,
> because in case of crash for example *you* want to be in control, not some
> script which is designed only for certain circumstances.

Too often it's someone who, um, accidently leaves his pager where he can't hear it at night :-)

>
> Tanel.
>
>
> >
> > Why would I be unable to connect as SYSDBA?
> >
> > And in the case of a crash, who has time to manually shutdown a
> > database?
> >
> >
> > Cheers,
> > Brian
> >
> >
> > --
> > ===================================================================
> >
> > Brian Peasland
> > oracle_dba_at_remove_spam.peasland.com
> >
> > Remove the "remove_spam" from the email address to email me.
> >
> >
> > "I can give it to you cheap, quick, and good. Now pick two out of
> > the three"

jg

--
@home.com is bogus.
http://www.signonsandiego.com/news/uniontrib/thu/business/news_1b29tech.html