If the host is a hostname, you could have an issue with your client’s local “hosts” file or the network DNS server.Ĭheck both of these. If the host is defined as an IP address, is it the correct IP address? At this point, you need to verify that the host is in the tnsnames.ora resolves to the database server. Again, on the database server, you will not see an error in the database listener.log or the alert.log because the connection never made it to the database host. Connect failed because the target host or object does not exist: If the connect identifier you’re using does exist in the tnsnames.ora but the host defined cannot resolve to the database server this error occurs.You could have a typo or be missing the connection details in the tnsnames.ora file (on windows %ORACLE_HOME%\network\admin). Go to the $ORACLE_HOME/network/admin directory and open the tnsnames.ora file and look for the connect identifier, verify that it’s correct.Your entries from tnsnames.ora should now display here. Select TNS as connection type in the drop down box. Now in SQL Developer right click on Connections and select New Connection.From the Windows command line: echo %TNS_ADMIN%.Confirm the os is recognizing this environmental variable.In Linux, define the TNS_ADMIN variable in the.In Windows, this is done by navigating to Control Panel > System > Advanced system settings > Environment Variables.Define an environmental variable called TNS_ADMIN to point to the folder that contains your tnsnames.ora file. If your tnsnames.ora file is not getting recognized, use the following procedure: To see which one SQL Developer is using, issue the command show tns in the worksheet LocalMachine\SOFTWARE\ORACLE\ORACLE_HOME_KEY SQL Developer will look in the following location in this order for a tnsnames.ora file $HOME/.tnsnames.ora
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |