F.1 About Managing Ports

During installation, Oracle Universal Installer (OUI) assigns port numbers to components from a set of default port numbers. Many Oracle RAC 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 server.

Most port numbers are assigned during installation. Every component and service has an allotted port range, which is the set of port numbers Oracle RAC attempts to use when assigning a port. Oracle RAC 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 can be either active or inactive 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, including processes other than Oracle Database processes.

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

F.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 directory $ORACLE_HOME/install.

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

F.3 Port Numbers and Protocols of Oracle Components

Table F-1 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 F-1 Ports Used in Oracle Components

Component and Description

Default Port Number

Port Range

Protocol

Used Only On Interconnect

Cluster Manager

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

This port is used exclusively with the cluster interconnect, which is a private network that is physically separated from the public network, and uses dedicated hardware for the interconnect.

Dynamic

Dynamic

UDP

Yes

Cluster Synchronization Service (CSSD)

Node restart advisory messages fixed port.

This port is used on all interfaces that have broadcast capability. Broadcast occurs only when a node eviction restart is imminent.

42424

Dynamic

UDP

Yes

Event Manager (EVM)

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

This port is used exclusively with the cluster interconnect, which is a private network that is physically separated from the public network, and uses dedicated hardware for the interconnect.

Dynamic

Dynamic

UDP

Yes

Grid Plug and Play (GPNPD)

GPNPD provides access to the Grid Plug and Play profile, and coordinates updates to the profile among the nodes of the cluster to ensure that all of the nodes node have the most recent profile.

Dynamic

Dynamic

TCP

No

Multicast Domain Name Service (MDNSD)

Grid Plug and Play uses the mDNS process to locate profiles in the cluster, as well as by GNS to perform name resolution. The mDNS process is a background process on Linux and UNIX, and a service on Windows.

5353

Dynamic

UDP/TCP

No

Oracle Data Guard

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

Port for ONS, used to publish and subscribe service for communicating information about all Fast Application Notification (FAN) events. The FAN notification process uses system events that Oracle publishes when cluster servers become unreachable or if network interfaces fail. Use srvctl to modify ONS ports. If you do not specify the ONS port values, then the ONS daemon listener local port defaults to 6100, and the ONS daemon remote port defaults to 6200.

6100 (local)

6200 (remote)

Configured manually

TCP

No

Oracle Real Application Clusters

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

This port is used exclusively with the cluster interconnect.

Dynamic

Dynamic

UDP

Yes

Oracle Net Listener

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

1521

Port number changes to the next available port.

Modifiable manually to any available port.

TCP

No

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.

0

Configured manually

HTTP

No

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.

0

Configured manually

FTP

No

F.4 Changing the Oracle 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, where host_sid is a string that contains the local host name and the SID for the Oracle RAC database.