RE: Re: emctl fails with "failed to initialize TargetManager"

From: Daniel W. Fink <>
Date: Mon, 7 Dec 2009 13:31:01 -0500
Message-ID: <>

I read through every trace and log file in those directories. All it ever said was that emctl failed with that other information that was meaningful.
  • Original Message ------- On 12/7/2009 6:04 PM Kellyn Pedersen wrote: Hey Dan, Have you look in the $AGENT_HOME/sysman/log directory for more information?  The .trc and .log files should assist you in finding out a little more, (although I agree on the lacking info issue with grid control logs...)    I had a similar issue with a grid control stating the agent was already running/no it's not and found it had to do with the environment confusing the ORACLE_HOME and the AGENT_HOME.  The agent needed to run from the AGENT_HOME but was attempting to start it from the ORACLE_HOME.   Hope this helps, Kellyn Pedersen Multi-Platform DBA I-Behavior Inc.   "Go away before I replace you with a very small and efficient shell script..."--- On Mon, 12/7/09, Daniel W. Fink <> wrote: From: Daniel W. Fink <>Subject: emctl fails with "failed to initialize TargetManager"To: oracle-l_at_freelists.orgDate: Monday, December 7, 2009, 10:54 AM Oracle (64 bit) on Linux Centos 5RACI can't get the emagent started. emctl start agent terminates with  "failed to initialize TargetManager". Background - The person responsible for DBA support on this server is not available and did not leave notes. The 'agent died' a few weeks ago, but no other details. It did work at one time (and works fine on other server in cluster) and no changes were known to have been made at the time of the agent termination.I first tried to start the agent, but emctl reports that the agent is running. I tried to stop the agent, but emctl reports that the agent is not running. No emagent process is found in the process table (ps -ef | grep emagent).The targets.xml file was missing, so I ran agentca (agentca -d -c "<node1>,<node2>") to recreate it. However, it does not create the targets.xml. Nor does it return any error. The output says that the configuration was successful, but it obviously is not. Running the same command on the working node generates a new targets.xml and the agent works fine.I'm not very familiar with grid control agents and see nothing in the doc/logs that provides me leads to solve the problem. And I am not seeing any configuration differences (in the $AGENT_HOME directory structure) that is not node related.Is there a way to set more verbose logging?Why does emctl think that the agent is both running and not running?Thank you for any assistance,Daniel FinkDaniel FinkOptimalDBA    http://www.optimaldba.comOracle Blog   http://optimaldba.blogspot.comLost Data?
Received on Mon Dec 07 2009 - 12:31:01 CST

Original text of this message