Purview Oracle Scan via SHIR - ConnectionString Error (11402) despite successful SHIR to Oracle connectivity

Question

Purview Oracle Scan via SHIR - ConnectionString Error (11402) despite successful SHIR to Oracle connectivity

Mohamed ElSheikh 30 Microsoft Employee

We are facing an issue while configuring Microsoft Purview to scan an on-premises Oracle database using Self-Hosted Integration Runtime (SHIR).

✅ SHIR → Oracle connection is successful (validated via SHIR Configuration Manager – see attached screenshot)
❌ Purview → SHIR test connection fails (from Purview scan configuration – see attached screenshot)

Error message:
Error: (11402) The value of the property 'connectionString' is invalid: 'The required property is not specified. Parameter name: connectionString'.#### Configuration summary

Data source type: Oracle (on-premises)
Integration Runtime: Self-hosted (Running and reachable)
JDBC driver: ojdbc8 installed on SHIR machine
Credential: Basic authentication using Azure Key Vault (username + password stored securely)

Troubleshooting already performed

Recreated data source and scan configuration
Validated host, port, and service name
Verified driver installation and path accessibility
Confirmed SHIR is online and functioning

Error seen on testing connection or scaning from Purview:

2026-05-13_211450

SHIR connection to oracle looks fine:
User's image

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

SAI JAGADEESH KUDIPUDI 3,650 Reputation points Microsoft External Staff Moderator

2026-05-13T20:10:57.2833333+00:00

Hi **Mohamed ElSheikh,
**Could you please share requested details in private message
SAI JAGADEESH KUDIPUDI 3,650 Reputation points Microsoft External Staff Moderator

2026-05-13T20:19:13.8166667+00:00

Hi Mohamed ElSheikh,
Since the SHIR connectivity test is succeeding, the issue appears to occur during the Oracle connector initialization/validation phase rather than a network or authentication failure.

In similar Microsoft Purview Oracle scan scenarios, this behavior is commonly related to one of the following:

SID vs SERVICE_NAME mismatch in the Oracle connection configuration

Oracle JDBC driver compatibility or driver path issues on the SHIR machine

SHIR runtime/version inconsistencies

Stale or inconsistent scan metadata in Purview

Occasional transient backend/service-side validation issues

Please try the following:

Verify whether the Oracle server expects SERVICE_NAME or SID and test both formats in the connection string.

Ensure a supported Oracle JDBC driver (commonly ojdbc8.jar) is installed on the SHIR server and accessible to the DIAHostService account.

Restart the Self-hosted Integration Runtime service after any driver or Java changes.

Delete and recreate the scan and credential object completely instead of reusing the existing one.

Review SHIR diagnostic logs from Integration Runtime Configuration Manager or Event Viewer for additional Oracle connector errors.

Also, there have been cases where similar scan validation errors appeared temporarily due to transient backend/service-side issues without any prior service announcement, so retrying after some time may also help.

Official documentation:

Oracle scan configuration in Microsoft Purview

Troubleshoot Self-hosted Integration Runtime

Integration Runtime concepts and configuration

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.
Marianna Piacentini 0 Reputation points

2026-05-14T15:54:36.2033333+00:00
Hi,

I’m seeing the same issue reported here after a SHIR upgrade (necessary because the previous version was outdated). Before the upgrade, the same Oracle source/scan configured had been working without issues.

The Purview test connection now fails with:

Error: (11402) The value of the property 'connectionString' is invalid: 'The required property is not specified. Parameter name: connectionString'

From the local SHIR log under Connectors – Integration Runtime, the failure seems to happen before the actual Oracle connection attempt:

TraceMessageId: QueryRuntimeTestConnectionV2Exception

Stack includes:

Microsoft.DataTransfer.Runtime.Oracle.OracleConnectionSettings.InitConnectionString()

Microsoft.DataTransfer.Runtime.OracleCapabilityBase.BuildConnectionString()

Microsoft.DataTransfer.Runtime.OdbcConnectorValidator.TestConnection()

There is also this warning around the same timestamp:

TraceMessageId: TransparentConnectorMigration Failed while creating connection instance from the upgraded connection properties for connector type Oracle due to The required property is not specified. Parameter name: connectionString

I also checked the Purview Scanning Data Plane API. The datasource JSON contains the expected Oracle fields:

kind: Oracle

properties.host

properties.port

properties.service

The scan JSON also contains:

credential BasicAuth reference

driverLocation pointing to a folder containing ojdbc8.jar

connectedVia SelfHosted IR reference

scanRulesetName: Oracle

kind: OracleOracleCredential

I also tried creating a new datasource, new credential, and new scan, but the same error persists.

Given that this started only after the SHIR upgrade, and the log points to TransparentConnectorMigration, this looks more like a regression or connector migration issue in the Oracle connector rather than a network, service name, credential, or JDBC driver path problem.

Hope this helps in further investigations on your side @SAI JAGADEESH KUDIPUDI . Thanks
Smaran Thoomu 35,960 Reputation points Microsoft External Staff Moderator

2026-05-20T01:46:52.4333333+00:00
Hi Mohamed ElSheikh,

Thank you for sharing the additional screenshots and findings.

We were able to correlate this behavior with an existing known issue currently being tracked internally by the Product Group affecting Oracle scans through SHIR in Microsoft Purview.

Current understanding:

Oracle connectivity itself is functioning correctly

SHIR connectivity validation succeeds

External Oracle tools/connectivity tests also succeed

The failure occurs specifically during Purview “Test connection” validation

The error: Error (11402): connectionString is invalid / missing is currently identified as a known connector validation issue related to Oracle scan connection testing after SHIR upgrade/migration scenarios

At this moment, Product Group has confirmed:

this is largely a cosmetic validation issue,

and the “Test connection” failure does not necessarily prevent the actual scan execution itself.

As a workaround, please proceed directly with creating/running the scan despite the test connection error and validate whether the scan execution itself completes successfully.

The engineering team is already working on a permanent fix/removal of the problematic validation component.

Thank you for your patience while the fix is being worked on internally.
Smaran Thoomu 35,960 Reputation points Microsoft External Staff Moderator

2026-05-26T02:48:35.6966667+00:00
Hi @Mohamed ElSheikh

We checked internally with the Product Group and found this issue is currently being tracked as part of an Oracle + SHIR connector/runtime issue affecting some Purview Oracle scans.

PG has provided an updated SHIR build (5.64.9578.2) containing fixes related to:

linked service version errors

11402 connectionString

Oracle connector/runtime scan initialization issues

Could you please upgrade the SHIR node to version 5.64.9578.2 and retry:

Test connection

Oracle scan execution

Once tested, please share:

updated behavior/result

latest Scan Run ID

whether the 3818 metadata is not available error still persists

Based on internal guidance, this SHIR version should help address the current Oracle connector issue.
Luis Daniel Elvir Lainez 5 Reputation points

2026-05-26T17:44:39.5833333+00:00

Hi @Anonymous , the version you mentioned 5.64.9578.2, doesn't appear on the official download page:
https://www.microsoft.com/en-us/download/details.aspx?id=105539
Smaran Thoomu 35,960 Reputation points Microsoft External Staff Moderator

2026-05-27T01:54:19.9166667+00:00

@Mohamed ElSheikh Luis Daniel Elvir Lainez Apologies for that, let me check with team and provide you an update.
Luis Daniel Elvir Lainez 5 Reputation points

2026-06-01T16:17:10.27+00:00

Hi @Anonymous , is there any new update on whether a new version of the Integration Runtime exists?
Smaran Thoomu 35,960 Reputation points Microsoft External Staff Moderator

2026-06-03T04:08:21.25+00:00

@Mohamed ElSheikh Luis Daniel Elvir Lainez Could you please check and try upgrading this SHIR https://www.microsoft.com/en-us/download/details.aspx?id=39717
Mohamed ElSheikh 30 Reputation points Microsoft Employee

2026-06-03T09:09:14.27+00:00

@Anonymous , this is the latest version available in this link IntegrationRuntime_5.66.9620.1.msi, should we try this one?
Smaran Thoomu 35,960 Reputation points Microsoft External Staff Moderator

2026-06-04T05:53:03.53+00:00

@Mohamed ElSheikh Could you please test both versions and let me know the results?
Luis Daniel Elvir Lainez 5 Reputation points

2026-07-06T17:37:48.99+00:00
Hello @Anonymous the error remains the same: Error: (11402) The value of the property 'connectionString' is invalid: 'The required property is not specified. Parameter name: connectionString'.

As mentioned @Mohamed ElSheikh : We have already tried all the suggested steps, but the issue persists. The scan continues to fail with ConnectionString error (11402).

rerequisites (OpenJDK 8, OJDBC8, VC++): Verified and correctly installed

Driver path and permissions: Configured with a valid absolute path and the SHIR service account has access to it

Use of service name (not SID): Confirmed and validated

SHIR reinstallation/rollback: Multiple versions tested, uninstalled and reinstalled, no changes

Connection validation: "Test Connection" in Purview succeeds consistently

We even installed the latest version of the Purview Integration Runtime, and we still cannot scan Oracle databases. SQL Server and other options work without any issues, even Google's BigQuery which is similar in that it requires a Driver also works for us, so the problem is specifically with Oracle.
Pavan Kumar Jonnakuti 0 Reputation points

2026-08-11T20:26:30.76+00:00
@SAI JAGADEESH KUDIPUDI @Sina Salam @Mohamed ElSheikh Is this issue resolved for anyone? We are getting the below error when trying to test connection from purview.

Error: (0) Failed while creating connection instance from the upgraded connection properties for connector type Oracle due to The required property is not specified. Parameter name: connectionString

We have already tried all the suggested steps, but the issue persists. The scan continues to fail with ConnectionString error (0). It is not throwing 11402.

Prerequisites (OpenJDK 8, OJDBC8, VC++): Verified.

Driver path and permissions: Configured with a valid absolute path and the SHIR service account has access to it

Use of service name (not SID): Confirmed and validated

SHIR upgraded to latest version 5.68.9683.1

Connection validation: "Test Connection" in Purview fails.

Triggering manual scan fails with the below error.

All scheduled Oracle scans are not triggered automatically.

Internal system error. Please contact support with correlationId: 49d35f19-bf52-4495-a051-e19ee7ddd9b2 System Error, contact support: (119) System error while attempting to launch datascan process. ActivityId: e0e8f262-dde1-4118-a3ba-ef72271dd59e ) Please suggest if anyone knows the solution to fix this issue.

2 answers

SAI JAGADEESH KUDIPUDI 3,650 Reputation points Microsoft External Staff Moderator

2026-05-13T20:10:57.2833333+00:00

Hi **Mohamed ElSheikh,
**Could you please share requested details in private message
SAI JAGADEESH KUDIPUDI 3,650 Reputation points Microsoft External Staff Moderator

2026-05-13T20:19:13.8166667+00:00

Hi Mohamed ElSheikh,
Since the SHIR connectivity test is succeeding, the issue appears to occur during the Oracle connector initialization/validation phase rather than a network or authentication failure.

In similar Microsoft Purview Oracle scan scenarios, this behavior is commonly related to one of the following:

SID vs SERVICE_NAME mismatch in the Oracle connection configuration

Oracle JDBC driver compatibility or driver path issues on the SHIR machine

SHIR runtime/version inconsistencies

Stale or inconsistent scan metadata in Purview

Occasional transient backend/service-side validation issues

Please try the following:

Verify whether the Oracle server expects SERVICE_NAME or SID and test both formats in the connection string.

Ensure a supported Oracle JDBC driver (commonly ojdbc8.jar) is installed on the SHIR server and accessible to the DIAHostService account.

Restart the Self-hosted Integration Runtime service after any driver or Java changes.

Delete and recreate the scan and credential object completely instead of reusing the existing one.

Review SHIR diagnostic logs from Integration Runtime Configuration Manager or Event Viewer for additional Oracle connector errors.

Also, there have been cases where similar scan validation errors appeared temporarily due to transient backend/service-side issues without any prior service announcement, so retrying after some time may also help.

Official documentation:

Oracle scan configuration in Microsoft Purview

Troubleshoot Self-hosted Integration Runtime

Integration Runtime concepts and configuration

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.
Smaran Thoomu 35,960 Reputation points Microsoft External Staff Moderator

2026-05-20T01:46:52.4333333+00:00

Hi Mohamed ElSheikh,

Thank you for sharing the additional screenshots and findings.

We were able to correlate this behavior with an existing known issue currently being tracked internally by the Product Group affecting Oracle scans through SHIR in Microsoft Purview.

