E Managing Oracle Database Port Numbers

During installation, Oracle Universal Installer assigns port numbers to components from a set of default port numbers. This appendix lists the default port numbers and describes how to change the assigned port after installation. It includes information about the following topics:

E.1 About Managing Ports

During installation, Oracle Universal Installer assigns port numbers to components from a set of default port numbers. Many Oracle Database components and services use ports. As an administrator, it is important to know the port numbers used by these services, and to make sure that the same port number is not used by two services on your host.

Most port numbers are assigned during installation. Every component and service has an allotted port range, which is the set of port numbers Oracle Database attempts to use when assigning a port. Oracle Database starts with the lowest number in the range and performs the following checks:

  • Is the port used by another Oracle Database installation on the host?

    The installation may be up or down at the time; Oracle Database can still detect if the port is used.

  • Is the port used by a process that is currently running?

    This could be any process on the host, even a non-Oracle Database process.

  • Is the port listed in the /etc/services files?

If the answer to any of the preceding questions is yes, Oracle Database moves to the next highest port in the allotted port range and continues checking until it finds a free port.

E.2 Viewing Port Numbers and Access URLs

In most cases, the Oracle Database component's port number is listed in the tool used to configure the port. In addition, ports for some Oracle Database applications are listed in the portlist.ini file. This file is located in the $ORACLE_HOME/install directory.

If you change a port number, it is not updated in the portlist.ini file, so you can only rely on this file immediately after installation. To find or change a port number, use the methods described in this appendix.

E.3 Port Numbers and Protocols of Oracle Components

The following table lists the port numbers and protocols used by components that are configured during the installation. By default, the first port in the range is assigned to the component, if it is available.

Table E-1 Ports Used in Oracle Components

Component and Description Default Port Number Port Range Protocol

Oracle SQL*Net Listener

Allows Oracle client connections to the database over Oracle's SQL*Net protocol. You can configure it during installation. To reconfigure this port, use Net Configuration Assistant.

1521

1521

TCP

Data Guard

Shares the SQL*Net port and is configured during installation. To reconfigure this port, use Net Configuration Assistant to reconfigure the Oracle SQL*Net listener.

1521 (same value as the listener)

1521

TCP

Connection Manager

Listening port for Oracle client connections to Oracle Connection Manager. It is not configured during installation, but can be configured using Net Configuration Assistant.

1630

1630

TCP

Oracle Management Agent

HTTP port for Enterprise Management Agent. It is configured during installation.

"Changing the Oracle Enterprise Management Agent Port" explains how to modify its port number.

3938

1830–1849

HTTP

Oracle Enterprise Manager Database Console

HTTP port for Enterprise Manager Database Control. It is configured during installation. "Changing the Oracle Enterprise Manager Database Console Ports" explains how to modify its port number.

1158

5500–5519

TCP/HTTP

Oracle Enterprise Manager Database Console

RMI port for Enterprise Manager Database Control. It is configured during installation."Changing the Oracle Enterprise Manager Database Console Ports" explains how to modify its port number.

5520

5520–5539

TCP

Oracle Enterprise Manager Database Console

JMS port for Enterprise Manager Database Control. It is configured during installation. "Changing the Oracle Enterprise Manager Database Console Ports" explains how to modify its port number.

5540

5540–5559

TCP

Oracle Ultra Search

HTTP port for Oracle Ultra Search. Its port number is assigned automatically when you install Oracle Ultra Search, by using the Custom installation type. "Changing the Oracle Ultra Search Ports" explains how to change its port number.

5620

5620–5639

TCP/HTTP

Oracle Ultra Search

RMI port for Oracle Ultra Search. Its port number is assigned automatically when you install Oracle Ultra Search, by using the Custom installation type. "Changing the Oracle Ultra Search Ports" explains how to change its port number.

5640

5640–5659

TCP

Oracle Ultra Search

JMS port for Oracle Ultra Search. Its port number is assigned automatically when you install Oracle Ultra Search, by using the Custom installation type. "Changing the Oracle Ultra Search Ports" explains how to change its port number.

5660

5660–5679

TCP

Oracle XML DB

The Oracle XML DB HTTP port is used if Web-based applications need to access an Oracle database from an HTTP listener. It is configured during installation, but you cannot view it afterward. "Changing the Oracle XML DB Ports" explains how to change its port number.

Dynamic

Dynamic

HTTP

Oracle XML DB

The Oracle XML DB FTP is used when applications need to access an Oracle database from an FTP listener. It is configured during installation, but you cannot view it afterward. "Changing the Oracle XML DB Ports" explains how to change its port number.

Dynamic

Dynamic

FTP

Oracle RAC (UNIX)

The port number is assigned automatically during installation. You cannot view or modify it afterward.

Dynamic

Dynamic

UDP

Oracle Clusterware

Oracle Clusterware Daemon internode connection. The port number is assigned automatically during installation. You cannot view or modify it afterward.

49896

49896

TCP

Cluster Synchronization Service (CSS)

CSS daemon internode connection for the GM layer. The port number is assigned automatically during installation. You cannot view or modify it afterward.

49895

49895

TCP

Oracle Cluster Registry

The port number is assigned automatically during installation. You cannot view or modify it afterward.

Dynamic

Dynamic

TCP

Oracle Event Manager

The port number is assigned automatically during installation. You cannot view or modify it afterward.

49897

49897–49898

TCP

Cluster Manager

The port number is assigned automatically during installation. You cannot view or modify it afterward.

Dynamic

Dynamic

TCP


E.4 Changing the Oracle Enterprise Management Agent Port

To find the current setting for the Oracle Management agent port, search for EMD_URL in the $ORACLE_HOME/host_sid/sysman/config/emd.properties file.

To change the Oracle Management Agent HTTP port, use the emca -reconfig ports command:

emca -reconfig ports -AGENT_PORT 1831

E.5 Changing the Oracle Enterprise Manager Database Console Ports

To find the current HTTP, RMI, and JMS port settings, search in the following files:

  • HTTP port: Search for REPOSITORY_URL in the $ORACLE_HOME/host_sid/sysman/config/emd.properties file.

  • RMI port: Search for the port attribute in the rmi-server tag in the $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_host_sid/config/rmi.xml file.

  • JMS port: Search for the port attribute in the jms-server tag in the $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_host_sid/config/jms.xml file.

To change the Oracle Enterprise Manager Database Control ports, use the emca -reconfig ports command:

$ORACLE_HOME/bin> emca -reconfig ports option setting

where option can be:

  • DBCONTROL_HTTP_PORT: Sets the HTTP port, for example:

    emca -reconfig ports -DBCONTROL_HTTP_PORT 1820
    
  • RMI_PORT: Sets the RMI port, for example:

    emca -reconfig ports -RMI_PORT 5520
    
  • JMS_PORT: Sets the JMS port, for example:

    emca -reconfig ports -JMS_PORT 5521
    

You can enter multiple -reconfig port settings in one line, for example:

emca -reconfig ports -DBCONTROL_HTTP_PORT 1820 -AGENT_PORT 1821 -RMI_PORT 5520

E.6 Changing the Oracle Ultra Search Ports

The following sections describe how to change the Oracle Ultra Search ports.

Changing the HTTP Port

To change the HTTP port, modify the port attribute of the web-site element in the $ORACLE_HOME/oc4j/j2ee/OC4J_SEARCH/config/http-web-site.xml file:

<web-site port="5620"...>

Changing the RMI Port

To change the RMI port, modify the port attribute of the rmi-server element in the $ORACLE_HOME/oc4j/j2ee/OC4J_SEARCH/config/rmi.xml file:

<rmi-server port="5640"...>

Changing the JMS Port

To change the JMS port, modify the port attribute of the jms-server element in the $ORACLE_HOME/oc4j/j2ee/OC4J_SEARCH/config/jms.xml file:

<jms-server port="5660"...>

E.7 Changing the Oracle XML DB Ports

To change the Oracle XML DB FTP and HTTP ports, you need to run the catxdbdbca.sql script, which in a default installation is located in $ORACLE_HOME/rdbms/admin.

To change the Oracle XML DB ports:

  1. Check that the Oracle listener is running. To do so, in the Services control panel, make sure that the Oracle TNS Listener service (for example, OracleOraDb11g_home1TNSListener) is set to Started.

    If you cannot start the listener, refer to Oracle Database Net Services Administrator's Guide.

  2. Log into SQL*Plus as SYS or XDB using the SYSDBA role.

    For example, to log in to SQL*Plus as SYS using the password welcome:

    $ $ORACLE_HOME/bin/sqlplus 
    SQL> CONNECT SYS as SYSDBA
    Enter password: SYS_password
    
  3. Run the catxdbdbca.sql script.

    For example, to use 2200 for the FTP port and 8200 for the HTTP port, and assuming the Oracle home is in the following location, enter the following command:

    SQL> $ORACLE_HOME/rdbms/admin/catxdbdbca.sql 2200 8200
    
  4. Exit SQL*Plus.