Wednesday, November 7, 2012

ORA-12154: TNS:could not resolve the connect identifier

This is the most common error which we are finding these days and it creates a havoc among the users who are working with Oracle. It is mainly because of some setting issues or some configuration issues, which cause this and our www has a numerous solution to this problem.

Most of them stating the same solution and workaround for the problem. But most of the times, we had all this and the problem still exists. Solution to that is the user should cool down himself first and then again retry with the available solution because sometimes we tend to skip some points/check from the solution.

Few of the sites, from which I got my solution is :-

http://www.dba-oracle.com/t_ora_12154_tns_resolve_service_name.htm

http://ora-12154.ora-code.com/

But, today I have found one more probable cause for this. In my case, it was the Unix machine and access permission in that was causing me this error.

Scenario :- I was having oracle installed in one of  the Unix machine and  only oracle user was having full rights in the oracle/db folder and other users have only read access. When other users are trying to access the user created in Oracle, it was giving a "tns :12154" error.

Solution :-
The "tnsnames.ora" was not granted full access ( read, write, execute ) to other users who were trying to access the database.

So, the solution is chmod 777 tnsnames.ora and then try again with the user. It may solve your problem.



Enjoy Testing and keep Sharing :)

No comments:

Post a Comment