 ORA-12154 [message #481625] |
Thu, 04 November 2010 13:45  |
sh.hazeri
Messages: 12
Registered: August 2007
|
Junior Member |
|
|
I have a really strange problem connecting from a new client to an Oracle server, here are the points :
- There is no problem with DB server and its listener and all that as I am able to connect from other clients
- I have installed the oraclient on this machine ( it is a XP machine ) and copy/pasted the TNSNAMES.ORA from one of those correct PCs here and when I do a TNSPING is returns OK
- even when I open oracle net manager I see the TNS entries in there and when I test a connection thru it is says successfull
- BUT WHEN I USE SQL+ or TOAD or ODBC ( any of these) trying to make a connection using the exact same TNS entries it returns :
"ORA-12154: TNS:could not resolve the connect identifier specified"
- I have tried with both IP and Host name but no luck
- TNSNames.Ora and sqlnet.ora both are located here : oracle\product\10.2.0\client_1\NETWORK\ADMIN
- there is just one oracle home
- I have already uninstalled/installed oracle client
- These lines are included in Sqlnet.ora :
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES)
I marked those entries in Sqlnet.ora and that made no diff in result, another thing : if I use easy connect method : sqlplus scott/tiger@<Servername>:1521/ORCL it does connect but using TNSNames still I can not get connected. so strange!!, seems somehow the TNS file even is not being picked or looked at !
Any Idea what else can cause this issue please?
Thanks!
[Updated on: Thu, 04 November 2010 13:47] Report message to a moderator |
|
|
|
|
|
| Re: ORA-12154 [message #481631 is a reply to message #481625] |
Thu, 04 November 2010 14:11  |
 |
Michel Cadot
Messages: 68716
Registered: March 2007
Location: Saint-Maur, France, https...
|
Senior Member
Account Moderator |
|
|
ORA-12154: TNS:could not resolve the connect identifier specified
*Cause: A connection to a database or other service was requested using
a connect identifier, and the connect identifier specified could not
be resolved into a connect descriptor using one of the naming methods
configured. For example, if the type of connect identifier used was a
net service name then the net service name could not be found in a
naming method repository, or the repository could not be
located or reached.
*Action:
- If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the
NAMES.DIRECTORY_PATH parameter in the Oracle Net profile
(SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper
directory and is accessible.
- Check that the net service name used as the connect identifier
exists in the TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA
file. Look for unmatched parentheses or stray characters. Errors
in a TNSNAMES.ORA file may make it unusable.
- If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the
NAMES.DIRETORY_PATH parameter in the Oracle Net profile
(SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is
accessible.
- Verify that the net service name or database name used as the
connect identifier is configured in the directory.
- Verify that the default context being used is correct by
specifying a fully qualified net service name or a full LDAP DN
as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the
NAMES.DIRETORY_PATH parameter in the Oracle Net profile
(SQLNET.ORA).
- Make sure the host, port and service name specified
are correct.
- Try enclosing the connect identifier in quote marks.
See the Oracle Net Services Administrators Guide or the Oracle
operating system specific guide for more information on naming.
Regards
Michel
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
