Forum Discussion
Solved
Oracle 2.0 Upgrade Woes with Self-Hosted Integration Runtime
This past weekend my ADF instance finally got the prompt to upgrade linked services that use the Oracle 1.0 connector, so I thought, "no problem!" and got to work upgrading my self-hosted inte...
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!
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?
Updating the parameter template did not work, however, the issue seems to have been resolved by Microsoft as deploys now include the authenticationType entry