ORA-12454: connect failed because target host or object does not exist

HIGDST used Ask the Experts™
Just installed Oracle ORACLE CLIENT Client on a Windows 2003 server.  Trying to conect to Oracle database through SQL plus and get the error: ORA-12454: connect failed because target host or object does not exist.  TNSPING unsucessful also.  Replicated same install procedures on a Windows XP computer and could sucessfully connect.  Used same SQLNET.ORA and TNSNAMES.ORA on both server and desktop PC to verify both files are valid.
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
ping the host by name and by ip-address
if ping by name is unsuccessful but ping by ip is successful add to $WINDOWS_SYSTEM_DIR\drivers\etc\hosts file an entry to resolve name to ip.
if both are unsuccessful you do not rich the host at all and you`ll need some help of your network admin
Devinder Singh VirdiLead Oracle DBA Team
ORA-12545: Connect failed because target host or object does not exist
Cause: The address specified is not valid, or the program being connected to does not exist.
Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps "oracle" is missing.) If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again.

You can also check your database name from control panel---> services and look for oracle service with your database name. It is possible that there is some kind of typing mistake happened, or service name (or ip address) you are providing in connecting string is not appropriate.
RindbaekSenior Consultant
is the windows firewall turned on on the server? if it is try to turn it off or allow access through port 1521 (if thats the port your listener are using).
I had the same problem last year. I finally had to set the TNS_ADMIN environment variable to target the tnsnames.ora location. There seems to be an issue on some win2003 under some oracle client scenarios. If the same config under a WinXP station works, this may be the problem.

That is, go to the environment variables on System Properties and add a System wide variable like:
TNS_ADMIN = c:\client_10204\network\admin
or whatever your tnsnames.ora folder is located.

You can test this locally inside a cmd session like:
set TNS_ADMIN=c:\client_10204\network\admin
tnsping myoraclehost


Thank you everyone for all your responses.  They were very helpful troubleshooting the situation.  Eventhough the same TNSNAMES.ORA worked seperately on a seperate PC, once a change was made to include DomainName.Com we were able to successfully connect to the Oracle database.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial