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

Hi **Mohamed ElSheikh,
**Could you please share requested details in private message

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.

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

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.

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.