|
|
|
For full instructions on installing Ingres on OpenVMS, see the Installation Guide. The installation process has not changed significantly from Ingres II 2.0.
Ingres uses the VMSINSTAL procedure to install and configure its software. Using VMS, it is possible to create the new Ingres system administrator account, extract the software required, and configure Ingres. However, depending on how the installation progresses, some issues may develop.
You can install Ingres either directly from the CD-ROM or from a working area on the target system. If the files are transferred to the target node through FTP, they must be moved across in binary mode.
|
|
|
If the machine has a CDROM drive, you can use the following command to mount the CD:
$ MOUNT /OVERRIDE=IDENTIFICATION /MEDIA_FORMAT=CDROM -
/UNDEFINED_FAT=(FIXED:CR:32256) <CD Device>
To access the readme use the following:
$ MOUNT /OVERRIDE=IDENTIFICATION /MEDIA_FORMAT=CDROM -
/UNDEFINED_FAT=STREAM:32767 CD_Device
|
|
|
To run the installer, issue the following command from any privileged account that is defined as holding the privileges needed to run Ingres:
@sys$update:vmsinstal * distribution_medium
By default, the SYS$ROOT area is used by VMSINSTAL to unpack the savesets in preparation for installing Ingres. If there is insufficient space available, then VMSINSTAL will fail. To specify an alternate working directory, you can use the awd parameter, as follows:
@sys$update:vmsinstal * <distribution_medium> options awd=device:[dir]
To log the installation process specify the option L when calling VMSINSTAL:
@sys$update:vmsinstal * <distribution_medium> options L
|
|
|
Note: For more information about these issues, check the technical documents available at the Ingres Technical Support web site.
Creating the Ingres System Administrator account from within VMSINSTAL does not assign the correct process quotas to the account. (For the correct quotas, see the Installation Guide.) The workaround is to create the account before the VMSINSTAL process is started with the correct privileges and process quotas.
II_WORK is not picked up, if pre-defined in the local symbol table, when an Express installation is performed. The user must enter the correct information when prompted.
If Ingres is installed from a non-Ingres System Administrator account, imadb is created as the process owner for VMSINSTAL rather than the installation owner configured earlier. When Ingres is started, the RMCMD process will hang because it is running as a user that is unable to connect to the RMCMD catalogs in imadb. The workaround is to install Ingres as the intended Ingres System Administrator.