During Upgrade, DBUA Changes LOCAL_LISTENER Parameter Setting
(Doc ID 737339.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Net Services - Version 10.1.0.2.0 to 188.8.131.52 [Release 10.1 to 12.2]
Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Information in this document applies to any platform.
This document describes a problem that can occur during a database upgrade where the DBUA can change the LOCAL_LISTENER.
It has been reported that it can also set LOCAL_LISTENER to null.
After upgrading the Oracle database using DBUA, you find that the value for LOCAL_LISTENER has been changed in the pfile:
For example, the parameter might have been changed from:
Note that it has been reported that DBUA has changed the LOCAL_LISTENER setting to NULL.
In addition, DBUA would have added a connect string to the local tnsnames.ora file that would make this value resolvable:
(ADDRESS = (PROTOCOL = TCP)(HOST = <HOSTNAME>)(PORT = 1532))
The DBUA upgrade log would have an entry similar to the following:
[Thread-30] [9:37:0:605] [NetworkUtils.getOneLocalListenerProtocolAddress:2856] Returning
[Thread-30] [9:37:0:606] [NetworkUtils.getOneLocalListenerProtocolAddress:2856] Returning
[Thread-30] [9:37:0:606] [EMConfiguration.run:228] Setting LISTENER_NAME=CYCLTEST,
LISTENER_HOME=/opt/oracle/10g2cyc02, REP_DB_PORT=1532, REP_DB_HOST=<HOSTNAME>,
DBUA is designed to use the tnsnames alias reference using the nomenclature "LISTENER_<sid>" rather than a full connect string for the LOCAL_LISTENER parameter.
The goal of this Note is to answer the following questions:
1. What are the advantages of tnsnames.ora, over inline specification?
2. How to revert the changes done by DBUA to tnsnames.ora file?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document