How to get the new data factory oracle 2.0 connector to connect?

Question

How to get the new data factory oracle 2.0 connector to connect?

Blasko, Dan W 60

We currently connect to oracle using the 1.0 connector.

We must be moved to the new oracle 2.0 connector before end of support, 7/31/25.

I was able to get this to connect to a non encrypted database, but unable to connect to an encrypted database.

I had to add encryption client and crypto checksum client to get this to connect to our non encrypted dev.

Those changes will not work for production.

For dev, I used "accepted" for both.

For prod, i tried both accepted and required

User's image

Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-22T14:27:13.3633333+00:00
Hi @Blasko, Dan W
The Oracle 2.0 connector in Azure Data Factory does enforce stricter security protocols compared to the legacy 1.0 connector, especially when connecting to encrypted Oracle databases.

For encrypted databases, specifying the following under Additional connection properties is necessary:

Encryption client = required

Crypto checksum client = required

However, if your production Oracle instance is not configured to require encryption (but only accepts it), setting both to required can lead to failures. In such cases, please try:

Encryption client = accepted

Crypto checksum client = required

Also, ensure the Oracle server’s sqlnet.ora file supports the encryption settings being requested. The relevant parameters are:

SQLNET.ENCRYPTION_SERVER

SQLNET.CRYPTO_CHECKSUM_SERVER

If the database uses TLS or wallet-based encryption, and you're using a managed Azure IR, the connection might fail unless those configurations are accessible. In such cases, using a Self-hosted IR where Oracle client and wallet are installed may be required.

If possible, please share:

The full error message from the failed production attempt

The type of integration runtime used (Azure vs. Self-hosted)

Oracle server version

This will help further troubleshoot the issue.

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.
Blasko, Dan W 60 Reputation points

2025-05-22T14:47:54.64+00:00

Here is what the production server has in the sqlnet.ora

SQLNET.ENCRYPTION_SERVER=REQUIRED

SQLNET.ENCRYPTION_TYPES_SERVER=(AES128,AES256,AES192) SQLNET.CRYPTO_CHECKSUM_SERVER = REQUIRED

SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER=(SHA1,SHA256)

sqlnet.encryption_client=REQUIRED

sqlnet.encryption_types_client=(AES128,AES256,AES192)

SQLNET.CRYPTO_CHECKSUM_CLIENT = REQUIRED

sqlnet.crypto_checksum_types_client=(SHA1,SHA256)

That is the reason I tried required and required. Upper and lower case.

This is the error i get when both are set to required.

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/
Blasko, Dan W 60 Reputation points

2025-05-22T15:43:44.17+00:00

Sorry...missed these questions.

Oracle is Oracle 19.3 database.

Using SHIR. Just upgraded to 5.52.9229.1
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-26T13:17:57.9033333+00:00

@Blasko, Dan W I kindly request you to provide the details mentioned in the private message so we can identify the root cause and address the issue effectively.
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-27T12:40:14.83+00:00

Hi @Blasko, Dan W
Just to clarify - the Oracle 2.0 connector in Azure Data Factory supports only TLS 1.3. If your Oracle server or the Oracle client on your Self-hosted Integration Runtime is currently configured to use TLS 1.2, this could be the reason you're encountering the ORA-12650: No common encryption or data integrity algorithm error.

Could you please verify if TLS 1.3 is enabled and being used for connections between your SHIR and the Oracle database?

If the environment is still on TLS 1.2, upgrading to support TLS 1.3 would be necessary for the Oracle 2.0 connector to function as expected.

Let us know what you find - happy to assist further based on the results.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Blasko, Dan W 60 Reputation points

2025-05-27T13:52:43.3966667+00:00

This doesn't make much sense to me. This is coming from Microsoft site.

TLS 1.3 is supported starting in Windows 11 and Windows Server 2022. Enabling TLS 1.3 on earlier versions of Windows is not a safe system configuration.

