Re: Bringing down Oracle in a script.

HansF wrote:
> On Tue, 26 Jul 2005 16:53:40 -0700, Arthur Salazar interested us by
> writing:
>
> > I am writing a script that will bring Oracle 9i or 10g up or down.
> >
> > Generally I reverse my actions to bring the services down. I notice that
> > after I bring things down that there are occationally processes left
> > around that appear to be part of Oracle or are at least owned by
> > oracle.
> >
> > Can I safely kill these? Should they even be left around?
> >
> > Any thoughts would be appreiciated.
> >
>
> First thought - assuming you are using a *nix ... use dbstart and dbshut
> instead of writing your own.

Hans, are you using an unmodified dbshut on *nix? Is it really working the way you expect?

To me, dbstart is fine, but dbshut is wrong for system shutdowns, and only works if there is some rc timeout that kills it. Plain old shutdown in there, you know... maybe it's been so long since I've used it that I've missed something? I used to always modify it to work, but the past few years just make it a manual procedure to shut oracle down cleanly, let crash recovery do its thing if some emergency requires down hardware. For the odd off-hour cold backup or damager wants, a script that kills user processes, shuts agent, listener, then dbshut seems to work ok, though I can imagine situations where it wouldn't.

Windows is another story, and less happy.

jg

-- 
@home.com is bogus.
http://www.takeourword.com/images/