This content has been marked as final. Show 4 replies
Normally the agent on the servers are busy with a lot of upload.
Do you mean often there are a lot of files pending upload? If so, you may want to start with checking whether this problem is isolated to just this agent or it happens to other agents as well. If it happens to several agents, then it may be an OMS/repository issue.
BTW, the database server to be monitored are in oracle 10gR2 version. Can 12c agent and oms monitoring 10g version?
Currently the following database versions are certified (as managed targets) in EM 12c: 22.214.171.124.0, 126.96.36.199.0, 188.8.131.52.0, 184.108.40.206.0, 10.2.0.5.0, 10.2.0.4.0, 10.1.0.5.0, 220.127.116.11.0.
Thanks for the information! I will check on the detail. I can see, from OEM web page, the agent and server are not connected, but agent can upload successfully and we deployed the agent from OEM succefully. The OEM server has 2 IP configured by our sys admin. One IP is for our ssh login to the server and the other is for the between servers connection. Should this confuse the OEM connection to the agent?
The OEM server has 2 IP configured by our sys admin.That is the problem, you need static ip address, please check the Prerequisites from the below doc.
May I know the reason for having two ip address?
What exactly do you mean by "the agent and server are not connected"? If the agent can upload successfully, then I would check the communication from the OMS to the agent.
A couple of things to try:
- Assuming you deployed the agent using a host name, can you ping that host name from the OMS host? Is the IP address shown in the output what you expect it to be?
- Run wget on the agent's URL (you can get the URL from the output of <Agent Home>/bin/emctl status agent.
Note: wget may return some certificate error, but it will give you an idea whether there is problem getting from the OMS host to the agent host on the port.