One of the most confusing (and frustrating) things with Oracle Enterprise Manager is figuring out why agents are not uploading from time-to-time. This issue was worse in previous versions; in OEM12c the uploading issues have been somewhat corrected and do not seem to be that big of an issue. What I have found to be more of an issue with OEM12c is when the agent says it is unreachable within OEM12c.
An unreachable agent could be almost anything, a firewall blocking the required upload port, invalid DNS entries, and hostname configuration issues to network related issues. In most of these cases, except for agent configuration issues, the DBA doesn’t have access to resolve these issues and require the assistance of different departments within the IT. Sometimes these external resources are not available to help troubleshoot and resolve network issues; example, if you are trying to configure OEM12c at home as I have.
The problem I recently ran into while adding an agent to a local server without DNS; was that the agent would install and run; yet OMS couldn’t sync it due to metric collection errors. The status of the agent after the install was up and running yet OEM still wouldn’t recognize it. This prompted me to uninstall the agent and push the agent again. From the OEM12c management server, I was able to push the agent and add the target successfully though the Add Host Targets wizard. Although the host target is added successfully, the status in OEM12c still showed “Unreachable” due to Metric Collection Error. Why is this target unreachable, I just added the agent and didn’t have any problems with the push form OEM12c?
I was perplexed to say the least; however, in searching MOS I came across a note that helped resolve this issue. The note number for reference is: 1440682.1. This note outlines similar symptoms to what I was having and provided a workable solution. What I found interesting in this note was the fact that this issue is an unpublished bug. The note also gives examples of what messages may be received from OEM via notification messages.
The incorrect message that may be received is (via notification emails):
Message=Agent is Unreachable (REASON = unable to connect to the agent at https://hostname.domain:3872/emd/main/ [Connection timed out]). Host is unreachable (REASON = Unknown Error pinging the host of URL https://hostname.domain:3872/emd/main/.1)
As outlined in the MOS note, the workaround for this issue is to check to see if the ping property is set. If so, then it needs to be disabled to allow for the target host status to be changed. The steps below will assist in resolving this issue:
On the OMS, check the property via emctl
./emctl get property –name oracle.sysman.core.omsAgentComm.ping.pingCommand
If it returns this status:
Emdrep.ping.pingCommand=%EM_PING_COMMAND%
This is the reason for the invalid agent status and metric collection error in OEM12c.
Disable the ping command:
./emctl delete property –name “oracle.sysman.core.omsAgentComm.ping.pingCommand”
With this property removed, the OMS will ping targets using an alternative successful method (getPingCmdForOS).
Now stop and restart the OMS:
./emctl stop oms
./emctl start oms
Lastly, ensure that the agent is started and that the status in OMS is saying up. (may take a few minutes due to agent uploads)
Let me know what you thing about this resolution to this interesting problem.
Please follow and like:
Bobby Curtis
I’m Bobby Curtis and I’m just your normal average guy who has been working in the technology field for awhile (started when I was 18 with the US Army). The goal of this blog has changed a bit over the years. Initially, it was a general blog where I wrote thoughts down. Then it changed to focus on the Oracle Database, Oracle Enterprise Manager, and eventually Oracle GoldenGate.
If you want to follow me on a more timely manner, I can be followed on twitter at @dbasolved or on LinkedIn under “Bobby Curtis MBA”.
Follow if you like:
A volatilidade do Spaceman é variável e será influenciada pela sua estratégia. Levantar antecipadamente resultará numa estratégia de menor volatilidade. Por outro lado, esperar por ganhos mais avultados é uma estratégia de maior volatilidade que envolverá ganhar menos vezes, em média, mas ganhar prémios maiores quando ganhar. O Spaceman é um jogo multijogador online com um tema espacial no qual os jogadores apostam no progresso do lançamento de um pequeno astronauta na estratosfera. Não há muito contexto para explicar o motivo pelo qual o astronauta quer voar, mas ele voa. O Spaceman é um jogo multijogador online com um tema espacial no qual os jogadores apostam no progresso do lançamento de um pequeno astronauta na estratosfera. Não há muito contexto para explicar o motivo pelo qual o astronauta quer voar, mas ele voa.
https://aprenderfotografia.online/usuarios/ulleposbumb1983/profile/
A rede de parques indoor Game Station anunciou investimento de R$ 300 mil em iniciativas voltadas à inclusão de crianças autistas em suas unidades. Os recursos foram aplicados em treinamentos de equipe, aquisição de equipamentos como abafadores de ruído e em benefícios diretos às famílias neurodivergentes na aquisição de serviços da rede segundo revela a afirma Paula Margolis, vice-presidente do grupo. a rede Game Station atua há mais de 25 anos e conta com mais de 65 unidades em 10 estados brasileiros e agora faz parte do grupo Azeka Games depois da fusão em meados de 2020 entre os empresários, Ernesto Margolis (que faleceu este ano) e Ernani Azeka. É importante notar que o Telegrupos não tem qualquer vínculo com o Telegram FZ-LLC. As informações disponibilizadas neste site têm caráter meramente informativo e não nos responsabilizamos pelo conteúdo das conversas, contatos ou pela veracidade dos grupos listados. Todas as interações ocorrem diretamente nos canais e grupos do Telegram, fora do nosso site.