July 9, 2009 at 12:22 pm
Hi,
When I am trying to connect to the Oracle data source from BIDS on a 64-Bit Windows machine, I am getting the following error.
Test connection failed because of an error in initializing provider. ORA-12154: TNS: could not resolve the connect identifier specified.
Could anyone help me with this?
Thank You,
Yours,
SQLBuddy
July 9, 2009 at 3:24 pm
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.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.July 10, 2009 at 7:51 am
Hi Pablo Berzukov,
Thank you very much for your reply.
But, I am still trying to understand your detailed reply.
I'll try that solution and If have any questions, I will ask you.
Yours
SQLBuddy.
July 10, 2009 at 11:33 am
sqlbuddy123 (7/10/2009)
your detailed reply
And the credit goes to... Oracle's oerr utility 😉
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.July 10, 2009 at 1:38 pm
Hi
In oracle there is file called TNSNAMES.ORA in client software
when you trying to connect to oracle server from clinet usually u do
>connect username/pwd@sidname
that sid will usually stores in your tnsnames.ora file
and at the same time you have to make sure the listerner at the server is on
you can check on that on server machine
C:\lsnrctl
it will display what is the listener status and what SID's it is listening to
on client side you can make sure the sid is configured correctly and it can establish a connection to the server using
C:\tnsping SIDNAME
If you get message OK that means SID is configured correctly on ur local pc
and does not gurantee to you that you can esatablish connection to the server
you have to make sure the listener service is running on server
I hope that is clear to you
Regards
Reddy
July 13, 2009 at 9:24 am
SQLBuddy:
We have had the same issue after corporate changed the requirements from 32 to 64-bit on any server running Reporting Services (SSRS). The TNS would resolve correctly using the TNSping utility. The issue seems to revolve around the fact that on 64-bit OS/SQL when connecting with Oracle, you must install the 32-bit AND 64-bit drivers. The reason is that BIDS, SSRS and most other applications need the 32-bit drivers. The system also then maintains separate ODBC connections.
The 32-bit ODBC is in C:\[windows directory]\SysWOW64\odbcad32.exe - oddly enough
The 64-bit ODBC is in C:\[windows directory]\system32\odbcad32.exe
It's also my understanding that drivers are best pulled from Oracle as MSFT made a statement before 10g was released that they were no longer going to write drivers for Oracle.
We are waiting on corporate IT to finish the installs and config for our server. Hope you work through the issue on your connection.
July 13, 2009 at 12:17 pm
Hi Reddy,
Thank you very much for your reply.
I really appreciate your help.
Yours
SQLBuddy
July 13, 2009 at 12:20 pm
Hi ChaoticCoder,
Thanks a lot for your help.
I'm still working on that issue.
Yours
SQLBuddy
July 17, 2009 at 1:23 pm
SQLBuddy:
I wanted to post back to let you know how our similar situation was resolved.
After scouring forums, and making sacrificial offerings to the google gods, I found this posting.
http://blogs.msdn.com/debarchan/archive/2009/02/04/good-old-connectivity-issue.aspx
In the msdn link, it explains that the best option for resolving the issue is to simply go with Oracle11g driver in the 32 and 64-bit flavors.
The Best possible solution is to upgrade to Oracle 11G Release 1 version of Client tools (Build: 11.1.0.6.0) rather than applying the series of patches over the 10G client which may not produce desired results. The 11G version of the Client tools are tested and confirmed to include a FIX
Since installing the drivers, all of the connections in BIDS work great, and the boss could not be happier.
I hope that fix works for you.
July 20, 2009 at 9:01 am
Hi Chaotic Coder,
Thank you very much for your reply.
I really appreciate your help.
Great advise! But I made it to work with Oracle 10g 32-bit client and some other minor modifications. If I get any chance, I will try to test this with Oracle 11g drivers too.
Yours
SQLBuddy.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply