Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Year 2000 Compliance
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.
>
> Is this true? And if so, what do I need to do to my packages and
> procedures to make them Y2K compliant? Can you give examples?
>
> Thanks,
> Jason
Jason,
I haven't seen this particular article, but I did read a similar article about Oracle applications a while back... they said basically the same thing as what you've described, but they're not talking about the Oracle DBMS itself -- they're talking about application software that the Oracle Corp. sells & supports.
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 U S WEST Communications Information Technologies jverbil_at_uswest.com (303) 896-0916Received on Wed Jan 08 1997 - 00:00:00 CST