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: Best way to handle Oracle shutdowns from Unix script

Re: Best way to handle Oracle shutdowns from Unix script

From: Chuck Hamilton <Xchuckh_at_dvol.com>
Date: 1997/10/14
Message-ID: <01bcd8c2$b7c00100$269014ce@hamilton.qvc.com>#1/1

Steve Walterhouse <microcon_at_magicnet.net> wrote in article <3442FB37.7AEB_at_magicnet.net>...
> question 2: exp help=yes
>
> question 1: write a script to capture process id(s) of active Oracle
> connections - $pid=`ps -ef | grep oracle<SID> | cut <options>`
>
> then superuser kill those process ids,
> then shutdown normal.
>
> This works better than doing a shutdown immediate every time you
> shutdown. If you shutdown immediate time after time, eventually you run
> into problems.
>

I wouldn't do it with my database! By killing oracle background processes this way you're just asking for trouble. A better way is to:

  1. shutdown abort
  2. startup in restricted mode
  3. shutdown immediate or normal

This will kill all active connections, rollback open transactions, and put the database into a consistent state so it can be backed up cold. Received on Tue Oct 14 1997 - 00:00:00 CDT

Original text of this message

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