| ODBC DRIVER for ORACLE 9.2 [message #197766] |
Thu, 12 October 2006 10:33  |
daniele.barone
Messages: 1
Registered: October 2006
|
Junior Member |
|
|
Hi guys, I have a problem.
On the PC, I had installed Oracle 8, with the ODBC driver. I have an application with ASP that connect to the driver in the following way : conn.Open "schedwin", "Driver={ORAOLEDB.ORACLE};UID=uid;PWD=password;Database=database"
Since I installed the new version of Oracle this line gives an error : Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Oracle][ODBC][Ora]Error while trying to retrieve text for error ORA-12154
I guess that its the Driver (ORAOLEDB.ORACLE) that gives me this error. Do you know if the name of this driver has been changed with the new version of Oracle..??
It would be really helpfull, Thanks..
|
|
|
|
| Re: ODBC DRIVER for ORACLE 9.2 [message #197868 is a reply to message #197766] |
Fri, 13 October 2006 00:49  |
 |
Maaher
Messages: 7065
Registered: December 2001
|
Senior Member |
|
|
| Quote: |
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.
|
Look also here
MHE
[Updated on: Fri, 13 October 2006 00:51] Report message to a moderator |
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
