Re: Setting SYSDATE to January 5, 2000

Hi.
In addition to my previous note, I should point out 2 things.

1 In certain versions of Oracle, the fixed_date parameter is only picked up in SQL and not in PL/SQL. In other words, a "select sysdate from dual" would pick up the date as per the fixed_date parameter, whereas as in PL/SQL " l_variable := sysdate" would ignore fixed_date and pick up the date as per the Server operating system clock.
I think this is a bug that has been fixed in latest versions.

2. If using Oracle Developer/2000, references to sysdate may  refer to the local PC clock rather than the Server sysdate. Thus whereas a "select sysdate from dual" will get executed on the server and hence return the Fixed_date paramter value, a "l_variable := sysdate" will in certain versions be exactly equivalent to the "select sysdate from dual" but will return the local PC date in other versions. This modification was made in an effort to reduce network traffic and calls to the RDBMS -- You need to check your specific version of Developer!!!

Coakleyj

In article <7mi6eo$jib$1_at_bgtnsc02.worldnet.att.net>,   "Frank Siegel" <NorthernSnow_at_worldnet.att.net> wrote:
> Thanks in advance for any help you may provide.
>
> Is there a way to set SYSDATE to year 2000 without
> touching the system date in UNIX? We need this for
> Y2K testing and it would be a major league inconvience
> concerning UNIX crons and backups if we have to touch
> UNIX dates.
>
> Thanks again,
> Frank S.
> New Hampshire
>
>

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Wed Jul 14 1999 - 13:54:46 CDT