EMD upload failure for Oracle EM Grid Control 11g Problem

After installing the OEM grid control 11g, reinstall the agent on a monitoring server and the agent will not be able to work. The error "EMD upload error: uploadXMLFiles skipped" will be reported during the emctl upload check ". As follows:

[Oracle @ codb2 ~] $ Emctl upload

Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0

Copyright (c) 1996,201 0 Oracle Corporation. All rights reserved.

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

EMD upload error: uploadXMLFiles skipped: OMS version not checked yet. If this issue persists check trace files for ping to OMS related errors.

This is an issue that occurs when the agent is configured after the installation of EM Grid Control 11g is completed. If you need to know how to install and configure grid control 11g, refer to this article.

How can this problem be solved?

First, I used emctl verifykey for verification on the monitoring server, that is, the codb2 server. It was found that OMS gave this agent to the block.

[Oracle @ codb2 ~] $ Emctl verifykey

Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0

Copyright (c) 1996,201 0 Oracle Corporation. All rights reserved.

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

Verifykey: Successfully Completed communication with agent

EMD pingOMS error: Invalid ping response "ERROR-Agent is blocked. blocked reason is: Agent is out-of-sync with repository. this most likely means that the agent was reinstalled or recovered. please contact an EM administrator to unblock the agent by using Ming an agent resync from the console. please contact EM adminstrator to unblock the agent"

Then, I will go to the OEM grid control 11g console to solve this block.

In the main directory of the console, select an unknown object and re-Synchronize the agent. The following error is reported:

"The proxy operation has been completed, but an error has occurred. For targets that cannot be saved, go to the target monitoring configuration page to save them. All other targets are successfully saved. The blocked proxy is not canceled.

An error occurred while communicating with the proxy. Error message-oracle. sysman. emSDK. emd. comm. CommException: IOException in reading Response: Connection reset"

The proxy cannot be canceled on the Interface operation. Therefore, we log on to the grid control database to directly modify the configuration information.

Use the mgmt_admin.cleanup_agent ('host: port') function to clear the agent.

The host and port values are obtained from the emctl status agent output information on the monitoring server.

The details are as follows:

[Oracle @ codb1 ~] $ Emctl status agent

Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0

Copyright (c) 1996,201 0 Oracle Corporation. All rights reserved.

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

Agent Version: 11.1.0.1.0

OMS Version: 11.1.0.1.0

Protocol Version: 11.1.0.0.0

Agent Home:/u01/app/oracle/product/10.2.0/oms/agent11g/codb1.htsc.com.cn

Agent binaries:/u01/app/oracle/product/10.2.0/oms/agent11g

Agent Process ID 21727

Parent Process ID: 21673

Agent URL: https://codb1.htsc.com.cn: 3872/emd/main

Repository URL: https: // htwebapp1: 4900/em/upload

Started at: 15:54:52

Started by user: oracle

Last Reload: 16:05:04

Last successful upload: 16:10:07

Total Megabytes of XML files uploaded so far: 0.39

Number of XML files pending upload: 0

Size of XML files pending upload (MB): 0.00

Available disk space on upload filesystem: 44.51%

Last successful heartbeat to OMS: 16:22:05

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

Agent is Running and Ready

Pay attention to this line

Agent URL: https://codb1.htsc.com.cn: 3872/emd/main

Codb1.htsc.com.cn: 3872 is the value of these parameters. Log on to the database as a sysman user in sqlplus and run

Execute mgmt_admin.cleanup_agent ('codb1 .htsc.com.cn: 100 ');

The execution process is as follows:

/U01/oracle/home @ webdg2 => emrep $ sqlplus sysman/htzq2012

SQL * Plus: Release 10.2.0.4.0-Production on Thu May 31 17:15:54 2012

Copyright (c) 1982,200 7, Oracle. All Rights Reserved.

Connected:

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-64bit Production

With the Partitioning, Real Application Clusters, OLAP, Data Mining

And Real Application Testing options

SQL> execute mgmt_admin.cleanup_agent ('codb1 .htsc.com.cn: 100 ');

PL/SQL procedure successfully completed.

Next, we went to the monitoring server to clean up some files.

Go to the installation directory of grid control and run the following command.

Rm-r./sysman/emd/state /*

Rm-r./sysman/emd/collection /*

Rm-r./sysman/emd/upload /*

Rm./sysman/emd/lastupld. xml

Rm./sysman/emd/agntstmp.txt

Rm./sysman/emd/blackouts. xml

Rm./sysman/emd/protocol. ini

Finally, reconfigure the agent.

Emctl clearstate agent

Emctl secure agent

Emctl start agent

After all these operations are completed, check whether emctl upload is normal.

[Oracle @ codb1 ~] $ Emctl upload

Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0

Copyright (c) 1996,201 0 Oracle Corporation. All rights reserved.

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

EMD upload completed successfully

The execution result is displayed as OK.