So the only way to connect to oracle using data factory is to upgrade every one of your oracle servers to windows server 2022???

Or am i missing something?
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-27T14:47:24.3333333+00:00
@Blasko, Dan W To clarify: the TLS 1.3 requirement applies to the communication from Azure Data Factory's Oracle 2.0 connector client (i.e., the Self-hosted Integration Runtime), not the Oracle database server itself.

You're absolutely right - TLS 1.3 is only supported on Windows Server 2022 and Windows 11. So, if you're running SHIR (Self-hosted Integration Runtime) on Windows Server 2019 or earlier, it likely doesn't support TLS 1.3, which could lead to handshake or encryption negotiation issues like the ORA-12650.

In other words:

You do not need to upgrade your Oracle servers.

But you may need to run the SHIR on a TLS 1.3–capable OS, such as Windows Server 2022, for the Oracle 2.0 connector to work properly with encrypted Oracle DBs.

Suggested Steps:

Can you confirm the OS version where the SHIR is installed?

If it's earlier than Windows Server 2022, try moving the SHIR to a machine running Windows Server 2022 or Windows 11 (for testing) and reattempt the connection.

Let us know what you find, and we can help troubleshoot further from there.
Blasko, Dan W 60 Reputation points

2025-05-27T14:54:24.38+00:00

IR Nodes are Server 2022.

TLS 1.3 was not listed under protocols.

Googling shows that i most likely need to do a regedit and add it. Still researching before I do the regedit.
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-27T16:04:10.75+00:00
@Blasko, Dan W Thanks for the quick update, and great to hear that your IR nodes are already running on Windows Server 2022 - that clears up the OS compatibility aspect.

You're correct: TLS 1.3 is not enabled by default on Windows Server 2022, and it typically needs to be enabled manually via the registry (regedit) or via Group Policy if enforced centrally.

Next Steps:

Before making registry changes, we recommend reviewing the official Microsoft guidance on enabling TLS 1.3: TLS registry settings – Microsoft Docs

If you're in a production environment, ensure that:

You back up your registry before making changes.

Any TLS policy changes align with your organization’s security and compliance standards.

A reboot may be required after changes to TLS settings.

Once TLS 1.3 is enabled and verified (you can confirm via tools like PowerShell or IISCrypto), retry the connection with the Oracle 2.0 connector using:

Encryption client = required Crypto checksum client = required

Let us know how it goes or if you encounter anything unexpected - we’re happy to assist further!
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-28T09:40:48.0766667+00:00

@Blasko, Dan W We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Blasko, Dan W 60 Reputation points

2025-05-28T11:39:13.7433333+00:00

I did the regedit and rebooted this morning.

I am still having issues connecting.

Trying to find a way to confirm TLS 1.3 is actually being used.
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-28T13:22:34.2766667+00:00
@Blasko, Dan W Thanks for the update. Since the issue persists post-regedit and reboot, here are quick steps to confirm TLS 1.3 is enabled and in use:

Check registry settings via PowerShell:

Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Client"

Ensure Enabled=1 and DisabledByDefault=0.

Use IISCrypto to verify TLS 1.3 is enabled.

Confirm Oracle client version supports TLS 1.3.

Let us know what you find - we’ll assist further based on that.
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-29T09:53:28.2766667+00:00

@Blasko, Dan W We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Blasko, Dan W 60 Reputation points

2025-05-29T11:30:43.0166667+00:00

1.3 is enabled as well as 1.2. When I disabled 1.2 I caused issues where i was unable to connect to that server anymore using rdp or cyberark. Sysadmin had to revert back to before I screwed everything up. I did the 1.3 setup again and left 1.2 enabled. Still does not work.

You mention oracle client supports 1.3 but I do not have the oracle client installed on any of the IR nodes.

The 1.0 client has been working for a year now without the client. Does the 2.0 connector need the oracle client? It doesn't appear to need it from what i read. Just confirming.
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-30T14:58:37.2466667+00:00

