Ingres Log Files
Ingres maintains several log files to which it writes information about the installation activities. The various log files are:
• Transaction Log File
• DBMS Error Log
• Archiver Log
• Recovery Log
• VMS Cluster Service Process Log
• Primary Configuration Log Files
• Operational Configuration Log Files
• Optional Log Files
• X100 Write-ahead Log
• X100 Error Log
Transaction Log File
Each installation has a transaction log file, and an optional dual log file. The transaction log file is a write-ahead log file that holds information about all open transactions and is used to recover active databases after a system failure. You have the option to change its size and number of partitions at startup.
UNIX: The log file can be created as a raw partition or as a number of raw partitions. For details, see the Installation Guide.
DBMS Server Error Log
The Error Log (errlog.log) file is the main log file for the DBMS Server. It is a readable text file that you can use for troubleshooting. Messages about the installation are appended to this log with the date and time at which the error occurred. This is generally the first place to look when troubleshooting a problem. The error log contains the following information:
• Error messages
• Warning messages
• Server start up and shutdown messages
The system administrator maintains the error log file. This file continues to grow until manually truncated. The installation must be shut down before truncating or removing the errlog.log file.
The error log file is located in the $II_SYSTEM/ingres/files/ directory.
Archiver Log
The archiver log (iiacp.log) contains information about the current archiver process. The archiver log file is appended to when the archiver process starts. The log contains the following information:
• Archiver start up
• Archiver error messages
• Archiver warning messages
The archiver log is located in the $II_SYSTEM/ingres/files/ directory.
Recovery Log
The recovery log (iircp.log) contains information about the current recovery process. This file is appended to when the recovery process starts. The log contains the following information:
• Current logging and locking parameter values
• Recovery process error messages
• Recovery process warning messages
• Recovery operations information
Note: The recovery log must be monitored if you are unable to connect to Ingres and suspect that the DBMS Server is in recovery mode.
The recovery log is located in the $II_SYSTEM/ingres/files/ directory.
Primary Configuration Log Files
Ingres maintains transcripts of various configuration operations. The primary configuration log files that Ingres uses are as follows:
config.log
The config.log file contains a log of the changes made with the Configuration Manager or Configuration-By-Forms (cbf) utility.
rcpconfig.log
The rcpconfig.log file contains log and error information of the last time rcpconfig was run. For details of the rcpconfig command, see the Command Reference Guide.
The primary configuration log files are located in the $II_SYSTEM/ingres/files/ directory.
Optional Configuration Log Files
Ingres provides the following optional configuration log files. These files, if present, are in the directory indicated by II_CONFIG.
Note: In UNIX, the II_CONFIG file must always be in $II_SYSTEM/ingres/files.
iilink.log
Contains a log of the last time the iilink command was run. This log is used only in conjunction with the Object Management Extension.
Note: This log exists on Windows only.
iivdb.log
Contains a transcript of the last time verifydb was used to diagnose or attempt recovery of a damaged or inconsistent database. This file is created the first time verifydb is run.
Note: This log does not exist on Linux.
lartool.log
Contains a transcript, with any errors, of the last time lartool was used to manually abort or commit a running transaction. This file is created the first time lartool is run.
Last modified date: 01/30/2023