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

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 ".

SAP_COLLECTOR_FOR_PERFMONITOR dumping MEMORY_NO_MORE_PAGING

Dear friends,
In one of our BW production system, 2 instance of hourly job SAP_COLLECTOR_FOR_PERFMONITOR is dumping MEMORY_NO_MORE_PAGING.
I have already checked this thread :
MEMORY_NO_MORE_PAGING
But I am unable to find out the reason and also i do not find any Moni Key in abap dump. Please suggest.
PART OF ABAP DUMP :
   40          SEGMT     = SEGMT.
   41 *     exceptions
   42 *          others       = 1.
   43
   44 EXPORT TS    TO MEMORY ID 'RSORAT2M'.
   45 EXPORT TD110 TO MEMORY ID 'RSORAT4M'.
>>>>> EXPORT SEGMT TO MEMORY ID 'RSORAT6M'.
   47
   48 * INCLUDE rsorat0b.       T.S. 11/96
   49 * INCLUDE rsorat0m.       T.S. 11/96
   50 * INCLUDE rsorat0f.       T.S. 11/96
   51 *INCLUDE RSORAT2F.
thanks
ashish

Hello friends,
Of-Course MEMORY_NO_MORE_PAGING is a memory dump and it can be avoided if i increage paging sizes. We have smaller value for this parameter and I am not convinced if it is required now to increase it. This was working nicely sometime back.
So, When we say we have abap statement EXPORT which is causing MEMORY_NO_MORE_PAGING. But the same abap statement was working fine sometime back and we did not had this problem. So i assume if there is something like large number of history records as per SAP Note 713211 is troubling us.
Now, i want to findout what is causing so much of memory requirement & page files.
We also get similar dumo when we manually try to perform DB Checks & update histories with transaction DB02OLD. This is the same this what Collector Job also doing and dumping.
Any new suggestion please..
thanks
ashish

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

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

Solution Manager 7.1 SP04 - Job SAP_COLLECTOR_FOR_PERFMONITOR

Dear Experts
I got an issue with some differences between what SolMan Setup did and SAP Note 966309 for TCOLL in SAP_BASIS 700 - 702 sais.
SolMan Setup creates the job SAP_COLLECTOR_FOR_PERFMONITOR with the following step in working client 001:
1 RSCOLL00             ABAP                             SOLMAN_BTC EN
According to SAP Note 966309, this job is supposed to run as user DDIC (or any other with same rights) in client 000. On top, there are a lot of differences between SAP Note 966309 and the content of TCOLL.
Would you change TCOLL according to this SAP Note or would you hang on what SolMan Setup did?
Thanks for short answer.
Regards, Michael

Michael,
This note is clear regarding the client and user:Note 16083 - Standard jobs, reorganization jobs
and this note is release independent.
If you check using RTCCTOOL you'll be able to see a recommendation regarding TCOLL:
7. [Note 12103 ]    Collectors and TCOLL
Description     Planning table TCOLL for SAP workload collectors for 700 (note 966309 )
Implementation Press the lights icon to get the detailed check log.
                Add missing entries to table TCOLL using ST03N > Expert Mode > Collector
                and Performance DB > Performance Monitor Collector > Execution Times.
                Schedule RSCOLL00 as an hourly batch job if not scheduled.
"schedule standard jobs" steps is required if the jobs are not scheduled already:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Basic+Configuration
"In the activities schedule Background jobs and standard jobs different jobs are scheduled. The Background job that are scheduled are jobs for the housekeeping of SAP Solution Manager. The standard jobs are the same jobs as the jobs scheduled in transaction SM36 --> u201EStandard Jobs" and schedules jobs for general SAP housekeeping. Please make sure that the jobs are not already scheduled in SM36 before executing this activity. "
Cheers,
Diego.

SAP_COLLECTOR_FOR_PERFMONITOR Behaviour

Hello,
The Basis job SAP_COLLECTOR_FOR_PERFMONITOR
runs every hour in our system. 23 times a day it runs in just a few minutes. However, every morning at the 7:30 run, it will execute for 2-3 hours.
Is there some event/activity within the system that would trigger/cause the collector job to run for hours only once a day? The program we see in SM50 that is executing for the extended amount of time is RSORAT6M.
Thanks
chris

Hi Chris,
There is nothing wrong with the job behaviour. SAP_COLLECTOR_FOR_PERFMONITOR is using TCOLL table definition to identify what reports should be executed at particular times. That means that this job will not execute the same reports all the time (e.g. each hour) it's scheduled (unless it's defined in TCOLL matrix).
To see/change the content of TCOLL table you need to run ST03 (ST03N) transaction in the Expert mode and open Collector & Performance DB => Performance Monitor Collector => Execution Times. Check out the following link for more info: http://help.sap.com/saphelp_erp2005/helpdata/en/84/9e0e422dfcdc2ce10000000a1550b0/frameset.htm
Regards,
Mike

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

Job    SAP_COLLECTOR_FOR_PERFMONITOR getting delay.

