Re: Must reboot before 248 days??

From: Howard J. Rogers <howardjr_at_www.com>
Date: Wed, 13 Sep 2000 22:25:41 +1000
Message-ID: <39bf63de@news.iprimus.com.au>

You ought to backing the controlfile to trace every time you make a physical alteration to the database, and in fact (given that the trace file is trivial in size) I recommend you backup controlfile to trace every night as some sort of cron job, or AT command.

Regards
HJR

--
--------------------------------------------------------------------------
Opinions expressed are my own, and not those of Oracle Corporation
Oracle DBA Resources:               http://www.geocities.com/howardjr2000
--------------------------------------------------------------------------



<dwilliams_at_lifetouch.com> wrote in message
news:8pleir$hhc$1_at_nnrp1.deja.com...


> My colleague contacted Oracle support. This problem only applies to

> Solaris. The problem has to do with the Solaris system clock. The

> database just "hangs", and will only shut down with a shutdown abort,

> which has the possibility of corrupting the control file.

>

> To find the error on metalink, look for Article-ID 118228.1

>

> The workaround is to reboot before 248 days.

> I'm guessing a backup control file to trace before you do a shutdown

> abort wouldn't be a bad idea.

>

>

> Sent via Deja.com http://www.deja.com/

> Before you buy.

Received on Wed Sep 13 2000 - 07:25:41 CDT