Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Shutdown problem

Re: Shutdown problem

From: Dan Benwell <danbenwell_at_dial.pipex.com>
Date: Fri, 26 Jun 1998 15:46:49 +0100
Message-ID: <3593B458.B88DA0E0@dial.pipex.com>


Try a shell script like this

svrmgrl << EOF
connect internal
shudown immediate
EOF sleep 30

svrmgrl << EOF
connect internal
shutdown abort
startup
shutdown
EOF This works all the time for me.

Alfons Riesebeek wrote:

> Confessions ?
>
> Oke I also did it.
>
> But first I tried a shutdown immediate as a backgroud process (&).
> Then I told the script to wait for a while (sleep) .
> If after a while if the database was still running I started a
> process which did a shutdown abort.
>
> Note: If you are killing Unix processes you should also look at the parent/child
> proceses and at the processes/sessions within Oracle.
>
> Regards,
> Alfons
>
> shreterh_at_my-dejanews.com schrijfbewerkingen: > Confession: I'm doing the same thing as the original author (shutdown abort /
> > startup / shutdown). I changed it one day to "immediate" and was immediately
> > rewarded with a hung backup and angry sys admin/helpline.
> >
> > Is there an alternative? Look for running processes against Oracle
> > (LOCAL=NO; LOCAL=YES) and kill them, letting Oracle groom itself afterward?
> > What can we do between ABORT and IMMEDIATE that gets the job done?
> >
> > Appreciate in advance any suggestions. - Hilary Shreter.
> >
> > In article <6mlq97$h93$1_at_hdxf08.telecom.ptt.nl>,
> > Alfons Riesebeek <A.Riesebeek_at_wxs.nl> wrote:
> > >
> > > You should do a shutdown immediate. In this way Oracle rolls back
> > > actions of processes with are still running before killing them.
> > >
> > > In most cases this works fine. Never do a shutdown abort !!
> > >
> > > Regards,
> > > Alfons Riesebeek
> > >
> > > Gilberto Casiraghi <edipi_at_candy.it> schrijfbewerkingen: > Hello all !
> > ...
> > > > shutdown hanging (it seems incredible but it's true).
> > > > To avoid this situation I change the shutdown script in this way:
> > > > alter system checkpoint
> > > > shutdown abort
> > > > startup
> > > > shutdown
> > > > So the db will be ALWAYS closed and with the checkpoint I don't
> > > > lose any data (I hope!).
> > > > What do you think about it ? Is there a better way ? (I want to be SURE
> > > > the shutdown CLOSE the db, so the backup procedure can end rightly).
> > > > Any suggestion it will be appreciated.
> > > >
> > > > Thanks in advanced.
> > > > Gilberto Casiraghi.
> > > >
> > >
> > >
> >
> >
> > -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> > http://www.dejanews.com/ Now offering spam-free web-based newsreading
Received on Fri Jun 26 1998 - 09:46:49 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US