5.4 Checking the server logs

HA Monitor Kit outputs the messages issued by the server start, termination, and monitoring commands to server logs. The standard output and standard errors of any Oracle commands executed inside the server start, termination, and monitoring commands are also output to server logs. By checking the server logs, you can review the processing results of the server start, termination, and monitoring commands. While the system is running, the server log content is constantly being updated based on the result of the monitoring process.

Note
When checking the server logs while the server is running, only view them and do not save them. Otherwise, the log information that is output while you are viewing the server log may be lost.

This section explains the details of the server logs.

Organization of this section
(1) File types
(2) File size
(3) Output example
(4) Message language environment

(1) File types

The table below lists the server logs. The value of the LOGNAME environment variable of the server start, termination, or monitoring command provided by HA Monitor Kit is substituted for server-alias-name in the file name.

Table 5-1 List of server logs

File nameDescription
/opt/hitachi/HAmon/spool/server-alias-name.oralogThis is the server log file. The content of the messages issued by the server start, termination, and monitoring commands is output to this file.
/opt/hitachi/HAmon/spool/server-alias-name.oralog_oldThis is the previous generation of the server log file. It is created by adding the _old suffix to the server log file when it exceeds the specified size at the following times:
  • When the server start, termination, or monitoring command is executed
  • Immediately before a monitoring process is executed in the server monitoring command
/opt/hitachi/HAmon/spool/server-alias-name.oralog_errThis is the server log file created during the occurrence of the most recent error. It is created by adding the _err suffix to the server log file when the server start, termination, or monitoring command terminates with a non-zero return value. View this file when investigating an error.

(2) File size

You can change the server log file size in the LOGsize environment variable of the server start, termination, or monitoring command. The default is 1,048,576 bytes (1 megabyte). Under normal conditions, use this default file size. Increase the size only if the volume of output is large and may cause the log to run out of room.

When changing the file size, choose the largest value among the results (in bytes) obtained from the following Formulas 1 through 3:

Formula 1
240 + (number of Oracle instances and Oracle listeners inside server) [Figure] 160
+ (combined total size of messages output by products other than HA Monitor Kit such as Oracle during startup process)
Formula 2
60 + (number of Oracle instances and Oracle listeners inside server) [Figure] 170
+ (combined total size of messages output by products other than HA Monitor Kit such as Oracle during single monitoring process)
Formula 3
240 + (number of Oracle instances and Oracle listeners inside server) [Figure] 160
+ (combined total size of messages output by products other than HA Monitor Kit such as Oracle during termination process)

For details about the LOGSIZE environment variable of the server start, termination, or monitoring command, see 4. Setting Up the Server Start, Termination, and Monitoring Commands.

To estimate a size that is large enough to hold logs for a certain duration or to calculate the total size of the logs that the file can hold, determine the combined total size of messages that are output during the entire period from server start to termination.

Note that formula 1, formula 2, and formula 3 in the following formula mean the results of the above formulas for estimating the server log file size:

formula 1 + formula 2[Figure] (server operation time (in seconds) [Figure] monitoring interval of server monitoring command (in seconds)) + formula 3

(3) Output example

The following figure shows an example of a server log that is output when the startup of an Oracle instance fails:

[Figure]

The numbers in the figure are explained below.

  1. This is a message that is output by a HA Monitor Kit command. Message output date/time and ID are output. In this example, messages KAMK00401-I and other information are output. For details about the messages that are output by HA Monitor Kit, see 6.2 Message details.
  2. These are messages that are output by Oracle after it is initiated by HA Monitor Kit and messages that are output by processes that the user added to the server start, termination, and monitoring commands. For details about the messages that are output in these lines, see the Oracle documentation and other documents.

(4) Message language environment

Oracle messages are output to the server logs in the language corresponding to HA Monitor's language environment. The following table shows the correspondence between message language environments:

Table 5-2 Correspondence between message language environments

HA Monitor's language environment (LANG)Oracle's language environment (NLS_LANG)Message language
ja_JP.UTF-8JAPANESE_JAPAN.AL32UTF8Japanese (UTF-8)
ja_JP.eucJPJAPANESE_JAPAN.JA16EUCJapanese (EUC)
ja_JP.SJISJAPANESE_JAPAN.JA16SJISJapanese (S-JIS)
OtherNot set.English