I have a OEM 13c installation on my test network – and a few databases with 13c agents all running linux.
After adding an agent succussfully, the IP changed on OMS (moved the VM that as hosting and the IP was DHCP based)- and I forgot to update one of the hosts files on one of the agents. Which generated the dreaded:
oem agent can’t communicate with oms
So a quick ping of the OMS server would have identified the issue. For some reason I didn’t do this check.
Good news is – I learned something valuable in my mind – before getting to the solution (a simple update to a hosts file).
And that is the command: $AGENT_HOME/bin/emctl pingOMS
[oracle@bronze bin]$ . ./emctl pingOMS
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
—————————————————————
EMD pingOMS error: Failure connecting to https://sampson.localdomain:4903/empbs/upload , err No route to host
[oracle@bronze bin]$ . ./emctl pingOMS
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
—————————————————————
EMD pingOMS error: Failure connecting to https://sampson.localdomain:4903/empbs/upload , err No route to host
# emctl pingOMS – TELLS YOU WHAT THE PROBLEM IS… at least it did in this case… it’s a nice tool to be aware of
# now go update the /etc/hosts file
[oracle@bronze bin]$ . ./emctl pingOMS
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
—————————————————————
EMD pingOMS completed successfully
[oracle@bronze bin]$