ORACLE EM DBA

Problems, Solutions, Test Cases from my professional and personal experience in technologies like Oracle Enterprise Manager 13 c,Oracle Enterprise Manager 12c, Oracle Configuration Manager and some other stuff.

Month: September 2016

Back to OEM Basics – Agent12c Blocked by OMS [Agent Resynchronization]

This blog is a part of my “Back to OEM Basics” series. In this I have explained in details how easily you can solve your “Agent blocked by OMS” issue. With the help of logs and screenshots I have made it more simple to understand.

Lets got step by step and see how you can fix your problem and can Unblock an blocked agent.


Oracle Agent usually gets blocked when it is Out-Of-Sync with the OMR repository database.

 

Step 1: How to check if agents are blocked, this can be simply done by login-in to OEM.

 

Please login to OEM and navigate to “Setup-> Manage Cloud Control –> Agents” as shown in the screenshot.

 

agent_blocked0

 

The “Manage Cloud Control” AGENTS home page will give you list all of the installed agents, you can sort the list using the “STATUS” column as shown in the below screenshot.

 

image1

 

Step 2: Login to Agent server and check the logs to verify the cause.

 

I checked agent logs on the server where agent was BLOCKED and this is what I found.

 

Agent Logs:-

2016-09-20 10:13:04,906 [9825:547A0FF8:GC.SysExecutor.1036 (Ping OMS)] INFO - attempting initial heartbeat

2016-09-20 10:13:04,919 [9825:547A0FF8] INFO - The agent has been blocked by the OMS.

2016-09-20 10:13:04,919 [9825:547A0FF8] INFO - Reason the OMS blocked the agent: 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.

2016-09-20 10:13:41,530 [9743:2F24D3F3] WARN - Subsystem (Ping Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@21a09189

2016-09-20 10:13:41,531 [9743:2F24D3F3] WARN - Subsystem (Upload Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@653b1740

2016-09-20 10:14:41,530 [9822:669C9195] WARN - Subsystem (Ping Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@354632cf

2016-09-20 10:14:41,531 [9822:669C9195] WARN - Subsystem (Upload Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@6cde3ddf

2016-09-20 10:15:41,532 [9836:6A4F37D3] WARN - Subsystem (Ping Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@39af50a4

2016-09-20 10:15:41,532 [9836:6A4F37D3] WARN - Subsystem (Upload Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@9bce0a

2016-09-20 10:16:04,938 [9759:755A5435:GC.SysExecutor.1028 (Ping OMS)] INFO - attempting initial heartbeat

2016-09-20 10:16:04,948 [9759:755A5435] INFO - The agent has been blocked by the OMS.

2016-09-20 10:16:04,948 [9759:755A5435] INFO - Reason the OMS blocked the agent: 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.

 

Step 3: Check status of agent by running “emctl status agent” command.

 

D:oracleproductagent12cr3agent_instbin> emctl status agent

Oracle Enterprise Manager Cloud Control 12c Release 2

Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.

—————————————————————

Agent Version     : 12.1.0.2.0

OMS Version       : (unknown)

Protocol Version  : 12.1.0.1.0

Agent Home        : D:/oracle/product/agent12cr3/agent_inst

Agent Binaries    : D:oracleproductagent12cr3core12.1.0.2.0

Agent Process ID  : 3416

Parent Process ID : 2524

Agent URL         : https://HANHRRP3.oiiad.com:3872/emd/main/

Repository URL    : https://hanoemap1.oii.oceaneering.com:4904/empbs/upload

Started at        : 2016-09-16 22:43:30

Started by user   : HANHRRP3$

Last Reload       : (none)

Last successful upload                       : (none)

Last attempted upload                        : (none)

Total Megabytes of XML files uploaded so far : 0

Number of XML files pending upload           : 690

Size of XML files pending upload(MB)         : 1.13

Available disk space on upload filesystem    : 47.09%

Collection Status                            : Collections enabled

Heartbeat Status                             : Agent is blocked

Last attempted heartbeat to OMS              : 2016-09-20 10:43:05

Last successful heartbeat to OMS             : (none)

Next scheduled heartbeat to OMS              : 2016-09-20 10:46:05

—————————————————————

Agent is Running and Ready

 

Step 4: Navigate to Agent home page in Oracle Enterprise Manager Console to verify and rectify issue.

 

agent_blocked1

 

The error message in console as well clearly shows that agent is Blocked and need to “unblock” it manually.

 

Step 5: Navigate to “Resynchronization” under “Agent” on the home page as show in the screenshot below.

 

agent_blocked2

 

Step 6: Select unblock agent Under “Agent Resynchronization” make the checkbox is checked and click on “Continue”.

 

agent_blocked3

 

 

Step 7: This confirms that “Agent Resynchronization” job has been executued successfully.

 

You can monitor the progress of the job by clicking the Job Name {eg. RESYNC_20160920104720}

 

agent_blocked4

 

Step 8: Check RESYNC Job Details and verify  if it is completed.

 

agent_blocked5

 

Step 9: Navigate back to agent home page and verify Agent status.

It should be “UP & RUNNING” after the RESYNC job has completed successfully.

 

agent_blocked6

 

This way you can easily un-block all of your Blocked agents and make them again fit for monitoring your targets.

Stay tuned for more “BACK TO OEM BASICS” Topics.

 

Thanks

ADDKS

EM12c login FAILED for all users after database upgrade from 11.2.0.2 to 12.1.0.2

Two days back I ran into an issue where I was not able to login to my OEM12c test environment using any of the account. This happened after OEM database upgrade. Recently I did upgrade of my OEM database from 11.2.0.2 to 12.1.0.1 followed by upgrade to 12.1.0.2.

After upgrade was done successfully I tried to login to OEM using my account “dksharma” it gave me error, then I tried using the “sysman” but login failed again. All other users also  reported the same issue.

I have document all  my findings and solution to that in the attached document. If you also face the same Issue you use to document to fix your problem.

em12c-login-failed

Regards

ADDKS

 

Prerequisite for OEM12cR4 to OEM13cR1 upgrade

If you have Oracle Enterprise Manager 12cR3/12cR4/12cR5 running on either RHEL or OEL and you are planning to upgrade your OEM to new release of 13c you must make sure that you meet below mentioned requirements.

I have shortlisted few mandatory and minimum requirements which you should keep in mind  while planning to upgrade to Oracle Enterprise Manager 13c or fresh installation of OEM13cR1.

oem13c_upgrade_checklist

In my next blog I’ll put the complete step by step document for OEM13cR1 upgrade.

Share your feedback and stay connected for next blog.

Regards

ADDKS

 

 

Upgrade your OEM12c to OEM13c -WHY?

In this blog I  have shared my recent webinar on Upgrade to OEM13c  -WHY?”. In this video I have explained few important features with example {screenshot} of Oracle Enterprise Manager 13c. These explained features are the one which were either missing or have been updated with some additional stuff.

This Webinar was done for AIOUG-North India Chapter for their monthly tech meet. This video is also shared on our Youtube channel as well. You can also find videos of all our previous webinar held in this year and last year.

G+ Link: https://plus.google.com/+DeepakSharmaEMDBA/posts/R3SfsVKJ1zo

Youtube Link: https://youtu.be/9Det73a2ZaI

Do share your feedback as it will help me do the improvement in my future posts.

 

Regards

ADDKS

 

 

© 2017 ORACLE EM DBA

Theme by Anders NorenUp ↑