Re: Y2K problem with sysdate

what exactly is your problem with this? in this data format the first two digits of the year is truncated but if you use to_char, you will see that the data will still be correct.

Deepa Dinendra wrote:

> We recently moved from sgi to sun and from oracle7.x to 8i for Y2k
> compliance.
> All the programs were recompiled and worked fine till Dec.30th. The
> problem came up when the programs were used for the first time after
> Jan.2000. Nothing was changed since the compiling to the programs.
>
> I checked the NLS_DATE_FORMAT by
> select * from V$NLS_PARAMETERS where parameter = 'NLS_DATE_FORMAT';
>
> The result is:
> NLS_DATE_FORMAT DD-MON-YY
>
> -Deepa
>
> Chris wrote:
> >
> > What's your platform and OS?
> >
> > What's your Oracle version number?
> >
> > What's your default NLS date format? Since you appear to have a 15
> > character format, I am guessing 'DD-MON-YYHH:MI'. If you want a 4 digit
> > year, use YYYY, to maintain a two digit year, use RR. If you expand to
> > YYYY, you will need two extra characters in your varchar. Have you done
> > any Y2K work on this at all?
> >
Received on Mon Jan 10 2000 - 19:06:05 CST