Purview Data Map Oracle scan via SHIR fails – “The version of the linked service is not supported”

Hi Mohamed ElSheikh,
Thankyou for reacing microsoft Q&A!
Thank you for sharing the details. Based on the information provided, the connectivity between SHIR and your Oracle database is working correctly, as confirmed by the successful test connection.

The failure is occurring specifically during the scan execution step due to the error “The version of the linked service is not supported.” This typically indicates a mismatch in the linked service definition used internally by Microsoft Purview during scan configuration, rather than an issue with network, credentials, or Oracle connectivity.

Before we proceed further, we recommend updating the connection configuration to use Service Name instead of SID, as newer scan configurations may expect this format. Please recreate the data source and scan from scratch after making this change. Also ensure that the Self-Hosted Integration Runtime (SHIR) is fully up to date, and consider a clean reinstall if the issue persists. Additionally, verify that the Oracle client or driver installed on the SHIR machine is compatible with Oracle 19c.

If the issue continues after these steps, we will proceed with a deeper internal validation from our end, as it may require backend investigation. Please let us know once you’ve tried the above, and we’ll assist you further.

The error text points to a configuration/compatibility issue with how the Oracle source is wired to SHIR rather than basic network connectivity.

For Purview to scan Oracle via SHIR, the following prerequisites must be in place on the SHIR machine and for the Oracle account; if any of these are missing or misconfigured, scan creation or execution can fail even when “Test connection” passes:

1. Verify SHIR is the correct type and supported for Oracle

• Oracle is supported only via Self‑hosted Integration Runtime (SHIR) (not Azure IR / Managed VNet IR / Kubernetes SHIR) in the Purview Data Map.
• Confirm the scan is explicitly configured to use the SHIR instance (not an Azure IR) for this Oracle source.

Reference capability matrix:

• Oracle appears only under the SHIR column in the supported data sources list.

2. Confirm all Oracle connector prerequisites on the SHIR host On the VM where SHIR is installed, ensure all of the following are installed and visible to the SHIR service account:

• OpenJDK 8 installed.
• Oracle JDBC driver 8 (OJDBC8) downloaded and present on disk.
• Visual C++ Redistributable (Visual Studio 2012 Update 4 or newer) installed.
• The SHIR service account (by default NT SERVICE\DIAHostService) has Read & execute and List folder contents permissions on the folder where the Oracle JDBC driver is stored.

If any of these are missing or the driver folder is not accessible to the SHIR service account, the Oracle connector layer used by Purview can fail in ways that surface as “linked service version not supported” when running a scan.

3. Validate Oracle user permissions for scanning The Oracle account used in the Purview Oracle connection must have at least:

• Permission to create a session.
• Role SELECT_CATALOG_ROLE assigned, or SELECT granted on every system table the connector queries.
• For classification, SELECT on the relevant user tables.

Example grants if needed:

GRANT SELECT ON [table_name] TO [purview_user];
GRANT SELECT ANY TABLE TO [purview_user];

Insufficient metadata permissions can cause scan failures even when a basic connectivity test succeeds.

4. Re‑create the scan after fixing SHIR/driver prerequisites After verifying and, if needed, correcting the above:
5. Restart the SHIR service (or the VM) so new JDK/driver/VC++ installs are picked up.
6. In Purview, ensure the Oracle data source is associated with this SHIR.
7. Recreate the scan rule set/scan and run it again.
8. If the error persists, collect SHIR logs and contact support If all prerequisites and permissions are correct and the error still appears:
9. On the SHIR machine, open Windows Event Viewer → Applications and Services Logs → Integration Runtime.
10. Clear the Integration Runtime logs.
11. Start a new Oracle scan from the Purview governance portal and wait for it to fail.
12. Return to Event Viewer and review the new Integration Runtime entries for detailed connector errors.
13. From the SHIR UI, use Send Logs to upload logs and capture the Report ID.
14. Use that Report ID when opening a support ticket so Microsoft can correlate the “linked service version” error with the underlying SHIR/Oracle connector failure.

This sequence ensures the Oracle connector on SHIR is fully compliant with Purview’s requirements and provides the detailed telemetry needed if the issue is due to a backend version mismatch.

References:

• Connect to and manage Oracle in Microsoft Purview
• Choose the right integration runtime configuration for your scenario
• Troubleshoot Microsoft Purview self-hosted integration runtime (SHIR)