Purview Oracle Scan via SHIR (recent versions) - persisting ConnectionString Error

Good afternoon,

as reported in this question

https://learn.microsoft.com/en-us/answers/questions/5889828/purview-oracle-scan-via-shir-connectionstring-erro

I am facing a similar situation.

At May 14th, I was facing the following issue:
Before upgrading SHIR, Oracle sources/scans still configured had been working without issues.

The Purview test connection 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.

After your suggestions in that question reported, I downloaded another updated SHIR version (5.66.9620.1) and the Oracle TestConnection still fails before any actual Oracle network/authentication attempt, both for existing and attempts for new configured scans.

Trace details:

TraceComponentId: QueryTask
TraceMessageId: QueryRuntimeTestConnectionV2Exception
FunctionName: TestConnection
jobId: 00000000-0000-0000-0000-000000000000
activityId: <omiss>
Error:
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

//The stack trace still goes through:
Microsoft.Connectors.Migration.Oracle.OracleV1ConnectionSettings.InitConnectionString()
Microsoft.Connectors.Migration.Oracle.OraclePropertiesUpgradeHandler.UpgradeConnectionProperties()
Microsoft.DataTransfer.Runtime.UpgradeHandlerConnector.CreateConnection(...)

This is the same Oracle connector migration path described in this thread: the connector expects a legacy connectionString even though the Purview Oracle source is configured with structured fields.

Also, the referenced build 5.64.9578.2 does not seem to be publicly available, while SHIR 5.66.9620.1 is newer and still reproduces the same issue.

Additionally, the SHIR is shown in the Purview portal as Running (Unhealthy), although locally everything appears healthy:

• SHIR service is running
• node is visible in Purview
• heartbeat/last connection is working
• version is 5.66.9620.1
• no relevant local errors are shown

Please verify and fix this on the Microsoft/Purview side, or provide a working hotfix/build.

Thanks