OpenVMS: Getting started with the 10.2 Grid Control Agent on OpenVMS
(Doc ID 739445.1)
Last updated on APRIL 14, 2022
Applies to:Enterprise Manager Base Platform - Version 10.2.0.2 to 10.2.0.2 [Release 10.2]
HP OpenVMS Alpha
HP OpenVMS Itanium
The purpose of this note is to provide information on the standalone EM Grid Control Agent 10.2 for OpenVMS.
The EM Grid Control Agent 10.2 for OpenVMS Alpha and Itanium was released on September 19th, 2008 and is available as download from OTN as of September 24th:
The staging area requires 7742480 OpenVMS blocks.
This article lists
- pointers to other relevant reference articles
- instructions for file capture to assist Oracle Support in troubleshooting
- pointers to patches and/or available patchsets
- any other information that may be helpful to customers
The GRID CONTROL AGENT for OPENVMS 10.2 is a STANDALONE product that MUST be INSTALLED IN ITS OWN SEPARATE LOCATION (ORACLE_HOME).
The Grid Control Agent for OpenVMS is certified on the following OS versions:
OpenVMS AlphaServer 8.2, 8.3
OpenVMS Integrity Server 8.2-1, 8.3-1H1
Future certifications can be found in:
<Note.412431.1> Oracle Enterprise Manager 10g Grid Control Certification Checker
(Select the correct version tab for the Agent part)
This article was last updated November 1st, 2010.
This article is for customers running Oracle RDBMS on OpenVMS who plan to install the EM Grid Control Agent to monitor those databases.
The information in this article assumes you are familiar with OpenVMS installations as well as the Grid Control Console, repository database and OMS on Unix or Windows that the agent will connect to.
Dbconsole is not available on OpenVMS, and the Agent requires the above pieces to work.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
A. Mandatory Reading
A.1. "My Oracle Support" articles
B. Tips to install and setup the Grid Control Agent
|B.1. Precreate ORAINST.LOC|
|B.2. Specifying Management Server Name during installation.|
|B.3. Listener.ora file content formatting|
B.4. Empty Targets.xml
|B.5. Ensure that your agent can talk to the OMS|
|B.6. Ignore certain messages from orauser.|
B.7. Temporary Files
|B.8. File ownership|
|B.9. LOGIN.COM must have a $set noverify|
|B.10. "$" sign in disknames|
|B.11. Cluster wide deployment|
C. Troubleshooting steps
C.1. Check the startup and trace files.
C.2. Files needed for Support to identify your issue.
|C.2.1 Provide startup and emagent trace and log files:|
C.2.2 Zip and upload targets.xml and emd.properties
C.2.3 Provide WGET results
C.2.3 Provide the batch queue definitions:
C.2.4. If your issue is related to some job/screen on the OMS:
C.2.5 Provide reverse nslookup information:
|C.2.6 Provide Ping results from the Grid Agent Node|
C.2.7 Provide TCPIP information from the OpenVMS node
|C.2.8. Delete status files only *IF* requested to do so by Support|
C.2.9 Provide an RDA from the OpenVMS node
|C.2.10. Provide the Grid Agent patch level|
|D. Patches, Patchsets and Known workarounds|