Forum Discussion
Oracle 2.0 Upgrade Woes with Self-Hosted Integration Runtime
In my case the root cause ended up being that the source Oracle server was version 11g which is not supported in the new connector.
Instead, I am connecting to the Oracle data using ODBC connector going forward. Hope this helps someone else!
We faced the same issue with this upgrade and connection.
First, we upgraded our IR to 5.52 as it was lower than 5.50. Then, we used 2.0 version of Oracle Linked service. Ended up with the same error.
Then we understood that it's related to connection encryption that is enforced by default.
So, we try some testing using various parameters and ended up finding a temporary solutions.
After using "accepted" in both "Encryption client" and "Crypto checksum client" under the "Additional Connection Properties", we were able to test the connection successfully.
Some info about these parameter.
Hope it's useful for someone!
Thank you!
Thanks for posting this!!
I did this method and I was able to upgrade the existing version and the test connection also working fine and I tried copying data using the updated linked service and able to do it. Can this be permanent fix and will it work when we deploy it to PROD, I'm asking this because I saw some convo here in this thread about the deployment ?
Is it working fine ??