Vector Processes on Windows
The major Vector processes are as follows:
• X100 service (x100)
• Name Server process (iigcn)
• Communications Server process (iigcc)
• Recovery process (II_IUSV_nnn)
• Archiver process (dmfacp)
• DBMS Server process (iidbms)
• Data Access Server process (iigcd)
• Bridge Server process (iigcb)
• Remote Command process (rmcmd)
Check for Name Server Errors on Windows
The Name Server process (iigcn) is not running if either of the following occurs:
• You receive a specific error indicating that the Name Server failed to start.
• The iigcn.exe does not appear in the process list.
You can verify this by attempting to start the Name Server manually.
The most common causes of Name Server startup failure are:
• An improper installation environment exists. Be sure to verify the installation environment by performing the
Check Vector Installation on Windows before attempting to start the Name Server.
• The Name Server fails to start if there is already a Name Server running for this installation.
If you still have problems, set the following trace to capture additional diagnostic data before calling technical support:
ingsetenv II_GC_TRACE 4
ingsetenv II_GC_LOG filename
iirun iigcn
Check for Communications Server Process Errors on Windows
If the Communications Server process (iigcc) does not start, verify that you have installed the Ingres Net component and that you have installed the correct protocol drivers.
If you are still having problems, set the following trace to capture additional diagnostic data before calling technical support:
ingsetenv II_GC_TRACE 4
ingsetenv II_GC_LOG filename
iirun iigcc
Check for Remote Command Process Errors on Windows
You can check for the presence of the Remote Command process (rmcmd) using the Windows Task Manager. View the Processes tab for the existence of the process.
Check for Recovery Process Errors on Windows
The Recovery process (II_IUSV_nnn) must be running before a DBMS Server can be started. Failure of the II_IUSV_nnn starting process indicates one of the following:
• Problems with the log file
• Insufficient shared memory
If the Recovery process does not start, perform the following procedure:
1. Check for the existence of the transaction log by opening the Primary Transaction Log window in Configuration Manager (or the Transaction Log screen in the Configuration-By-Forms (cbf) utility), and noting the directories listed in the Log File Root Locations table in Configuration Manager (or the Primary Transaction Log Locations table in cbf).
2. In the ingres/log directory (located below all other listed directories), look for the file ingres_log.lnn where nn is an integer between 1 and 16.
3. Make the following checks on the transaction log file ingres_log.lnn:
a. Verify that ingres_log.lnn exists at that location by entering the following command at the operating system prompt:
dir
b. If it does not exist, you must create it using the iimklog command, and format it using the rcpconfig -init command.
4. If you corrected a recovery process problem, verify that Vector starts normally by completing the following steps:
a. Shut down the partially started installation with the ingstop command.
b. Restart the installation with the ingstart command.
If you still cannot start the II_IUSV_nnn, you must erase it and recreate and reformat it. This step is done only as a last resort.
Note: This step reinitializes the log file, causing any outstanding transactions to be lost.
Check for Archiver Process Errors on Windows
The archiver process (dmfacp) does not start unless the II_IUSV_
nnn recovery process is running. However, an installation runs without an archiver process until the log file fills up. The user programs are suspended until any outstanding transactions in the log file are backed out. More information about Vector in a recovery state is provided in
Recovery Process Monitoring.
Archiver process (dmfacp) startup errors are likely to result from:
• Improperly shared memory resource
• Inability to read the transaction log file
• Inability to write journal files
Use the following procedure to check archiver process startup problems. Some of these checks are the same as for the recovery process in the previous section.
1. Make the following check on the transaction log file ingres.log:
Verify that ingres.log exists at that location by entering the following command at the operating system prompt:
dir
If it does not exist, you must create it using the iimklog command, and format it using the rcpconfig –init command.
2. Check journal locations by verifying that:
The journal location name points to a valid directory containing subdirectories ingres\jnl\default\dbname.
3. Check that the disk partition containing the journal files is not full. Issue the following command from the operating system prompt:
dir
If the journal partition is 100% full, this makes it impossible to write journals and stalls the archiver. If this is the reason preventing archiver start up, you must either free space on the journal partition or temporarily disable journaling with the alterdb command.
4. If you corrected a recovery process problem, verify that Vector starts normally.
a. Shut down the partially started installation with the ingstop command.
b. Restart the installation with the ingstart command.
Check for DBMS Server Process Errors on Windows
The command to start the DBMS Server process (iidbms) from the Vector login is ingstart -iidbms. If the DBMS Server did not start:
2. Verify that the recovery process II_IUSV_
nnn is not in a recovery state, as described in
Recovery Process Monitoring. This is a likely situation if there was a sudden shutdown because of a power failure or some other system failure.
3. Try to start the DBMS Server. Issue the following command at the operating system prompt:
ingstart -iidbms
4. If you corrected a recovery process problem, verify that Vector starts normally.
a. Shut down the partially started installation with the ingstop command.
b. Restart the installation with the ingstart command.
Check for Data Access Server Errors on Windows
If the Data Access Server process (iigcd) does not start, follow this procedure:
1. Verify that you have installed the Ingres Net component
2. Verify that you have installed the correct protocol drivers
If you are still having problems, set the following trace to capture additional diagnostic data before calling technical support:
ingsetenv II_GCD_TRACE
ingsetenv II_GCD_LOG filename
ingstart -iigcd