Log Files

Ingres maintains log files to which it writes information about the installation activities.

Transaction Log File

Each installation has a transaction log file and an optional dual log file. The log file holds information about all open transactions and is used to recover active databases after a system failure. Optionally, you can change its size and number of partitions at startup.

UNIX: The UNIX log file can be created as a raw partition or a number of raw partitions.

Error Log

The main error log is a readable text file that you can use for troubleshooting. The error log file (errlog.log) is maintained in $II_SYSTEM/ingres/files/ directory.

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
• Archiver shutdown
• DBMS server start up and shutdown

The system administrator maintains the error log file. The file continues to grow until manually truncated. The installation must be shut down before truncating or removing the errlog.log file.

Archiver Log

The archiver log contains information about the current archiver process. The archiver log file (iiacp.log) is located in the $II_SYSTEM/ingres/files directory.

This file is appended to when the archiver process starts. The log contains the following information:

• Archiver start up
• Archiver error messages
• Archiver warning messages

Recovery Log

The recovery log (dmfrcp) contains information about the current recovery process. The recovery log file (iircp.log) is located in the $II_SYSTEM/ingres/files/ directory.

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

The recovery log must be monitored if you are unable to connect to Ingres and suspect that the DBMS Server is in recovery mode.

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

Configuration log files that are optionally maintained are follows. These files, if present, are in the directory indicated by II_CONFIG:

• iilink.log

  This log is used only in conjunction with the Object Management Extension. The file contains a log of the last time the iilink command was run. For details on the iilink command, see the Object Management Extension User Guide.

• 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

• 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.

Other Optional Log Files

The following types of optional log files are present on your installation:

• Individual process logs. For the following processes you can set up a separate log file to isolate the error messages relating to that process:
  • DBMS
  • GCC

    You normally do this only for a specific troubleshooting purpose. The default is that these messages are sent to the errlog.log. If you define one of these separate error logs, all messages are sent to both that file and errlog.log.

• Trace log for tracking messages at a greater level of detail
• Log for an optional Ingres facility

These optional log and trace log files can be established by setting the associated Ingres variables:

• DBMS Error log

  The DBMS error log, optionally defined as a separate file.

  This log file is established by setting the Ingres variable II_DBMS_LOG to a user file name For additional information, see the appendix "Environment Variables and Logicals." The default is all DBMS server errors and messages are sent to errlog.log.

• GCC error log

  The GCC error log, for installations using Ingres Net. This is in a user-defined file.

  This log file is established by setting II_GCCxx_LOG to the full name of a file. The error logging level is specified by II_GCCxx_LOG_LVL. These Ingres environment variables/logicals are listed in the appendix "Environment Variables and Logicals."

• GCC trace log

  The GCC trace log is set up for specific troubleshooting efforts. You set II_GCA_LOG to a user file name. The associated Ingres variable II_GCC_TRACE defines the level of tracing. These Ingres environment variables/logicals are listed in the appendix "Environment Variables/Logicals." Details on using a GCC trace are descried in User-Server Communications.

• Star error log

  The Star error log for installations running Ingres Star, if defined.

  This log file is established by setting the Ingres variable II_STAR_LOG to a user file name. For additional information, see the appendix "Environment Variables and Logicals." The default is all Ingres Star errors and messages are sent to errlog.log.