Share via

Purview unable to connect to Oracle DB - Metadata Ingestion Failed

Danrlei Alves 0 Reputation points
Dec 9, 2024, 9:21 AM

I am trying to scan and catalog an Oracle DB using Purview Oracle connector.

We went through all the steps, setting the SHIR, granting the permissions in the DB, testing the connection (it went through), but when we ran the scan, the Metadata Ingestion step Failed without error message, so I have no clue how to even troubleshoot.

The scan itself does not fail, instead it keeps running indefinitely (one of the attempts I left running for over 3 days before canceling it).

User's image

Does anyone have any clue what might be the issue? Thanks!

Azure Data Catalog
Azure Data Catalog
An Azure service that serves as a system of registration and system of discovery for enterprise data assets.
106 questions
Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,300 questions
{count} votes

1 answer

Sort by: Most helpful
  1. phemanth 12,575 Reputation points Microsoft Vendor
    Dec 9, 2024, 6:35 PM

    @Danrlei Alves

    Thanks for reaching out to Microsoft Q&A.

    Here are a few steps you can take to troubleshoot the issue:

    1. Check Permissions: Ensure that the Oracle user has the necessary permissions. The user should have read access to system tables and the SELECT_CATALOG_ROLE role assigned.
    2. Verify SHIR Configuration: Make sure the Self-Hosted Integration Runtime (SHIR) is correctly configured and running. Check the SHIR logs for any errors.
    3. JDBC Driver: Confirm that the Oracle JDBC driver is correctly installed and accessible by the SHIR. The driver should be in a location that the SHIR service account can access.
    4. Event Viewer Logs: Look at the Windows Event Viewer logs on the machine where SHIR is installed. This can provide more detailed error messages that might not be visible in the Purview portal.
    5. Network Issues: Ensure there are no network issues or firewall rules blocking the connection between Purview and the Oracle database.
    6. Review Documentation: Go through the Microsoft Purview documentation for any additional prerequisites or steps that might have been missed.

    I hope the above steps will resolve the issue, please do let us know if issue persists. Thank you

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.