Tuesday 9 February 2010

Connection Refused - error message for targets in Enterprise Manager Grid Control

"Connection Refused" - error message for targets in Enterprise Manager Grid Control

The Oracle Management agent 10g is installed on a AIX box. On the Oracle Enterprise Manager Grid Control, the target host is displayed with the status up.

When you try to connect to the target database, you receive "Connection Refused" error message.

The problem is the Enterprise Manager repository database has two entries for the target.

To fix this problem, Go to Enterprise Manager Grid Control Host page and click targets tab. You may find two entries for agent10g on two different ports

eg:
host.host1.com:1830/
host.host1.com:3872/

1. In the agent server, check the "Agent URL" for active url

/bin>emctl status agent

For eg: If "https://host.host1.com:3872/emd/main" is the active url then

2. Stop the agent

/bin>emctl stop agent

3. Verify no processes are running on the agent, If you find a process then kill the process.

ps -ef | grep emagent

4. Go to /sysman/emd and remove the below files

rm -rf agntstmp.txt protocol.ini lastupld.xml recv/* upload/* state/*

5. On the Enterprise Manager Repository Database login as sysman using sqlplus

$ sqlplus sysman/password

SQL>exec mgmt_admin.cleanup_agent('host.host1.com:1830');
SQL>commit;

6. Go to the agent and start the agent and check the status

/bin>emctl start agent

/bin>emctl status agent

7. Upload the agent details to repository

/bin>emctl upload agent

8. Refresh and Confirm on the Enterprise Manager Grid Control Host page > targets tab

There should be only one entry for the agent10g host.host1.com:1830/

No comments: