Solaris Error 126

Anand Reddy got this error while starting listener

TNS-12545: Connect failed because target host or object does not exist
TNS-12560: TNS:protocol adapter error
TNS-00515: Connect failed because target host or object does not exist
Solaris Error: 126: Cannot assign requested address

Here's a description of the Solaris OS error code 126

126 EADDRNOTAVAIL Cannot assign requested address
Results from an attempt to create a transport endpoint with an address not on the current machine.

It turned out that he was starting the listener with an incorrect hostname.

Once he corrected it, the error stopped coming.

Shoaib pinged me with the same error and told me that he had located this blog post on a google search.  In Shoaib's case the error was same, but cause was different:

TNSLSNR for Solaris: Version 10.1.0.5.0 - Production
System parameter file is $INST_TOP/ora/10.1.2/network/admin/listener.ora
Log messages written to $LOG_HOME/ora/10.1.2/network/apps_appsr12.log
Error listening on: (ADDRESS=(PROTOCOL=TCP)(Host=apps101)(Port=1705))
TNS-12545: Connect failed because target host or object does not exist
TNS-12560: TNS:protocol adapter error
 TNS-00515: Connect failed because target host or object does not exist
  Solaris Error: 126: Cannot assign requested address

Listener failed to start. See the error message(s) above...

When I pinged apps101 on the apps101 server it returned the address 192.168.1.20


When I pinged apps101 from my laptop it returned the address 192.168.2.20


The IP address of apps101 was incorrect in the /etc/hosts file.


Whenever we were starting the listener, it was trying to access the non existant IP 192.168.1.20.


I verified this with ifconfig -a command which did not show any IP with 192.168.1.* address.


After correcting the IP address in the /etc/hosts file, the listener started without issues: