Check Shutdown Problems on VMS
If Ingres has problems during shutdown on VMS, follow these steps:
1. Check that you are logged in as the system administrator or another privileged account by issuing the following command at the operating system prompt:
show process
Make sure you have the WORLD and CMKRNL privileges required for stopping Ingres processes by issuing the following command at the operating system prompt:
show process/privilege
A privileged account must not only have the aforementioned VMS privileges but also must have the SERVER_CONTROL privilege authorized in II_CONFIG:CONFIG.DAT.
2. Check that the logical II_SYSTEM is defined by issuing the following command at the operating system prompt:
show logical II_SYSTEM
3. Check to see that users are logged out of Ingres. You can use the utility logstat to determine which databases are open and active and find out whom to notify of the impending shutdown. For additional information, see the Logstat section in the Command Reference Guide.
To obtain a list of running processes, use the DCL command:
show system
4. This command gives you a complete list of all processes that are running on your machine. It displays the process ID ('Pid'), Process Name, and other information. The main processes have the names as shown in
Detect Ingres Startup Problems on VMS.
If you use the form show system/full, you can also see the owner of the process. This is helpful if you have group level installations.
5. Identify your installation code if there is more than one Ingres installation on this machine.
For a group level installation the two-lettered code is displayed after the process name. In this example, the code is BE:
Pid Process Name State Pri I/O CPU Page flts Ph.Mem
236012AD II_DBMS_BE_1E3F HIB 6 86463 0 00:13:53.24 14401 8192
IMPORTANT! If your site has more than one Ingres installation, examine the installation code associated with the II_DBMS_nnn process to make sure you are only shutting down processes associated with the installation you need to shut down.
6. Use the iinamu utility to find the names of the servers for this installation; iinamu shows you only the servers for the installation in which you currently reside. For example:
IINAMU> show ingres
INGRES * II_DBMS_BE_1E3F
found.
IINAMU> show comsvr
COMSVR * II_GCC_BE_2B77
7. Shut down servers. See the individual descriptions below.
Note: Ingres can be shut down in several ways. Following are some tips on how each shutdown procedure works to enable you to make a choice as to how to shut down the installation.
• The ingstop utility shuts down servers in the following order:
– Remote Command Server (rmcmd)
– Communications Server
– Data Access Server
– Protocol Bridge Server
– Star Server
– DBMS Server
– Recovery and archiver processes-IUSV and ACP by rcp.config.
– If present, the Cluster Server is also shut down.
– Name Server
• The following order also works. This ordering manually shuts down the installation, shutting down the Name Server first:
– Name Server
– Communications Server
– Data Access Server
– Star Server
– DBMS Server
– Recovery and archiver processes-IUSV and ACP
a. Shutting down the Name Server
When you issue the stop command from iinamu, the Name Server process is stopped. Once this command is issued, no new servers are allowed to register with the Name Server. Therefore, it makes sense to take the Name Server down first for a clean shutdown. Current, active sessions are not affected by this command.
b. Shutting down the DBMS Server
Use iimonitor to stop the DBMS Server. The two commands you can use are:
set server shut
This causes the server to refuse further connections and shuts the server down gracefully, completing all current transactions first, including the iimonitor session.
stop server
This stops the server immediately without waiting for current connected sessions to complete. Use this command instead of the VMS command stop/id.
c. Shutting down the recovery and archiver processes
Take down the recovery and the archiver processes, either quickly or slowly, depending on the method you used to take down the DBMS Server in step b. Use either of the following commands at the operating system prompt:
rcpconfig/shutdown
This causes the processes to refuse all further connections and transaction processing, but allows current transactions to finish. This allows the archiver and recovery processes to shut down cleanly.
rcpconfig/imm_shutdown
This stops all pending transactions and immediately shuts down the recovery and archiver processes. This leaves open transactions in the log file, which requires rollback (and slow startup) when the system is restarted.
d. Writing a DCL command file to take Ingres down
Alternatively, you can write a DCL script that puts the above steps in a command procedure to shut down each of the Ingres processes.
a. After shutting down Ingres, check that all processes are stopped:
b. Issue the following command at the operating system prompt:
show system
Check to be sure that none of the processes listed in the Ingstart on VMS section is shown.
c. If any of these installation processes are not shut down, note the process ID (PID#) of the running process and issue either of the following commands at the operating system prompt:
stop process_name
or
stop/id = pid#
Note: For serious system problems that require immediate attention, the VMS stop command can be used to stop an Ingres process. This is not recommended because it does not permit the recovery process to back out open transactions or the archiver process to flush the log file to disk.
If this is a cluster installation, remember that these Ingres processes run on each node.