@Blasko, Dan W Could you please check my private message and respond to it?
Deleted

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

3 answers

Your answer

Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-22T14:27:13.3633333+00:00

Hi @Blasko, Dan W
The Oracle 2.0 connector in Azure Data Factory does enforce stricter security protocols compared to the legacy 1.0 connector, especially when connecting to encrypted Oracle databases.

For encrypted databases, specifying the following under Additional connection properties is necessary:

Encryption client = required

Crypto checksum client = required

However, if your production Oracle instance is not configured to require encryption (but only accepts it), setting both to required can lead to failures. In such cases, please try:

Encryption client = accepted

Crypto checksum client = required

Also, ensure the Oracle server’s sqlnet.ora file supports the encryption settings being requested. The relevant parameters are:

SQLNET.ENCRYPTION_SERVER

SQLNET.CRYPTO_CHECKSUM_SERVER

If the database uses TLS or wallet-based encryption, and you're using a managed Azure IR, the connection might fail unless those configurations are accessible. In such cases, using a Self-hosted IR where Oracle client and wallet are installed may be required.

If possible, please share:

The full error message from the failed production attempt

The type of integration runtime used (Azure vs. Self-hosted)

Oracle server version

This will help further troubleshoot the issue.

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.
Blasko, Dan W 60 Reputation points

2025-05-22T14:47:54.64+00:00

Here is what the production server has in the sqlnet.ora

SQLNET.ENCRYPTION_SERVER=REQUIRED

SQLNET.ENCRYPTION_TYPES_SERVER=(AES128,AES256,AES192) SQLNET.CRYPTO_CHECKSUM_SERVER = REQUIRED

SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER=(SHA1,SHA256)

sqlnet.encryption_client=REQUIRED

sqlnet.encryption_types_client=(AES128,AES256,AES192)

SQLNET.CRYPTO_CHECKSUM_CLIENT = REQUIRED

sqlnet.crypto_checksum_types_client=(SHA1,SHA256)

That is the reason I tried required and required. Upper and lower case.

This is the error i get when both are set to required.

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/
Blasko, Dan W 60 Reputation points

2025-05-22T15:43:44.17+00:00

Sorry...missed these questions.

Oracle is Oracle 19.3 database.

Using SHIR. Just upgraded to 5.52.9229.1
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-26T13:17:57.9033333+00:00

@Blasko, Dan W I kindly request you to provide the details mentioned in the private message so we can identify the root cause and address the issue effectively.
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-27T12:40:14.83+00:00

Hi @Blasko, Dan W
Just to clarify - the Oracle 2.0 connector in Azure Data Factory supports only TLS 1.3. If your Oracle server or the Oracle client on your Self-hosted Integration Runtime is currently configured to use TLS 1.2, this could be the reason you're encountering the ORA-12650: No common encryption or data integrity algorithm error.

Could you please verify if TLS 1.3 is enabled and being used for connections between your SHIR and the Oracle database?

If the environment is still on TLS 1.2, upgrading to support TLS 1.3 would be necessary for the Oracle 2.0 connector to function as expected.

Let us know what you find - happy to assist further based on the results.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Blasko, Dan W 60 Reputation points

2025-05-27T13:52:43.3966667+00:00

This doesn't make much sense to me. This is coming from Microsoft site.

TLS 1.3 is supported starting in Windows 11 and Windows Server 2022. Enabling TLS 1.3 on earlier versions of Windows is not a safe system configuration.

So the only way to connect to oracle using data factory is to upgrade every one of your oracle servers to windows server 2022???

Or am i missing something?
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-27T14:47:24.3333333+00:00

@Blasko, Dan W To clarify: the TLS 1.3 requirement applies to the communication from Azure Data Factory's Oracle 2.0 connector client (i.e., the Self-hosted Integration Runtime), not the Oracle database server itself.

