Professional Documents
Culture Documents
After upgrading the OMS and Agent to 10.2.0.5 version, getting the following err
or in <AGENT_HOME>/sysman/log/emagent.trc:
Did not receive valid response to ping "ERROR-Agent is blocked. Blocked reason i
s: Agent is out-of-sync with repository. This most likely means that the agent w
as reinstalled or recovered. Please contact an EM administrator to unblock the a
gent by performing an agent resync from the console. Please contact EM adminstra
tor to unblock the agent"
The command: emctl upload agent
fails with:
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
--------------------------------------------------------------EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..
The Agent can however be secured successfully with the OMS.
Cause
The Agent Re-synchronisation is a new feature in 10.2.0.5 Grid Control which ver
ifies whether an Agent that been uploading earlier to the OMS is re-installed or
restored from a backup. If yes, the OMS blocks further updates from this Agent
until the information about the Agent and all its targets are synchronized betwe
en the Repository and the Agent.
Factors which can cause the Agent to go out-of-sync with the Repository:
1. Agent is re-installed or restored from a backup, on the same port number as b
efore.
2. The <AGENT_HOME>/sysman/emd/agntstmp.txt is manually deleted for some reason.
Solution
To solve the issue you have to perform following from grid console
+ Login to 10.2.0.5 Grid Console as sysman user
+ Navigate to Setup -> Agents -> Click on problematic Agent name
+ In Agent home page click on "Resynchronize" Button on right hand top of the pa
ge.
Choose the 'Unblock Agent' option and click Continue
Ensure that the Agent is up and running when attempting the Resynchronization.
Once the re-synchronization is completed successfully, the Agent should be able
to communicate with the OMS.
Sometimes, the re-synchronization may complete with results such as:
Agent Operation completed with errors. For those targets that could not be saved
, please go to the target's monitoring configuration page to save them. All othe
r targets have been saved successfully. Agent has not been unblocked.
1. Error saving target database1.domain:oracle_database - Skipping target {datab