Hi Friends,
In one of my customer system, the job    SAP_COLLECTOR_FOR_PERFMONITOR is getting delay on particular time.
Normally every hour it is getting finished with 5 to 40 secs.
But at a particular the job starts at i.e. 02:26am is finishing successfully but taking much time. It's nearly taking 37,000 secs.
Job log:
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Job finished
My system details are:
Comp version :BBPCRM 4.0
Database system: ORACLE , 10.2.0.4.0.
Kernel release :   640
SAP_BASIS:SAPKB62063
I can submit if any information required. Earlier solution is much aspirated.
Regards
Sudhakar

Sorry Guys I was not well to answer your replies.
Thanks for your replies.
Still the issues persists. Here are some more information which would help you to help me.
I have checked BTC are available.
In SM51 one BTC is running for long time for this with a entry of u201CSAPLSTUW   000 DDICu201D
& Daily BTC process is Disconnecting from oracle at 2 Ou2019clk then this job is taking that BTC. Is there any relation between this?
Wed Oct 6 01:50:01 2010
got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment
Client NLS settings:
Logon as OPS$-user to get SAPCRM's password
Connecting as /@SID on connection 1 (nls_hdl 0) ... (dbsl 640 070308)
Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
   0 UTF8                                                      1 0x114876050 0x114888db0 0x114888668
Starting user session (con_hdl=1,svchp=0x1160b89c8,srvhp=0x11488bd68,usrhp=0x1160b85b0)
Now '/@SID' is connected: con_hdl=1, nls_hdl=0, session_id=687.
Got SAPCRM's password from OPS$-user
Disconnecting from connection 1 ...
Close user session (con_hdl=1,svchp=0x1160b89c8,usrhp=0x1160b85b0)
Now I'm disconnected from ORACLE
Connecting as SAPCRM/<pwd>@SID on connection 1 (nls_hdl 0) ... (dbsl 640 070308)
Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
   0 UTF8                                                      1 0x114876050 0x114888db0 0x114888668
Starting user session (con_hdl=1,svchp=0x1160b89c8,srvhp=0x11488bd68,usrhp=0x1160b85b0)
Now 'SAPCRM/<pwd>@SID' is connected: con_hdl=1, nls_hdl=0, session_id=687.
Connection 1 opened (DBSL handle 1)
Wp Hdl ConName          ConId     ConState     TX PRM RCT TIM MAX OPT Date     Time   DBHost
134 000 R/3              000000000 ACTIVE       NO YES NO 000 255 255 20100930 152615 host05
134 001 R/3*WORKFLOWTRAC 134000057 ACTIVE       NO NO NO 004 255 255 20101006 015001 host05
ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
Wed Oct 6 02:08:47 2010
Disconnecting from connection 1 ...
Close user session (con_hdl=1,svchp=0x1160b89c8,usrhp=0x1160b85b0)
Now I'm disconnected from ORACLE
Disconnected from connection con_da={R/3*WORKFLOWTRACE,134000057,1}
Job is taking much time to finish at 02:26 with a lock entry in MONI table. In ST03n sometimes 3:26 job is showing error but it is not failing.
Error log:
System name                            Host name                        Report   Date       End time
Error message
Host05_SID_00                       Host05                        RSCUECRM 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSHOSTDB 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSORACOL 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSORAHCL 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSRFCDLT 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSRFCDMN 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSSTAT60 06.10.2010 03:26:06
Table MONI is locked by user DDIC
Host05_SID_00                       Host05                        RSSTAT87 06.10.2010 03:26:06
Host05a_SID_01                      Host05a                       RSHOSTDB 06.10.2010 03:26:07
Host05a_SID_01                      Host05a                       RSRFCDMN 06.10.2010 03:26:07
Host05_SID_00                       Host05                        RSSTAT83 06.10.2010 03:26:11
Begin error recovery:
Host05_SID_00                       Host05                        RSSTAT60 06.10.2010 03:27:16
Table MONI is locked by user DDIC
Contents of TCOLL
Report      Days of Week                                   Hours of Day                                Repe-    System
                                                                                titions
         Mo    We    Fr    Su 0     2     4     6     8    10    12    14    16    18    20    22
RSCUECRM X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSDBPREV X X X X X X X X     X     X     X     X     X X X     X     X     X     X     X        1         C
RSDB_PAR X X X X X X X                          X              X                 X                 1         C
RSDB_TDB X X X X X X X                       X                                      X              1         C
RSDB_WDB                    X                                      X                                      1         C
RSHOSTDB X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         *
RSHOSTDC X X X X X X X X     X     X     X     X     X     X     X     X     X     X     X        1         C
RSHOSTPH X X X X X X X                             X        X                    X                 1         *
RSORA811 X X X X X X X                                      X                    X                 1         C
RSORACOL X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSORAHCL X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSRFCDLT X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSRFCDMN X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         *
RSSDBDLY X X X X X X X     X                                                                       1         C
RSSTAT60 X X X X X X X           X        X        X     X        X     X        X        X        1         C
RSSTAT83 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSSTAT87 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSSTAT90 X X X X X X X                                         X                 X                 1         *
RSSTAT98 X X X X X X X              X        X        X        X        X        X                 1         *
RSSTATPH X X X X X X X                             X        X                 X                    1         *
RSTUNE80 X X X X X X X                             X              X                          X     1         *
RSXRPM          X                             X                                                           1         C

