E.4 Port Numbers and Protocols of Oracle Components
Review this information for 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 |
TCP |
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 |
TCP |
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 Windows, and is necessary for Grid Plug and Play and GNS. |
5353 |
Dynamic |
TCP |
No |
Oracle Cluster Registry The port number is assigned automatically during installation. You cannot view or modify it afterward. |
Dynamic |
Dynamic |
TCP |
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 |
TCP |
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 |
Quality of Management Service (QOMS) Server The CRS Agent uses port 8888 locally to manage the lifecycle of the container. |
8888 |
8888 |
HTTP |
Not applicable |
Quality of Management Service (QOMS) Server Port for the Quality of Management Service server. |
23792 |
23792 |
JMX/RMI |
No |
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 |
TCP |
Yes |
Oracle Grid Interprocess Communication (GIPCD) A support daemon that enables Redundant Interconnect Usage. |
42424 |
Dynamic |
TCP |
Yes |
Oracle Grid Naming Service (GNSD) The Oracle Grid Naming Service daemon performs name resolution for the cluster. |
53 |
53 |
UDP |
No |
Oracle Grid Naming Service (GNSD) The Oracle Grid Naming Service daemon performs name resolution for the cluster. |
Dynamic |
Dynamic |
TCP |
No |
Oracle HA Services daemon (OHASD) The Oracle High Availability Services (OHAS) daemon starts the Oracle Clusterware stack. |
42424 |
Dynamic |
TCP |
Yes |
Oracle Net Listener Allows Oracle clients to connect 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 for the 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 |
9000 to 64999 |
UDP |
Yes |
Oracle Services for Microsoft Transaction Server The port number for Microsoft Transaction Server is configured automatically by Oracle Universal Installer (OUI) the first time you install the software on a particular server. If you install the software in multiple Oracle homes on the same server, then OUI uses the same port number for all installations. In most cases, you do not have to reconfigure the port number. |
Dynamic |
49152 to 65535 |
TCP |
No |
Oracle XML DB - FTP The Oracle XML DB FTP port is used when applications must access an Oracle database from an FTP listener. The port is configured during installation and you cannot view it afterward. |
0 |
Configured manually |
FTP |
No |
Oracle XML DB - HTTP The Oracle XML DB HTTP port is used if web-based applications must access an Oracle database from an HTTP listener. The port is configured during installation, and you cannot view it afterward. |
0 |
Configured manually |
HTTP |
No |
See Also:
-
Oracle XML DB Developer's Guide for information about changing Oracle XML DB FTP port number.
-
Oracle XML DB Developer's Guide for information about changing Oracle XML DB HTTP port number.
-
"Changing the Oracle Services for Microsoft Transaction Server Port" for information about changing Oracle Services for Microsoft Transaction Server port number.
Parent topic: Managing Oracle Database Port Numbers