Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
Showing results for 
Search instead for 
Did you mean: 
Former Member

In this case the EXPORT_TOO_MUCH_DATA short dump is not related to a memory problem but it is related to reaching the level of maximum amount

of data what can be stored in the memory.


ABAP program "CL_SWNC_COLLECTOR_DB==========CP"

The exception, which is assigned to class 'CX_SY_COMPRESSION_ERROR', was not caught in

procedure "SAVE_AGGREGATE" "(METHOD)", nor was it propagated by a RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

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.


Termination occurred in the ABAP program "CL_SWNC_COLLECTOR_DB==========CP" -in "SAVE_AGGREGATE".The main program was "SWNCTOTAL ".


FRom the dump >>>>> EXPORT datatable FROM rfcserver_aggtable TO DATABASE swncmoni(wo) ID monikey.



The short dump displays the profile that triggers the termination. When the short dump EXPORT_TOO_MUCH_DATA occurs in

the report CL_SWNC_COLLECTOR_DB, the value of the variable is AGGTYPE : WO

[WO] RFC client profile (refer to note: 1110822 and use the report SWNC_COLLECTOR_COMPRESSION )


Run SWNC_COLLECTOR_COMPRESSION from SE38, set check to WO, and select "Schedule Background Program" in the bottom of screen, then execute.




Technical name# Description in ST03N

ACCOUNT, MANDT, USERID# Account, client, user

PROG_NAME, RFC_CALLER# RFC program, RFC caller

TARGET, LOCAL_DEST, REMOT_DEST (*)# RFC destination, local server,

RFC destination

ENTRY_ID, FUNC_NAME (*)# Report name, transaction name or name of the background job.



Do the following: please call ST03, and navigate to:


Collector and Performance DB ->

Workload Collector ->

TOTAL Collector ->



On this screen You can exclude profile WO (RFC Client Profile) from being collected for TOTAL values. This means that You will not see

details for these statistics under TOTAL in ST03 (only for RFC Client Profile statistics of course), but You can still see the values for the

individual servers, so this can be calculated any time when needed.


Access the transaction SE16 and check for each profile which ones have more than 20000 entries in the table.

You can check all the W* profiles for this. The table name to be checked is SWNCMONI.


Use the below criteria


Area                 W* (WL, WD, WF, WJ, WM, WO, etc items)

Host / Instance      TOTAL

Period Type          M


For each profile (area) with more than 20000 entries, please run the SWNC_COLLECTOR_COMPRESSION report and activate a switch for this

profile area. After this please run the report SWNC_COLLECTOR_RECOMPRESS one time and do the counting again. The only affected table is SWNCMONI.


See also

1578639 - Shortdumps "EXPORT_TOO_MUCH_DATA" in "SWNCTOTAL"




Releated notes:


2070383 - ST03n: Reorg of workload data does not work