Oracle Linked Service 2.0 Failing with Bad Username and Password

Question

Oracle Linked Service 2.0 Failing with Bad Username and Password

17468030 0

We currently have the Oracle v1 Linked Service configured and running with an Oracle 9iR2 database. It works with no issues. However with v2 it will not connect no matter what combination or Encryption client and/or Crypto Checksum Client we use. We've verified that the request does make it to the database.

User's image

The username and password is the same as V1 which tests successfully. I'm out of ideas.

Chandra Boorla 14,510 Reputation points Microsoft External Staff Moderator

2025-06-19T00:19:38.5+00:00
@17468030

We understand that you're encountering a "Bad username and password" error when using the Oracle Linked Service Version 2.0 in Azure Data Factory, despite using the same credentials that work successfully with Version 1.0.

After reviewing your setup and considering the fact that your Oracle instance is version 9iR2 (which is quite legacy), it’s likely that the issue is not with your credentials, but rather due to incompatibilities introduced in the v2 connector, particularly around encryption and checksum expectations.

The Oracle connector version 2.0 in Azure Data Factory supports TLS 1.3. While this brings enhanced security and encryption standards, it's important to note that Oracle 9iR2 does not support TLS 1.3, which can cause compatibility issues during the connection handshake.

For more details, please refer: Differences between Oracle version 2.0 and version 1.0

As a result, when using v2:

The connection attempt may fail before credentials are even validated, due to protocol mismatches.

This often leads to misleading errors like "Bad username and password," even if the credentials are correct.

Here are few recommended steps:

In your linked service configuration, under Additional connection properties, please set the following:

Encryption client = rejected

Crypto checksum client = rejected

If the issue persists, try removing the additional properties altogether and test the connection again.

The v2 connector introduces stricter security protocols that older Oracle databases like 9iR2 may not support, which can lead to misleading errors during the authentication handshake.

As a temporary workaround, if v1 continues to work reliably and securely for your use case, you may continue using it. However, please note the deprecation notice, long-term support will eventually require a move to v2 or an update to a more recent Oracle version.

For additional information, please refer: Supported capabilities

If the issue still persists, could you please share the below details:

The full error message from the v2 test connection

The type and version of the integration runtime used (self-hosted/cloud)

Which combinations of Encryption client and Crypto checksum client you've tested

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

Thank you.
17468030 0 Reputation points

2025-06-19T16:32:27.42+00:00

Chandra,

I tried both at rejected and still got the access denied with bad username and password. If I remove the additional connection properties, I get the error:

Test connection operation failed.

Failed to open the Oracle database connection. ORA-50201: Oracle Communication: Failed to connect to server or failed to parse connect string ORA-12650: No common encryption or data integrity algorithm https://docs.oracle.com/error-help/db/ora-12650/

Unfortunately, the oracle database is for our legacy ERP system which is still in production. There would be no plans to update it to a newer version. We understand that this is a terribly old Oracle database, it's just not possible to upgrade.

Will V1 stop working after July 30th or is it just no longer supported? I've looked over every piece of documentation I can find, every forum post, everything I can to get this to work and have come up empty.
Chandra Boorla 14,510 Reputation points Microsoft External Staff Moderator

2025-06-20T16:23:21.3633333+00:00

@17468030

Just checking in to see if the below suggestion helped. 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.

As your feedback is valuable and can assist others in the community facing similar issues.

2 answers

Your answer

17468030 0 Reputation points

2025-06-19T16:32:27.42+00:00

Chandra,

I tried both at rejected and still got the access denied with bad username and password. If I remove the additional connection properties, I get the error:

Test connection operation failed.

Failed to open the Oracle database connection. ORA-50201: Oracle Communication: Failed to connect to server or failed to parse connect string ORA-12650: No common encryption or data integrity algorithm https://docs.oracle.com/error-help/db/ora-12650/

Unfortunately, the oracle database is for our legacy ERP system which is still in production. There would be no plans to update it to a newer version. We understand that this is a terribly old Oracle database, it's just not possible to upgrade.

Will V1 stop working after July 30th or is it just no longer supported? I've looked over every piece of documentation I can find, every forum post, everything I can to get this to work and have come up empty.
Chandra Boorla 14,510 Reputation points Microsoft External Staff Moderator

2025-06-20T16:23:21.3633333+00:00

@17468030

Just checking in to see if the below suggestion helped. 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.

As your feedback is valuable and can assist others in the community facing similar issues.

Answer 1

@17468030

Thank you for the detailed update and for confirming the results of your testing.

You've done a great job troubleshooting this, and we understand the challenge of working with a legacy Oracle 9iR2 system that is still in production and cannot be upgraded. Given that you've already tried both Encryption client = rejected and Crypto checksum client = rejected, and are still encountering the ORA-12650: No common encryption or data integrity algorithm error, it confirms that the issue is rooted in protocol incompatibility between Oracle 9i and the v2 connector, which enforces newer encryption standards such as TLS 1.3.

User's image

For additional information, please refer: Troubleshoot the Oracle connector in Azure Data Factory and Azure Synapse

Regarding v1 Support - To clarify your question:

Oracle Linked Service v1 is not being disabled on July 30, 2025.

Instead, it is moving into an unsupported state, meaning:

Existing v1 connections may continue to work after this date.
However, they will no longer receive updates or support, and any future issues may not be addressed by Microsoft.

Please refer to the following document for some useful insights: Oracle 2.0 Upgrade Woes with Self-Hosted Integration Runtime

I hope this information helps.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

Chandra Boorla 14,510 Reputation points Microsoft External Staff Moderator

2025-06-23T16:28:36.19+00:00

@17468030

Following up to see if the above suggestion was helpful. 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.

As your feedback is valuable and can assist others in the community facing similar issues.

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

Oracle Linked Service 2.0 Failing with Bad Username and Password

2 answers

Your answer