VCS has two error message logs that can be viewed to monitor system performance: the engine log and the agent log. Log file names are appended by letters. Letter ”r;A” indicates the first log file, ”r;B” the second, ”r;C” the third, and so on.
Both logs use the following tags to indicate the seriousness of errors:
TAG_A indicates a critical error within a VCS process. Contact VCS Technical Support immediately if you see this tag.
TAG_B indicates failure of a cluster component, unanticipated state change, or termination or unsuccessful completion of a VCS action.
TAG_C indicates a warning or error, but not an actual fault.
TAG_D informs the user that VCS has initiated an action.
TAG_E informs the user of various state messages or comments.
The logs can be viewed using any text editor.
The engine log is located at /var/VRTSvcs/log/engine_A.log.
The format of an engine log messages is:
TAG | Date (yy/mm/dd) | Time | Product | Message ID | Message
The following is a typical engine log entry:
TAG_C 2001/12/03 18:54:58 VCS:10075:building from remote system.
The agent log is located at $VCS_HOME/log/agent_A.log. The format of agent log messages is:
TAG | Date (yy/mm/dd) | Time | Product | Message ID | Agent Type |Resource Name | Entry Point | Message
The following is a typical agent log entry:
TAG_C 2001/12/03 19:40:01 VCS:254001:Oracle:oracle1:online:One or more attributes contain invalid values.
All tag entries are written to the engine and agent logs. Tag A and B entries are also written to the system log, which can be viewed at _____________.
See these topics: