Using Attunity Connectors to connect to Oracle

  • Hello,

    I am hoping someone may be able to assist me in troubleshooting why the Attunity connectors are not appearing in my connection manager in SSIS.

    I am running Windows 7 SP1 (64-bit), Visual Studio 2013 Business Intelligence, SQL 2012 Enterprise Edition (64-bit).

    I have installed the Attunity drivers - 64 bit version:

    But when I try to connect to an Oracle database, there is no option in either the connection manager nor the data flow task under other sources.

    I have the 32-bit Oracle client installed along with PL/SQL and I am able to connect to the database; and the TSNAMES file has already been configured and pointing to the right databases.

    I just don't see the option with VS 2013 to connect. What am I doing wrong? Please advise.

    Thanks,

  • You'll need to manually add the components in VS, see the thread here: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9a362710-1cfa-41f0-a7e1-54fdaed9123c/attunity-option-not-showing?forum=sqlintegrationservices

    Also note that the designer of SSIS runs in 32-bit mode, so you will have to install the 32-bit versions of the driver as well.

  • Hey Martin,

    According to Attunity's documentation, a 64-bit connector installs both the X86 (32-bit) and X64 (64-bit) DLLS.

    Unfortunately, I cannot manually add the items. Looks like this feature might have been removed in VS 2013:

    This worked before I did a fresh install of Windows on my machine and re-installed all programs. But now I don't see the Oracle connection in either place I saw them before:

    or

  • Go to Tools >> Choose Toolbox Items >> COM Components

    The Attunity connectors should be in that list for you to add. If not, you may have to manually register the dll's.

  • Hey Martin,

    I don't see them listed under COM but if I open SQL Sever Data Tools (using Visual Studio 2010 Shell) - the Attunity connectors are there and I can connect to an Oracle database.

    This seems to be isolated to Visual Studio 2013 in my case.

    Thanks,

  • Hey Martin,

    Turns out I need the SQL 2014 connectors:

    And it works.

    Thanks for your help however.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply