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 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.
Last modified date: 01/30/2023