Does OAC support "Lazy loading of visualizations/charts”?

Chethana Kumari-Oracle

Summary

OAC's ability to fetch data from database based on the filter applied by the user in OAC project

Content

Hello All,

I have a dataset pointing to a table in Autonomous Data Warehouse (ADW DB) and am fetching about 4.5million records from this table. I am fetching all the records from this dataset and am using it in a dataflow to perform some transformations/calculations as part of it. The resultant dataset is being used in a project dashboard in OAC. 

Issue: As huge data (4.5 million records) is being fetched from DB, the charts in OAC take longer time to load (4-5min). This is definitely a pain point for any customer, who has to wait so long, for all the charts in a canvas to load up. We do have a top level date filter in the canvas (applicable for all charts ) that would show the data for 'last one week' only and this is by default.

Ask: Is it possible using OAC to fetch only those records from DB, for which the user has chosen the top level date filter, in a canvas. This means, by default, OAC would fetch 'last one week' of data only and show it in the charts (loading time would be few seconds only). If user, selects, say, 'last one month' then OAC should fetch corresponding data from DB and show it in the charts (loading time would increase) and so on. We are talking about, lazy loading of data from DB based on users' date filter selection in OAC. Is this feasible using OAC?

Please let me know!

Thanks in advance,

Chethana

FPonte

Hi Chethana.

You may find some ideas on the following video.

ADW to OAC - Avoiding query challenges with large datasets - https://www.youtube.com/watch?v=nvtsCvC0Eno

Not sure this one below applies in this case but can be helpful.

Oracle DV - Increasing Config Limit on OAC Datasets Cache - https://www.youtube.com/watch?v=mmj5toEn250

Some questions:

1) Is the dashboard going to a level of detail that you can't aggregate the data and reduce the dataset?

2) What is the use case (don't need to go in details)? Users will drown on that amount of information, wouldn't? Can you consider saving the output of the DataSet into a Reporting table (if already doing that ok, back to question 1)?

3) Are the dataset using Live or Cache data?

If anyone else has other ideas it will be good to hear.

Cheers

Fernando

 

Chethana Kumari-Oracle

Thanks a tonne Fernando, for your response.

To answer your questions

1) Is the dashboard going to a level of detail that you can't aggregate the data and reduce the dataset? Yes

2) What is the use case (don't need to go in details)? Users will drown on that amount of information, wouldn't? Can you consider saving the output of the DataSet into a Reporting table (if already doing that ok, back to question 1)? This is already being done

3) Are the dataset using Live or Cache data? It is using Cache data

1. Currently, I've initiated the process to increase the config limit
2. Also trying out to build the initial dataset (from ADW) using a SQL query, so that, I could leverage Oracle Pagination..

 

It would be great to hear ideas from others too, on this front.

Thanks in advance,

Chethana