Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Y2K problem with sysdate

Re: Y2K problem with sysdate

From: Chris <chris_at_foo.com>
Date: Thu, 06 Jan 2000 19:59:58 -0500
Message-ID: <38753A8E.CE62F496@foo.com>


Get rid of the two digit date, and go with YYYY or RR and expand your variable in the code.

Try select to_char(sysdate,'DD-MON-YYYY') from dual. If you see 2000 for the year, your server is working.

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 Thu Jan 06 2000 - 18:59:58 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US