Job SAP_COLLECTOR_FOR_PERFMONITOR canceled

Good evening everybody,
The job SAP_COLLECTOR_FOR_PERFMONITOR is being canceled hourly with the log below:
                                                                                Date       Time     Message text                                                  Message class Message no. Message type
04.08.2009 15:30:55 Job started                                                        00           516          S
04.08.2009 15:30:55 Step 001 started (program RSCOLL00, variant , user name DDIC)      00           550          S
04.08.2009 15:30:57 ABAP/4 processor: CONVT_OVERFLOW                                   00           671          A
04.08.2009 15:30:57 Job cancelled                                                      00           518          A
The dump generated in the ST22 is CONVT_OVERFLOW
Overflow when converting from 15362394
What happened?
The current ABAP/4 program "RSHOST2M " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
Everyone can help me to solve this issue? Our SAP version is R/3 4.6C.
Best Regards,
Fábio Karnik Tchobnian

Dear Friend,
Thanks for your help.
I apllied the part below from the note 903220
To remove the corrupted data in table MONI:
1. Call transaction ST03
2. With Goto -> Performance database -> Contents of Database
3. Select entry you want to delete
4. Further info will be '** delete**'
5. Confirm the delete
05.08.2009 Page 2 of 2
SAP Note 903220 - Short dumps CONVT_OVERFLOW in RSHOSTDB
or RSHOST2M
A sufficient way to find out which entries to delete would be:
- check when the short dump occured first
- delete the OS entries from MONI since the day before the first
short dump occured
The job SAP_COLLECTOR_FOR_PERFFMONITOR now is not being canceled anymore , however it is happening the same dump dump from a differente program after the job is finished as the log below from the ST22
ABAP runtime errors    CONVT_OVERFLOW
       Occurred on     05.08.2009 at 15:50:38
Overflow when converting from "-3.10504e+231"
What happened?
The current ABAP/4 program "SAPLSTUW " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
When attempting to convert the value "-3.10504e+231",
an overflow occurred.
Do you have some advice?
Best Regards
Fábio Karnik Tchobnian:

Job SAP_COLLECTOR_FOR_PERFMONITOR - short dump (DBIF_SETG_SQL_ERROR)

Hi gurus,
Good day.
I would like to ask for your help with regard to the short dump that we experienced with Job SAP_COLLECTOR_FOR_PERFMONITOR (program RSCOLL00). The error is DBIF_SETG_SQL_ERROR.
Date       Time     Message text
24.11.2008 02:30:39 Job started
24.11.2008 02:30:39 Step 001 started (program RSCOLL00)
24.11.2008 02:30:44 ABAP/4 processor: DBIF_SETG_SQL_ERROR
24.11.2008 02:30:44 Job cancelled
ORA-01455 is said to be the reason why we encountered DBIF_SETG_SQL_ERROR.
Database error text........: "ORA-01455: converting column overflows integer datatype"
Can you advise an OSS Note or certain solution that can fix this issue? Thank you very much!

This looks like an SAP Upgrade ECC 6 Problem, right?
Do you have any idea where I can check the date when the ECC 6 upgrade or patch has been made?
I'm an ABAPer and to be honest, currentlly, I don't have any idea if the client really did an ECC 6 upgrade --- when they did it. I will just check the table that you sent.
I just had the impression that it might be due to an ECC 6 Upgrade since I saw this case over the Internet:
"DBIF_SETG_SQL_ERROR" and "ORA-03106: fatal two-task communication protocol error" after ERP 6.0 Upgrade ( http://sap.ittoolbox.com/groups/technical-functional/sap-basis/dbif_setg_sql_error-and-ora-03106-fatal-two-task-communication-protocol-error-after-erp-60-upgrade-1640408 ).
Yes, we are also experiencing DBIF_SETG_SQL_ERROR (ORA-03106). But, I'm taking care of DBIF_SETG_SQL_ERROR (ORA-01455).
By the way, I saw that jobs EU_PUT and EU_REORG are being executed in background every morning at around 1 AM. And we are receiving the error DBIF_SETG_SQL_ERROR (ORA-01455) at around 2 AM - 3 AM, and a few at around 3 AM - 5 AM.
With these I have two questions:
(1) Do you think we still need to rerun EU_PUT and EU_REORG? Perhaps before 2 AM ?
(2) Do you think this is a Basis Issue and nothing to do with ABAP anymore?
Thank you very much!

SAP_COLLECTOR_FOR_PERFMONITOR

Similar Messages

Maybe you are looking for