How to fix the Azure Data Factory Oracle Linked Service Error?

Question

I'm setting up a new linked service for the on-premises Oracle server. 

I set up an Azure VM and downloaded and installed the self-hosted integration run time (5.27.8441.3) on this VM. The status of the integration runtime is "Running." ( Please note that I did not install the self-hosted integration runtime on the on-premises server. I can do that if needed. FYI - One of the Microsoft MVPs on our project recommended installing self-hosted integration runtime on the Azure VM rather than on an on-premises server. )

Next, I'm creating a new Oracle-linked service and connecting via the new self-hosted integration runtime.

I receive the following error while testing the connection.

Error details -

Error code - 9603

Details

ERROR [08S01] [Microsoft][ODBC Oracle Wire Protocol driver]Socket closed.

ERROR [08001] [Microsoft][ODBC Oracle Wire Protocol driver][Oracle]ORA-12203: unable to connect to destination

Activity ID: f85b7da2-5cb7-4fe2-b54b-df0fae266f9d.

Answer 1

@Nitin Patil Thanks for the question and using MS Q&A platform.

The error message indicates that the Oracle-linked service is unable to connect to the Oracle server. There could be several reasons for this error, including network connectivity issues, incorrect connection settings, or authentication errors.

Here are some troubleshooting steps you can follow to resolve the issue:

1. Verify that the Oracle server is up and running and is accessible from the Azure VM where the self-hosted integration runtime is installed.
2. Check the firewall settings on the Oracle server and ensure that the necessary ports are open for communication.
3. Verify that the connection settings for the Oracle-linked service are correct. Check the hostname or IP address, port number, and other connection settings to ensure they match the Oracle server configuration.
4. Check the credentials used for authentication. Ensure that the username and password are correct and have the necessary permissions to access the Oracle server.
5. Check the ODBC driver configuration on the Azure VM where the self-hosted integration runtime is installed. Ensure that the driver is configured correctly and that the correct version is installed.
6. Check the logs for the self-hosted integration runtime to see if there are any errors or warnings related to the Oracle-linked service. You can access the logs by logging in to the Azure portal and navigating to the integration runtime's properties page.

If you are still unable to resolve the issue, you may want to consider installing the self-hosted integration runtime on the on-premises server instead of the Azure VM. This can help reduce network latency and improve performance.

Hope this helps. Do let us know if you any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.