SAP_COLLECTOR_FOR_PERFMONITOR error

I have a system DXD that is getting this error on SAP_COLLECTOR_FOR_PERFMONITOR:
ABAP/4 processor: EXPORT_TOO_MUCH_DATA
Has anyone had this problem?
ANy advice would be appreciated.

Its a background job, mostly used for data collection for ABAP statistics records (DSR). It is by default scheduled for an hourly run. Check these two parameters stat/file (points to the instance specific data dir) and the parameter stat/maxfiles (max number of files before the first one is overwritten). See if the data directory has enough space or something.
Do you have any more info on the actual error?
Try checking your CCMS for alerts. Use transaction STAD or ST03N for further information on this report.

Similar Messages

SAP_COLLECTOR_FOR_PERFMONITOR getting cancelled

Dear All,
The job SAP_COLLECTOR_FOR_PERFMONITOR is getting cancelled daily at 7.00 AM. It is scheduled to run hourly. All other times it finishes succesfully. But only 1 time at 7 it gets cancelled. The job log is :-
Date       Time     Message text                                                Message class Message no. Message type
15.11.2007 07:00:17 Job started                                                      00           516          S
15.11.2007 07:00:17 Step 001 started (program RSCOLL00, variant , user ID DDIC)      00           550          S
15.11.2007 07:00:38 ABAP/4 processor: CONNE_IMPORT_WRONG_COMP_TYPE                   00           671          A
15.11.2007 07:00:38 Job cancelled                                                    00           518          A
the Dump is pasted below:-
                                                                                ShrtText
Error when attempting to IMPORT object "HIST2".
What happened?
Error in ABAP application program.
The current ABAP program "RSORAT4M" had to be terminated because one of the
    statements could not be executed.
This is probably due to an error in the ABAP program.
When attempting to import data, it was discovered that the data
    type of the stored data was not the same as that specified in the
    program.
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR',
     was neither
    caught nor passed along using a RAISING clause, in the procedure
     "AKT_DAY_HIST2" "(FORM)"
Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    When importing the object "HIST2", the component no. 8 in the
    dataset has a different type from the corresponding component
    of the target object in the program "RSORAT4M".
The data type is "I" in the dataset, but "P" in the program.
How to correct the error
    Try to find out why the type of the object is different.
    There are several possible reasons:
--- In the ABAP Dictionary, the type of the imported
field has changed. Make sure that the type of the imported
field matches the length of the Dictionary field.
|   If the data could not be restored from another source, this data
    |   must be read with the "old" structure, then converted and exported
    |   back with the new structure, so that future IMPORTs always work
    |   with the new structure.
    |
--- A new program version is active, and it no longer matches the
        dataset. Try to solve the error by generating the program "RSORAT4M" again
        as follows:
        In the SAP System, choose the transaction SE38. Enter the program
        name "RSORAT4M". Then choose the "Activate" function.
===
It is saying
The data type is "I" in the dataset, but "P" in the program.
But it runs 23 times correctly except 1 time.
Can Anyone help me in this please
Thanks
Tajinder

Hi,
Can u please suggest me what will be the monikey here. below is the dump for that
154   DATA: FLAG VALUE ' '.
155   LOOP AT HIST2.
156     IF HIST2-DATE = DATE. DELETE HIST2. FLAG = '*'. ENDIF.
157   ENDLOOP.
158   IF FLAG NE SPACE. SUBTRACT 1 FROM LOGBUCH-ANZDAYS. ENDIF.
159 ENDFORM.
160
161 FORM AKT_DAY_HIST2.                    " Aktualisiere Tage-Historie
162   PERFORM PREPARE_MONIKEY USING 36.    " Lese Historie
>>>>   IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.
164   IF SY-SUBRC <> 0.
165     REFRESH HIST2. CLEAR HIST2.
166     PERFORM LOGBUCH_INIT USING 1.
167     PERFORM TRANSFORM_ALL_HISTORIES.   " Strukturaenderung fuer Dynami
168     PERFORM PREPARE_MONIKEY USING 36.    " Lese Historie
169     IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.
170   ENDIF.
171   READ TABLE HIST2 INDEX 1.
172   IF SY-SUBRC <> 0.
173     REFRESH HIST2. CLEAR HIST2.
174     PERFORM LOGBUCH_INIT USING 1.
175   ENDIF.
176   PERFORM DELETE_AKT_DAY_HIST2.        " Delete aktuellen Tag
177   LOOP AT HIST2_DAY.                   " Füge neue Analyse an
178     MOVE-CORRESPONDING HIST2_DAY TO HIST2.
179     APPEND HIST2.
180   ENDLOOP.
181   ADD 1 TO LOGBUCH-ANZDAYS.
182   MOVE DATE TO LOGBUCH-LASTDAY.
Thanks
tajinder

SAP_COLLECTOR_FOR_PERFMONITOR background job cancelled in SM37

Dear all ,
One of the scheduled background job has been cancelled .
Kindly check the below loga and Background job details .
Job name        SAP_COLLECTOR_FOR_PERFMONITOR
Job class       C
Status          Canceled
(ABAP Program
Name           RSCOLL00
Variant
Language       EN)
Job Log :
30.05.2010 06:20:32 Job started
30.05.2010 06:20:32 Step 001 started (program RSCOLL00, variant , user ID DDIC)
30.05.2010 06:20:37 Clean_Plan:Cleanup of DB13 Plannings
30.05.2010 06:20:37 Clean_Plan:started by RSDBPREV                       on server PRDCIXI
30.05.2010 06:20:38 Clean_Plan:Cleaning up jobs of system IRP
30.05.2010 06:20:39 Clean_Plan:finished
30.05.2010 06:20:43 ABAP/4 processor: DBIF_RTAB_SQL_ERROR
30.05.2010 06:20:43 Job cancelled
Kindly suggest