Current understanding:

Oracle connectivity itself is functioning correctly

SHIR connectivity validation succeeds

External Oracle tools/connectivity tests also succeed

The failure occurs specifically during Purview “Test connection” validation

The error: Error (11402): connectionString is invalid / missing is currently identified as a known connector validation issue related to Oracle scan connection testing after SHIR upgrade/migration scenarios

At this moment, Product Group has confirmed:

this is largely a cosmetic validation issue,

and the “Test connection” failure does not necessarily prevent the actual scan execution itself.

As a workaround, please proceed directly with creating/running the scan despite the test connection error and validate whether the scan execution itself completes successfully.

The engineering team is already working on a permanent fix/removal of the problematic validation component.

Thank you for your patience while the fix is being worked on internally.
Smaran Thoomu 35,960 Reputation points Microsoft External Staff Moderator

2026-05-26T02:48:35.6966667+00:00

Hi @Mohamed ElSheikh

We checked internally with the Product Group and found this issue is currently being tracked as part of an Oracle + SHIR connector/runtime issue affecting some Purview Oracle scans.

PG has provided an updated SHIR build (5.64.9578.2) containing fixes related to:

linked service version errors

11402 connectionString

Oracle connector/runtime scan initialization issues

Could you please upgrade the SHIR node to version 5.64.9578.2 and retry:

Test connection

Oracle scan execution

Once tested, please share:

updated behavior/result

latest Scan Run ID

whether the 3818 metadata is not available error still persists

Based on internal guidance, this SHIR version should help address the current Oracle connector issue.
Luis Daniel Elvir Lainez 5 Reputation points

2026-05-26T17:44:39.5833333+00:00

Hi @Anonymous , the version you mentioned 5.64.9578.2, doesn't appear on the official download page:
https://www.microsoft.com/en-us/download/details.aspx?id=105539
Smaran Thoomu 35,960 Reputation points Microsoft External Staff Moderator

2026-05-27T01:54:19.9166667+00:00

@Mohamed ElSheikh Luis Daniel Elvir Lainez Apologies for that, let me check with team and provide you an update.
Luis Daniel Elvir Lainez 5 Reputation points

2026-06-01T16:17:10.27+00:00

Hi @Anonymous , is there any new update on whether a new version of the Integration Runtime exists?
Smaran Thoomu 35,960 Reputation points Microsoft External Staff Moderator

2026-06-03T04:08:21.25+00:00

@Mohamed ElSheikh Luis Daniel Elvir Lainez Could you please check and try upgrading this SHIR https://www.microsoft.com/en-us/download/details.aspx?id=39717
Mohamed ElSheikh 30 Reputation points Microsoft Employee

2026-06-03T09:09:14.27+00:00

@Anonymous , this is the latest version available in this link IntegrationRuntime_5.66.9620.1.msi, should we try this one?
Smaran Thoomu 35,960 Reputation points Microsoft External Staff Moderator

2026-06-04T05:53:03.53+00:00

@Mohamed ElSheikh Could you please test both versions and let me know the results?
Luis Daniel Elvir Lainez 5 Reputation points

2026-07-06T17:37:48.99+00:00

Hello @Anonymous the error remains the same: Error: (11402) The value of the property 'connectionString' is invalid: 'The required property is not specified. Parameter name: connectionString'.

As mentioned @Mohamed ElSheikh : We have already tried all the suggested steps, but the issue persists. The scan continues to fail with ConnectionString error (11402).

rerequisites (OpenJDK 8, OJDBC8, VC++): Verified and correctly installed

Driver path and permissions: Configured with a valid absolute path and the SHIR service account has access to it

Use of service name (not SID): Confirmed and validated

SHIR reinstallation/rollback: Multiple versions tested, uninstalled and reinstalled, no changes

Connection validation: "Test Connection" in Purview succeeds consistently

We even installed the latest version of the Purview Integration Runtime, and we still cannot scan Oracle databases. SQL Server and other options work without any issues, even Google's BigQuery which is similar in that it requires a Driver also works for us, so the problem is specifically with Oracle.
Pavan Kumar Jonnakuti 0 Reputation points

2026-08-11T20:26:30.76+00:00

@SAI JAGADEESH KUDIPUDI @Sina Salam @Mohamed ElSheikh Is this issue resolved for anyone? We are getting the below error when trying to test connection from purview.

