Steve Rowe wrote: ↑Wed Nov 22, 2017 9:24 am
Hi Thomas, would you mind giving some more detail on the use case for active form client memory runaway?
Sure Steve.
In PA2 Local there is a known bug in PAX client relating to active forms consuming all available client memory. If you have an active form with more than 1 dimension nested on the rowset, with zero suppression turned on, the active form will runaway and consume all available client memory until Excel fails. It consumed all 16gb on my notebook. The cube was small and sparse.
I came across this by accident doing testing between Perspectives and PAX. The same Active form in Perspectives works fine.
The bug is serverside, not client side. The root cause is when the server is returning the data call it is not doing so efficiently (zero suppression is not working as it should). The active form is fetching all records and not just those after zero suppression.
I raised a PMR and finally was advised it was a known issue. I also spoke with an IBM Worldwide Technical Executive who confirmed there are 2 fixes coming. One is a workaround for PAX (being released very shortly) which will require a change to any existing active forms. This is not really practical if you have many active forms in production! The second is a proper server-side fix which is expected sometime early next year.
We want to go "all in" with PAX/PAW, but have 3 items causing us to wait. Active form issue above, cube drill through in PAX (missing feature) and the pending security mode 6. We have deployed PA2 local (TM1 Server 11.0.002) with Perspectives. Looking forward to working with PAX and PAW when these updates are made.
Hope this helps.
Cheers
Thomas