Today the Agent Configuration Assistant (Agent on 64bit Windows Server 2003, Grid Control on 32bit Windows XP) failed in running the last optional step. It hang for a long time, too long (a hour or so). After canceling this last step, checking the [configToolFailedCommands] showed the [oracle.sysman.emcp.agent.AgentPlugIn] was messing up the set-up.
Running the ‘agentca’ again (check for options), this strange (Java) stack trace kept popping up from [emctl.perl], telling ‘unexpected end of file EOF’ occured, pointing to something like [10.2.0.1.0.xml].
This file did not exist… There were files like [10.2.0.4.0.xml], the version of the database on the nodes. I don’t know if it was hitting a bug and it was referencing to the database ‘version’ of OMS, but I’m sure this stack trace was not by design…
The ’emctl config agent listtargets’ returned an almost empty result, not showing all the targets present on the database (configured in [AGENT_HOME/sysman/emd/targets.xml]).
After manually adding database targets with ’emctl config agent addtargets <database targets.xml>’ and stopping, starting and reloading (we also had some username/password problems) the Agents’ service, ‘listtargets’ showed the targets we wanted to see. You can check the [state] en [upload] directories in [AGENT_HOME/sysman/emd/] to see if there are errors while uploading (.err files). If all is fine now, ’emctl status agent’ will show only a view files pending for upload.