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.

Right After Install, the Grid Control Agent Generates ERROR-Agent is blocked. Blocked reason is: Agent is out-of-sync with repository [ID 1307816.1]

Applies to:

Enterprise Manager Base Platform - Version: 10.2.0.5 to 11.1.0.1 - Release: 10.2 to 11.1
This problem can occur on any platform.

Symptoms

After installing the agent, it generates the following errors in the emagent.trc file.

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"

In this case, there is no issue with the agent start and Securing the Agent is always successful.

./emctl secure agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Agent successfully stopped... Done.
Securing agent... Started.
Enter Agent Registration Password :
Agent successfully restarted... Done.
Securing agent... Successful.

But the command emctl status agent shows:

Last successful upload : (none)
Last attempted upload : (none)
Last successful heartbeat to OMS : unknown

emctl upload agent does not give the error as "EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet"

But gives the error similar to the following:

[oraoem@lgpodb002 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: Failed to upload file A0000001.xml: HTTP error.

Resynchronization of the agent as per the document Note 799618.1 does not resolve the issue and gives an error message that resynchronization is failed.

Cause

As this issue is happening right after the installation of agent, this can happen if there was a duplicate/old entry in the repository tables with the name of same agent and targets on this host.

Executing the following query gives this information:

SQL>select target_name, target_type from mgmt_targets where EMD_URL='https://hostname.domainname:<port>/emd/main/'

TARGET_NAME                                           TARGET_TYPE
------------------------------------------------------------------------------
<hostname.domainname>:<port>                                oracle_emd

Solution

Follow this action plan to resolve the issue. 

Please note that this needs to be done only for the new agent installation as the action plan will remove all the targets and agent historical information from the repository.

1. Stop the agent 
<AGENT_HOME>/bin>./emctl stop agent

2. Ensure that there are no emagent processes on the server

$ps -ef|grep emagent

If you see any process, please kill all of them.

3. Login to the repository database as SYSMAN user and execute the following query to clean up the old agent:

SQL>exec mgmt_admin.cleanup_agent('<hostname.domainname>:<port>');