Listener Dynamic Registration Issue: Change to LOCAL_LISTENER Setting
(Doc ID 2315830.1)
Last updated on OCTOBER 18, 2017
Applies to:Oracle Net Services - Version 10.1.0.2 to 22.214.171.124 [Release 10.1 to 12.2]
Information in this document applies to any platform.
- Init parameter LOCAL_LISTENER points to a tnsnames.ora file entry.
In our example, the TNS alias is: LSNR_TNS
Show parameter LOCAL_LISTENER shows the setting: LISTENER
The local tnsnames.ora file contains this entry.
(ADDRESS = (PROTOCOL = TCP)(HOST = 126.96.36.199)(PORT = 1522))
- The server's IP address was changed to a new IP. The local listener has been restarted on this new ip.
So we also need to change our tnsnames entry for LISTENER so that the HOST field reflects the change:
(ADDRESS = (PROTOCOL = TCP)(HOST = 188.8.131.52)(PORT = 1522))
- lsnrctl status shows that service name 'ora12' can not be registered to listener
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=184.108.40.206)(PORT=1522)))
STATUS of the LISTENER
Version TNSLSNR for 64-bit Windows: Version 220.127.116.11.0 - Production
Start Date 10-OCT-2017 11:50:34
Uptime 0 days 1 hr. 6 min. 35 sec
Trace Level off
Security ON: Local OS Authentication
Listener Parameter File C:\app\orauser\product\12.1.0\dbhome_1\network\admin\listener.ora
Listener Log File C:\app\orauser\diag\tnslsnr\ICFANG-LAP\listener\alert\log.xml
Listening Endpoints Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
The IP address was changed on this server. The listener has been been restarted so that it's running on the new IP address.
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