MIMB_DRIVER_F004 MIMB response is empty error when scaning Oracle data source

admin_zohreh@rucdk.onmicrosoft.com 10 Reputation points
2024-02-13T08:50:39.2033333+00:00

I am working with Microsoft Purview to create a data catalog. In this process, I have created an Oracle data source and now I want to create an Scan for it. The Oracle database is an on-premise database which is not publicly accessible. So I have created SHIR. The credential is set with key-vault and secret. The OJDBC driver is also set. However, when I want to test the connection , the connection fails and I get following error:

Error: (27001) ErrorCode=,ERROR_EXE MIMB_DRIVER_F004 MIMB response is empty.

Does anyone has an idea about it?

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,461 questions
{count} votes

1 answer

Sort by: Most helpful
  1. PRADEEPCHEEKATLA 90,571 Reputation points
    2024-02-13T10:02:01.7666667+00:00

    @******@rucdk.onmicrosoft.com - Thanks for the question and using MS Q&A platform.

    It seems like you are facing an error while scanning your Oracle data source in Microsoft Purview. The error message "MIMB_DRIVER_F004 MIMB response is empty" indicates that the scan engine is not able to retrieve any metadata from the Oracle data source. This could be due to various reasons such as incorrect configuration, connectivity issues, or permission issues. To troubleshoot this issue, you can follow the steps below:

    • Confirm that you have followed all the prerequisites mentioned in the documentation for scanning Oracle data sources in Microsoft Purview.
    • Check if the self-hosted integration runtime is set up correctly. If not, use the steps mentioned in the documentation to create a self-hosted integration runtime.
    • Verify that the credential you are using to connect to the Oracle data source is correct and has the necessary permissions to access the data source.
    • Check if the OJDBC driver is set up correctly. You can refer to the documentation for more information on how to set up the OJDBC driver.
    • Ensure that the Oracle database is up and running and is accessible from the network where the self-hosted integration runtime is running.
    • Check if there are any firewall rules or network restrictions that are preventing the self-hosted integration runtime from accessing the Oracle database.

    If none of these steps resolve the issue, you can provide more details on the error message and the steps followed. If the issue persists, please let me know and I will try to assist you further.

    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.