Mismatch of Hostname in the Listener.ora file and the Listener Endpoints after Hostname Change
(Doc ID 3077231.1)
Last updated on MARCH 28, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 19.26.0.0.0 [Release 11.2 to 19]Oracle Net Services - Version 11.2.0.4 to 19.25.0.0.0 [Release 11.2 to 19.0]
Gen 2 Exadata Cloud at Customer - Version N/A to All Versions [Release All Releases]
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A to N/A
Information in this document applies to any platform.
Goal
1#After changing the Hostname from < Hostname1 > to < Hostname01 > Looking for the root cause on why the hostnames in the << Connecting to >> and the <
lsnrctl status
LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 14-MAR-2025 13:16:05
Copyright (c) 1991, 2024, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=Hostname01)(PORT=1521))) <============= << Hostname01 >>
STATUS of the LISTENER
------------------------
Alias listener
Version TNSLSNR for Linux: Version 19.0.0.0.0 - Production
Start Date 14-MAR-2025 13:03:34
Uptime 0 days 0 hr. 12 min. 31 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/19.3/db_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/prddbsouth01/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=Hostname1)(PORT=1521))) <============= << Hostname1 >>
Solution
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
| Goal |
| Solution |
| References |