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 ??First of all thanx for posting that. I tired the same config and test connection succeeded, but only for once, then it still fails with the same error. Any ideas why? I'll try to have my DBA to provide a list of encryption or data integrity algorithms accepted by Oracle DB, the issue might be here, but sill in my config I listed almost all of them, and still failing
This solution worked for me, but only when I created a new Linked Service (LS) instead of updating the existing one from version 1.0 to 2.0. That said, it does work!
However, I'm running into issues in the production environment. The authenticationType parameter is not included in the ARM template, so when I deploy from dev to prod, the parameter is missing, which causes the connection to fail in prod.
Anyone else encountering this issue?
We have experienced the same issue. I am going to try adding it to my parameters template so it can be updated on a deploy
Did it work?
These parameters worked for me even though I'm using an Oracle 11g server. I'm interested in understanding the security implications of setting both parameters to "accepted".
