🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.databases.ingres
1 messages
1 total messages Started by mal@adc.com (Mic Thu, 16 Sep 1993 13:24
Re: Info re: using Ingres in a mixed SunOS 4.1.3/Solaris 2.2 env
#3972
Author: mal@adc.com (Mic
Date: Thu, 16 Sep 1993 13:24
83 lines
3225 bytes
>Message 23:
>From tjb@MATH.AMS.ORG Thu Sep 16 02:24:12 1993
>Errors-To: tjb@MATH.AMS.ORG
>From: dlkiehl@afterlife.ncsc.mil (Dana Kiehl)
>Subject: Info re: using Ingres in a mixed SunOS 4.1.3/Solaris 2.2 env
>To: info-ingres@MATH.AMS.ORG
>Errors-To: tjb@MATH.AMS.ORG
>Content-Transfer-Encoding: 7BIT
>Path:
> cv3.cv.nrao.edu!uvaarpa!darwin.sura.net!haven.umd.edu!cs.umd.edu!afterlife!dlkiehl
>
>Hello fellow netters,
>I run Ingres in a client server environment, where Ingres is on
>a Sparc 2 and users can access from their Suns using Ingres/Net.
>Right now, all machines are running SunOs 4.1.3. There is a
>possibility of client Suns (Like LXs I think) being added to
>the net, with Solaris 2.2 running on them. Ingres has told me
>that it is not possible for a client Sun running Solaris to
>access Ingres from a server Sun running 4.1.3 (or vice versa).
>Ingres said it's a matter of incompatible binaries, since the
>clients need to mount the Ingres home directory.
>My question is, has any brave soul actually tried to do this
>and get it to work? I would appreciate hearing what has been
>done.

You may have been confused by the documentation and/or INGRES.

There are several ways one can set up a client/server network
with INGRES.  If one is in a homogenous network (all platforms
can use the same binaries), then one can perform "client" installations
on the nodes that are only going to run INGRES/NET.  A "client"
installation mounts the INGRES tree on the server node, and has
a separate configuration file in the admin directory.  All such
"client" nodes require the "server" node be avaliable in order
to run INGRES/NET.

You could also install the INGRES tree on EVERY node, even though
some of these nodes are only going to run INGRES/NET.  In a large
installation, you may have 10 nodes with full INGRES binaries each
serving 100 clients, if you so desire.  Or you could have 1 node
serving 1009 clients (which I would not recommend).

If you are in a "heterogenous" network, you must do something different.
Let's take a simple scenario we had a month ago:

   2 Ingres installations running SunOS 4.1.1.
   1 machine had binaries, other was a "client" installation running NET only.

Today's scenario:

   1 full Ingres installation running SunOS 4.1.1, running server and NET.
   1 full Ingres installation running SunOS 5.2 (Solaris 2.2),running NET only.

Our users see the "same" environment.  The system admin, however, has
to deal with twice as much disk space requirements.

So...we do exactly what you need to do.  If we had 5 other 5.2 systems,
I would just "client" install them to the 5.2 machine with the binaries.
If we had 5 other 4.1.1 systems, I would just "client" install them to the
4.1.1 machine with the binaries.

The is no need to make a mass migration to SunOS 5.2, unless you absolutely
don't have the disk space on ONE of your 5.2 machines for the full INGRES
installation.

(BTW, on my 5.2 machine, the "full" installation has been trimmed to include
only the files needed to run NET and do client installs.)

Hope this helps,








Michael Leo
ADC Telecommunications
(612) 936-8305 (voice)
mike_leo@adc.com


Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads