Forum Discussion

oj606481's avatar
oj606481
Frequent Visitor
4 years ago

Paginated Reports with Oracle DB Connection Type

Greetings, I am using Power BI Report Builder to generate a report using Oracle DB as the connection type.

 

It runs fine on my local machine, but when published to the server I get the displayed error when trying to access it. The "Additional steps are required to view this report" link brings me this this page Power BI gateway and Report Builder support for ODBC data sources (preview) - Power BI | Microsoft Docs , which outlines how to configure and use ODBC with paginated reports. 

 

We have explored and configured this option, but it does not perform as well as the Oracle DB connection type when connected to our Oracle database.

 

So far we have confirmed the 64 bit ODAC 12.2 is installed on the host server, following the instrutions here [Oracle Connection Type (SSRS & Power BI Report Server) - SQL Server Reporting Services (SSRS) | Microsoft Docs ]to register the ODP.NET Managed Client to both the GAC and machine.config.

 

We have Power BI reports that use the existing Oracle connection just fine on the server, so not sure what next to try in resolving this. Any help will be apreciated, and should more details be required I will provide.

 

4 Replies

    • oj606481's avatar
      oj606481
      Frequent Visitor

      Hi v-henryk-mstf ,

       

      Thank you for your replay, and apologies for the delay in my response. That solution does not help in this regard.

       

      Below is the full error message received when I try accessing the report with Oracle Database as the Connection Type.

      An unexpected error occurred

      A data source used by this report returned an error. An exception encountered while creating the target data source Unable to find the requested .Net Framework Data Provider. It may not be installed.


      We have Oracle 12c installed, along with the 64 bit ODAC 12.2.

       

      Based on the error message it is having difficulty finding the .Net Framework Data Provider, which unless I am mistaken would be the ODP.NET covered in the ODAC installation. 

  • Anonymous's avatar
    Anonymous
    Not applicable

     Hi, 

     

    I am facing the same issue, did you find any solution for it ?

     

    Regards,

    Aarti

  • Anonymous's avatar
    Anonymous
    Not applicable

    Was there ever a solution to this? I am having the same issue. It works locally but once I publish it, I cannot seem to get it to work with same error. I believe I have the gateway configured the same as I do locally but perhaps not.