Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OAC Direct Connection to On-Prem Essbase - Slow Workbook Initialization

Accepted answer
51
Views
7
Comments

We have created data visualization reports in OAC using On-Prem Essbase as a source. When a user first goes in and opens up a workbook it takes 2-3 minutes for the workbook to open. It sits on the fun fact page and spin until everything is loaded. After Metadata is loaded and queries are sent to essbase cube and returned the workbooks work fairly well. We have some ideas on why this may be happening but curious if anyone has had a similar issue.

Tagged:

Answers

  • Conor Murnane
    Conor Murnane Rank 5 - Community Champion

    Thanks Mostafa - We have reviewed these and have implemented best practices. Although we are not using an RPD just a direct connection.

  • Mostafa Morsy-Oracle
    Mostafa Morsy-Oracle Rank 6 - Analytics Lead
    edited Sep 18, 2024 9:30PM

    @Conor Murnane

    if you are using filters make sure you disable filters when workbook loads because that will execute queries during the workbook load

  • Conor Murnane
    Conor Murnane Rank 5 - Community Champion

    @Mostafa Morsy-Oracle Is there any way to pre load/automate the internal rpd/cache that loads when you open a workbook with a direct connection?

  • Have you tired creating RPD based connection and testing this instead of direct connection? This will eliminate the internal rpd that gets created based on XSA for direct connection and might have better load times IF the slowness is caused due to the loadmetadata.

  • Conor Murnane
    Conor Murnane Rank 5 - Community Champion

    @GayathriAnand-Oracle - That is our next step. We were hoping there was some type of work around since we put in a lot of effort on our initial dashboard building with the direct connection.

  • GayathriAnand-Oracle
    edited Sep 27, 2024 2:14PM

    Understand but I dont think there is any workaround to how the product internally handles xsa source based on essbase. Support for Essbase as a source for Semantic Model is on the roadmap, so in future you can do this via semantic model instead of admintool to make it a bit easier.

    I see you already have a Service Request for this issue with support, so it would be good to work via the SR.