21 Haziran 2012 Perşembe

[EN] EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet.

Problem:


[XXXPRO1]/oracle/product/11.1.0/agent11g/bin $ ./emctl upload agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 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.

Solution:

When you get this warning you should also check "emctl status agent" output. 


[XXXPRO1]/oracle/product/11.1.0/agent11g/bin $ ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0 
Copyright (c) 1996, 2010 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        : /oracle/product/11.1.0/agent11g/hostxxx01
Agent binaries    : /oracle/product/11.1.0/agent11g
Agent Process ID  : 8091
Parent Process ID : 8080
Agent URL         : https://hostxxx01:1830/emd/main
Repository URL    : https://hostemgrid01:1159/em/upload
Started at        : 2012-06-21 11:13:55
Started by user   : oracle
Last Reload       : 2012-06-21 11:13:55
Last successful upload                       : (none)
Last attempted upload                        : (none)
Total Megabytes of XML files uploaded so far :     0.00
Number of XML files pending upload           :      273
Size of XML files pending upload(MB)         :    52.42
Available disk space on upload filesystem    :    47.97%
Collection Status                            : Disabled by Upload Manager
Last attempted heartbeat to OMS              : 2012-06-21 11:26:12
Last successful heartbeat to OMS             : unknown
---------------------------------------------------------------
Agent is Running and Ready



As you see in the output, "Last successful heartbeat to OMS" is "unknown"

Second, you should check "emagent.trc" trace file located in /oracle/product/11.1.0/agent11g/hostxxx01/sysman/log. You should see warnings like this;



2012-06-21 11:26:34,851 Thread-119 ERROR pingManager: Did not receive valid response to ping "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 performing an agent resync from the console. Please contact EM adminstrator to unblock the agent" 
2012-06-21 11:26:43,000 Thread-121 ERROR pingManager: Did not receive valid response to ping "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 performing an agent resync from the console. Please contact EM adminstrator to unblock the agent" 
2012-06-21 11:26:43,129 Thread-121 ERROR pingManager: Did not receive valid response to ping "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 performing an agent resync from the console. Please contact EM adminstrator to unblock the agent" 
2012-06-21 11:26:50,147 Thread-4 ERROR http: Error in obtaining IP address, ret = 7005
2012-06-21 11:27:13,269 Thread-123 ERROR pingManager: Did not receive valid response to ping "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 performing an agent resync from the console. Please contact EM adminstrator to unblock the agent" 
2012-06-21 11:27:13,397 Thread-123 ERROR pingManager: Did not receive valid response to ping "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 performing an agent resync from the console. Please contact EM adminstrator to unblock the agent" 



To solve the problem you should first logon to Oracle Enterprise Manager Grid Contol home page. Click the "Setup" link upper right corner of the page. Then click "Agents" link on the blue bar. On the next screen find your host and click the link on the "Agent" bar.


On the next page you should see that agent is unreachable. Click "Agent Resynchronization" button.


Select the "Unblock agent on successful completion of agent Resynchronization" and click "Continue" button.


Wait for a few seconds.


On the next screen wait for some time again and click the refresh button until the agent is reachable.



On UNIX console execute "emctl status agent" command again.


[XXXPRO1]/oracle/product/11.1.0/agent11g/bin $ ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0 
Copyright (c) 1996, 2010 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        : /oracle/product/11.1.0/agent11g/hostxxx01
Agent binaries    : /oracle/product/11.1.0/agent11g
Agent Process ID  : 8091
Parent Process ID : 8080
Agent URL         : https:// hostxxx01 :1830/emd/main
Repository URL    : https://hostemgrid01:1159/em/upload
Started at        : 2012-06-21 11:13:55
Started by user   : oracle
Last Reload       : 2012-06-21 11:33:09
Last successful upload                       : 2012-06-21 11:33:11
Total Megabytes of XML files uploaded so far :    15.64
Number of XML files pending upload           :        0
Size of XML files pending upload(MB)         :     0.00
Available disk space on upload filesystem    :    48.08%
Last successful heartbeat to OMS             : 2012-06-21 11:32:15
---------------------------------------------------------------
Agent is Running and Ready


If you see that "Last successful heartbeat to OMS" shows a time value then the problem is solved.

Hiç yorum yok:

Yorum Gönder