Dear all ,
Kindly check the ST22 error logs .
Short text SQL error occurred in the database when accessing a table. What happened? The database system detected a deadlock and avoided it by rolling back your transaction. What can you do? If possible (and necessary), repeat the last database transaction in the hope that locking the object will not result in another deadlock. 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 The database system recognized that your last operation on the database would have led to a deadlock. Therefore, your transaction was rolled back to avoid this. ORACLE always terminates any transaction that would result in deadlock. The other transactions involved in this potential deadlock are not affected by the termination. Last error logged in SAP kernel Component............ "SAP-Gateway" Place................ "SAP-Gateway on host PRDCIXI / sapgw01" Version.............. 2 Error code........... 679 Error text........... "program prodoradb.sapccmsr.99 not registered" Description.......... "TP prodoradb.sapccmsr.99 not registered" How to correct the error Database error text........: "ORA-00060: deadlock detected while waiting for resource" Internal call code.........: "[RTAB/UPD /MONI ]" Please check the entries in the system log (Transaction SM21). 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: "DBIF_RTAB_SQL_ERROR" " " "RSHOST3M" or "RSHOST3M" "PUT_LOGBOOK" 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 (Unconverted)". 3. If the problem occurs in a problem of your own or a modified SAP System call.......... " " Module............... "gwr3cpic.c" Line................. 1835 The error reported by the operating system is: Error number..... " " Error text....... " "
for detail log.
System environment
SAP-Release 700
Application server... "PRDCIXI"
Network address...... "10.54.145.32"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "000184CAD400"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 8
Shortdump setting.... "full"
Database server... "PRODORADB"
Database type..... "ORACLE"
Database name..... "IRP"
Database user ID.. "SAPSR3"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 7 2010 21:00:49"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 246
Patch text.. " "
Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 1217248
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 1050520
MM Free. 146024
and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4BFF227871E00187E10080000A369120"
In the source code you have the termination point in line 521
of the (Include) program "RSHOST3M".
The program "RSHOST3M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 02033500
In the source code you have the termination point in line 521
of the (Include) program "RSHOST3M".
The program "RSHOST3M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 02033500
Program............. "RSHOST3M"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
rmation on where terminated
Termination occurred in the ABAP program "RSHOST3M" - in "PUT_LOGBOOK".
The main program was "RSHOST3M ".

SAPSQL_ARRAY_INSERT_DUPREC - ABAP runtime error

Dear Experts,
I am getting a abap dump.
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Exception CX_SY_OPEN_SQL_DB
Error analysis |
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", 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: If you use an ABAP/4 Open SQL array insert to insert a record in the database and that record already exists with the same key, this results in a termination.
Information on where terminated
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in
"BAL_DB_INTERNAL_NO_UPDATE_TASK". The main program was "SWNCCOLL ".
In the source code you have the termination point in line 64
of the (Include) program "LSBAL_DB_INTERNALU02".
The program "SAPLSBAL_DB_INTERNAL" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "SAPADMIN"
Job Number..... 16160100
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", but it was neither
handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPLSBAL_DB_INTERNAL "; its source code begins in
line
1 of the (Include program "LSBAL_DB_INTERNALU02 ".
Please give me your suggestions to sort out this problem
Thanks in advance
Venkat

Check note 196113 it contains the solution to your problem.
Most of the time this issue is due to a mismatch between the last assigned log number in table BALHDR and the one in the number range object.

Development server performance is slow [ Review the error and help me,]

Runtime Errors         CONNE_IMPORT_WRONG_COMP_TYPE
Exception              CX_SY_IMPORT_MISMATCH_ERROR
Date and Time          24.12.2007 07:02:58
Short text
Error when attempting to IMPORT object "HIST2".
What happened?
Error in the ABAP Application Program
The current ABAP program "RSORAT4M" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in
procedure "AKT_DAY_HIST2" "(FORM)", 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:
When importing the object "HIST2", the component no. 8 in the
dataset has a different type from the corresponding component
of the target object in the program "RSORAT4M".
The data type is "I" in the dataset, but "P" in the program.
How to correct the error
Try to find out why the type of the object should be different.
There are various possible options:
1. The type of the imported field has changed in the Data Dictionary.
Make sure that the type of the imported field matches the type
of the field in the Data Dictionary.
If the data cannot be restored from another source, the data must be
read by the 'old' structure, converted und again eported with the new
structure, so that future IMPORTs will always function with the new
structure.
2. A new program version is active, which no longer fits the dataset.
Try to solve the error generating the program "RSORAT4M" again. This
works as follows: Select transaction SE38 in the SAP system. Enter
the program name "RSORAT4M". Then activate the function 'Generate'.
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:
"CONNE_IMPORT_WRONG_COMP_TYPE" "CX_SY_IMPORT_MISMATCH_ERROR"
"RSORAT4M" or "RSORAT4M"
"AKT_DAY_HIST2"
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
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"AKT_DAY_HIST2" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "UBSDEV"
Network address...... "10.22.6.68"
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4v"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 11
Shortdump setting.... "full"
Database server... "UBSDEV"
Database type..... "ORACLE"
Database name..... "UBD"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 21:14:52"
create on........ "SunOS 5.9 Generic_117171-13 sun4u"
Database version. "OCI_101 "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "SunOS 5.9, SunOS 5.10"
Memory consumption
Roll.... 1117168
EM...... 0
Heap.... 0
Page.... 93315072
MM Used. 638120
MM Free. 458608
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "RSORAT4M"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAT4M" - in "AKT_DAY_HIST2".
The main program was "RSORAT4M ".
In the source code you have the termination point in line 163
of the (Include) program "RSORAT4M".
The program "RSORAT4M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 06004902
The termination is caused because exception "CX_SY_IMPORT_MISMATCH_ERROR"
occurred in
procedure "AKT_DAY_HIST2" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "RSORAT4M "; its source code begins in line
161 of the (Include program "RSORAT4M ".
Source Code Extract
Line
SourceCde
133
134
REFRESH HIST2_DAY.
135
CLEAR HIST2_DAY.
136
137
HIST2_DAY-SIZE    = TD110-TSSI.
138
HIST2_DAY-FREE    = TD110-TSFR.
139
HIST2_DAY-USED    = 100 - TD110-TSFRP.
140
HIST2_DAY-TABLES = TD110-TANO.
141
HIST2_DAY-INDICES = TD110-TINO.
142
HIST2_DAY-TSIZE   = TD110-TASI.
143
HIST2_DAY-ISIZE   = TD110-TISI.
144
145
PERFORM new_analysis_db.
146
HIST2_DAY-DATE = DATE.
147
HIST2_DAY-TIME = TIME.
148
APPEND HIST2_DAY.
149
ENDFORM.
150
Beschaffung neuer Analyse-Daten für Historien <<<
151
152
Historie, Tage >>>
153
FORM DELETE_AKT_DAY_HIST2.
154
DATA: FLAG VALUE ' '.
155
LOOP AT HIST2.
156
IF HIST2-DATE = DATE. DELETE HIST2. FLAG = '*'. ENDIF.
157
ENDLOOP.
158
IF FLAG NE SPACE. SUBTRACT 1 FROM LOGBUCH-ANZDAYS. ENDIF.
159
ENDFORM.
160
161
FORM AKT_DAY_HIST2.                    " Aktualisiere Tage-Historie
162
PERFORM PREPARE_MONIKEY USING 36.    " Lese Historie
>>>>>
IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.
164
IF SY-SUBRC <> 0.
165
REFRESH HIST2. CLEAR HIST2.
166
PERFORM LOGBUCH_INIT USING 1.
167
PERFORM TRANSFORM_ALL_HISTORIES.   " Strukturaenderung fuer Dynami
168
PERFORM PREPARE_MONIKEY USING 36.    " Lese Historie
169
IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.
170
ENDIF.
171
READ TABLE HIST2 INDEX 1.
172
IF SY-SUBRC <> 0.
173
REFRESH HIST2. CLEAR HIST2.
174
PERFORM LOGBUCH_INIT USING 1.
175
ENDIF.
176
PERFORM DELETE_AKT_DAY_HIST2.        " Delete aktuellen Tag
177
LOOP AT HIST2_DAY.                   " Füge neue Analyse an
178
MOVE-CORRESPONDING HIST2_DAY TO HIST2.
179
APPEND HIST2.
180
ENDLOOP.
181
ADD 1 TO LOGBUCH-ANZDAYS.
182
MOVE DATE TO LOGBUCH-LASTDAY.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20071224
SY-UZEIT
070256
SY-XPROG
SAPMSSY0
SY-XFORM
NEW-LINE
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
2 FORM         RSORAT4M                            RSORAT4M                              163
AKT_DAY_HIST2
1 EVENT        RSORAT4M                            RSORAT4M                               73
END-OF-SELECTION
Chosen variables
Name
Val.
No.       2 Ty.          FORM
Name AKT_DAY_HIST2
SCREEN
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
MONIKEY
--UBD     days    h/2
0000000000000000000000
0000000000000000000000
2254422222667722226232
DD52400000419300008F20
MONI
DB--UBD     days    h/2 ## ##################################################################
00000000000000000000000000000F0083300C019880423CCCCBA185073210552E8C0334266086A470B60061642777
00000000000000000000000000000F1204000802DCF80B619C242588C81881810C0A70020645DC07BF1AFE070ECE1C
4422544222226677222262320022800003300001090100EE1161721CA580CAFEA65BC607333BC23214789666B6D8BC
42DD52400000419300008F20000076120120000F291C430000062325261E520B6388C203600303CA0830014245D093
MONI-CLUSTR
8912646
08
07
OBJ3
0000000000000000000000000000000
0000000000000000000000000000000
2222222222222222222222222222222
0000000000000000000000000000000
OBJ4[]
Table[initial]
HIST2[]
Table[initial]
SY-SUBRC
0
0000
0000
HIST2
00000000000000######################
000000000000000000000000000000000000
000000000000000000000000000000000000
333333333333330000000000000000000000
00000000000000000C000C000000000C000C
S2
0
0
2
0
KBYTES
0.0.0.0.0.0.0.1.
00000000
0000000C
No.       1 Ty.          EVENT
Name END-OF-SELECTION
TSN
000000000000000
000000000000000
222222222222222
000000000000000
TYP
00000000000000000
00000000000000000
22222222222222222
00000000000000000
S3
0
0
2
0
LOGBUCH-LASTDAY
20070315
00000000
00000000
33333333
20070315
DATE
20071224
00000000
00000000
33333333
20071224
SY-REPID
RSORAT4M
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545453422222222222222222222222222222222
23F2144D00000000000000000000000000000000
S5
0
0
2
0
S7
0
0
2
0
ROOT
000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000
222222222222222222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000000000000000000
SEG_TYPE
00000000000000000
00000000000000000
22222222222222222
00000000000000000
S4
0
0
2
0
Internal notes
The termination was triggered in function "CheckSimpleComponent"
of the SAP kernel, in line 1183 of the module
"//bas/700_REL/src/krn/runt/abconne.c#16".
The internal operation just processed is "IMPO".
Internal mode was started at 20071224070256.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
DoStack2 ( 0x105c65dc0, 0xffffffff7fff9900, 0x1004ffecc, 0x0, 0x20, 0x10315f010 ), at 0x1004ff
CTrcStack2 ( 0x105c65dc0, 0x0, 0x18800, 0x1031a4d20, 0x100b21370, 0x10315f010 ), at 0x1004ffa6
__1cQrabax_CStackSave6F_v_ ( 0x103385400, 0x3385400, 0x103a0e490, 0x1021a9af0, 0x100000000, 0x
ab_rabax ( 0x100000000, 0x31a4c00, 0x103a0d000, 0x3a0d000, 0x2000, 0x0 ), at 0x100b21370
__1cUCheckSimpleComponent6FkpnICONNE_RD_kpnQDESCRIPTION_CNTL_kCkL6kpknHAB_DATA_kI9D9D_i_ ( 0xf
__1cRConneCmpCheckList6FkpnICONNE_RD_kpnQDESCRIPTION_CNTL_kppnMImportOpHead_kLpknHAB_DATA_kpk9
__1cNConneCmpCheck6FkpnICONNE_RD_pknHAB_DATA_kpnQDESCRIPTION_CNTL_ppnMImportOpHead_kLkpLII_i_
__1cMimport_check6FpnICONNE_RD_ppnMImportOpHead_kpCC_i_ ( 0xffffffff7fffa9a8, 0xffffffff7fffbb
__1cLab_connread6FIpnLIMPORT_INFO_kpkHpnHAB_DATA_pFpHLp6ppv_ipFppCpLInJEXPO_MODE__i_i_ ( 0xfff
__1cLexpo_import6F_v_ ( 0x0, 0xfffffffe324a90a4, 0xfffffffe324a90ac, 0x105be9e84, 0x0, 0x105ce
__1cIab_jimpo6F_v_ ( 0x100000000, 0x5c66400, 0x1, 0x0, 0x0, 0x94 ), at 0x1009d7f64
__1cIab_extri6F_i_ ( 0x100000000, 0x5cea400, 0x230, 0x1, 0x0, 0x46 ), at 0x1006f9298
__1cJab_xevent6FpkH_i_ ( 0xfffffffe324a9fe8, 0xfffffffe324a7398, 0x2ac, 0x0, 0x4c, 0x105c6648
__1cIab_trigg6F_i_ ( 0x105bea340, 0x105c69588, 0x10093cc48, 0x20, 0x215fc00, 0x0 ), at 0x1009
ab_run ( 0x1062f8288, 0x105c69000, 0x1021b23fc, 0x0, 0x105c6647c, 0x0 ), at 0x100b9346c
dynpmcal ( 0x106305708, 0x6, 0xc, 0x1035867c8, 0x100589628, 0x1031a4d14 ), at 0x100581e1c
dynppai0 ( 0x106305708, 0x106306d14, 0x0, 0x1031a4d78, 0x0, 0x105c86004 ), at 0x10057f120
dynprctl ( 0x106305708, 0x0, 0x103199024, 0x1300, 0x1, 0x128c ), at 0x10057d764
dynpen00 ( 0x0, 0x106305708, 0x106305708, 0x0, 0x106305708, 0x102a5fc00 ), at 0x100579c64
TskhLoop ( 0x0, 0xb, 0xffffffff6f408530, 0x0, 0x100288854, 0x0 ), at 0x10028f248
ThStart ( 0x1, 0x280800, 0x100280800, 0x100000000, 0x1, 0x10319a0c0 ), at 0x1002815f4
DpMain ( 0x37e6800, 0x3197400, 0x100000000, 0x1, 0x0, 0x0 ), at 0x1001b2e8c
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAT4M
0
21.03.2007
19:50:50
98304
E
1
Prg
SAPMSSY0
1
21.03.2007
19:51:33
90112
E
2
Prg
SAPMSSYD
1
21.03.2007
19:51:17
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
11264
E
4
Prg
RSDBRUNT
0
21.03.2007
19:50:43
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
21.03.2007
19:28:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
12
Prg
SAPLSABE
12
09.09.2004
14:18:36
13312
E
13
Prg
SAPLSECU
13
27.03.2007
17:41:57
87040
E
14
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
15
Prg
SAPLSTUP
15
08.03.2005
19:04:31
74752
E
16
Prg
SAPLCNDP
16
21.03.2007
16:17:37
193536
E
17
Prg
SAPLSCNT
17
18.02.2005
14:16:06
30720
E
18
Prg
SAPSHDTV
17
05.01.2005
16:26:16
36864
E
19
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
20
Prg
SAPLOLEA
20
05.07.2005
13:10:18
96256
E
21
Prg
SAPLSGUI
21
21.03.2007
19:51:33
82944
E
22
Prg
SAPLSTTM
22
05.07.2005
13:10:18
69632
E
23
Prg
SAPLSBDC
23
05.07.2005
13:10:18
44032
E
24
Prg
SAPLSFES
24
27.03.2007
17:42:13
257024
E
25
Prg
SAPLTHFB
25
27.03.2007
17:38:01
392192
E
26
Typ
WPINFO
0
26.02.1999
14:49:01
6144
27
Prg
SAPLURFC
27
15.06.2005
11:39:01
22528
E
28
Prg
SAPLSPLUGIN
28
09.09.2004
14:18:36
8192
E
29
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
30
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
31
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
32
Typ
MONI
0
31.03.2004
16:41:21
5120
33
Prg
CX_SY_IMPORT_MISMATCH_ERROR===CP
33
05.07.2005
13:10:16
10240
E
34
Typ
SCX_SRCPOS
0
18.05.2004
14:07:11
2048
35
Prg
CX_DYNAMIC_CHECK==============CP
35
05.07.2005
13:10:16
10240
E
36
Prg
CX_ROOT=======================CP
36
05.07.2005
13:10:16
11264
E
37
Prg
CX_NO_CHECK===================CP
37
05.07.2005
13:10:16
10240
E
38
Prg
CX_SY_NO_HANDLER==============CP
38
05.07.2005
13:10:16
10240
E
39
Typ
SYST
0
09.09.2004
14:18:12
31744
Directory of Application Tables
Name                                     Date       Time       Lngth
Val.
Program RSORAT4M
SYST                                     09.09.2004 14:18:12   00004612
00000x00010000000000000000000
MONI                                       . .       : :     00002944
DB--UBD     days    h/2 00 x0087######00#0####
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
1841
BRAX
01
FFF2
RSORAT4M
157
1842
comp
00
0242
C000
00A2
RSORAT4M
158
1844
BRAF
05
0005
RSORAT4M
158
1845
ccqi
4C
0000
0000
2610
0001
0000
0000
2610
RSORAT4M
158
1849
ENDF
00
0000
RSORAT4M
159
1850
00
0000
RSORAT4M
159
1851
PERP
00
0000
RSORAT4M
161
1852
perf
00
000C
RSORAT4M
162
1853
PERP
80
0001
RSORAT4M
162
1854
PERP
80
00CC
RSORAT4M
162
1855
IMPO
00
0001
007B
007A
010C
0000
00EA
0000
RSORAT4M
163
1859
PAR2
06
0000
00EB
009B
RSORAT4M
163
>>>>>
IMPO
07
0000
0000
0000
0000
0000
0000
0000
RSORAT4M
163
1865
cmpr
00
00CA
00F8
0000
RSORAT4M
164
1867
BRAF
05
0016
RSORAT4M
164
1868
REFR
00
0000
009B
0000
RSORAT4M
165
1870
CLEA
00
009C
RSORAT4M
165
1871
perf
00
0035
RSORAT4M
166
1872
PERP
80
0001
RSORAT4M
166
1873
PERP
80
0006
RSORAT4M
166

Hi,
Please apply the following correction manually.
1. Go to transaction ST03N
2. Change user from 'Administrator' to 'Expert Mode'.
3. Go to Collector and performance analysis -> Performance database
   -> Monitoring database -> Contents
4. Search where further info contains the string "h/2"
like the following monikeys:
- 'days h/2'
- 'weeks h/2'
- 'months h/2'
5. Double click on each, so that they become red and show ** delete
6. Finally SAVE
This will remove the corresponding database related history up to the deletion date. It will accumulate anew afterwards.
How can I identify the monikey that has to be deleted?
When you load the text of the dump and then jump off to the break point of the debugger you may find the error break point look like:
"IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY".
To find the right monikey entry causing the dump you can search for the word 'MONIKEY' within the text of the dump. This can be 'days h/3' or
'tabgrowth 2'...
You can then go back to the procedure above and search where further info contains the monikey that you found in the text of the dump.
997535     DB02: Problems with History Data.
Award points if helpful.
Thanks,
Tanuj

Errors in weekly data collection

Hello,
I am running ecc6 sp 15 on AIX 5.3 and oracle 10.2.0.2
when i goto transaction st03 -> workload -> <instance_name> ->week dir - when i try to open one of the logs i get the following error message
on the botton of the screen - "unknown period type (W).
when i try to watch a daily log it is displayed without a problem.
moreover when i push on the change user mode button (expert mode or
service engineer options) and move to service engineer, i try to
calculate both in background and in dialog i get the same error
message - unknown period type (W).when i press again on the user mode
button (expert mode or service engineer options) i get a dump -
DYNPRO_NOT_FOUND - dynpro does not exist, the current abap progrem
SAPWL_ST03N HAD TO BE TERMINATED.
the saposcol is running, the background job -
SAP_COLLECTOR_FOR_PERFMONITOR is running and working (daily data is
collected and displayed correctly)
each week i get an early watch alert report but with errors in data
collection section with the following exception -
SAPWL_WORKLOAD_GET_SUMMERY_I_W - NO_DATA_FOUND.
please advise asap
Regards,
Moshe

done - had to import note 1014116

Runtime error in DB02 IMPORT_OBJECT_DESTROYED

Hi Guys,
When i call up Tx : DB02 and choose Space Statistics under Tablepace Tab, runtime error is occurring " IMPORT_OBJECT_DESTROYED".
The short dump mentions as :
Error analysis
Unable to import the dataset because it has an unexpected
format. It was
destroyed as a result of direct manipulation of the
IMPORT/EXPORT data by other means (for instance, explicit deletion of parts of the dataset using SQL instead of DELETE FROM DATABASE).
In this case, the records in the dataset do not appear in the
expected order, which is 0,1,2,3...
(sequence counter in field SRTF2).
The next record expected here is number 0,
but number 1 appears.
Information where termination occurred:
The termination occurred in the ABAP/4 program "RSORAT2M " in
"IMPORT_FROM_MONI_SAFE".
The main program was "RSORAT2M ".
The termination occurred in line 908
of the source code of program "RSORAT2M " (when calling the editor 9080).
The program "RSORAT2M " was started as a background job.
Any help is appreciated.
Naren

Hi,
Check the note [393658|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=393658]
For me it seems that the historical data is not gathered. If so, please schedule the job SAP_COLLECTOR_FOR_PERFMONITOR for each hour .
Regards,
Srihari

SAP_COLLECTOR_FOR_PERFMONITOR - canceled only at specific time

Hi All,
Job SAP_COLLECTOR_FOR_PERFMONITOR is scheduled hourly on ECC system.
All jobs are finished successfully in a day but only at specific time its getting failed.
Recently we have upgrade the support package of SAP_BASIS & SAP_ABP from 05 to 13. After then we are getting this error message.
In ST22 we getting ABAP dump for job:-
Runtime Errors         LOAD_PROGRAM_NOT_FOUND
Date and Time          27.08.2014 12:19:42
Short text
     Program "RSORA811" not found.
What happened?
     There are several possibilities:
     Error in the ABAP Application Program
     The current ABAP program "RSCOLL00" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     or
     Error in the SAP kernel.
     The current ABAP "RSCOLL00" program had to be terminated because the
     ABAP processor detected an internal system error.
Error analysis
    On account of a branch in the program
    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
    or a transaction call, another ABAP/4 program
    is to be loaded, namely "RSORA811".
    However, program "RSORA811" does not exist in the library.
    Possible reasons:
    a) Wrong program name specified in an external PERFORM or
       SUBMIT or, when defining a new transaction, a new
       dialog module or a new function module.
    b) Transport error
How to correct the error
    Check the last transports to the R/3 System.
    Are changes currently being made to the program "RSCOLL00"?
    Has the correct program been entered in table TSTC for Transaction " "?
    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:
    "LOAD_PROGRAM_NOT_FOUND" " "
    "RSCOLL00" or "RSCOLL00"
    "LOOP_AT_SYSTEMS_AND_REPORTS"
System Details :-
SAP Version - SAP ECC 6.0 EHP 4
Oracle DB - 10.2.0.5.0
OS- HP UNIX 11.31
Kernel Release 721 - patch level 201
Please suggest for solution
Regards,
Ajay Asawa

Hi Ajay,
If any job is failing at a particular time, you should look for other changes happening in you system.
Perhaps, any other job running causing problems.
Alos, refer: 1841778 - LOAD_PROGRAM_NOT_FOUND in RSCOLL00
Regards,
Divyanshu

MS Sql error in production server: DBIF_REPO_SQL_ERROR

Hi experts,
I am getting this error in my production server.
Environment : OS - Windows 2008, Database: MSsql 2005 sp2, ECC6.0
when the job SAP_COLLECTOR_FOR_PERFMONITOR executes the dump occurs with the following error.
DBIF_REPO_SQL_ERROR, SQL error 0 occurred when accessing program "CX_SY_OPEN_SQL_DB=============CP "
and also i am not able to open db13 with ends up with abap dump.
In the sql server log i found this error too.
Database ID 5, Page (1:4804273) is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
Please help me on this.
Regards
Shankar PV

I raised the Message with SAP and they asked to do the H/W audit. My H/W vendor executed the diagnostic reports and given the report as "NO H/W ISSUE".
That we already get into know when i did the system refresh, (I Mean i moved the database to another machine there also i am getting those same error).
As per the DBCC checkdb log we found 1 consistency errors in database 'PRD', and we found that the table too 'DB6PMPROT'.
Since its the table for the the records of DB13, i can lose this table data. So I tried to delete the data from the table, tried to truncate the table
and also tried deleting using the commands
1. DELETE FROM [PRD].[prd].[DB6PMPROT]
2. TRUNCATE TABLE [PRD].[prd].[DB6PMPROT]
3. USE [PRD]
GO
IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID
(N'[prd].[DB6PMPROT]') AND type in (N'U'))
DROP TABLE [prd].[DB6PMPROT]
4. DROP TABLE [PRD].[prd].[DB6PMPROT]
For all the above mentioned commands the result is below
Msg 829, Level 21, State 1, Line 3
Database ID 5, Page (1:4804273) is marked RestorePending, which may
indicate disk corruption. To recover from this state, perform a restore.
Since the data in this table is not necessary, we need to drop and
recreate the table.

SAP job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND

Dear Experts,
Background job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND.
As it is hourly scheduled job and it gets finished 22 times in a day but other 2 times fails with abap dump.
Finished Job log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server
Clean_Plan:Cleaning up jobs of system DEV
Clean_Plan:finished
Job finished
Failed Job Log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Internal session terminated with a runtime error (see ST22).
Kindly suggest on this..
Thanks,
Bharath.

Dear Divyanshu,
Our system in ERP 6.0 EHP5 with SP level 10. The ABAP Dump shows below error.
|Short text                                                                                        |
|    Program "RSORA811" not found.                                                                 |
|What happened?                                                                                    |
|    There are several possibilities:                                                              |
|                                                                                                  |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "RSCOLL00" had to be terminated because it has                       |
|    come across a statement that unfortunately cannot be executed.                                |
|    or                                                                                            |
|    Error in the SAP kernel.                                                                      |
|                                                                                                  |
|    The current ABAP "RSCOLL00" program had to be terminated because the                          |
|    ABAP processor detected an internal system error.                                             |
|What can you do?                                                                                  |
|    Note down which actions and inputs caused the error.                                          |
|                                                                                                  |
|                                                                                                  |
|    To process the problem further, contact you SAP system                                        |
|    administrator.                                                                                |
|                                                                                                  |
|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
|    at and manage termination messages, and you can also                                          |
|    keep them for a long time.                                                                    |
|Error analysis                                                                                    |
|    On account of a branch in the program                                                         |
|    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)                                              |
|    or a transaction call, another ABAP/4 program                                                 |
|    is to be loaded, namely "RSORA811".                                                           |
|                                                                                                  |
|    However, program "RSORA811" does not exist in the library.                                    |
|                                                                                                  |
|    Possible reasons:                                                                             |
|    a) Wrong program name specified in an external PERFORM or                                     |
|       SUBMIT or, when defining a new transaction, a new                                          |
|       dialog module or a new function module.                                                    |
|    b) Transport error                                                                            |
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "RSCOLL00" - in                                      |
|     "LOOP_AT_SYSTEMS_AND_REPORTS".                                                               |
|    The main program was "RSCOLL00 ".                                                             |
|                                                                                                  |
|    In the source code you have the termination point in line 535                                 |
|    of the (Include) program "RSCOLL00".                                                          |
|    The program "RSCOLL00" was started as a background job.                                       |
|    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                                               |
|    Job Initiator.. " bharath"                                                                       |
|    Job Number..... 18243400
Kindly check and suggest..
Thanks,
Bharath.

SAP_COLLECTOR_FOR_PERFMONITOR failing with dump

HI All,
SAP standard job SAP_COLLECTOR_FOR_PERFMONITOR is failing with below job log
31.05.2012 00:19:03 Job started
31.05.2012 00:19:03 Step 001 started (program RSCOLL00, variant , user ID CP1SUP)
31.05.2012 00:19:06 Clean_Plan:Cleanup of DB13 Plannings
31.05.2012 00:19:06 Clean_Plan:started by RSDBPREV on server ttahmsv2050
31.05.2012 00:19:06 Clean_Plan:Cleaning up jobs of system PRD
31.05.2012 00:19:06 You are not authorized for DB access (S_DBCON: <LOCAL SYSTEM> PRD <Windows authentication> 03)
31.05.2012 00:19:06 Function DB6_PLAN_STOP_BATCH_JOB failed with return code = Job error
31.05.2012 00:19:06 Clean_Plan:terminated with error
31.05.2012 00:19:06 REASON=Job error
31.05.2012 00:19:06 ABAP/4 processor: COMPUTE_INT_TIMES_OVERFLOW
31.05.2012 00:19:06 Job cancelled
and its also getting finished with job log
31.05.2012 01:19:03 Job started
31.05.2012 01:19:03 Step 001 started (program RSCOLL00, variant , user ID CP1SUP)
31.05.2012 01:19:06 Database system not supported
31.05.2012 01:19:06 Database system not supported
31.05.2012 01:19:11 Job finished
i.e every alternate run it gets finsihed and gets cancelled
Dump obtained is COMPUTE_INT_TIMES_OVERFLOW
I have found this note 1027512 not sure if there is any other way

Hi,
thank you all for your help. I tried the solution provided in SAP Note 199586. Although, it does not talk about my specific issue, however, I tried solution 1 and after that job is running fine.
Thanks again for all your help.
Regards,
Sudhir

SAP_COLLECTOR_FOR_PERFMONITOR

Hi All,
In our BW PRD server job SAP_COLLECTOR_FOR_PERFMONITOR is scheduled on hourly basis,
all the jobs finish sucessfully , but it has been observed that in the morning 7:30 & evening 22:30 , same jobs are cancelling daily and giving dump as ABAP/4 processor: COMPUTE_BCD_OVERFLOW.
What could be the problem. any suggestions.
Thanks in advance.
Regards!!
Ahmed

Hi,
In addition to above notes,can you check notes 798970,360464 & 496233 see if it is relevant to you?
Also below 2 threads may be useful for you.
Runtime error COMPUTE_BCD_OVERFLOW
Re: ORA-01455 error
Thanks
Sushil

SAP_COLLECTOR_FOR_PERFMONITOR job cancellation

Hello SAP,
The SAP Standered job "SAP_COLLECTOR_FOR_PERFMONITOR job cancelled due to DUMP                    "CONNE_ILLEGAL_TRANSPORT_HEADER".
DUMP details:
The current ABAP program "SAPLSEU_COMPONENT" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Could you please let me know how to resolve this issue.
Thanks & Regards
Prabhu
Edited by: Prabhu on Jul 23, 2009 1:05 PM

HI,
Here is the log :
Runtime Errors         CONNE_ILLEGAL_TRANSPORT_HEADER
Date and Time          07-26-2009 05:49:42
Short text
IMPORT dataset cannot be interrupted.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSEU_COMPONENT" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
Error analysis
In this particular case, already the header of the dataset is invalid.
More precisely: The first byte of the dataset, which is
used for security purposes, is already invalid.
User and Transaction
Client.............. 000
User................ "BATCH-USER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4A65E5E38F2F6948E10000000AFC02C1"
Program............. "SAPLSEU_COMPONENT"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLSEU_COMPONENT" - in
"RS_COMPONENT_VIEW".
The main program was "SAPMS07A ".
In the source code you have the termination point in line 35
of the (Include) program "LSEU_COMPONENTU01".
The program "SAPLSEU_COMPONENT" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BATCH-USER"
Job Number..... 04494200
Source Code Extract
Line
SourceCde
5
*"     VALUE(LANGUAGE) LIKE SY-LANGU DEFAULT SY-LANGU
6
*"     VALUE(OBJECT_TYPE) LIKE TADIR-OBJECT OPTIONAL
7
*"     VALUE(REFRESH) LIKE SY-INPUT OPTIONAL
8
*"     VALUE(WITHOUT_TREE_SETTING) LIKE SY-INPUT OPTIONAL
9
*"     VALUE(IGNORE_SFW_SWITCHES) TYPE CHAR1 DEFAULT SPACE
10
*" TABLES
11
*"      NODETAB STRUCTURE SNODETEXT
12
13
14
DATA: subrc LIKE sy-subrc.
15
DATA: l_delete TYPE i.
16
DATA: date LIKE sy-datum.
17
18
CLEAR sy-subrc.
19
date = sy-datum.
20
REFRESH nodetab. CLEAR nodetab.
21
G_IGNORE_SFW_SWITCHES = IGNORE_SFW_SWITCHES.
22
23
IF object_type = 'FUNC'.
24
object_type = 'FUGR'.
25
ENDIF.
26
IF object_type = space.
27
object_type = 'APPL'.
28
ENDIF.
29
apid-langu = language.
30
apid-type = object_type.
31
32
IF refresh IS INITIAL.
33
get table "nodetab" of all object lists
34
of the desired type "object_type":
>>>>>
IMPORT date nodetab FROM DATABASE dwtree(ap) ID apid
36
ACCEPTING PADDING.
37
subrc = sy-subrc.
38
ENDIF.
39
40
IF subrc NE 0 OR refresh = 'X'.
41
IF object_type = 'APPL' OR
42
object_type = 'DEVC'.
43
CASE object_type.
44
WHEN 'APPL'.
45
PERFORM get_components TABLES nodetab.
46
WHEN 'DEVC'.
47
PERFORM get_devc_view TABLES nodetab.
48
ENDCASE.
49
IF without_tree_setting IS INITIAL.
50
CALL FUNCTION 'RS_TREE_CONSTRUCT'
51
TABLES
52
nodetab = nodetab
53
EXCEPTIONS
54
OTHERS = 4.
Edited by: Prabhu on Jul 26, 2009 12:17 PM

SAP_COLLECTOR_FOR_PERFMONITOR Not Running

Hi ,
In my PI 7`0 system , SAP_COLLECTOR_FOR_PERFMONITOR this background job get canceled . it running hourly based .But it get canceled every day 7.20 AM And 20.20PM. other hours run success and finished. can any one help me regarding this
Thanks in advance.

Hi Gagan
thanks for your reply , at that time it giving Dump ,
Error in the ABAP application program.
The current ABAP program "RSORAT4M" had to be interrupted because it contains
a statement that cannot be executed.*
When attempting to import data, it was discovered that the data
type of the stored data was not the same as that specified in the
program.
Can you check with this , i searched and then i am posting .
<modified_by_moderator>
There's no need to use bolds, read the "Rules of Engagement"
Edited by: Juan Reyes on Nov 25, 2010 9:50 AM

DDIC job 'SAP_COLLECTOR_FOR_PERFMONITOR' fail 2 times daily

Hi Gurus,
we have an issue with DDIC job 'SAP_COLLECTOR_FOR_PERFMONITOR'.
this job daily fails at 08am and 10pm of system time throwing ST22 dump.
DDIC job log is 'Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Database system not supported
ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
Job cancelled
ST22 runtime Runtime error 'TSV_TNEW_PAGE_ALLOC_FAILED' occurred for users 'DDIC'.
Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time          06/17/2009 20:07:11
Short text
No more storage space available for extending an internal table.
What happened?
     You attempted to extend an internal table, but the required space was
     not available.
ECC6.0,Kernel700,patch 185,oracle 10.2.0.4.0
regards
nag

Hi,
Check this note "Note 945279 - Workload Collector terminates due to memory problems"
With Regards,
Saurabh

SAP_COLLECTOR_FOR_PERFMONITOR error

Similar Messages

Maybe you are looking for