Known issue: Using the Microsoft Connector for Oracle by Attunity for Full Load

[Itamar.Ankorion]

By default, the product uses an Attunity OLEDB connector to load the source Oracle data. If you’re using SQL Server 2008 Enterprise Edition, then you can update the Full Load package and use instead the high-speed Oracle connector. If you do that the full load process may return an error, which is caused due to the different instances of oracle client that are loaded by the different processes.

You can resolve this using the following workaround:

In the registry, under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE add a key that will be the last key (According to the name sort). Under this key add the following string values:
1. ORACLE_HOME_NAME - Any name
2. ORACLE_HOME - Set its value to "C:\Program Files\Attunity\Oracle-CDC for SSIS\OracleInstantClient"