How to change ports for DB Control 10.2.x.x

	Doc ID:	395755.1	Type:	BULLETIN
	Modified Date :	26-SEP-2008	Status:	PUBLISHED

In this Document
  Purpose
  Scope and Application
  How to change ports for DB Control 10.2.x.x
     Ports used by the DB Control for RDBMS 10.2.x.x
     Difference between 10.1.x.x DB Control and 10.2.x.x DB Control
     Change DB Control port numbers on a single node
     Change DB Control port numbers on a RAC node
  References

---

Applies to:

Enterprise Manager Grid Control - Version: 10.2.0.1
Information in this document applies to any platform.

Purpose

This bulletin explains how to change ports using emca for DB Control 10.2.x.x.

Scope and Application

Database Administrators in charge of DB Control configuration and setup.

How to change ports for DB Control 10.2.x.x

Ports used by the DB Control for RDBMS 10.2.x.x

When the DB Control is initially configured, it uses a set of default system ports.
If this is the first DB Control configured on the node, the default ports are:
DB Control HTTP port: 1158
RMI port: 5521
JMS port: 5541
DB Control Agent port: 3938

Each new configuration of a DB Control on the node uses a set of default system ports, each port number being incremented by 1.

DB Control HTTP and Agent ports are stored in the file portlist.ini located in the RDBMS $ORACLE_HOME/install directory.
If you have several DB Control configured on a node, DB Control HTTP and Agent ports are stored in the same file portlist.ini.

The utility emca reads the file portlist.ini to check which ports are already used.

Difference between 10.1.x.x DB Control and 10.2.x.x DB Control

In release 10.1.x.x, it was possible to change the port numbers used by DB Control components by manually updating several configuration files.
See the note Note 289966.1 How to Change the Port Numbers for DB Control

In release 10.2.x.x, you must use the emca command-line to change the port numbers allocated to a DB Control
This is also documented in:
Enterprise Manager Advanced Configuration - Chapter 1.2.6.6 Specifying the Ports Used By the Database Control
available on OTN: http://download.oracle.com/docs/cd/B16240_01/doc/nav/portal_booklist.htm

It is possible to change one, some or all four port numbers in one emca command-line

Change DB Control port numbers on a single node

ORACLE_HOME must be set
ORACLE_HOME and ORACLE_HOME/bin must be set in the environment variable PATH

Launch emca in interactive mode

$ emca -reconfig ports [-DBCONTROL_HTTP_PORT <port_number>] [-RMI_PORT <port_number>] [-JMS_PORT <port_number>] [-AGENT_PORT <port_number>]

Example:
$ emca -reconfig ports -DBCONTROL_HTTP_PORT 1160 -AGENT_PORT 3940 -RMI_PORT 5523 -JMS_PORT 5543

Enter the following information:
Database SID: db102



This emca command does the following:

1. stops the DB Control
   
   
2. updates the port number in the following files in $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_hostname_sid/config
   
   • rmi.xml
   • jms.xml
   • http-web-site.xml
     
     
3. updates the port number in the following files in $ORACLE_HOME/install
   
   • portlist.ini
   • readme.txt
     
     
4. updates the port number in the following files in $ORACLE_HOME/hostname_sid/sysman/config
   
   • emoms.properties
   • emd.properties
     
     
5. starts the DB Control
   
   

Log files to check:
emca log file for this operation is located in $ORACLE_HOME/cfgtoollogs/emca/sid.
emca log file name is in format emca_<timestamp_of_the_operation>.log

Launch emca in silent mode:
It is also possible to execute this command in silent mode with parameters provided in a response file:

$ emca -reconfig ports -silent -respFile /oracle/app/oracle/admin/db102/scripts/emca_port_change.rsp

Example of response file: /oracle/app/oracle/admin/EM102/scripts/emca_port_change.rsp
SID=db102
DBCONTROL_HTTP_PORT=1160
RMI_PORT=5523
JMS_PORT=5543
AGENT_PORT=3940

Change DB Control port numbers on a RAC node

ORACLE_HOME must be set.
ORACLE_HOME and ORACLE_HOME/bin must be present in the environment variable PATH.

The command can be executed from any node of the cluster.

DBCONTROL_HTTP_PORT,  RMI_PORT, JMS_PORT and AGENT_PORT  numbers are the same on each node of the cluster for a DB Control monitoring the same RAC database.
Hence it is not possible to change the port number of DBCONTROL_HTTP_PORT on one node of the cluster, without changing DBCONTROL_HTTP_PORT on all nodes of the cluster with same value. This is true for all DB Control ports (DBCONTROL_HTTP_PORT, RMI_PORT, JMS_PORT and AGENT_PORT).

Launch emca in interactive mode

$ emca -reconfig ports -cluster -DBCONTROL_HTTP_PORT <port_number> -RMI_PORT <port_number> -JMS_PORT <port_number> -AGENT_PORT <port_number>

Example:
$ emca -reconfig ports -cluster -DBCONTROL_HTTP_PORT 1159 -AGENT_PORT 3939 -RMI_PORT 5522 -JMS_PORT 5542

Enter the following information:
Database unique name: db102


This emca command does the following:

1. stops the DB Control on all nodes of the cluster where a DB Control is configured for this database

2. updates the port number in the following files in all sub-directories
    $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_hostname<i>_sid<i>/config on the local node
    and deploys the changes on all nodes of the cluster where a DB Control is configured in all sub-directories
* rmi.xml
* jms.xml
* http-web-site.xml

3. updates the port number in the following files in $ORACLE_HOME/install on the local node
    and deploys the changes on all nodes of the cluster where a DB Control is configured for this database
* portlist.ini
* readme.txt

4. updates the port number in the following files in all sub-directories
    $ORACLE_HOME/hostname<i>_sid<i>/sysman/config on the local node
    and deploys the changes on all nodes of the cluster where a DB Control is configured for this database
* emoms.properties
* emd.properties

5. starts the DB Control on all nodes

Log files to check:
emca log file for this operation is located in $ORACLE_HOME/cfgtoollogs/emca/sid.
emca log file name is in format emca_<timestamp_of_the_operation>.log

Launch emca in silent mode:
It is also possible to execute this command in silent mode with parameters provided in a response file:

$ emca -reconfig ports -cluster -silent -respFile /oracle/app/oracle/admin/EM102/scripts/emca_port_change.rsp

Example of response file: /oracle/app/oracle/admin/EM102/scripts/emca_port_change.rsp
DB_UNIQUE_NAME=EM102
DBCONTROL_HTTP_PORT=1159
RMI_PORT=5522
JMS_PORT=5542
AGENT_PORT=3939

References

Bug 5611763 - EMCA -RECONFIG PORTS LEAVES THE OLD AGENT IN THE REPOSITORY
Note 289966.1 - How to Change the Port Numbers for DB Control 10.1.x.x