'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Microsoft Purview Oracle Scan Metadata Ingestion Failures
Question details
The user needs to resolve an issue where the Microsoft Purview Oracle connector passes the initial connection test but fails during metadata ingestion, causing the scan to run indefinitely.
- Product
- Microsoft Purview
- Device & OS
- not provided
- Scenario
- Running an Oracle connector scan for metadata ingestion within Microsoft Purview.
- Observed behavior
- The connection test passes successfully, but the scan gets stuck during the metadata ingestion phase and runs indefinitely without completion.
Gather your diagnostic information in advance, including scan logs, connector configuration details, and Self-hosted Integration Runtime (SHIR) versions, to make troubleshooting and support requests more efficient.
Seek Support from Microsoft Q&A Purview Specialists
Because metadata ingestion errors involving Oracle connectors are highly specific to your network and database environment, posting on the official Microsoft Q&A forum is the most effective way to get a resolution.
Microsoft Q&A connects you directly with Purview engineers and specialists who can analyze your specific SHIR logs and Oracle database configurations to identify the root cause of the endless scan.
Gather your scan logs, Self-hosted Integration Runtime (SHIR) details, Oracle version, current permissions setup, scan duration, and the exact error message provided by Purview.
Carefully review all logs and configuration snippets to remove user credentials, internal IP addresses, and other confidential data before making them public.
Navigate to the official Microsoft Q&A platform (https://learn.microsoft.com/en-us/answers/questions/) and create a new detailed post describing the ingestion failure for Purview specialists to investigate.
Verify Self-hosted Integration Runtime and Oracle Permissions
Before reaching out to support, you can perform basic checks on your integration runtime and database permissions to ensure they are not blocking the ingestion process.
Need a Reliable Document Suite? Try WPS Office
While you troubleshoot complex database and Microsoft Purview ingestion issues, simplify your daily documentation and data analysis tasks with WPS Office. It is a powerful, lightweight alternative to Microsoft Office that is completely free.
- 1. Download the installer: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to set up the suite.
- 3. Open and edit your files: Launch WPS Office to instantly open, edit, and save your existing Microsoft Office documents without any formatting loss.
Frequently Asked Questions
Why does my Microsoft Purview Oracle scan run indefinitely?
This usually happens when the connector successfully pings the database (passing the connection test) but encounters hidden permission blocks, network timeouts, or Self-hosted Integration Runtime (SHIR) conflicts when trying to pull the actual metadata.
What information should I include when asking for Purview support?
To get effective help on Microsoft Q&A, include your complete scan logs, connector configuration details, SHIR version, Oracle database version, current permission settings, scan duration, and the exact error message. Always redact passwords and private data before posting.
Can an outdated Self-hosted Integration Runtime cause ingestion failures?
Yes. If your SHIR is outdated, lacks necessary system resources, or momentarily loses network connectivity during the deep scan process, it can interrupt metadata ingestion even after a successful initial connection test.
