Re: Oracle Dying ??

If you are absolutely sure that the Oracle processes are no more have you tried looking for the $ORACLE_HOME/dbs/sgadef<sid>.dbf file.

This exist in all but the newest versions (should be obsolete soon) whilst the instance is up and running.

If you KNOW the instance is not running you could rename or if brave delete this file and start the instance from scratch.

You to be sure - try the documentation on the subject first.

As to why the instance 'dies' try looking in the Alert Log for any clues.

Regards

--
Kevin A Lewis (BOCM PAULS LTD) - Animal Feed Manufacturer - Ipswich United Kingdom)

                        <Kevin_A_Lewis_at_Hotmail.com>

The views expressed herein by the author of this document are not necessarily those of BOCM PAULS Ltd. <markp7832_at_my-deja.com> wrote in message news:84vqce$22j$1_at_nnrp1.deja.com...
> In article <38725B6D.1952D896_at_yahoo.com>,
> Michael Rothwell <marothwell_at_yahoo.com> wrote:
> > Twice today, on a system that has been running for months, my Oracle
> > processes have turned up dead. When I go to svrmgrl I can connect
> > internal but when I try to startup, I get the error message stating
> that
> > the instance is already running, when I try to shutdown immediate it
> > tells me that I'm not logged on. I can shutdown abort without
> problem.
> >
> > this is a 7.3.4 db on an UX 10.4
> >
> > pmon, smon, dbwr, lgwr are all gone when this happens.
> >
> > Thanks for any help
> >
> > Michael
> >
> When the Oracle background processes just go away the sgadef file for
> the instance probably still exists and Oracle is going to tell you that
> you can not start it because it is still running. The proper procedure
> is to do a shutdown abort followed by a startup.
>
> Then you should go looking for messages in the alert log just prior to,
> during, and after you startup. If the log is clean then proceed back
> for several hours looking for internal error messages.
>
> Next check for trace files from the background processes pmon, smon,
> etc... and look at those.
>
> Finally check out the user trace files.
>
> Once you have an error message and some trace files you should probably
> call support or do your own search on the error number. If you do not
> find any message and/or trace you can call support but I do not think
> they will be able to help.
>
> You could try checking out any recent changes to the system and Oracle
> such as adding or modifing a job to kill runaway sessions, hot swapping
> of disk was in progress (sometimes these invisible tasks are not so
> invisible) etc....
>
> Good luck!
> --
> Mark D. Powell -- The only advice that counts is the advice that
> you follow so follow your own advice --
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Thu Jan 06 2000 - 06:09:33 CST