RDBPROD: LISTENER.ORA and SQLSRV_CONFIG File to Be Used Clusterwide
Last updated on OCTOBER 27, 2017
Applies to:Oracle SQL/Services for Rdb on OpenVMS - Version 7.2 and later
HP OpenVMS Itanium
HP OpenVMS Alpha
When using OCI Services within SQL/Services, the configuration file named LISTENER.ORA contains the TCPIP related data.
The OCI dispatcher definition in SQLSRV_CONFIG file has a pointer to the entry in LISTENER.ORA:
SQL*Net listener oci_listener Running OCI clients
where oci_listener is the pointer to the entry in LISTENER.ORA
The entry looks like:
(COMMUNITY = TCP_COM.world) (PROTOCOL = TCP)
(Host = own-node) (Port = 1527)
Each node (in a cluster) requires a different entry for OCI_LISTENER, as the host entry would be different for each node.
Adding more address lines for each node in a cluster does not work. When the dispatcher encounters an invalid address line within a listener specification, startup of the dispatcher will fail - the dispatcher logfile logs an error TNS 12545.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms