Hi All,
When we run the run the report in Bex Analyzer and drill down the report at granular level that is at Material get the error mentioned below:
Error reading the data of Infoprovider Z..
Amount of data being to be read from BIA server is too large
The following error 6952 occured in BIA server.
Error executing Physical plan: Attr engine not enough memory.
We are currently We are currently on BIA 7.00 Revision pack 54.
I have gone through the SAP note 1018798 and 1002839, and I am aware that whenever the number of crosses the limit of max_cells_one_index.
We modified the max_cells_one_index setting from default 40 million to 50 Million last year January. We are aware that the TrexRfcServer, the
RFC connection or the application server can stop working if the result set does not fit into the memory of the service. Business is nervous about increasing the limit as it might result to Outages. We are getting this error as the resultant is exceeding 53 million cells.
1)What is the percentage of risk of an outage associated with the setting change from 50 Million to 60 million. I am aware that it not
easy to substantiate the risk, I would like to know whether it is low,medium or high risk. I Know that we can increase to higher limits but
that would involve huge amount of risk. Is 40 or 50 Million cell data transfer using RFC the limitation of the BIA tool. In our company we
are using complex queries and reporting huge number of KF’s and theparticular report which business is trying to refresh is feeding data to all the business models. So changing the report wouldn’t be anviable option for the business. How are other companies using BIA
handling data transfer more than 50 Million.
Is it fair to say that the 50 Mil cells is the limitation of the BIA tool as it not able to handle large amount of data.,gone through the
note 1018798, as you are aware that we being from IT expected to give solutions. What Solutions SAP suggesting to clients who are handling
huge amount of data.
3) )Can any one please elaborate whether the planned changes mentioned below will have any impact on the amount of data being transferred through
RFC in BIA. Will this help reducing the 6952 error to certain extent.
a)Turning on the FEMS compression.
b)Using dynamic max_cells_one_index. We are currently at revision 54,
do you reckon upgrading to service patch level 63 will help resolve the
issue current 6952 error.
c)Can increasing the memory that is adding another blade, will that
help sorting out the 6952 error.
d)To increase the package chunk size read to the recommended value of
2000000.
e)Using ICM instead of RFC as communication method for query execution.
Shall we change the communication method to ICM instead of RFC.
Is the Max Cell one index setting limitation for the BIA tools for companies handling large amount of data and complex queries
Please let me know your thoughts on this. I have gone through many SAP notes in BWA, any other solution would be much appreciated
Thanks
Krish.