HI DP,
Here are some things to keep in mind when u have problems with DB Runtime, Frontend runtime or OLAP runtime..
A)High Database Runtime
Check if an aggregate is suitable (use All data to get values "selected records to transferred records", a high number here would be an indicator for query performance improvement using an aggregate)
Check if database statistics are update to data for the Cube/Aggregate, use TX RSRV output (use database check
for statistics and indexes)
Check if the read mode of the query is unfavourable - Recommended (H)
B)High OLAP Runtime
Check if a high number of Cells transferred to the OLAP (use "All data" to get value "No. of Cells")
a) Use RSRT technical Information to check if any extra OLAP-processing is necessary (Stock Query, Exception Aggregation, Calc. before Aggregation, Virtual Char. Key Figures, Attributes in Calculated Key Figs, Time-dependent Currency Translation) together with a high number of records transferred.
b) Check if a user exit Usage is involved in the OLAP runtime?
c) Check if large hierarchies are used and the entry hierarchy level is as deep as possible. This limits the levels of the hierarchy that must be processed.
Use SE16 on the inclusion tables and use the List of Value feature on the column successor and predecessor to see which entry level of the hierarchy is used.
C)High Frontend Runtime
1)Check if a very high number of cells and formattings are transferred to the Frontend ( use "All data" to get value "No. of Cells") which cause high network and frontend (processing) runtime.
2) Check if frontend PC are within the recommendation (RAM, CPU Mhz)
3) Check if the bandwidth for WAN connection is sufficient.
hopr this helps,
regards,
kishore karnati
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.