[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::rdb_60

Title:Oracle Rdb - Still a strategic database for DEC on Alpha AXP!
Notice:RDB_60 is archived, please use RDB_70..
Moderator:NOVA::SMITHISON
Created:Fri Mar 18 1994
Last Modified:Fri May 30 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5118
Total number of notes:28246

5000.0. "Installing CMA incompatible with Rdb 4.1?" by ORAREP::NETRIX::"[email protected]" (George Paci) Wed Feb 05 1997 13:15

(This is pretty urgent -- we had to deinstall a system after installing
it -- so I'd really appreciate a quick reply.)

I wrote an extentsion to MAXCIM which goes off to another server
to grab some data.  We needed a timeout, to ensure that nothing
(e.g. networking oddities) would hang the request for more than
a minute or so.  My solution uses DECThreads, and so links to the
CMA$OPEN_RTL image.  None of my code actually uses or talks to Rdb.

We successfully installed the new version of MAXCIM (i.e. incorporating
my code) on ROCCER, which has Rdb 6.1 installed (and therefore DEC SQL 6.1,
and CMA$OPEN_RTL).

We could install, but not run, on the production cluster, TOLKIN.
The reason it won't run is that CMA$OPEN_RTL isn't installed on TOLKIN.
TOLKIN has Rdb 4.1 installed.

The solution seemed simple to us: install CMA$OPEN_RTL on TOLKIN.
But the support people saw that SQL$STARTUP is what installs
CMA$OPEN_RTL on ROCCER (which is running Rdb 6.1), and that SQL$STARTUP
doesn't install CMA$OPEN_RTL on TOLKIN (which is running Rdb 4.1),
and decided there must be some kind of incompatibility between
CMA$OPEN_RTL *just being installed* and Rdb 4.1 running.


What I need is simple: someone who knows about Rdb 4.1 to tell them
(via me) that installing CMA$OPEN_RTL on TOLKIN won't screw up Rdb 4.1 .

Note that my code does not access Rdb 4.1 in any way, shape, or form,
so this has nothing to do with the non-thread-reentrancy of Rdb 4.1 .
It's simply a matter of whether installing CMA$OPEN_RTL will interfere
with the (unchanged) operation of Rdb 4.1 .

Thanks in advance,
George Paci  BIGQ::PACI   [email protected]  DTN 225-5633

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
5000.1I'm not using *any* version of RdbORAREP::NETRIX::"[email protected]"George PaciWed Feb 05 1997 13:1912
I just realized I said I wasn't using Rdb 4.1 in any way, shape, or form.

What I meant to say was: My code doesn't use *any* version of Rdb,
in any way, shape, or form.

Sorry if that was misleading.

Also, TOLKIN only has version 4.1-2 of Rdb installed.

--George Paci   BIGQ::PACI  [email protected]  DTN 225-5633

[Posted by WWW Notes gateway]
5000.2NOVA::SMITHIDon't understate or underestimate Rdb!Wed Feb 05 1997 13:209
~(This is pretty urgent -- we had to deinstall a system after installing
~it -- so I'd really appreciate a quick reply.)

If it is urgent then please don't use notes.  Contact the Oracle World Wide
support center.

Notes is for non-critical discussions of these products.

Ian
5000.3It should workHOTRDB::PMEADPaul, [email protected], 719-577-8032Wed Feb 05 1997 15:1010
    I would suggest to your support people that they worry too much.  :-)
    Try it.  If it doesn't work I will be amazed.  In any case, they are
    far from being supported, so if they are that concerned about things
    working then maybe they should consider upgrading to the current
    version.  (Let's see 7 - 4 = 3.  That means they are three major
    versions behind, ignoring the minor versions 4.2, 6.1...).
    
    My bet is later SQL$STARTUP.COM files explicitly install the files
    because there were changes in later "Common Components" kits that
    required those images to be installed.