OEM 13c: Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered

-

Understanding OEM 13c Agent Out-of-Sync Errors

In Oracle Enterprise Manager (OEM) 13c, the Management Agent acts as the vital communication bridge between target host systems and the Management Repository (OMR). When an agent status throws the error "Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered," it signifies a mismatch in sequence numbers or timestamp tokens between the agent state and the Management Server (OMS).

This situation usually occurs during:

  • Host-level server recovery or disaster recovery tests.

  • Unscheduled agent re-installations without clearing old target metadata.

  • Long periods of network disconnection between the host and OMS.

  • Abrupt server shutdowns causing local state corruptions in the agent's filesystem.

Prerequisites & Initial Checks

Before starting the resynchronization process, log in to the affected target node via SSH as the Oracle installation owner and run an initial status check:

$ emctl status agent

If the status output confirms that the agent is blocked or marked out-of-sync, follow the step-by-step resolution steps below.

Step-by-Step Resolution Guide

Step 1: Attempt Manual Upload

First, try forcing a manual data upload from the target node to see if the OMS accepts the current sequence:

$ emctl upload agent

If the upload succeeds without errors, verify the status again. If it fails with a blockage warning, proceed to the OEM Console resynchronization.


Step 2: Navigate to the Blocked Agent in OEM Console

  1. Log into your Oracle Enterprise Manager 13c Cloud Control web console using an administrator account.

  2. Go to Setup > Manage Cloud Control > Agents.

  3. From the list of monitored agents, filter by selecting the Agent Unreachable or Blocked status category.


Step 3: Initiate Target Resynchronization

  1. Locate and click on the specific hostname corresponding to the blocked agent.

  2. From the Agent Dropdown Menu (top left of the agent home page), hover over Target Setup and click Resynchronization.

  3. Click Continue to confirm the action. OEM will submit an internal job to align the sequence keys between the repository and the host agent.


Step 4: Verify and Force Final Upload

Once the console resynchronization job completes successfully, switch back to your terminal session on the target server:

 $ emctl status agent

$ emctl upload agent


Below are the exact steps I followed to overcome the issue I faced.

On a Friday morning shift, during my monitoring routine I found the EM agent was out of sync in my tableau server.


A quick surf on the internet landed me on couple of Oracle's MOS documents and I was able to solve the issue. Below are the step by step process to fix the issue.

1. Try to upload the agent if in case it was recently recovered or reinstalled. If upload's successfully, then the issue is resolved else continue the remaining steps


2. Log in to the OEM console and select the Agents

3. Once you pulled the agents, select the 'Agent Unreachable' option

4. Now select the host against the blocked agent

5. From the LOV, choose the resynchronization option and continue the process


6. Once the sync is done, check the agent status

7. Now try to upload the agent. That's all and the issue is fixed.


****************************நன்றி****************************







Comments

Post a Comment

Popular posts from this blog

Common R12.2 adcfgclone Issues

-
ERROR: Failed to configure the target system – Failed to enable EBS_LOGON trigger The clone procedure for EBS R12.2 is quite different when compared with EBS R12.1. This post covers very generic   issues we may encounter while configuring the target server as a part of clone Process. ERROR : 1 Checking the port pool 6 done: Port Pool 6 is free Report file located at /u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/admin/out/portpool.lst The new APPL_TOP context file has been created : /u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/appl/admin/PRODERP_erpnode3.xml Check Clone Context logfile /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/bin/CloneContextPatch_0811105848.log for details. FMW Pre-requisite check log file location : /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/FMW/logs/prereqcheck.log Running: FMW pre-req check... ERROR: Run file system configuration has failed Check the logfile /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/l...
Read more

REP-3000: Internal error starting Oracle Toolkit

-
Image
Resolving "REP-3000: Internal error starting Oracle Toolkit" in Oracle EBS (11i / R12) When running concurrent programs in Oracle E-Business Suite (EBS) that produce PDF , PostScript , or HTML  output, DBAs frequently encounter the infamous runtime exception: ' REP-3000: Internal error starting Oracle Toolkit' .   This issue is notorious for disrupting the Output Post-Processor (OPP)  and concurrent manager operations across both Linux and UNIX platforms. In this post, we will examine the architectural reason behind the REP-3000 error, walk through testing the OS-level X11 display environment, update the EBS Context File, and ensure persistent display settings across AutoConfig executions.  1. Understanding the Cause: Why Does Oracle Reports Need a DISPLAY Variable? The core engine responsible for generating character-based, PDF, or PostScript reports in legacy Oracle Developer / Oracle Reports (such as ' rwrun'  or ' rwserver' ) relies on Oracle Toolk...
Read more

Error 404 -- Not Found From RFC 2068 hypertext Transfer Protocol -- HTTP/1.1

-
Image
In my environment we are having EBS(12.2.5) running with 12.1.0.2 database. One day in our DEV Instance  Front-End is not opening and faced the below error. So I followed the below steps as a solution and it worked. First, generate the JAR files Next, reload the generated jar files to the respective database  Now compile the APPS schema to reduce the count of Invalid objects. Once everything completed, you can clear your browser cache and try to login to the application., but normally the above steps will be accompanied by clearing the middle tier cache. So I gave the below steps to clear the middle tier cache from backend. To clear the cache, follow the below steps. Stop the application services Navigate to $OA_HTML/cabo/images/cache Take a backup of contents of the folder cache and then clear all the contents inside that cache folder Navigate to $OA_HTML/cabo/styles/cache Take a backup of contents of the folder ca...
Read more