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:
• Improper installation configuration, as described in Problems with Startup, Shutdown, or Configuration.
• 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 Ingres 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.
Last modified date: 01/30/2023