Check Ingres Installation on VMS
It is recommended that you first make the following basic installation checks:
1. Check that you are logged in as the ingres system administrator (ISA) user by issuing the following command at the operating system prompt:
show process
If the ISA is not shown, log off and log in again as the ISA. The ISA is typically ingres if there is only a single installation per machine. For multiple installations, there is a different ISA for each installation.
2. Check that all users have II_SYSTEM set by issuing the following command at the operating system prompt:
show logical II_SYSTEM
3. Check that each of the Ingres installation logicals has a valid value.
Ingres symbols are defined in the following files:
• II_SYSTEM:[INGRES.UTILITY]INGSYSDEF.COM - Defines Ingres system administration, DBA, and user symbols.
• II_SYSTEM:[INGRES.UTILITY]INGDBADEF.COM - Defines Ingres DBA and user symbols.
• II_SYSTEM:[INGRES.UTILITY]INGUSRDEF.COM - Defines Ingres user symbols.
If you are in doubt about the function or legal value of a particular logical, see the chapter "Setting Environment Variables and Logicals" and the appendix “Environment Variables and Logicals”.
Ingres logicals denoting installation locations (II_DATABASE, II_CHECKPOINT, II_DUMP, II_JOURNAL, II_LOG_FILE, II_SYSTEM) can not be reset. To change these, you must edit II_CONFIG:config.dat, update the existing definition, and execute @ii_system:[ingres]ingsysdef.com. For additional details, see
Installation Locations.
4. Check the Ingres logicals that have been set locally, overriding the Ingres installation-level definitions. Issue the following command at the operating system prompt:
show logical *II*, *ING*
This shows which ones have been set at process, job, or group level, overriding the system-level definitions.
Only a small category of Ingres logicals are defined in the local user environment: those that permit you to access Ingres, and those that define values that are different for your local environment. They can include TERM_INGRES and ING_EDIT.
If you trace the problem to an Ingres logical setting, correct the value. For procedures and scenarios for setting these logicals, see the chapter "Setting Environment Variables and Logicals." If the installation does not start up, continue with this procedure.
5. Identify your installation code if there is more than one Ingres installation on this machine. To do so, type the following command at the operating system prompt:
show logical II_INSTALLATION
The two-letter installation code is displayed. For example:
II_INSTALLATION=R6
If this is a system-wide Ingres installation, there is no definition for II_INSTALLATION. The installation code is used to distinguish which processes belong to which installation at sites with more than one Ingres installation on the same machine:
7. Restart Ingres. Attempt once again to start up the installation by issuing the following command at the operating system prompt:
ingstart
8. If startup problems persist, continue diagnostics contained in the next section—vmsinstal or ingstart.
VMSINSTAL on VMS
The executable script vmsinstal performs all the steps necessary to set up an installation. It checks system resources, installs shared images, configures DBMS server parameters, configures the logging and locking system, and starts all the required processes.
During the execution of the vmsinstal script, if a problem occurs, do the following:
1. Execute the vmsinstal program with the L option to log the contents of the VMSINSTAL session:
@sys$update:vmsinstal * device_name options L
2. Examine the DCL by issuing the following command at the operating system prompt:
set verify
3. Examine the vmsinstal log for error notifications and attempt to resolve the problem.
4. If the Installation Verification Procedure (IVP) for the DBMS Server fails with the message “ii.node_name.syscheck.gblpages not found in config.dat” after you enter the number of concurrent users that the installation supports, check the value of the account parameter PRCLM (process limit) to ensure that it is not zero. The PRCLM must be a minimum of 15.
Detect Ingres Startup Problems on VMS
If you are having ingstart problems, use the following procedure:
1. Display the processes that are running by issuing the following command at the operating system prompt:
show system /out = filename
search filename "II_", "DMF"
The search command searches the user-specified filename for the process names.
2. Verify that all required Ingres system processes are running. The following processes (in the order they are started) are the minimum required for a complete installation:
• II_IUSV_nn_ppp—Recovery process
• DMFACP_nn—Archiver process
• II_GCN_nn—Name Server process
• II_GCC_nn_pppp—Communications Server process (present only on sites with Ingres Net)
• II_DBMS_nn_pppp—DBMS Server process
• II_STAR_nn_pppp—Star Server process (present only on sites with Ingres Star)
• RMCMD_nn_ppp—Remote Command Server for use with VDBA
• II_GCB_nn_pppp—Bridge Server process (present only on sites with Ingres Bridge)
Where nn is the optional two-letter installation code, and pppp is the lower two bytes of the process’ process ID.
Note: If you are checking the processes on a client node, only the Name Server and Communications Server processes are displayed when issuing the $ SHOW SYSTEM command.
3. If ingstart does not complete successfully, do the following:
a. Check for error messages in the errlog.log:
II_SYSTEM:[INGRES.FILES] II_CONFIG:errlog.log
b. Try to identify the reason for startup failure.
• The problem is with ingstart. If the ingstart executable fails due to results of the checks it makes for sufficient resources and installation settings, correct the deficiency.
• A process failed to start. If a process failed to start, continue on to the detail sections on startup problems for that specific process.