SAP_COLLECTOR_FOR_PERFMONITOR Job is failing

[Former Member]

Hi All,

A background Job SAP_COLLECTOR_FOR_PERFMONITOR is failing at specific time i.e, at 0,4,8,12,16 hours daily with a dump (EXPORT_TOO_MUCH_DATA) and i cannot find logs in ST03 (what are the programs it is executing) .

Job

Spool Job Doc Job CreatedB Status

Start date Start time Duration(sec.) Delay (sec.

SAP_COLLECTOR_FOR_PERFMONITOR	DDIC	Canceled	31.05.2013 16:00:26	44	26
SAP_COLLECTOR_FOR_PERFMONITOR	DDIC	Canceled	31.05.2013 00:00:26	55	26

Job Log :

Date

Time

Message text

31.05.2013 16:00:26 Job started

31.05.2013 16:00:26 Step 001 started (program RSCOLL00, variant , user ID DDIC)

31.05.2013 16:00:30 Job CCMS_COLL_DB:RSDBPREV

has been sche

31.05.2013 16:00:30 Clean_Plan:Cleanup of DB13 Plannings

31.05.2013 16:00:30 Clean_Plan:started by RSDBPREV

on server ep1vci

31.05.2013 16:00:30 Clean_Plan:Cleaning up jobs of system EP1

31.05.2013 16:00:31 Clean_Plan:finished

31.05.2013 16:01:10 Internal session terminated with a runtime error (see ST22)

31.05.2013 16:01:10 Job cancelled

ST22 : ABAP Dump

Runtime Errors	EXPORT_TOO_MUCH_DATA
Except.	CX_SY_COMPRESSION_ERROR
Date and Time	31.05.2013 16:01:10

Short text

Too much data for export.

What happened?

	Runtime error
	The current ABAP program "CL_SWNC_COLLECTOR_DB==========CP" had to be
	terminated because one
	of the statements could not be executed at runtime.

What can you do?

	Note which actions and input led to the error.
	For further help in handling the problem, contact your SAP administrator
	You can use the ABAP dump analysis transaction ST22 to view and manage
	termination messages, in particular for long term reference.

Error analysis

	An exception occurred that is explained in detail below.
	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.

How to correct the error

	1. Data must be distributed into portions of 2GB
	2. 3 possible solutions:
	- Either increase the sequence counter (field SRTF2) to include INT4
	or
	-export less data
	or
	-distribute the data across several IDs
	If the error occures in a non-modified SAP program, you may be able to
	find an interim solution in an SAP Note.
	If you have access to SAP Notes, carry out a search with the following
	keywords:
	"EXPORT_TOO_MUCH_DATA" "CX_SY_COMPRESSION_ERROR"
	"CL_SWNC_COLLECTOR_DB==========CP" or "CL_SWNC_COLLECTOR_DB==========CM00O"
	"SAVE_AGGREGATE"
	If you cannot solve the problem yourself and want to send an error
	notification to SAP, include the following information:
	1. The description of the current problem (short dump)
	To save the description, choose "System->List->Save->Local File
	(Unconverted)".
	2. Corresponding system log
	Display the system log by calling transaction SM21.
	Restrict the time interval to 10 minutes before and five minutes
	after the short dump. Then choose "System->List->Save->Local File

ST03 : Unable to find Error logs (Expert Mode--> Collector and performance DB-->Performance Monitor--> log and execution times)

04.06.2013    07:00:35    No errors

04.06.2013    06:00:34    No errors

04.06.2013    05:00:35    No errors

04.06.2013    03:00:39    No errors

04.06.2013    02:00:34    No errors

04.06.2013    01:00:34    No errors

Please help me out.

Vijay

Message was edited by: Benny Schaich-Lebek

[Former Member · Accepted solution]

Hello ,

Note 1110822 does describe how to reduce the size of aggregates for the new workload collector.

Please have a look again in 1110822 - Workload collector: Reducing the
size of aggregates. You should at first deactivate a less important part of the aggregate,then start the recompression report and check if the dump still occurs.
Accordint to the note, it only suggest how can be compressed but the choice is individual

"The only solution is to decrease the size of the aggregate by not using
single fields. We are providing the programs SWNC_COLLECTOR_COMPRESSION
and SWNC_COLLECTOR_RECOMPRESS for this."

In addition, you should also reaggregate the data that already exists
in the database for your selected profile(s).  To do this select the
option "Schedule background program" (at the bottom) when running the
report.  Then the additional report SWNC_COLLECTOR_RECOMPRESS is
scheduled to run once in the background.

For further information on these statistics you can also refer to the
following link:

http://help.sap.com/saphelp_nw70/helpdata/en/d8/f5374210549923e10000000a155106/frameset.htm
  #1362295 - SWNC_COLLECTOR_RECOMPRESS: No compression, short runtime

About ST03:The workload monitor reads the workload statistics from the

workloadcollector database. Various collectors must run at regular time

intervals so that this database always contains current data.

The background job SAP_COLLECTOR_FOR_PERFMONITOR starts the program

RSCOLL00 and this program checks the TCOLL table for program which needs

to be started.

Workload collector program starting from system release 7.00 the

background job SAP_COLLECTOR_FOR_PERFMONITOR should always be scheduled

in client 000  and the #System Time Zone# which is maintained in the

transaction STZAC in client 000 should be exactly the same as the OS

time zone setting.

#12103 - Contents of the TCOLL table

#926290 - SWNCCOLL: SAP workload NW collector collects no data

#198411  - Current data and information about time zones

#481835  - Analyzing the time zone settings

RB

Tamas

[Former Member]

Hi All,

Thanks for your Replies

I am surprised to see that the issue got resolved i.e, Background job are finishing successfully. But there was no manual intervention nor there was a restart of the system.

I have observed that in ST03, we are not able to check( Expert Mode --> Workload --> Total -->) day wise Work load analysis ( when the jobs are failing), now I can check the Day wise workload Analysis.

I am still searching for any work around

Thanks and Regards

Vijay

[former_member144433]

Hi Vijay,

Can you please check if the program SWNC_COLLECTOR_COMPRESSION scheduled as background job as per note 1110822.

And also please check the note specified below.

1631033 - Normalization of background job names for statistics data

Thank You.

Regards,

Deepika

[Former Member]

Hi,

Check these notes.

713211 - Poor performance of database collector and DB02

1283931 - SAP_COLLECTOR_FOR_PERFMONITOR dump during EXPORT

Johan

[Former Member]

Dear Vijay..

Read and correct your issue with Note 713211.

The solution will be depend on your system if you are running SAP NetWeaver  BI then you can have a solution by following the NOTE 1166731.

If you want any further support let me know.

Priyan

[Former Member]

Hello Vijay,

Can you please check if "SAP Note 1283931 - SAP_COLLECTOR_FOR_PERFMONITOR dump during EXPORT" helps in resolving the issue.

Regards,

Denish

[Former Member]

Check if Note 1578639 - Shortdumps "EXPORT_TOO_MUCH_DATA" in "SWNCTOTAL" is relevant for your issue.