This chapter explains the various installation considerations that are needed while installing the Ingres Distribution Option. You have the option of installing Ingres Star during the standard Ingres installation procedure.
The following are requirements for installing Ingres Star:
VMS: In a cluster installation, a distributed database is accessible from all nodes in the installation but Net must be installed. For example, assume there are three nodes in the installation, Nodes A, B and C. If the distributed database is created on Node A, Ingres Star requires Net to access the distributed database from Nodes B and C. 
During installation you will be prompted for certain information needed by Ingres Star:
Each Ingres Star user session requires one connection for each remote LDB being referenced while connected to Ingres Star. For example, if a user needs to connect to ten remote LDBs, you must establish ten outbound connections on the Ingres Star node, plus one inbound connection on each of the remote nodes.
If a distributed database has tables registered from 10 remote LDBs and all 10 remote LDBs are accessed by Ingres Star during the user's session, then 10 connections are required. If two users are to access this distributed database simultaneously, then 20 Net connections are required.
All connections are kept open until the user ends the session.
To specify or modify the number of inbound and outbound connections, see the System Administrator Guide.
For each Ingres Star user session, three local sessions (connections) are required between the Star Server and the local DBMS for Ingres Star access to the coordinator database. For example, if the Star Server is configured for five user sessions, the local Ingres DBMS Server must be configured for at least 15 user sessions.
UNIX: The Star Server is a DBMS Server, which is started with the command:
ingstart -iistar
VMS: The Star Server is a DBMS Server, which started with the parameter:
ingstart /star
The following are operating system requirements for Star:
UNIX: The executable setuid must be turned on. Only the user who owns the installation can start the Star Server. The install sets up the correct protections (that is, setuid) on the Star Server.
VMS: The Star Server requires the following privileges to run: PRMMBX, WORLD, READALL (for client/server communication), SYSPRV (to open error and status logging files), and SHARE (to open terminals for trace output). The vmsinstal utility installs the Star Server with all of the appropriate permissions.