InfoScale™ 9.0 Cluster Server Implementation Guide for Oracle - Windows
- Introducing the VCS agents for Oracle and NetApp
- Installing and configuring VCS
- Installing and configuring Oracle
- About installing Oracle
- Prerequisites for installing Oracle
- Installing Oracle
- About creating and configuring Oracle
- Prerequisites for configuring Oracle
- Configuring Microsoft iSCSI initiator
- Managing storage using Windows Logical Disk Manager
- Managing storage using NetApp filer
- Creating a temporary service group
- Configuring Oracle on the first node
- Dismounting a volume
- Bringing the temporary service group online
- Creating the Oracle database on shared disks
- Creating the listener service
- Configuring the listeners to use the virtual IP address
- Associating the database with the listener
- Configuring the Oracle database
- Configuring the Oracle and listener services
- Disconnecting virtual disks from the first node
- Releasing disks (if you use Windows LDM)
- Configuring Oracle on failover nodes
- Configuring the Oracle service group
- Administering the Oracle service group
- Troubleshooting
- Appendix A. Resource type definitions
- Appendix B. Sample configuration
- Appendix C. Oracle Enterprise Manager 10g Grid Control with VCS
- About Oracle Enterprise Manager 10g Grid Control with VCS
- Installing the VCS agent for Oracle
- Installing Oracle Enterprise Manager server
- Installing Oracle
- Installing the Oracle Management Agent
- Creating and configuring Oracle database and listener on the first node
- Configuring Oracle on failover nodes
- Configuring the Oracle service group
- Configuring a virtual network name
- Configuring the listener for virtual network name
- Configuring the database service for virtual network name
- Configuring an additional Oracle management agent
- Adding the database to the OEM 10g Grid Control
- Making the additional agent highly available
VCS logging
VCS generates two error message logs: the engine logs and the agent logs. Log file names are appended by letters. The letter A indicates the first log file, B indicates the second, C indicates the third, and so on.
The agent log is located at: %VCS_HOME%\log\agent_A.txt.
The format of agent log messages is: Timestamp (YYYY/MM/DD) | Mnemonic | Severity | UMI | Agent Type | Resource Name | Entry Point | Message Text.
The following table describes the agent log message components and their descriptions.
Table: Log message components and their description
Log message component | Description |
|---|---|
Timestamp | Denotes the date and time when the message was logged. |
Mnemonic | Denotes which Arctera product logs the message. For Cluster Server, the mnemonic is 'VCS'. |
Severity | Denotes the severity of the message. Severity is classified into the following types:
|
UMI or Unique Message ID | UMI is a combination of Originator ID, Category ID, and Message ID. For example, the UMI for a message generated by the Oracle agent would resemble: V-16-20046-5. Originator ID for all VCS products is 'V-16.' Category ID for Oracle agent is 20046, for Netlsnr agent is 20047. Message ID is a unique number assigned to the message text. |
Message Text | Denotes the actual message string. |
You can view these message logs using Notepad or any text editor. All messages are logged to the engine and the agent logs. Messages of type CRITICAL and ERROR are written to the Windows event log.
A typical agent log resembles:
2010/05/10 09:32:44 VCS NOTICE V-16-20046-5 Oracle:
Oracle-DATA1:online:Service status is Running