Oracle DBA Tips and Techniques

By Arjun Raja

Archive for October, 2011

SPECIFYING GRID CONTROL AGENT – PORT TO USE .

Posted by Arjun Raja on October 21, 2011

In some companies, servers are built behind a secure LAN.

When grid agents are then installed on these servers, firewall rules dictate which ports can be accessed from outside the secure lan.

In our case port 3872 was open for use by the agent but when I installed a new 11g agent , by default it picked the 1830 port.

Therefore I was unable to configure the database instances via the grid using the dbsnmp user.

To solve this.

Shutdown agent.

cd /u01/oracle/agent11g/bin > ./emctl stop agent

edit AGENT_HOME/sysman/config/emd.properties file.

vi /u01/oracle/agent11g/sysman/config/emd.properties

Change following –

EMD_URL=https://xxxxx.xxxxxx.com:1830/emd/main/

to

EMD_URL=https://xxxxx.xxxx.com:3872/emd/main/

And to permanently use only the port mentioned in the EMD_URL above change this value too ( in the same emd.properties file )

AgentListenOnAllNICs=TRUE

to

AgentListenOnAllNICs=FALSE

Restart agent

cd /u01/oracle/agent11g/bin > ./emctl start agent

cd /u01/oracle/agent11g/bin > ./emctl upload agent

You will be able to configure the database via the Grid now.

Finally remove the old agent which was started using port 1830 from the repository as it still shows up as a target in the grid webpage.

Login as sysman into emrep repository and clear agents from repository.

SQL> exec mgmt_admin.cleanup_agent(‘xxxxxx.xxxxx.com:1830’);

PL/SQL procedure successfully completed.

SQL> exec mgmt_admin.cleanup_agent(‘xxxxxxx.xxxxxx.com:1830’);

PL/SQL procedure successfully completed.

Posted in Uncategorized | Leave a Comment »