You're absolutely right - TLS 1.3 is only supported on Windows Server 2022 and Windows 11. So, if you're running SHIR (Self-hosted Integration Runtime) on Windows Server 2019 or earlier, it likely doesn't support TLS 1.3, which could lead to handshake or encryption negotiation issues like the ORA-12650.

In other words:

You do not need to upgrade your Oracle servers.

But you may need to run the SHIR on a TLS 1.3–capable OS, such as Windows Server 2022, for the Oracle 2.0 connector to work properly with encrypted Oracle DBs.

Suggested Steps:

Can you confirm the OS version where the SHIR is installed?

If it's earlier than Windows Server 2022, try moving the SHIR to a machine running Windows Server 2022 or Windows 11 (for testing) and reattempt the connection.

Let us know what you find, and we can help troubleshoot further from there.
Blasko, Dan W 60 Reputation points

2025-05-27T14:54:24.38+00:00

IR Nodes are Server 2022.

TLS 1.3 was not listed under protocols.

Googling shows that i most likely need to do a regedit and add it. Still researching before I do the regedit.
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-27T16:04:10.75+00:00

@Blasko, Dan W Thanks for the quick update, and great to hear that your IR nodes are already running on Windows Server 2022 - that clears up the OS compatibility aspect.

You're correct: TLS 1.3 is not enabled by default on Windows Server 2022, and it typically needs to be enabled manually via the registry (regedit) or via Group Policy if enforced centrally.

Next Steps:

Before making registry changes, we recommend reviewing the official Microsoft guidance on enabling TLS 1.3: TLS registry settings – Microsoft Docs

If you're in a production environment, ensure that:

You back up your registry before making changes.

Any TLS policy changes align with your organization’s security and compliance standards.

A reboot may be required after changes to TLS settings.

Once TLS 1.3 is enabled and verified (you can confirm via tools like PowerShell or IISCrypto), retry the connection with the Oracle 2.0 connector using:

Encryption client = required Crypto checksum client = required

Let us know how it goes or if you encounter anything unexpected - we’re happy to assist further!
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-28T09:40:48.0766667+00:00

@Blasko, Dan W We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Blasko, Dan W 60 Reputation points

2025-05-28T11:39:13.7433333+00:00

I did the regedit and rebooted this morning.

I am still having issues connecting.

Trying to find a way to confirm TLS 1.3 is actually being used.
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-28T13:22:34.2766667+00:00

@Blasko, Dan W Thanks for the update. Since the issue persists post-regedit and reboot, here are quick steps to confirm TLS 1.3 is enabled and in use:

Check registry settings via PowerShell:

Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Client"

Ensure Enabled=1 and DisabledByDefault=0.

Use IISCrypto to verify TLS 1.3 is enabled.

Confirm Oracle client version supports TLS 1.3.

Let us know what you find - we’ll assist further based on that.
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-29T09:53:28.2766667+00:00

@Blasko, Dan W We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Blasko, Dan W 60 Reputation points

2025-05-29T11:30:43.0166667+00:00

1.3 is enabled as well as 1.2. When I disabled 1.2 I caused issues where i was unable to connect to that server anymore using rdp or cyberark. Sysadmin had to revert back to before I screwed everything up. I did the 1.3 setup again and left 1.2 enabled. Still does not work.

You mention oracle client supports 1.3 but I do not have the oracle client installed on any of the IR nodes.

The 1.0 client has been working for a year now without the client. Does the 2.0 connector need the oracle client? It doesn't appear to need it from what i read. Just confirming.
Smaran Thoomu 31,835 Reputation points Microsoft External Staff Moderator

2025-05-30T14:58:37.2466667+00:00

@Blasko, Dan W Could you please check my private message and respond to it?
Deleted

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

Answer 1

Hey, I have been following this post in close detail as recently I have also tried to upgrade to the v2 oracle connector, but have failed to do so.

I have self-hosted IR installed on Windows Server 2022 with TLS 1.3 enabled and have the required additional properties already set up in the linked service. The Oracle source version is 19c (v.19.26).

