Scenario is this: Database 12.2 installed on Windows 2016 server, upgrading from 12.1 currently residing on different server.
Application vendor is doing most of this upgrade. Because of application nuances that reference server name, once final datapump import has been done, shutting server down and changing name and IP address to match old server that currently has 12.1 running in production. It will be renamed and shut down, and is the back out plan of this upgrade.
I go look at listener, and see it's listening address refers to the server name, so I change it to "localhost" and bounce the listener. Also changed any references to local server name in tnsnames file to localhost.
I am unable to connect with sqlplus or tnsping tnsname entries from server command prompt, but I can test the same tns aliases ok from net manager. So I look at listener log file and it says listener will not start because port is already in use, but listener shows as running.
Stop listener, bounce database, can now connect locally but not from remote machine. Tnsping from remote machine just hangs.
Shutdown database and bounce server to make sure ports are released.
Server comes up, start up database, listener, can connect locally thru listener ok, but tnsping from remote machine fails saying listener not running on remote machine.
Change listening address from localhost to server name.domain again, and everything works fine, can connect thru listener both remotely and locally. Remote machine points at server name of course - but it should not care that database server uses localhost or server name, as I have other database servers using localhost instead of server name as listening address.
What was causing remote machines not able to see listener on it? I don't ever remember issues like this on Solaris servers, windows issue?
I am not a fan of changing server names once Oracle has been installed, things like this are just one reason why. Guess I will just change listener and tnsnames files to match renamed server name, I am thinking I'll also be changing some other things that pop up, like logfile locations etc. since Oracle now incorporates the server name into some of its directory structures in the oracle home.