Depending on the version (8.0 and lower), Oracle creates a file
called sgadef$ORACLE_SID.dbf. If you manually kill the process
you should remove the file. As per the lk$ORACLE_SID file it
shouldn't matter if is there or not but I always do a shutdown
abort after a crash to be sure all the resources are free
(shared memory, semaph, etc)
bchorng_at_yahoo.com (Bass Chorng) wrote in message news:<bd9a9a76.0201171433.3cec5a21_at_posting.google.com>...
> ilker_at_hiperaktif.com (ilker ARABACI) wrote in message news:<6fcdbf89.0201160951.72d250c6_at_posting.google.com>...
> > Hi,
> >
> > At some cases sqlplus connot terminate oracle
> > shutdown / shutdown immidiate hanges up my system
> > so I tried to kill the oracle process and restart oracle
> >
> > but whenever I restart , and reconnect to db , Oracle says;
> > db is still on shutdown process, it it related to sumthing like .pid
> > file ?
> > if I kill the oracle ( I know it is so violate :) ) , may i also
> > delete some temp/pid file or any like ?
>
> It is because Oracle touches a file under $ORACLE_HOME/dbs. If
> you just kill one of the background processes, this file is not
> removed and next time it comes up it thinks it is already running.
>
> You can manually remove the file after the kill. But the best way
> is thru shutdown.
Received on Fri Jan 18 2002 - 19:48:45 CST
