Re: Oracle 7.3 not Y2K compliant on Digital Unix?

From: BobH <b-horton_at_worldnet.att.net>
Date: 1998/05/04
Message-ID: <6iltbg$lgi@bgtnsc03.worldnet.att.net>#1/1

Saad Ahmad wrote:
>
> They might be referring to issues like:
> SYS SQL> desc v$transaction
> Name Null? Type
> ------------------------------- -------- ----
> ADDR RAW(4)
> XIDUSN NUMBER
> XIDSLOT NUMBER
> XIDSQN NUMBER
> UBAFIL NUMBER
> UBABLK NUMBER
> UBASQN NUMBER
> UBAREC NUMBER
> STATUS VARCHAR2(16)
> START_TIME VARCHAR2(20) <<<------
>
> SYS SQL> update dual set dummy = dummy;
> SYS SQL> select start_time from v$transaction;
> START_TIME
> --------------------
> 05/04/98 09:38:03
> SYS SQL> rollback;
>
> But I won't sweat over it.
>
> Jim Smith <jim_at_jimsmith.demon.co.uk> wrote in article
> <5u4qPGA1f4S1EwY1_at_jimsmith.demon.co.uk>...
> > We have been told by a third party supplier that Oracle 7.3.2 is not
> > certified Y2K compliant on Digital UNIX 4.0.
> >
> > Does anyone have any details on this? If we have to go through an
> > expensive upgrade, we would like to know why.
> >
> > TIA
> > --
> > Jim Smith
> >

I would first ask Digital if the O/S software you have on your platform is compliant.

I'm not sure about 7.3.2 being compliant. I think that is why we upgraded to ORA 7.3.3 with Solaris 2.6 Received on Mon May 04 1998 - 00:00:00 CDT