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

Home -> Community -> Usenet -> c.d.o.misc -> Re: Year 2000 Compliance

Re: Year 2000 Compliance

From: <plaidlaw_at_hq.nasa.gov>
Date: 1997/01/10
Message-ID: <5b609k$5j3@centauri.hq.nasa.gov>#1/1

> Jason Botwick wrote:
> >
> > Hi,
> >
> > I just read an article in PCWeek that said that Oracle's "suite of
> > client/server business applications is not currently year
> > 2000-compatible . . . ", and that the base coding of applications
> > written in PL/SQL do not recognize four-digit years for Oracle versions
> > less than 10.7.
> >
>
> The DBMS itself is already Y2K compliant; you just need to make sure
> that your application doesn't do any MM/DD/YY conversions.
>
> The easiest and least-painful conversion, if you do indeed have MM/DD/YY
> conversions in your procedures, is to switch to MM/DD/RR, which
> automatically converts 2-digit years less than 50 (or is it 51?) to the
> 21st century. Works great as long as you don't have data with dates
> prior to 1950 already.
>
> --
> John Verbil

Does the NLS_DATE_FORMAT needed to be changed from DD-MON-YY to DD-MON-RR? Received on Fri Jan 10 1997 - 00:00:00 CST

Original text of this message

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