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 Actian X 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 Actian X starts normally.
a. Shut down the partially started installation with the ingstop command.
b. Restart the installation with the ingstart command.
Last modified date: 08/14/2024