Connectivity between MS-ACCESS AND ORACLE SQL [message #492858] |
Thu, 03 February 2011 01:48 |
|
grabalaji
Messages: 2 Registered: February 2011 Location: Dubai
|
Junior Member |
|
|
I am currently using Oracle 10.2.0.1 version, in a single PC (test server) and MS-Access (2003) in it.
I was trying to use the logic of HS ODBC connectivity, but when i try to select the table from the MS-Access i am getting the following error.
"ORA-12154: TNS:could not resolve the connect identifier specified".
Could anyone help me to create the successful connection between the MS-ACCESS and ORACLE. I just need to read some data from MS-ACCESS on a monthly base from a particular table.
Thanks & Regards,
RAM B G
|
|
|
Re: Connectivity between MS-ACCESS AND ORACLE SQL [message #492864 is a reply to message #492858] |
Thu, 03 February 2011 02:26 |
|
Michel Cadot
Messages: 68722 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
|
|
|