Listener.ora update needed after hostname change

As more systems are integrated with Windows Operating Systems, users run into new scenarios to consider every time a change to the environment is made. One issue, I ran into the other day, was the need to update the listener.ora config. We recently demoted a DC and moved the device onto a new domain. A couple of days later, users started to notice that they could not connect to one of their production servers running an Oracle database. Troubleshooting pointed to the OracleXETNSListener not being started. This realization came from the errors received by the product stating the port was unavailable. Attempts to restart the OracleXETNSListener failed thus investigation into this service issue began.

Windows event logs did not provide any assistance as to why the service continued to stop. The log files for OracleXETNSListener, indicated that

Pin It on Pinterest

Share This