I have stuck at 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-00542: SSL Handshake failed https://docs.oracle.com/error-help/db/ora-00542/ A call to SSPI failed, see inner exception. The message received was unexpected or badly formatted".

Inspecting the inner details I have seen the full error message:

TestConnection failed, error message: 'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Test connection operation failed.,Source=Microsoft.DataTransfer.Connectors.OracleV2Core,StackTrace= at Microsoft.DataTransfer.Connectors.OracleV2Core.OracleV2CoreValidator.TestConnection() at Microsoft.DataTransfer.TransferTask.InteractiveTaskFactoryV2.ConnectorTestConnection(ConnectionSetting connectionSetting, TestConnectionV2Response response) at Microsoft.DataTransfer.TransferTask.InteractiveTaskFactoryV2.TestConnection(TestConnectionV2Request request, TestConnectionV2Response response, OperationContext context, CancellationToken token) at Microsoft.DataTransfer.TransferTask.InteractiveTask2.Execute(),''Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Failed to open the Oracle database connection.,Source=Microsoft.DataTransfer.Connectors.OracleV2Core,StackTrace= at Microsoft.DataTransfer.Connectors.OracleV2Core.OracleV2CoreConnection.Open() at Microsoft.DataTransfer.Connectors.OracleV2Core.OracleV2CoreValidator.TestConnection(),''Type=Oracle.ManagedDataAccess.Client.OracleException,Message=ORA-50201: Oracle Communication: Failed to connect to server or failed to parse connect string,Source=Oracle Data Provider for .NET, Managed Driver,StackTrace= at OracleInternal.ConnectionPool.PoolManager3.Get(ConnectionString csWithDiffOrNewPassw, Boolean bGetForApp, OracleConnection connRefForCriteria, String affinityInstanceName, Boolean bForceMatch, Boolean bAsync) at OracleInternal.ConnectionPool.OraclePoolManager.Get(ConnectionString csWithNewPassw, Boolean bGetForApp, OracleConnection connRefForCriteria, String affinityInstanceName, Boolean bForceMatch, Boolean bAsync) at OracleInternal.ConnectionPool.OracleConnectionDispenser`3.Get(ConnectionString cs, PM conPM, ConnectionString pmCS, OracleOpaqueString securedPassw, OracleOpaqueString securedProxyPassw, OracleConnection connRefForCriteria, Boolean bAsync) at Oracle.ManagedDataAccess.Client.OracleConnectionInternal.OpenInternal(Boolean bAsync) at Oracle.ManagedDataAccess.Client.OracleConnectionInternal.Open() at Oracle.ManagedDataAccess.Client.OracleConnection.Open() at Microsoft.DataTransfer.Connectors.OracleV2Core.OracleV2CoreConnection.Open(),''Type=OracleInternal.Network.NetworkException,Message=ORA-50201: Oracle Communication: Failed to connect to server or failed to parse connect string,Source=Oracle.ManagedDataAccess,StackTrace= at OracleInternal.Network.OracleCommunication.DoConnect(String tnsDescriptor, Boolean bAsync) at OracleInternal.ServiceObjects.OracleConnectionImpl.Connect(ConnectionString cs, Boolean bOpenEndUserSession, OracleConnection connRefForCriteria, String instanceName, Boolean bAsync),''Type=OracleInternal.Network.NetworkException,Message=ORA-00542: SSL Handshake failed https://docs.oracle.com/error-help/db/ora-00542/,Source=Oracle.ManagedDataAccess,StackTrace= at OracleInternal.Network.TcpsTransportAdapter.Negotiate(ConnectionOption conOption) at OracleInternal.Network.OracleCommunication.SendConnectPacketAndProcessResponse(AddressResolution addrRes, Boolean bAsync) at OracleInternal.Network.OracleCommunication.ConnectViaCO(ConnectionOption connOption, AddressResolution addrRes, Boolean bAsync),''Type=System.Security.Authentication.AuthenticationException,Message=A call to SSPI failed, see inner exception.,Source=System,StackTrace= at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at OracleInternal.Network.TcpsTransportAdapter.Negotiate(ConnectionOption conOption),''Type=System.ComponentModel.Win32Exception,Message=The message received was unexpected or badly formatted,Source=,'. Log ID: Error

