My Oracle Support Banner

EM 13c Agent Block With Error "Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered" (Doc ID 2642969.1)

Last updated on MAY 09, 2023

Applies to:

Enterprise Manager Base Platform - Version 13.2.0.0.0 and later
Information in this document applies to any platform.

Symptoms

NOTE: Agent can be blocked due to various reasons. Scope of this document is to provide the solution when the agent is blocked due to BounceCtr Mismatch which is the popular use case.

Checking the agent status after the server restart gives the following error:

$emctl status agent
Oracle Enterprise Manager Cloud Control 13c Release x
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 13.x.0.0.0
...
Heartbeat Status : Agent is blocked
Blocked Reason : 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.

and

$emctl upload agent
Oracle Enterprise Manager Cloud Control 13c Release x
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD upload error:full upload has failed: The agent is blocked by the OMS. 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. (AGENT_BLOCKED)

$../gc_inst/em/EMGC_OMSx/sysman/log/emoms.log reports following errors

[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR gcloader.Util logp.251 - [EM-03555] Agent with URL https://<agent_home>:<port>/emd/main/ is out-of-sync with repository (2/120) !
java.lang.Exception: Agent with URLhttps://<agent_home>:<port>/emd/main/ is out-of-sync with repository (2/120) !
at oracle.sysman.core.pbs.gcloader.Receiver.validateBounceCounter(Receiver.java:1926)
...

These symptoms can also occur when an agent is reinstalled without cleaning up the old agent completely. 

OR

When the agent installation is done using a blocked port (No communication from OMS to Agent port)

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.