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!
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".