Error: (0) Failed while creating connection instance from the upgraded connection properties for connector type Oracle due to The required property is not specified. Parameter name: connectionString

We have already tried all the suggested steps, but the issue persists. The scan continues to fail with ConnectionString error (0). It is not throwing 11402.

Prerequisites (OpenJDK 8, OJDBC8, VC++): Verified.

Driver path and permissions: Configured with a valid absolute path and the SHIR service account has access to it

Use of service name (not SID): Confirmed and validated

SHIR upgraded to latest version 5.68.9683.1

Connection validation: "Test Connection" in Purview fails.

Triggering manual scan fails with the below error.

All scheduled Oracle scans are not triggered automatically.

Internal system error. Please contact support with correlationId: 49d35f19-bf52-4495-a051-e19ee7ddd9b2 System Error, contact support: (119) System error while attempting to launch datascan process. ActivityId: e0e8f262-dde1-4118-a3ba-ef72271dd59e ) Please suggest if anyone knows the solution to fix this issue.

Answer 1

SHIR connection issue resolved by enabling Windows Long Paths

We experienced a connection issue while configuring the Microsoft Purview Self-Hosted Integration Runtime (SHIR). After troubleshooting, we found that the problem was related to the Windows path length limitation (MAX_PATH).

The following registry setting resolved the issue:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v LongPathsEnabled /t REG_DWORD /d 1 /f

reg query "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v LongPathsEnabled

After enabling long paths and restarting the affected services/server, the SHIR connection worked successfully. This may help in scenarios where connection strings, cache paths, or temporary folders exceed the default Windows path length limitation.

Answer 2

Sina Salam 31,456 Volunteer Moderator

Hello Mohamed ElSheikh,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are having issues with Microsoft Purview Oracle scan failures after SHIR upgrade, specifically the error: Error (11402): connectionString is invalid or not specified

The minimal-risk way of resolving this is to:

Ensure Oracle connector prerequisites are correctly installed and effective (OpenJDK 8, OJDBC8, VC++ runtime)
Configure driver location with a valid absolute path (no spaces) and grant proper access to the SHIR service account
Use Oracle service name (not SID) in the Purview data source configuration
Perform a clean reinstall or rollback of SHIR if the issue started after an upgrade (to resolve connector migration/regression issues)
Validate connection only through Purview scan “Test connection”, not SHIR Diagnostics

After correcting prerequisites, driver configuration, and resolving any SHIR upgrade regression via clean reinstall or rollback, the Purview Oracle scan successfully initializes the connector and completes without the connectionString error.

The resource links below are for more reading and steps:

I hope this is helpful! Do not hesitate to let me know if you have any other questions, steps or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Mohamed ElSheikh 30 Reputation points Microsoft Employee

2026-05-19T13:14:14.63+00:00
We have already tested all the suggested steps, but the issue still persists. The scan still fails with ConnectionString Error (11402).

Prerequisites (OpenJDK 8, OJDBC8, VC++): Verified and properly installed

Driver path & permissions: Configured with a valid absolute path and SHIR service account has access to it

Service name usage (not SID): Confirmed and validated

SHIR reinstall/rollback: Multiple versions tested, uninstalled and reinstalled, with no change

Connection validation: “Test connection” in Purview succeeds consistently

The main challenge is that the error provides insufficient details/logging, with no clear root cause, which prevents further troubleshooting from our side.
Sina Salam 31,456 Reputation points Volunteer Moderator

2026-05-19T13:38:30.8833333+00:00

Hi @Mohamed ElSheikh

Thank you for your feedback.

The hidden truth is that Purview’s Oracle scan configuration is stored using structured properties such as host, port, and service, but the upgraded SHIR Oracle connector path is attempting to instantiate an older or different connector model that expects a literal connectionString. During TransparentConnectorMigration, the metadata conversion fails, so the connector receives no connectionString and throws error 11402.

Since you have done all listed and could not resolve, the next action is to escalate with a focused support case. Referencing this page and send your configurations. Of course, I will escalate right from here too as:

TransparentConnectorMigration

OracleConnectionSettings.InitConnectionString()

missing connectionString

after SHIR upgrade.

You can seek support with Priority Customer Support - (PCS).

Cheers.