SQL Server – Integration Services – Attunity – Error – OCI error encountered. ORA-12154: TNS:could not resolve the connect identifier specified

Error configuring Oracle Connection Manager:

OCI error encouneterd. ORA-12154: TNS:could not resolve the connect identifier specified

The error, though hard to decipher, was due to the server being 64-bit and Microsoft’s BIDS was installed as a 32-bit WOW Application (on to “C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe”)

The (x86) caused untold of problems for Oracle.

One workable solution was to create a symbolic link folder and launch BIDS via symbolic link.

  1. Download junction from http://technet.microsoft.com/en-us/sysinternals/bb896768
  2. Extract the compressed (zipped) app
  3. Create Junction such as by invoking -> junction  “C:\IDE”   “C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE”
  4. Launch from C:\IDE

References:

  1. ORA-12154:TNS COULD NOT RESOLVE THE CONNECT IDENTIFIER SPECIFIED
    http://www.linkedin.com/groups/ORA-12154-TNS-COULD-NOT-77941.S.61266076?qid=9376dfc1-2062-4358-b1b1-ffe92aa4a479&trk=group_most_popular-0-b-cmr&goback=.gmp_77941
  2. ORA-12154: TNS:could not resolve the connect identifier happened to 64 bit BizTalk Host
    http://blogs.msdn.com/b/asiatech/archive/2009/03/31/ora-12154-tns-could-not-resolve-the-connect-identifier-specified.aspx
  3. Error connecting to database after installing on Windows 64-Bit OS: “ORA-12154 TNS:could not resolve the connect identifier specified” or “ORA-06413: Connection not opened” or “Can’t initialize OCI. Error -1”
    https://support.quest.com/search/SolutionDetail.aspx?id=SOL12495
  4. Junction v1.06 (By Mark Russinovich)
    http://technet.microsoft.com/en-us/sysinternals/bb896768
  5. Connecting to Oracle on 64-bit (x64) machine
    http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/ab662d63-6385-4f73-b27f-d526048f601f

4 thoughts on “SQL Server – Integration Services – Attunity – Error – OCI error encountered. ORA-12154: TNS:could not resolve the connect identifier specified

  1. Another cause that just bit me was my TNS_ADMIN variable was setup as user variable rather than system variable and when I did a “run as” with SSDT it couldn’t find the tnsnames file.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s