Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Failed Refresh on Published Version only

Hello everyone!

 

I have a dashboard that gets different data from different SQL sources. When I try to refresh all data on the Power BI it works fine, just take quite some time due to the size of the sources. However, when I publish the dashboard and schedule an automatic refresh, it always returns me the same error ORA-00942, each time with a different table.

 

On the image below, you can see all tables importing data from Redlake. The ORA-00942 hapens most with the "VOLUME" and "VPZ" tables. Keep in mind that except "MARD_ECMF+PLCM", all the other tables have pretty light codes and data sizes.

 

The image below shows the SQL code I'm using for the "VOLUME" tables. I double tested all codes for all tables before and they work completely fine in the Oracle SQL and when manually refreshing data inside Power BI.

 

Any idea on how to solve this problem?

Thanks in advance!

General Comment
Need Help
Tips and Tricks

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    Hi Anonymous ,

    Based on the error description, the table or view does not exist.

    Please try to refresh the data manually and see the data if has error.

    Then, try to review the semantic model credential.

     

    Besides, make sure the Gateway is correctly configured if connecting to an on-premises database.

     

    Best Regards,

    Wisdom Wu

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • Anonymous's avatar
      Anonymous
      Not applicable
      2 years ago

      Hi Anonymous!

      Thank you for the help.

       

      I tried to refresh the data manually and there was no error. The semantic model credential is also OK, as I use it to other Dashboards and it works fine with the same configuration.

       

      With this, I think the problem is probably some configuration inside Power BI / Query. Do you know if the Data Source configuration (permissions and connections) could be the problem?

      Other than that, I have no ideia what could be the solution.