On Tue, 12 Oct 2004, bdick_at_cox.net wrote:
> On 12 Oct 2004 09:00:27 -0500, Galen Boyer wrote:
>
>> On Tue, 07 Sep 2004, igor.racicC_at_freesurf.fr_no_C wrote:
>>> yls177 wrote:
>>>> hi, oracle transaction time comes from the server time?
>>>> Therefore, if we changed the oracle time, then inherently,
>>>> this will affect the oracle and transaction time, right?
>>>> currently, we have an issue here. Some jobs were not run
>>>> properly and we were advised by the other party that the
>>>> only solution is to change the server time to past times, so
>>>> as to enable the job to run. Afterwhich, we can update the
>>>> time to the present time. Any advise?
>>>
>>> Probably Sybrand gave you good answer.
>>> But if you insist and know what you are doing, maybe
>>> fixed_date parameter could be of help:
>>>
>>>
>>> 1* alter system set fixed_date='2001-01-01-11-00-00'
>>> SQL> /
>>>
>>> System altered.
>>>
>>> SQL> select sysdate from dual;
>>>
>>> SYSDATE
>>> ---------
>>> 01-JAN-01
>>>
>>> SQL> alter system set fixed_date=none ;
>>>
>>> System altered.
>>>
>>> SQL> select sysdate from dual;
>>>
>>> SYSDATE
>>> ---------
>>> 07-SEP-04
>>
>> Okay,
>>
>> On my local development instance, I did this for some testing.
>> But, when I set it back using
>>
>> alter system set fixed_date=none
>>
>> and then shutdown, on restart I get the error,
>>
>> ORA-00065: initialization of FIXED_DATE failed
>>
>> Does anybody know how to fix this?
>
> Did you try adding scope=both?
Yes.
--
Galen Boyer
Received on Wed Oct 13 2004 - 13:16:13 CDT
