Bex Report with and without BIA . . Fails with a dump EXPORT_TOO_MUCH_DATA

Question

Hi Folks,
We have a report thats has been running well in production for more about 18 months. This month it did not complete execution.
We did implement BIA couple of 4 months back and the run times have drastically reduced after the BIA. Now this query execution results in a Dump with and without BIA.  FYI the underlying cube has 195,876,020 records only.
Name of Runtime error: EXPORT_TOO_MUCH_DATA
Short text:     Too much data for export.
What happened?     Runtime error
    The current ABAP program "CL_RSR_CACHE_DO_SPID==========CP" had to be
     terminated because one     of the statements could not be executed at runtime.
Error analysis: The dataset stored under an EXPORT/IMPORT ID is restricted
by
1. The maximum possible size of 2 GB
2. The length of a data record and the capacity of the sequence counter. This error occurs only if the capacity of the
sequence counter does not go beyond 255.
Source Code Extract:
    1 METHOD if_rsr_cache_data_object~get_xstring.
    2
    3   FIELD-SYMBOLS:
    4     <l_xstring>            TYPE xstring,
    5     <l_sp>                 TYPE ANY,
    6     <l_spinfo>             TYPE ANY.
    7
    8   CREATE DATA r_r_xstring.
    9   ASSIGN r_r_xstring->* TO <l_xstring>.
   10   ASSIGN n_s_spid-r_sp->*     TO <l_sp>.
   11   ASSIGN n_s_spid-r_spinfo->* TO <l_spinfo>.
   12
   13 *... Sp has to be the first component
>>>>>   EXPORT sp = <l_sp> spinfo = <l_spinfo>
   15          TO DATA BUFFER <l_xstring> COMPRESSION ON.
   16
   17 ENDMETHOD.
Referred to the below note 0001232573
which says to have 'RSRCACHE_ITAB_COMPR'  parameter using report SAP_RSADMIN_MAINTAIN
Note say the below (It might be a little tricky, to find an appropriate value for 'RSRCACHE_ITAB_COMPR' as it heavily depends on the query-specific data structures that are stored in the cache. The general recommendation would be to start with a value of about 5000. Test this with a query, that dumped previously. In case the dump persists reoccurs, reduce the value of the parameter significantly. Otherwise, if no dump occurs but you face noticeably longer runtimes, increase the parameter.)
We are trying not able to get to the right parameter value. (changed it from 5000, 4000, 3000, & 1000) without much  help.  Did any of you had to change this parameter. How low or High can this parameter be changed?
We would like to understand if changing any other parameters would help in RSADMIN table would help?
Any thoughts from the experts would be appreciated
Thanks,
FHF

Answer 1

Hi,
Are you running the report for all the selections(all the data )?
execute the report with data selection and check?
Is the data in the Ic - compressed?
Regards
KP