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:

Make sure you have the WORLD and CMKRNL privileges required for stopping Ingres processes by issuing the following command at the operating system prompt:

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:

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.

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 (see page 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:

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:

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:

– Recovery and archiver processes-IUSV and ACP by rcp.config.

• The following order also works. This ordering manually shuts down the installation, shutting down the Name Server first:

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.

Use iimonitor to stop the DBMS Server. The two commands you can use are:

This causes the server to refuse further connections and shuts the server down gracefully, completing all current transactions first, including the iimonitor session.

This stops the server immediately without waiting for current connected sessions to complete. Use this command instead of the VMS command stop/id.

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:

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.

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.

Alternatively, you can write a DCL script that puts the above steps in a command procedure to shut down each of the Ingres processes.

8. After shutting down Ingres, check that all processes are stopped:

a. Issue the following command at the operating system prompt:

Check to be sure that none of the processes listed in the Ingstart on VMS section is shown.

b. 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:

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.

Your Ingres installation is now shut down. Information about checking and restarting Ingres is described in Check Ingres Installation on VMS (see page Check Ingres Installation on VMS).