So many databases, so little time! :-)
Recently, I was trying to install em grid agent on target server, but through em grid console, on deploy option, always failed on Preinstall Script..
I tried on another target server, which have same OS (OEL linux), DB versions (10.2.0.4), but same thing happened...
I know, of course, that there is another way of installing agent, but I was determined that I can do that install with EM...
After some little digging through logs, I found this:
'/opt/oracle/agent/' is my target agent dir which I specified in em deploy agent form, and I guess that '/agent11g/cfgtoollogs/oui//' is something that deploy script build for install on target... So, how I see, problem is with creating this path and double '//' sign. I tried even without trailing '/' sign on the end of my target dir '/opt/oracle/agent' , but, without success, same thing...
After a 'few short weeks' comm with Oracle support, they concluded: "Clarified that Push Agent installation was reporting some communication errors may be due to ssh latency and he can install Agent on any server using response file which is simpler and faster"...
Well, I haven't see any comm errors, but...who am I... :-)
So, the workaround is this: to install the Agent using Reponse file by following the document below
When I tried to find additional_agent.rsp file:
The required file (additional_agent.rsp) file is not present in the OMS_Home in your setup.You must download the 126.96.36.199 Agent Software from the location agent_download and use the additional_agent.rsp file in it for installation.
Here is file, with parameters that I changed:
and than, run installation:
After sucessfull installation, start agent and upload the data on emgrid11g host:
Great, it works, but in EM grid for all db targets there is a message 'Target has encountered metric evaluation errors', for host it is ok. Upload was without errors. Well, now, should only to configure db parameters for dbmsnm user - password :-)
Here we are - working as expected, but, off course, with workaround.. :-)
pssst... I still think that something is wrong with script for deploying agent in em grid, ..no, I don't mean bug, but...:-)
sorry for my english, in a hurry...Cheers!