SQL Navigator 6.2.1

ORA-12154: TNS:could not resolve the connect identifier specified. Hi everybody i don’t knoy waht is happening because i can’t enter to sql navigator. I reviewed mi TSNNAMES,ORA but I don’t know what is it the trouble, Could you help with this issue?

Hi Jorge,

Can you please provide us more info of the issues, steps…Can you please also provide the screen shot of your SQL Navigator to show the error message.

  • Do you have many Oracle clients in your environment?

  • Do you have this issue everytime when trying to establish new DB connection? or it occurs at startup when SQL Navigator tries to restore connections in the last session?

If it only occurs at startup when SQL Navigator tries to restore past connections where you might use different Oracle home for those connections…If so, there is an option in the preference windows under View->Preferences->Project Manager->Remember Oracle Home/Client for each connection.

If you can provide more info, we will try to figure out why you have the issues.

Thanks and regards,
Bruce

Hi Bruce, thanks for your answer. This is the screen. My environment has differents databases (all in Oracle), 8i, 9i and 10g. If I use sqlplus I don’t have trobles to signon to db, but with SQL Navigator I have this issue. I installed this version on my PC and i can’t connect it. I installed SQL Nav in Windows 7 professional.

Thanks and regards.
Jorge
screen signon.jpeg

Hi Jorge,

Thanks for the addtional info.

I believe that you might only have Oracle 64 bit client. SQL Navigator can currently ONLY work with 32 bit client. This technical issue is with our third party connection management component we use in SQL Navigator.

Could you please try to install Oracle 32 bit client then select that Oracle Home/client in the drop down list in the log in window when do new DB connection.

Please let us know if you can connect with 32 bit client.

Thanks and regards,
Bruce

Hi Jorge,

If you already have Oracle 32 bits client and 64 bit client issue is not the case.
Could you please send us the the following info:

  • screen shot of your logon windows as attached samples.
  • Support bundle: Help->Summit Feedback, click Save to File, then attach the .dta file with your post.

Thank you Jorge.

Regards,
Bruce

Message was edited by: bruceduong

Hi Jorge,

If you already have Oracle 32 bits client and 64 bit client issue is not the case.
Could you please send us the the following info:

  • screen shot of your logon windows as attached samples.
  • Support bundle: Help->Summit Feedback, click Save to File, then attach the .dta file with your post.

Thank you Jorge.

Regards,
Bruce

Message was edited by: bruceduong

Hi Jorge,

If you already have Oracle 32 bits client and 64 bit client issue is not the case.
Could you please send us the the following info:

  • screen shot of your logon windows as attached samples.
  • Support bundle: Help->Summit Feedback, click Save to File, then attach the .dta file with your post.

Thank you Jorge.

Regards,
Bruce

Message was edited by: bruceduong

Hi Bruce
Thanks for your aswer. I suppoused that my trouble was my windows. I will be installing another oracle client or another sql nav version. In TOAD is the same think.

I apreciate your help.

Let me chance to install and I will comment you my results.

You are very welcome Jorge. Please let us know how you go and anything else we can asisst you with.

Thanks and regards,
Bruce

Hi Bruce, I’m again. I solved my trouble, let me explain you. In this forum I found a topic about the similar trouble and I installed again my SQL Nav but in different directory. I installed in PROGRAM FILES and not in PROGRAM FILES (X86). This was the problem.

Thanks for your time with this.

Have a nice day.

Thanks Jorge for your note. Great to hear that everything worked out.

Yes, it used to be an issue with older oracle client where SQL Navigator could not be installed in folder that contains ‘(’ or ‘)’, but we believe it has been addressed in the latest Oracle client version as we have SQL Navigator installed in PROGRAM FILES (X86) and we did not have the issue. Anyway, it is good that you have a working environment now. Thanks again for sharing your work around, we will keep it in mind in case other users might get same issue.

Regards,
Bruce

thanksssssssssssssssssssssssss