Hi Bob,

We need help to fix a bug in PMF 5.2.1 HF1.
Is quite of URGENT.

Bug :
When we trying to save a dashbboard, PMF try to HOLD 20 millions of ROWS !

We trace the bug:
When we clic "save" in the dasboard designer,
the "gadget_sample_data.fex" do a "TABLE FILE MEASURESDIM" (step : SMP01_C) and is HOLDING almost all the MEASURES TABLE !

So our user cannot build dashboard because they can save it ! And we don't want to change "gadget_sample_data.fex" because it's use in "gadget_page_shell_form.htm"


So Bob :
Why PMF is doing a TABLE FILE MEASURESDIM to save a dasboard and can we fix this Bob ?


Thx

In later PMF we did work to make this process ("magic") more efficient and run faster. It's not a change that can be quickly and safely patched into older PMF.

Can you possibly consider upgrading PMF?

thanks

Are you 100% sure about that Bob ?

Because we install 5.2.3 (without HF) in our "test laptop" and the "gadget_sample_data.fex" hasn't change. Indeed, the "look & feel" is much better, but if the internal process doesn't change, we still are in the same situation.


So if your are solid about that, we trust you.
But maybe a little discussion with your technical team just to be sure is appropriate...


Thx to be so involved.

Why would we ask you to upgrade to HF2 if we didn't think it would help you?

Here is the provenance of the work done on this particular item:

523 – Does NOT have any performance improvement on Magic runs.
523HF1 – Has some minor improvements to Magic runs (better aggregation).
523HF2 – Even further optimization was done on Magic runs.

Also Please Note: If you have 20M rows of Measure data, you should be creating Materialized Views as per the "Maintaining PMF" chapter in the PMF Installation and Configuration Guide.

You want those queries running as fast as possible, as this is a realtime app, and your RDBMS supports these. Please set those up.

Words from a friend.
thanks