Re: Strange Y2K date problem

["Blakeslee, Andy" <ALBlakeslee@HOMELOAN.COM>]

Doris - version 7.01c of HRizon is only Y2K compliant if all the September
98 patches have been applied.  The actual problem is probably that the
default date format is set to 'DD-MON-YY' instead of 'DD-MON-YYYY'.  You can
correct this by adding the following line to your Oracle.ini:
NLS_DATE_FORMAT=DD-MON-YYYY

Thanks,
Andy

> -----Original Message-----
> From: Doris K. Brinson [SMTP:DBrinson@COMMHOSPINDY.ORG]
> Sent: Wednesday, January 20, 1999 9:37 AM
> To:   Multiple recipients of list SQR-USERS
> Subject:      Strange Y2K date problem
>
> I am running HRizon (a Peoplesoft offshoot) version 7.01c on an Oracle
> platform. We are trying to implement Hrizon's Benefit Administration
> module. In our development system, we are attempting to run Open
> Enrollment for the date range 2/1/1999 to 1/31/2000. We are
> encountering problems in one of the programs. What is happening is that
> the program does an select, saves the info it selected, then does an
> insert in a seperate procedure.
>
> begin-SELECT
> (lots of fields unrelated to the problem deleted)
> D.Coverage_End_Dt          &1.Coverage_End_Dt
> D.Deduction_End_Dt         &1.Deduction_End_Dt
>
>   do Insert-Procedure
> (FROM and WHERE claused deleted)
> end-SELECT
>
> BEGIN-PROCEDURE Insert-Procedure
> INSERT INTO tablename
> (Coverage_End_Dt,
>  Deduction_End_Dt,
>  Values
> (&1.Coverage_End_Dt,
>  &1.Deduction_End_Dt);
> END-SQL
>
>
> Now, I have verified that D.Coverage_End_Dt and D.Deduction_End_Dt
> contain '31-JAN-2000'. However, the inserted record contains
> '31-JAN-1900'.  So the century is getting lost somewhere in the middle.
>
> I don't know if it is an Oracle issue, an SQR issue or what.  It is also
> possible that I don't have something set properly in my environment, but I
> don't know what.
>
> Does anyone have any ideas?