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: Steve Cosner <stevec_at_zimmer.csufresno.edu>
Date: 1997/01/13
Message-ID: <5bcncv$t95@shadow.CSUFresno.EDU>#1/1

In article <5b609k$5j3_at_centauri.hq.nasa.gov>, <plaidlaw_at_hq.nasa.gov> wrote:
>> 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.
>
>Does the NLS_DATE_FORMAT needed to be changed from DD-MON-YY to DD-MON-RR?

It might help in some places, but there may be a few where this causes a problem. The applications themselves really need to be changed. Just changing the NLS_DATE_FORMAT on the server may have no effect. It depends on what format the applications are using to transfer the date values to/from the server.

Steve Cosner Received on Mon Jan 13 1997 - 00:00:00 CST

Original text of this message

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