This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 95%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDA%3C/text%3E%3C/svg%3E)
Hi all
I am trying to scan an Oracle DB through Purview DataMap Oracle connector.
We did setup everything as per Microsoft documentation (SHIR, Oracle grants for the purview user) and the test connection went through.
When running a scan, the Metadata Ingestion step fails, but the scan keeps running indefinitely (i canceled one of the attempts after 3 days running). I also noticed the Metadata Discovery step fails to discover any assets.
Did anyone experience anything similar? Any tip is appreciated. Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 65%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECB%3C/text%3E%3C/svg%3E)
Greetings & Welcome to Microsoft Q&A forum! Thanks for posting your query!
As I understand that the scan is running indefinitely without any specific error messages and the Metadata Ingestion step fails silently, which can definitely make troubleshooting challenging.
Here are some troubleshooting steps that might help you in resolving the query:
Check Permissions: Ensure that the Oracle user you are using has the necessary permissions. The user must have read access to system tables to access advanced metadata. Additionally, for classification, the user needs to be the owner of the tables.
Review Configuration: Double-check your setup for the self-hosted integration runtime (SHIR) and ensure that the Oracle JDBC driver is correctly installed and accessible by the SHIR. The driver must be in a folder that the service account has permission to access.
Check SHIR Resource Usage: Since the scan is running indefinitely, it could be a sign that the Self-hosted Integration Runtime (SHIR) is struggling to process the scan. Check the resource usage on the machine running the SHIR (CPU, memory, and disk). If resources are maxed out or if there’s a performance bottleneck, it could cause the scan to hang indefinitely.
Connector Version: Ensure you're using the latest version of the DataMap Oracle Connector. Sometimes, older versions can have issues or bugs that have since been resolved in newer updates.
Check Purview Logs: Even though there are no visible error messages, Purview logs might still contain valuable information. Look for logs related to the Metadata Ingestion step or the SHIR logs on the machine running it. Sometimes, logs can reveal timeouts, connectivity issues, or resource constraints that aren't immediately visible in the Purview UI.
Please refer to the below Microsoft documentation for additional information:
Connect to and manage Oracle in Microsoft Purview
Troubleshoot your scans and connections in the Microsoft Purview Data Map
Audit logs, diagnostics, and activity history
I hope this information helps. Please do let us know if you have any further queries.
Thank you.
Hi Chandra,
Thanks for your return. We diligently followed your instructions and no issues were found.
Additionally, i tried to narrow down the scan selecting one schema only. This time around the scan actually completed, but no assets were ingested.
So, the issue seems to be that the scan is not discovering the assets in the source, therefore it cannot ingest them.
Any tips for this case?
Thanks for the update. Based on your latest information, it sounds like the scan is completing, but the issue is with metadata discovery - the assets are not being discovered in the source, so they can't be ingested.
Here are some additional considerations that might help you.
Review Oracle Database Configuration - Sometimes, Oracle database configurations (e.g., encryption, partitioned tables, or restricted views) can limit the visibility of metadata to external tools. If there are any such configurations, they might prevent Purview from discovering the assets. You can check if any of these factors are in play within your Oracle setup.
Check SHIR Configuration - Since you are using the Self-hosted Integration Runtime (SHIR), make sure it is properly configured and that there are no network or connectivity issues between the SHIR and your Oracle database.
Please refer to the similar threads that might help you to get some useful insights.
Please refer the following Microsoft documents for additional information:
Troubleshoot Microsoft Purview self-hosted integration runtime (SHIR)
Microsoft Purview scanning best practices
I hope this information helps. Please do let us know if you have any further queries.
Thank you.
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
No resolution yet. We will try verifying the SHIR logs to check for abnormalities. We will also check for firewalls.
Thank you for the update. Kindly inform us once you have verified the SHIR logs and reviewed the firewall configurations.
Just checking in to see if the below suggestion helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
We checked the logs, turns out it was an issue of lack of memory, apparently.
Microsoft.DataMap.Agent.Core.Common.ModuleFatalException: Connector Exception: java.lang.OutOfMemoryError: Java heap space
We increased the RAM memory of the VM and the Scan worked like a charm.
Thank you for the help!!!
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.
Issue:
I am trying to scan an Oracle DB through Purview DataMap Oracle connector.
We did setup everything as per Microsoft documentation (SHIR, Oracle grants for the purview user) and the test connection went through.
When running a scan, the Metadata Ingestion step fails, but the scan keeps running indefinitely (i canceled one of the attempts after 3 days running). I also noticed the Metadata Discovery step fails to discover any assets.
Solution:
After reviewing the logs, we determined the issue was due to a memory shortage.
Microsoft.DataMap.Agent.Core.Common.ModuleFatalException: Connector Exception: java.lang.OutOfMemoryError: Java heap space
We increased the VM's RAM, and the scan completed successfully.
If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.
Hope this helps. Do let us know if you have any further queries.
If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.