Limitations / Restrictions on Pivot table views in OBIEE

Another interview question here: Some of the limitations with solutions are listed below: 


1)  Pivot View doesn't support Write Back
2) Based on the Dim Hierarchy (Ragged) it might require to forcefully set the aggregation rule which is actually not required in Table View
3) Some limitations with the Chart Pivot Results Vs Chart View
4) View Display Error - Governor limit exceeded in cube generation (Maximum data records exceeded). This error comes up if the pivot tries to return more number of rows then the default limit set for it.
5) Pivot views return all the rows at once.If the number of rows are huge pivot view reports are bad for performance
6) Presentation Services might be taking more time to display the results( as pivoting does in memory calculations). This will have impact if you have a significant number pivot views for the reports.If the same layout is achievable in table layout, switching from pivot view to table view would improve performance
7) There is a default internal limit which should be enough in most of the reporting scenarios. However, to increase the limit following tags can be edited in instaceconfig.xml file.


< CubeMaxRecords >50000< /CubeMaxRecords >
< CubeMaxPopulatedCells >150000< /CubeMaxPopulatedCells >


Until Next Post... :)