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:

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:

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:

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:

The two-letter installation code is displayed. For example:

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:

6. Check that all Ingres processes are shut down. If processes continue to run, see Check Shutdown Problems on VMS.

7. Restart Ingres. Attempt once again to start up the installation by issuing the following command at the operating system prompt:

8. If startup problems persist, continue diagnostics contained in the next section--vmsinstal or ingstart.