VCS generates two types of logs: the engine log and the agent log. Log file names are appended by letters. Letter A indicates the first log file, B the second, C the third, and so on.
The engine log is located at /var/VRTSvcs/log/engine_A.log. The format of engine log messages is:
Timestamp (Year/MM/DD) | Mnemonic | Severity | UMI | Message Text
Timestamp: the date and time the message was generated.
Mnemonic: the string ID that represents the product (for example, VCS).
Severity: levels include CRITICAL, ERROR, WARNING, NOTICE, and INFO (most to least severe, respectively).
UMI: a unique message ID.
Message Text: the actual message generated by VCS.
A typical engine log resembles:
2011/07/10 16:08:09 VCS INFO V-16-1-10077 Received new cluster membership
The agent log is located at
/var/VRTSvcs/log/<agent>.log. The format of agent log messages resembles:
Timestamp (Year/MM/DD) | Mnemonic | Severity | UMI | Agent Type | Resource Name | Entry Point | Message Text
A typical agent log resembles:
2011/07/10 10:38:23 VCS WARNING V-16-2-23331 Oracle:VRT:monitor:Open for ora_lgwr failed, setting cookie to null.
Note that the logs on all nodes may not be identical because
VCS logs local events on the local nodes.
All nodes may not be running when an event occurs.
VCS prints the warning and error messages to STDERR.
If the VCS engine, Command Server, or any of the VCS agents encounter some problem, then First Failure Data Capture (FFDC) logs are generated and dumped along with other core dumps and stack traces to the following location:
For VCS engine:
For Command Server:
For VCS agents:
$VCS_DIAG/diag/agents/type, where type represents the specific agent type.
The default value for variable $VCS_DIAG is
If the debug logging is not turned on, these FFDC logs are useful to analyze the issues that require professional support.