Several log files are generated as part of normal GCM server
execution. Some of these log files are useful for GCM server troubleshooting
(see
Troubleshooting the GCM Server). Log files
may include the system node name as part of the file specification
as a means of isolating log files from individual system roots if
the system disk is a cluster common system disk.
The following log files are generated:
Run-time log files When a GCM server process is started, it creates the SYS$COMMON:[SYS$CONFIG]GCM_nodename_SERVER.LOG
log file. This log file may contain details to help troubleshoot
GCM server faults.
Command log files An additional log file is created for each GCM server command
that is executed. These log files have names in the following form:GCM_nodename_CMDsequence_number.LOGWhen a command executes successfully, the related log file
is deleted. In rare cases, a GCM server fault may orphan one of
these log files. At GCM server startup, any residual log files are
deleted.
Connection log files During run time, the GCM servers can be set to generate a
connection log file. This optional file, SYS$COMMON:[SYS$CONFIG]GCM_nodename_CONNECT.LOG,
contains a timestamped history of successful and failed GCM client
connections. During run time, the GCM servers can be set to generate a
GCM server event log. This optional file, SYS$COMMON:[SYS$CONFIG]GCM_nodename_EVENT.LOG,
contains a wide variety of information that may help with GCM server
troubleshooting. The content of this event log varies based on GCM server
diagnostic flags. Event log entries typically are disabled to avoid
generating excessively large files.