| ORA-12154 only when logging in with my own login. [message #228347] |
Mon, 02 April 2007 11:22  |
acgelbol
Messages: 1
Registered: March 2007
|
Junior Member |
|
|
Hi, I can login to sqlplus to all our remote databases from my pc if I login as system but not if I login as myself. I get the ORA-12154 message with my login. My tnsnames.ora is set correctly because I can login as system. My password is correct because I can connect to dbartisan with my login, I just can't use sqlplus if I'm connected as myself. I also tried to connect directly to sqlplus from the server where the database is located and I get the same error message. So I'm thinking this is really a misleading error message. My login has been granted connect, resource and dba roles. Is this an LDAP permission issue? Below is the setting for my sqlnet.ora.
SQL*Plus: Release 9.2.0.4.0 - Production on Mon Apr 2 09:10:40 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Enter password:
ERROR:
ORA-12154: TNS:could not resolve service name
# SQLNET.ORA Network Configuration File: C:\oracle\ora9i\network\admin\sqlnet.ora
# Generated by Oracle configuration tools.
#NAMES.DEFAULT_DOMAIN = pacificorp.us
SQLNET.AUTHENTICATION_SERVICES= (NONE)
NAMES.DIRECTORY_PATH= (ldap,tnsnames)
#NAMES.DIRECTORY_PATH= (tnsnames,ldap)
Please help, this driving me nuts.
Thanks,
Lyn
|
|
|
|
| Re: ORA-12154 only when logging in with my own login. [message #228352 is a reply to message #228347] |
Mon, 02 April 2007 11:48  |
 |
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
|
Senior Member |
|
|
12154, 00000, "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.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
