Skip to Content
avatar image
Former Member




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.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Feb 22, 2006 at 04:47 PM

    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:



    Add comment
    10|10000 characters needed characters exceeded

  • Jun 03, 2011 at 08:46 AM

    Hello Chris,

    You should check the following SAP note if RSORAT6M is taking that long to run:

    1. 713211 - Poor performance of database collector

    I believe report RSORAT6M is is executed by RSDB_TDB, which is defined in your TCOLL table. You should ensure that your TCOLL is setup correctly as shown in the following SAP notes, which depend on your release version:

    12103 - Contents of the TCOLL table

    970449 - Contents of TCOLL table in SAP_BASIS 640

    966309 - Contents of table TCOLL in SAP_BASIS 700

    966631 - Contents of TCOLL table in SAP_BASIS 710



    Add comment
    10|10000 characters needed characters exceeded