Skip Headers
Oracle® Real Application Clusters Installation Guide
12c Release 1 (12.1) for Linux and UNIX

E17889-12
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

E Managing Oracle Database Port Numbers

This appendix lists the default port numbers and describes how to change the assigned port after installation. This appendix contains the following topics:

E.1 About Managing Ports

During installation, Oracle Universal Installer (OUI) assigns port numbers to components from a set of default port numbers. Many Oracle Real Application Clusters (Oracle RAC) components and services use ports. As an administrator, it is important to know the port numbers used by these services, and to ensure that the same port number is not used by two services on your system.

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 system?

    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.

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 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.

E.3 Port Numbers and Protocols of Oracle Components

Table E-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 E-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.

Dynamic

Dynamic

UDP

Yes

Cluster Synchronization Service daemon (CSSD)

The Cluster Synchronization Service (CSS) daemon uses a fixed port for node restart advisory messages.

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

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 have the most recent profile.

Dynamic

Dynamic

TCP

No

Multicast Domain Name Service (MDNSD)

The mDNS process is a background process on Linux and UNIX, and a service on Window, and is necessary for Grid Plug and Play and GNS.

5353

Dynamic

UDP/TCP

No

Oracle Cluster Registry

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

Dynamic

Dynamic

UDP

Yes

Oracle Clusterware Daemon (CRSD)

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

Dynamic

Dynamic

UDP

Yes

Oracle Connection Manager

Listening port for Oracle client connections to Oracle Connection Manager. You can configure Oracle Connection Manager after installation using NETCA.

1630

1630

TCP

No

Oracle Containers for J2EE (OC4J)

The CRS Agent uses port 8888 locally to manage the lifecycle of the container.

8888

8888

TCP

Not applicable

Oracle Data Guard

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

1521 (same value as the listener)

modifiable manually to any available port

TCP

No

Oracle Event Manager (EVM)

Generates events for Oracle Clusterware. The port number is assigned automatically during installation. You cannot view or modify it afterward.

Dynamic

Dynamic

UDP

Yes

Oracle Grid Interprocess Communication (GIPCD)

A support daemon that enables Redundant Interconnect Usage.

42424

Dynamic

UDP

Yes

Oracle Grid Naming Service (GNSD)

The Oracle Grid Naming Service daemon provides a gateway between the cluster mDNS and external DNS servers. The gnsd process performs name resolution within the cluster.

53 (public),

Dynamic (interconnect)

53 (public),

Dynamic (interconnect)

UDP/TCP (public),

TCP interconnect

No

Oracle HA Services daemon (OHASD)

The Oracle High Availability Services (OHAS) daemon starts the Oracle Clusterware stack.

42424

Dynamic

UDP

Yes

Oracle Net Listener

Allows Oracle client connections to the database by using Oracle Net Services. You can configure this port during installation. To reconfigure this port, use NETCA.

1521

Port number changes to the next available port.

Modifiable manually to any available port.

TCP

No

Oracle Notification Services (ONS)

Port for ONS, used to publish and subscribe service for communicating information about Fast Application Notification (FAN) events. The FAN notification process uses system events that Oracle Database publishes when cluster servers become unreachable or if network interfaces fail.

Use srvctl to modify ONS ports.

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.

Dynamic

Dynamic

UDP

Yes

Oracle XML DB - FTP

The Oracle XML DB FTP is used when applications need to access an Oracle database from an FTP listener. The port is configured during installation and you cannot view it afterward.

Refer to Oracle XML DB Developer's Guide for information about changing this port number.

0

Configured manually

FTP

No

Oracle XML DB- HTTP

The Oracle XML DB HTTP port is used if Web-based applications need to access an Oracle database from an HTTP listener. The port is configured during installation and you cannot view it afterward.

Refer to Oracle XML DB Developer's Guide for information about changing this port number.

0

Configured manually

HTTP

No