Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Oracle and the VMS delta time restriction
At 06:02 PM 4/23/97 -0700, Douglas Miller wrote:
>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.
Oracle's got a fairly nasty linking process--I'd take them at their word and relink. Before you do, change the LNPRO*.COM files to link shared against the SQL, CORE, and UPI libraries. If you do that (or have already done it) there's no need to relink the world later for changes (like this one) to Oracle.
If you're using Oracle 7.1.5 then you're probably linking shared to CORE and UPI already, but you'll need to add SQL. If you're on 7.1.3, you'll need to add all three logicals (SHARED_x_LIB = "YES") to the top of the LNPRO*.COM files.
Linking shared'll also save you between 4000 and 5000 blocks over a fully static link, per executable. Worth it if you haven't done it, if you can.
Dan
----------------------------------------"it's like this"------------------- Dan Sugalski (541) 917-4364 even samurai Programmer/SysAdmin have teddy bears Linn-Benton Community College and even the teddy bears sugalsd_at_stargate.lbcc.cc.or.us get drunkReceived on Wed Apr 23 1997 - 00:00:00 CDT
![]() |
![]() |