Ragged Dimension Hierarchies causing PA2.0 crashes
Posted: Thu Aug 30, 2018 9:03 pm
We are having a major issue with PA2.0 crashing when opening a cube through Architect a second time if one of the dimensions contains a ragged or unbalanced hierarchy. It will also crash if using the cube viewer and opening the subset editor on said dimension. This behavior is consistent and repeatable.
This behavior does not happen in PAW, but performance is AWFUL. For example, if one closes a consolidation that has been drilled down on and the consolidation has five children, it literally takes 45 seconds+ for the drill down to close. ???! This is occurring on the same dimension.
The cube is small (8MB) and has 9 dimensions. The two largest dimensions have approximately 21K and 12K members. But that is immaterial because as long as we create a dimension with the structure described below and put it in a cube with three+ dimensions (have not seen this in two dimension cubes), whether the cube is populated or empty, the server crashes.
Now for some more fun. Here is the basic structure for the dimension causing the problems:
This crashes. Now here is the M. Night Shyamalan twist that does not make a lot of sense: switch the position of the two consolidations, Unregistered and All Accounts to where All Accounts comes first and the crashing stops.
So the questions are has anyone else experienced this? Is this a known "feature?" If so, is there documentation or a workaround, a set of rules for dimension building perhaps?
Thanks!
This behavior does not happen in PAW, but performance is AWFUL. For example, if one closes a consolidation that has been drilled down on and the consolidation has five children, it literally takes 45 seconds+ for the drill down to close. ???! This is occurring on the same dimension.
The cube is small (8MB) and has 9 dimensions. The two largest dimensions have approximately 21K and 12K members. But that is immaterial because as long as we create a dimension with the structure described below and put it in a cube with three+ dimensions (have not seen this in two dimension cubes), whether the cube is populated or empty, the server crashes.
Now for some more fun. Here is the basic structure for the dimension causing the problems:
Code: Select all
+Unregistered
-215-040-001
-215-040-002
+All Accounts
+Liabilities
+Payroll
-215-040-003
+Revenue
...
+Cost
...
+Expenses
...
So the questions are has anyone else experienced this? Is this a known "feature?" If so, is there documentation or a workaround, a set of rules for dimension building perhaps?
Thanks!