Would you be able to guide me on some possible next actions?

Blasko, Dan W 60 Reputation points

2025-07-14T10:59:41.6833333+00:00

I think our issues are slightly different. My second ora error is....ORA-12650: No common encryption or data integrity algorithm. Yours is a handshake error. I am able to connect roughly 50% of the time, but it fails the other 50%. I have a ticket open for months and no real answer. I added two more parameters to my linked service and that is was got me 50% success.
Blasko, Dan W 60 Reputation points

2025-07-14T11:00:56.0533333+00:00

I click test and it fails. I click test again and it fails. I click test a third time and it works. Sometimes it works the first time. No one has been able to help me.
Blasko, Dan W 60 Reputation points

2025-07-14T11:04:17.5766667+00:00

FYI....if you get this solved and are actually able to connect, then your next issue will be the terrible performance of the 2.0 connector. I also have a ticket open for that for over a month now. Again, absolutely no help. My 3 hour pipeline that loads 400+ tables is now a 10 hour pipeline. I can flip from 1.0 to 2.0 and the run times change accordingly, so I am 100% certain it's the new connector.
Moshekov, Ivaylo 0 Reputation points

2025-07-14T11:08:00.0633333+00:00

Did you eventually force your client to use TLS 1.3?
Blasko, Dan W 60 Reputation points

2025-07-14T11:11:13.6433333+00:00

I did a regedit and added 1.3. But I had to leave 1.2 there as well. Because when i removed 1.2, then i could no longer remote into the server and caused all kinds of issues and our sysadmin had to revert back to a saved snapshot of the vm. So 1.3 is in the registry, but so is 1.2
Blasko, Dan W 60 Reputation points

2025-07-14T17:41:46.9966667+00:00

fyi...it seems the 2.0 connector and clob columns don't play well. I found this doing my own research. Updated my ticket to see what MS has to say. Hopefully they can provide a fix.
Shailu81 0 Reputation points

2025-08-25T19:21:12.07+00:00

Ivaylo, I can see that error message you posted above was exactly same as mine. Did you have any luck with resolving that?

Answer 2

Shailu81 0

I also ran into the same error and have been working with msft support for over one month and issue hasn't been resolved yet. Below is the exact error message I saw while testing oracle ls 2.0 over tls enabled port: Failed to open the Oracle database connection. ORA-50201: Oracle Communication: Failed to connect to server or failed to parse connect string ORA-00542: SSL Handshake failed https://docs.oracle.com/error-help/db/ora-00542/ A call to SSPI failed, see inner exception. The message received was unexpected or badly formatted". This has been really time consuming so far and we haven't found any clues on yet. Any help/guidance to resolve the issue would be greatly appreciated. Thanks!

roeland rens 0 Reputation points

2025-10-22T12:36:33.2633333+00:00

can also confirm version 2022
TLS 1.2 working with v1.0 to oracle 19c.
upgrade to 2.0
not working with the same ora-00542 error.

Answer 3

roeland rens 0

regarding PROTOCOL=TCPS in version 2.0 on oracle 19c
resulting in
Failed to open the Oracle database connection. ORA-50201: Oracle Communication: Failed to connect to server or failed to parse connect string ORA-00542: SSL Handshake failed https://docs.oracle.com/error-help/db/ora-00542/ ...

check if you have an environment variable TNS_ADMIN pointing to to your tnsnames.ora and sqlnet.ora with the wallet_location specified within.

Share via

How to get the new data factory oracle 2.0 connector to connect?

3 answers

Your answer