Logging and Locking Systems
The logging and locking systems coordinate the locking, recovery, and journaling of the Ingres catalogs and table components of Vector databases. The system is composed of the following components:
• Lock manager
• Logging facility
• Recovery process
• Archiver process
• Log files
Log Files
Vector writes information to the following log files:
• X100 Write-ahead Log (WAL), which is the X100 transaction log
• X100 Error Log (vectorwise.log)
• Ingres Transaction Log File
• DBMS Error log (error.log)
• Archiver Log
• Recovery Log
• Primary Configuration Log Files
• Operational Configuration Log Files
• Optional Log Files
X100 Write-ahead Log (WAL)
Updates, inserts, and deletes to the data and the layout of the data in the data files are stored as log information in the main.wal file. The WAL also contains persistent catalog information. The data files and the WAL file must be considered together as files that represent the database. A WAL file exists for each database and is located in the wal subdirectory of the default data location.
X100 Error 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. For Vector for Windows installations: %ALLUSERSPROFILE%\Actian\VectorXX\files\vectorwise.log. You can configure error logging to change the level of information logged, the name and location of the log file, and the record format.
Ingres Transaction Log File
Each installation has an Ingres 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.
DBMS 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 Vector 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
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/ingres/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.
Optional Log Files
Vector provides various optional log files that can be used for troubleshooting purposes. Optional log files are provided for:
• Logging messages for specific processes
• Generating logs for a specific facility
• Tracing logs and tracking messages at a greater level of detail
Process Logs
Process logs can be set up for the following processes to isolate the error messages relating to that process:
• DBMS
• GCC
Optional Log Facility
Logging can be specified for a specific Vector facility. The following optional log and trace log files can be established by setting the associated Vector variables.
DBMS Error Log File
The DBMS Server error log is optionally defined as a separate file. This log file is established by setting the Vector variable II_DBMS_LOG to a user-defined file name.
Note: By default, all logged messages are sent to the errlog.log file. If you define separate error logs, all messages are sent to both that error log file and errlog.log.
GCC Trace Log File
The GCC trace log is set up for specific troubleshooting efforts. You set II_GCA_LOG to a user file name. The associated Vector environment variable II_GCC_TRACE defines the level of tracing.
For more information about these log files, see the chapter "Setting Environment Variables" and the appendix "Environment Variables."