Re: changing server time which affects oracle time

From: Holger Baer <holger.baer_at_science-computing.de>
Date: Thu, 14 Oct 2004 17:12:33 +0200
Message-ID: <ckm511$m6i$1@news.BelWue.DE>

Galen Boyer wrote:

> On Thu, 14 Oct 2004, holger.baer_at_science-computing.de wrote:
> 

>>A nicer workaround that I found recently but can't remember
>>who's to credit:
>>
>>1) create a new pfile e.g. temp.ora with the following content:
>> spfile=<path to your spfile>/spfile<SID>.ora
>> *.NLS_DATE_FORMAT='DD.MM.YYYY'
>> *.FIXED_DATE='01.06.2004'
>>2) startup nomount
>>3) alter system reset FIXED_DATE scope=spfile sid='*'
>>4) shutdown
>>5) startup
>>
>>Benefits: No fiddling in the spfile, and a nice demonstration
>>on how to use the alter system reset command correctly (the
>>documentation isn't very clear on the subject that you *need*
>>the sid part for reset).
>>
>>The mechanics behind this is, that you can have the same
>>parameter appear several times in your spfile/pfile, but only
>>the *last* one is actually evaluated. So you can start with a
>>temporary pfile that includes a spfile and thus repair your
>>spfile.
>>
>>The more I think about it, the more I believe I read this in
>>Tom Kytes last book, but I'm not sure. Maybe someone has it has
>>his/her desk and can clarify?

> 
> 
> I actually just brought the instance up with an init file that I
> created, then I did a "create file from spfile" and then shutdown
> the database again.  Edited that new init file, brought the
> database up with this init file and then did a "create spfile
> from file" and then shutdown once more and then started up once
> more.
> 

I forgot to mention that steps 4 and 5 are actually optional, so you can get your instance up and running in one go.

Quite nifty if you ask me ;-)

Cheers,

Holger Received on Thu Oct 14 2004 - 10:12:33 CDT