Re: Shutdown problem

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 Tue Jun 23 1998 - 00:26:36 CDT