Log Files
Vector maintains log files to which it writes information about the installation activities.
X100 Write-ahead Log
Vector keeps information on the internal state of the database in the Write-Ahead Log (WAL), which is stored in the wal directory. The wal directory exists for each database and is located in the database directory of the default data location. The wal directory contains the main.wal file and the pdts subdirectory. The pdts subdirectory contains per-partition wal files that store PDTs.
For information on the WAL, see
X100 Write-Ahead Log on page 82.
Ingres 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.
Linux: The Linux log file can be created as a raw partition or a number of raw partitions.
X100 Error Log (vectorwise.log)
Errors and other messages for the X100 engine are logged in the vectorwise.log file.
The file is located in: II_SYSTEM/ingres/files/vectorwise.log
DBMS Error Log (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 (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 (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 Vector and suspect that the DBMS Server is in recovery mode.
Primary Configuration Log Files
Vector maintains transcripts of various configuration operations. The primary configuration log files that Vector 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.
The primary configuration log files are located in the $II_SYSTEM/ingres/files/ directory.
Optional Configuration Log Files
Vector provides the following optional configuration log files. These files, if present, are in the directory indicated by II_CONFIG.
Note: In Linux, the II_CONFIG file must always be in $II_SYSTEM/Vector/files.
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.
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 Vector facility
These optional log and trace log files can be established by setting the associated Vector variables:
DBMS Error log
The DBMS error log, optionally defined as a separate file.
This log file is established by setting the Vector variable II_DBMS_LOG to a user file name For additional information, see the appendix “Environment Variables.” The default is all DBMS server errors and messages are sent to errlog.log.
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 Vector variable II_GCC_TRACE defines the level of tracing. These Vector environment variables are listed in the appendix “Environment Variables.” Details on using a GCC trace are descried in
User-Server Communications.
Configure Log Rotation
The error log files can be rotated automatically when they exceed a given size in megabytes by setting the max_log_sz parameter.
Rotated files include errlog.log, iiacp.log, iircp.log and DBMS logs. Archived files are placed in the same directory as the rotated file and are postpended with a .YYYYMMDDHHMM extension.
To configure log rotation
1. Establish the max_log_sz parameter by issuing the following command (for Linux and Windows):
iiinitres max_log_sz
The parameter is established in CBF.
2. Start CBF and then set a value for max_log_sz by using the InstConfig menu option.