Re: Oracle and the VMS delta time restriction

In article <1997Apr24.162744_at_alpha.vitro.com>, vaxs09_at_alpha.vitro.com (John Briggs) wrote:
>In article <335EB127.5E26_at_ici.co.uk>, Douglas Miller <dgm_at_super.zippo.com>
> writes:
>> Oracle Co. have told me that Oracle is affected by the VMS delta time
 restriction (of 9999 days on unpatched versions of VMS up to 7.0), and
>> recommended that any Oracle customer not running VMS 7.1 either upgrade or
 apply the Digital supplied patch to lift the restriction.
>>
>> But they also claim that I will need to relink all Oracle and Oracle-related
 EXE's after applying the patch (for versions 6.0 thu 7.0). I can
>> find no evidence that anything in the Oracle linking procedures pulls in any
 of the affected libray routines directly out of STARLET.OLB, which
>> is surely the only thing that would mandate a rebuild. Does anybody have any
 facts or opintions on this subject? I really don't want to
>> relink unless I have to --- our Oracle environment is too complex for this to
> be an easy job.
>
>Yes, I believe you do need to relink.
>
>The problem is that Oracle links their kernel with /NOSYSSHR. That means
>that they will pull run time routines out of the STARLET.OLB object
>library rather than out of the IMAGELIB.OLB shareable image library.
>
>Thanks for bringing this up. Turns out that I'll have to relink.

That's interesting, since we're running Oracle here, installed the patch on both AXP and VAX, and haven't heard a peep from our Oracle group that they had to relink. It's possible that they need to relink to pick up the patch, and that Oracle works fine with the new LIBRTL in place, but not used.

I will pass this information on to them, and thank you for raising the issue.

        .../Ed

Ed Wilts
Victoria, BC, Canada
mailto:ed_wilts_at_bc.sympatico.ca Received on Sun Apr 27 1997 - 00:00:00 CDT