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