Oracle Connector is not working in both VS2017 and VS2019

Tingyu Chiang 1 Reputation point
2020-11-06T09:33:32.483+00:00

I am planning to use VS2017 SSIS to access oracle database. Everything looks working. I see Oracle Source task (by Attunity, orange color). I can drag it to a Data Flow task. I can create a new Oracle Connector Manager with the TNS service name, username, password. I tested the connection. It says "Test connection succeeded". In the Oracle Source, I specified the SQL command, and click the "Review" button, it shows the data from Oracle database. But when I execute the data flow, it gives me the error:

[SSIS.Pipeline] Error: The component metadata for "Oracle Source, clsid {4F885D04-B578-47B7-94A0-DE9C7DA25EE2}" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.

[SSIS.Pipeline] Error: Cannot find the connection manager with ID "{8B86A6FB-6F84-45AB-ADCC-8F692341FA4C}" in the connection manager collection due to error code 0xC0010009. That connection manager is needed by "Oracle Source.Connections[MSOraConnection]" in the connection manager collection of "Oracle Source". Verify that a connection manager in the connection manager collection, Connections, has been created with that ID.

[SSIS.Pipeline] Error: Oracle Source failed validation and returned error code 0xC004800B.
[SSIS.Pipeline] Error: One or more component failed validation.
Error: There were errors during task validation.
Error: The connection "{8B86A6FB-6F84-45AB-ADCC-8F692341FA4C}" is not found. This error is thrown by Connections collection when the specific connection element is not found.

I also tried VS2019, with the newest Microsoft Oracle connector. The "Test Connection" in the connector manager is failed. It says - "There was an error trying to establish an Oracle connection with the database server.", but without any detail information.

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,459 questions
{count} votes

9 answers

Sort by: Most helpful
  1. Pedro Soares 396 Reputation points
    2022-05-03T16:53:50.67+00:00

    Hi @Yitzhak Khabinsky ,

    Sorry to dig this topic but I'm having the same error: Failed to deploy the project. Fix the problems and try again later.:Unable to create the type with the name 'DTS.ConnectionManagerOracle.1'.

    I've noticed you outlined the Enterprise Edition in bold. Does the connector work for standard edition?


  2. Pedro Soares 396 Reputation points
    2022-05-03T18:52:07.83+00:00

    I undertand, the tricky thing is, this is a public organisation, so I have limited control on those servers. I cannot run the installation center to check the options :) however I believe that Standard does not allow the change to Developer, as they are fundamentally different, in the way that Standard is licensed for production use and Developer is not :( if this is the case then I would need to ask for Developer install and then backup / restore from the Standard instance. After that, then uninstall Standard.

    0 comments No comments

  3. Pedro Soares 396 Reputation points
    2022-05-07T11:12:29.137+00:00

    Hi again @Yitzhak Khabinsky

    I tried but Standard to Developer it's not a supported upgrade path.

    199850-image.png

    Altough it was possible to upgrade Integration Services, it doesn't do the trick. The project doesn't deploy, the instance itself needs to be Enterprise / Developer.

    199864-image.png

    0 comments No comments

  4. Chiang,David 6 Reputation points
    2022-09-27T19:11:36.87+00:00

    In your Solution Explorer, right click the .dtsx file, then select "View Code". After that, you will see xml like source code of your dtsx file. Find your Oracle Connector definition, and find the <OraConnectionString> tab. It has the connection string you specified. You can ask your Oracle DBA to see if it is correctly specified. Please be careful, don't change this dtsx file. If you changed it directly in this text file, then you have great chance to corrupt the whole dtsx file.