Русские видео

Сейчас в тренде

Иностранные видео


Скачать с ютуб How to Troubleshoot OEM 13c agent unreachable issue - Reestablish Agent Communication to the OMS в хорошем качестве

How to Troubleshoot OEM 13c agent unreachable issue - Reestablish Agent Communication to the OMS 2 года назад


Если кнопки скачивания не загрузились НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием, пожалуйста напишите в поддержку по адресу внизу страницы.
Спасибо за использование сервиса savevideohd.ru



How to Troubleshoot OEM 13c agent unreachable issue - Reestablish Agent Communication to the OMS

In this tutorial I am demonstrating how to fix an OEM 13c agent with broken communication to the OMS. Sometimes we encounter this issue when we see that the agent communication to the OMS is broken, the agent is out of sync or its not able to upload data to the oms. when you login to the agent server, you will see the agent is up and running but in the OEM console you will see the agent is unreachable. A couple of situations that lead to this issue are: -when the file system where the agent is installed is 100% full for a long time and agent is not able to gather or upload new information to the oms -when there is a network issue and agent is not able to upload new information to the oms -a server level blackout did not end gracefully etc Even if you resolve the underlying issue that has caused these situations, you will see that the agent sometimes is not able to establish the communication with OMS. I am giving 3 different options to resolve this agent issue: Solution-1 most of the time this solution works: cd /u001/oracle/product/agent13c/agent_13.4.0.0.0/bin ./emctl stop agent ./emctl clearstate agent ./emctl start agent ./emctl upload agent Solution-2 if the solution-1 does not work then go ahead with this solution ./emctl stop agent ./emctl clearstate agent ./emctl secure agent [agent registration password] if you forgot the registration password, you can always create a new one-time or persistent password by going to setup - security - registration passwords ./emctl start agent ./emctl upload agent ./emctl pingoms ./emctl verifykey ./emctl status agent Solution-3 if the solution-1 and 2 did not work then go ahead with this solution. Go to setup - manage cloud control - agents select the agent and block it with a reason like "Temporary" then go to the agent home page - Agent - Resynchronization So before you take a more drastic measure like reinstalling an agent, this is how you can re-establish the agent to oms communication and bring the agent online or in-sync with OMS.

Comments