Oracle EM Grid Control cannot connect to the agent

Oracle em grid control 10.2.0.2 is installed on a windows Server, and an existing database is used as the database.

The oracle emgrid agent software is installed on various linux servers for monitoring the oracle database and rac system. The agent version I installed is 10.2.0.5.

The installation of this version leads to a major problem that will be introduced later.

When you use a browser to log on to the oms server, the host item is normally accessed and displays host-related information, such as memory and IO.

However, when accessing the database target, enter sys connection, and an error occurs.

Check the log file D: \ OracleEMGridControl \ oms10g \ sysman \ log \ emoms. log. The error is as follows:

14:06:09, 531 [Thread-27] ERROR em.jobs remoteOp.2114-DBVerify. remoteOp (): CommException: Internal ERROR

14:06:09, 531 [Thread-27] ERROR db. rac populateStatusPage.772-RacState. populateStatusPage: result from version retrieval had errors.

14:06:11, 593 [EMUI_14_06_11 _/console/rac/racState] ERROR db. rac onEndProcess.1069-RacStateController. onEndProcess: hasErr = true, errType = 6, errMsg = internal ERROR

2010-05-24 14:06:58, 312 [MetricCollector: RACHOMETAB_THREAD600: 60] ERROR rt. RacMetricCollectorTarget _ getAllData.184-oracle. sysman. emSDK. emd. comm. CommException: Connection timed out: connect

Oracle. sysman. emSDK. emd. comm. CommException: Connection timed out: connect

At oracle. sysman. emSDK. emd. comm. EMDClient. getResponseForRequest (EMDClient. java: 1541)

At oracle. sysman. emSDK. emd. comm. EMDClient. getMetrics (EMDClient. java: 913)

At oracle. sysman. emo. rac. perform. metric. rt. RacHomeTab. _ getAllData (RacHomeTab. java: 180)

At oracle. sysman. emo. rac. perform. metric. rt. RacHomeTab. getData (RacHomeTab. java: 91)

At oracle. sysman. emo. perf. metric. eng. MetricCached. collectCachedData (MetricCached. java: 404)

At oracle. sysman. emo. perf. metric. eng. MetricCollectorThread. _ collectCachedData (MetricCollectorThread. java: 596)

At oracle. sysman. emo. perf. metric. eng. MetricCollectorThread. run (MetricCollectorThread. java: 320)

At java. lang. Thread. run (Thread. java: 534)

Analysis and Solution Process
Step 1: analyze whether the agent can upload monitoring information to the OMS server on the agent Server

/U01/oracle/home @ webdg1 => servdb1 $ emctl upload

Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.

Copyright (c) 1996,200 9 Oracle Corporation. All rights reserved.

---------------------------------------------------------------

EMD upload completed successfully

/U01/oracle/home @ webdg1 => servdb1 $

If this step fails, you need to find the agent or network problems.

Step 2: Check the OMS status

D: \ OracleEMGridControl \ oms10g \ opmn \ bin> opmnctl status

 

Processes in Instance: EnterpriseManager0.gridctrl01.htsc.com

------------------- + -------------------- + ---------

Ias-component | process-type | pid | status

------------------- + -------------------- + ---------

DSA | N/A | Down

LogLoader | logloaderd | N/A | Down

Dcm-daemon | N/A | Down

Productname | home | 4576 | Alive

Productname | OC4J_EMPROV | 4536 | Alive

Productname | OC4J_EM | 5344 | Alive

HTTP_Server | 6080 | Alive

WebCache | 3088 | Alive

WebCache | WebCacheAdmin | 2280 | Alive

The display is normal.

Modified the/etc/hosts file of the OMS server and added the ip host name information of all monitored agent servers.

The monitored server is two database servers, which constitute a RAC cluster. Therefore, you need to add the VIP information together.

192.168.15.215 webdg1.htsc.com webdg1

192.168.15.217 webdg2.htsc.com webdg2

192.168.15.216 webdg1-vip.htsc.com webdg1-vip

192.168.15.218 webdg2-vip.htsc.com webdg2-vip

The error is returned when the configuration is performed again.

Oracle. sysman. emSDK. emd. comm. commException: SAXParseException in parsing Response: Computed columns can be specified only after other columns-SAXParseException in parsing Response: Computed columns can be specified only after other columns

 

In the metalink Document Cannot Configure Grid Targets [ID 840367.1], the following explanation is obtained:

Cause

The OMS 10.2.0.2 is too old and its not able to parse the response of the 10.2.0.5 agent

 

Solution

Upgrade the OMS to 10.2.0.4 or 10.2.0.5

In this environment, the agent is indeed 10.2.0.5, And the oms is 10.2.0.2. Only OMS can be upgraded.

For more information about Oracle, see Oracle topics page http://www.bkjia.com/topicnews.aspx? Tid = 12