ST03N noentries - SAP_COLLECTOR_FOR_PERFMONITOR running

Hi
I don't see any entries/data in ST03N for the current day. SAP_COLLECTOR_FOR_PERFMONITOR running successfully every one hour and SAPOSCOL service is also running on the operation System. This Windows 2003 Server Enterprise Edition with ABAP + J2EE on Oracle Database.
The data for previous day is available in st03n under expert mode as well as data for the last 10 minutes. When I try to calculate the data for the current day in Administrator mode (in Background and Dialog), I am getting an error that "data is not available for 13th July.06 i.e current day".
Any help in this regard would be highly appreciated.
Regards
Chandu

Chandu,
Please check the time zone settings in tcode: STZAD. Make sure that 'System Time Zone' field has time zone 'UTC'.
Then wait until BTC job 'SAP_COLLECTOR_FOR_PERFMONITOR' has run.
Please let me know the outcome.
Thanks,
Mohan

Similar Messages

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

DB space history not updating in DB02 after upgrading to NW7 patch level 11

We upgraded our NW04 system to NW7 patch level 11 and now when I go into DB02 and click on DB space history there is no new data since the upgrade. SAP_Collector_For_PerfMonitor runs every hour without error. I've checked st22 and there are no shortdumps and I can't find any timeout issues. Ideas?

You may need to a newer release of saposcol. Saposcol comes with your kernel, if you haven't updated your kernel recently that could be a conflict with your saposcol.
Lee

0BWTC_C02 Delta Update

Hi.
Is there any restriction in the delta upload for the above datasource? I am trying to do a delta for this datasource and it returns only 0 records eventhough a lot of usage has occured for the day (today). The delta mechanism per se seems to be working as I could do a delta today morning after the weekend.
Cheers
Anand

Hi.
I did some research and discovered (thanks to SDN) that the delta brings records only after the job SAP_COLLECTOR_FOR_PERFMONITOR runs every hour. If I try extracting data more than once after each of these runs, it returns no records. Are there any other nuances? Has anyone documented this clearly as to how exactly the delta extraction for technical content works.
Cheers
Anand

Horrible response times

Our ECC Ides system today had . For first time 17 users were working on the system (WIN2008/SQL2005 based). Before the people were maximally 5.
The server is done by making a homogeneous system copy from an blade machine(now it is an VIRTUAL)
There was enaught disk space. As I could not log in I had to restart system 3 times to get logged on the system and even then it took almost fewminute to log on.
However I checked Wokload st03n transaction) in system. and found out that
there top abap."Login_Pw", "SESSION_MANAGER", "?". (BAtch), "ADMSBUF, >DEleyed Function call, RSPOWPOO""RSWWclear", ""VA01", "SAPMHHTP "Buf Sync" >DDLOC CLEANUP)""rsbtctE"
What can I do?
¸
What I am most suspicios are 2 jobs. Namely I found 2 jobs canceled running in that period of time SAP_CCMS_MONI_BATCH_DP for 3000+ sekunds (cancelled two times as the system was twice restarted) ,the 2 main users under "users profile" in st03n were ZUGTIN running and SAPSYS( running many system jobs like ."Login_Pw", "SESSION_MANAGER", "?". (BAtch), "ADMSBUF, >DEleyed Function call, RSPOWPOO""RSWWclear", ""VA01", "SAPMHHTP "Buf Sync" >DDLOC CLEANUP)""rsbtctE)?
What else I could look for?
How to analyse/solve the problem for future
What is the role of job SAP_CCMS_MONI_BATCH_DP and how to disable it (I can see it is event triggered and runs every 3 days.

There are a few points coming to my mind:
- How much memory did you give to your database? If you use the default configuration the database will use 50 % of the available memory which is 2 GB then.
- How big are you buffers (ST02)? Did you change them?
If you did not yet run SGEN, the system will load, compile and save each program that has not yet been executed. This will trash the program buffer (abap/buffersize) and fragment it heavily. If you check ST02 you'll see a lot of swaps because programs need to be re-read again and again from the database.
Virtualized environments seriously suffer from syscalls. A syscall is made everytime the system is doing I/O or transferring data over the network. If you machine is using swap/paging, this will seriously impact performance on virtualized environments.
The increasing number of WPs is not affecting seriously, they use the same (shared) memory pool and just attach to it.
To have a good performance you need to make absolutely sure your database buffers and the SAP buffers fit in physical memory. You can check in ST06 - Detail analysis menu - previous 24 hours - memory if paging of memory is going on. If that is the case, you should tune the memory usage (fixed database memory and check buffers using sappfpar).
You may also set the parameter
es/use_mprotect = false
to decrease the number of syscalls.
Also install the hotfix http://support.microsoft.com/kb/931308.
See Note 1056052 - Windows: VMware ESX Server 3 configuration guideline
Markus

DbaCockpit - Oracle 10g - Stats Missing

Hi,
We are running Solution Manager 4.0 SP13 on Oracle 10.2.0.2 patch 16.
When we run transaction dbacockpit.
We highlight the SPACE Overview for the Local ( default ) database - size=0, free space = 0...
ALL the stats for tablespaces, size, etc are all zero !!!!
In transaction DB17 all the Database check conditions are marked.
The job SAP_COLLECTOR_FOR_PERFMONITOR runs every hour - RSCOLL00
The table TCOLL has the entry rsoracol.
The table ORA_MON_DBCON has CON_NAME = default database
Due to applying patch 16 we have ran - brconnect -u / -c -f stats -t oradict_stats
We decided to increase a tablespace and the ran - brconnect -u / -c -f stats -t system_stats
However if we run the old transaction DB02OLD, all the database performance, tables and indexes stats are available.
We can run - DB02OLD - Current Sizes - DB Analysis - refresh - perform DB checks - that Tablespace Stats are updated !
Please Help !

Thanks Baran.
Here is the fix:
Database = Oralce 10.2.0.2 Patch 16 ( patch 15 should be OK aswell)
SAP Netweaver 2004s SP12 or SP13
Run DbaCockpit - System configuration - Active System = 1( for Local database) -click On Default System - ( the Bottom Message Wiindow Will "pop" telling you what system is default )
Run Transaction DB17 and ensure all Conditions are active.
Run Transaction SM36 and Schedule Job SAP_COLLECTOR_FOR_PERFMONITOR to run every hour - (RSCOLL00)
Run se16 - table = TCOLL - Table of Contents ( F7 ) - ensure it has the entry rsoracol.
Run SE38 - RSORACUP - execute - CON_NAME = DEFAULT - OPERATIO = CREATE - execute
Run SE16 - table = ORA_MON_DBCON - table of Contents - ( leave all options blank ) - execute - the result will be similar to below:
CON NAME DEFAULT
STATUS A
MAX RUNTIME 1.800
MAX UPLOAD 1.000.000
LOG LIFE 100
DESCRIPTION Local R/3 Database
Run SE16 - Table= DB02_COLL_PLAN - Table of Contents (F7) - Leave all entries blank- Execute - Results will have found around 60 to 65 modules (the exact number depend on your R/3 release/patch) per DB connection - example of one of the entries below:
CON NAME DEFAULT
SMON ID 100
SMON NAME DB-GE-MD
FUNCNAME ORA_COLL_DB_GENERAL_MAIN_DATA
MONIFILL DEF100
RANK 2
STATUS A
SCH DATE XXXXXXX
SCH TIME X X
PROCESS TYPE S
Run transaction dbacockpit - Jobs - dba planning calender - action pad - check database - run immediately - Let job complete - highlight and check log
Run se16 - table = DB02_COLL_LOG = table of contents ( F7 ) - Leave all fields blank - Execute - page down and you will see a number of entries similar to the following:
COLL DATE 15.11.2007
COLL TIME 07:57:19
CON NAME DEFAULT
SMON ID 901
SMON NAME AD-GE-CM
MONIFILL DEF901
RCODE 0
UPLOAD 10
DURATION 1
Run transaction - dbacockpit - space - bouble click sapce overview - in the right hand pane you will see size - freespace - etc etc.
For further inforamtion note number: 1002840 ( Specifically steps 4 and 5 ) If stats not updated .. run the SAP_COLLECTOR_FOR_PERFMONITOR job - repeat steps 4 and 5 in the note and run the dba planning job check Database.
Run DBACockpit

SAP transaction code DB02 is showing one week old records

Hi,
In our landscape SAP transaction code DB02 is showing one week old records.
We want the same records to get displayed in DB02 as the current date.
Please help us to achieve the same.
Regards,
Ashutosh

Hi,
check whether background job SAP_COLLECTOR_FOR_PERFMONITOR running successfully or not.
check Note 966309 - Contents of table TCOLL in SAP_BASIS 700
Please u need further any doubt Note 1002840 solved the problem
Regards,
K.Ramamoorthy

Query Performance and Cache

Hi,
I am trying to analyze Query Performance in ST03N.
I run a Query with Property = Cache Inactive.
I get Runtime as say 180 sec.
Again when I run the same Query the Runtime is getting decreased .Now it is say 150 sec.
Pls expalin me the reason for the less runtime when there is No Cache used.

Could be two things occurring. When you say cache is inactive - that is probably referring to the OLAP Global Cache. The use session, still has alocal cache so that if they run execute the same navigation in the same session, results are retrieved from local cache.
Also,as the others have mentioned, if the same DB query is really being executed on the DB a second time, not only is the SQL stmt parsing/optimization not need to occur, but almost certainly some/all of the data still remains in the DB's buffer, so it only needs to be retrieved from memory, rather than physically reading the disk again.

ST03 on 46C/HP-UX/Cluster - Statistics not Updated.

Hi all,
We had a cluster, 4 physical servers / 14 SAP Instances.
We are managing a strange problem regarding the ST03 workload analysis, since not all instances are update to the same time.
Example:
ST03 -> Perfomance database ->
TOTAL                         12.01 23:59
host_1_<SID>_01         Today 07:01
host_1_<SID>_02         Today 16:06
host_1_<SID>_03         Today 16:06
host_1_<SID>_04         Today 16:06
host_2_<SID>_01         Today 07:00
host_2_<SID>_02         Today 16:06
host_2_<SID>_03         Today 16:06
host_2_<SID>_04         Today 16:06
host_3_<SID>_01         Today 06:05
host_3_<SID>_02         Today 16:06
host_3_<SID>_03         Today 16:06
host_3_<SID>_04         Today 16:06
host_4_<SID>_01         Today 16:06
host_4_<SID>_02         Today 16:06
sapgni_GNI_00              Today 16:06
Sometimes they delays could be of one day!
Example:
host_1_<SID>_01         Today 07:01
host_1_<SID>_02         Today 16:06
host_1_<SID>_03         Today 16:06
host_1_<SID>_04         Today 16:06
host_2_<SID>_01         14.01.2009 06:05
host_2_<SID>_02         Today 16:06
host_2_<SID>_03         Today 16:06
host_2_<SID>_04         Today 16:06
host_3_<SID>_01         Today 06:05
host_3_<SID>_02         Today 16:06
host_3_<SID>_03         Today 16:06
host_3_<SID>_04         Today 16:06
host_4_<SID>_01         Today 16:06
host_4_<SID>_02         Today 16:06
sapgni_GNI_00              Today 16:06
The following notes are related with this problem:
Note 127642 - RSCOLL00 Tuning COLLECTOR_FOR_PERFOMANCEMONITOR
Note 12103 - Contents of the TCOLL table
Note 6833 - Deleting statistics file, size of statistics file
Jobs:
SAP_COLLECTOR_FOR_PERFMONITOR until yesterday it was running each hour, now we chance it to run each 2 hours, the idea: We think one hour is no sufficient for the collector to read all the stat file, so there a lot of lock over this file.
Our Tcoll table have this:
                   Mo    We    Fr    Su 0     2     4     6     8    10    12    14    16    18    20    22
RSDBPREV X X X X X X X X     X     X     X     X     X     X     X     X     X     X     X
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
RSHOSTDC X X X X X X X                 X                       X                          X
RSHOSTPH X X X X X X X                                                           X
RSORA811 X X X X X X X                                      X                    X
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
RSORAPAR X X X X X X X                          X              X                 X
RSORATDB X X X X X X X                       X                                      X
RSORAWDB                    X                                      X
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
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
RSSDBDLY X X X X X X X     X
RSSTAT60 X X X X X X X           X        X        X     X        X     X        X        X
RSSTAT81 X X X X X X X                                                     X
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
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
RSSTAT90 X X X X X X X X     X     X     X     X     X     X     X     X     X     X     X
RSSTAT98 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
RSSTATPH X X X X X X X                                X
RSTUNE80 X X X X X X X                                         X
Our performance database configuration:
ST03 -> Goto -> Parameters -> Performance database
Workload Analysis: Parameters Relevant to MONI Reorg.
Statistical data to be cumulated & Controls for the collector
Cumulate data for weeks & month: CHECK
Cumulate hitlists (TopTime & TopRequests)    CHECK
Cumulate memory profile                               CHECK
Cumulate accounting & client profile               CHECK
Cumulate RFC profiles                                   CHECK
Cumulate terminal in/out messages (Req. bytes profile) CHECK
Cumulate server statistics for total system-wide stats CHECK (We activated this two yesterday)
Options for reorganizing statistical data (for all servers)
Delete seq.statfile after cumulation if size > 100 MB (sometimes there are stat files with size > 100 MB!! )
Max. no. of records cumulated per 600.000
Options for reorg of application statistics data (valid for all servers)
Delete appl.statfile after cumulation if size if > 100 MB
Max. number of records cumulated per call 600.000
By the way, what does mean cumulation?
Delete seq.statfile after cumulation if size > 100 MB
It means that the stat file was complete read by the collector?
Best Regards,
Erick Ilarraza

Hi Yoganand Vedagiri,
Wonderful Observation! Thanks a lot.
In Venezuela last year the time Zone change from: UTC-4 to UTC-43.
In our productive XXX client / users are set to UTC-43. System time is UTC-43.
But in the client 000 the time is set to UTC-4!!!
User DDIC on client 000 is set to UTC-4 Too.
Since the SAP_COLLECTOR_FOR_PERFMONITOR job is scheduled on the client 000 with user DDIC, there is something wrong...
In this moment we can't chance this setting until the next maintenance.
Please could you explain to me how this problem (UTC-4 vs UTC-43) can impact the Job SAP_COLLECTOR_FOR_PERFMONITOR running on the client 000? Maybe this is one of the root-caused of the problem.
Today we get this:
Server                  Last record
TOTAL                       15.01 23:59
Host1_<SID>_01        Today 07:02   -> 2 Hours of delay.
Host1_<SID>_02         Today 09:04
Host1_<SID>_03         Today 09:04
Host1_<SID>_04         Today 09:04
Host2_<SID>_01        Today 07:02   -> 2 Hours of delay
Host2_<SID>_02         Today 09:05
Host2_<SID>_03         Today 09:05
Host2_<SID>_04         Today 09:04
Host3_<SID>_01        Today 06:05   -> 3 Hours of delay.
Host3_<SID>_02         Today 09:05
Host3_<SID>_03         Today 09:05
Host3_<SID>_04         Today 09:05
Host4_<SID>_01         Today 09:05
Host4_<SID>_02         Today 09:05
On the other hand i found this log:
ST03 -> Enviroment -> Data Collector -> Stat. Rec. log
You get this: 16.01.2009   Several different errors occured
Double Click on the red line...
Click on File read info
Display Log on 16.01.2009
last record for the Host1_<SID>_01 and Host2_<SID>_01 was at 08:31 a.m you get this record: AS: No new records found in statistic file
last record for the Host3_<SID>_01   was at 07:31 a.m you get this record: AS: No new records found in statistic file
For the others servers you get this: Records successfully read
Best Regards,
Erick Ilarraza

DB02 is showing a tablespace 94% but it really only 75% full

How do I get DB02 to show the real value for the tablespace?

THe job SAP_COLLECTOR_FOR_PERFMONITOR runs program RSCOLL00 and this runs every hour.
But it still does not update the tablespace used space correctly.
Any advice?

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

Job SAP_COLLECTOR_FOR_PERFMONITOR keep on running

Dear All,
I am facing problem in prd ,we have 2 active node the job SAP_COLLECTOR_FOR_PERFMONITOR keep on running eg   44,21sec,tan I have to cancel it manual this is suddenly. this happened with not all the hourly jobs ,but only 1 or 2 time in a day a any time.
Please find the below . Please suggest how to solved it
We are using ECC6 on oracle 10g
25     BGD     1696     Running          Yes     4               2     SWNCTOTAL     000     DDIC     Insert     SWNCMONI
Sm37 log
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server nodea
Clean_Plan:Cleaning up jobs of system PRD
Clean_Plan:finished
Database destination not found
Cannot determine operating system data for database
kind regards,
kumar

Dear Sunny
Thanks for you suggestion , no it happened any time and there is sufficient no of background process are free
I have see it stuck in table SWNCMONI while Insert ans i have checked the snote .Please suggest
sm21 log
Time     Type Nr Clt User        TCode Priority Grp N Text
04:51:46 DIA 001 100 BASIS               AB 0 Run-time error "TIME_OUT" occurred
04:51:46 DIA 001 100 BASIS               AB 1 > Short dump "101021 045146 clusa " generated
04:51:46 DIA 001 100 BASIS               D0 1 Transaction Canceled SY 002 ( Time limit exceeded. )
05:01:04 RD                                      Q0 I Operating system call connect failed (error no. 10061)
05:01:45 RD                                      Q0 I Operating system call connect failed (error no. 10060)
05:01:45 DIA 000 100 BASIS               R4 9 Communication error, CPIC return code 017, SAP return code 236
05:01:45 DIA 000 100 BASIS               R6 4 > CPI-C function: CMINIT(SAP)
05:20:11 RD                                      Q0 I Operating system call connect failed (error no. 10060)
05:20:11 DIA 001 100 BASIS               R4 9 Communication error, CPIC return code 017, SAP return code 236
05:20:11 DIA 001 100 BASIS               R6 4 > CPI-C function: CMINIT(SAP)
05:20:24 RD                                      Q0 I Operating system call connect failed (error no. 10061)
05:21:18 RD                                      Q0 I Operating system call connect failed (error no. 10060)
05:21:18 DIA 001 100 BASIS               R4 9 Communication error, CPIC return code 017, SAP return code 236
05:21:18 DIA 001 100 BASIS               R6 4 > CPI-C function: CMINIT(SAP)
05:22:56 RD                                      Q0 I Operating system call recv failed (error no. 10054)
08:46:50 BTC 025 000 DDIC                       BY 4 Database error 24909 at UPD access to table TST01
08:46:50 BTC 025 000 DDIC                       F6 H Database error: TemSe->XRTAB(3)->1 for table TST01 key
08:46:56 RD                                      Q0 I Operating system call recv failed (error no. 10054)
08:47:11 BTC 025 000 DDIC                       F3 T Invalid object name for TemSe object: " "
08:47:13 BTC 025 000 DDIC                       EC F Failed to create log for job SAP_COLLECTOR_FOR_PERFMONITOR 19301600 %NEWSTEP/
08:47:13 BTC 025 000 DDIC                       F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
08:47:13 BTC 025 000 DDIC                       R4 7 Delete session 001 after error 023
09:38:51 DP                                      Q0 I Operating system call recv failed (error no. 10054)
09:38:51 DP                                      Q0 4 Connection to user 9850 ( ), terminal 90 (233 ) lost
10:00:24 RD                                      Q0 I Operating system call recv failed (error no. 10054)
10:00:24 RD                                      S2 3 Connection to CPI-C client 101 was closed
10:00:24 DIA 001 100 PORTAL                R4 9 Communication error, CPIC return code 020, SAP return code 223
10:00:24 DIA 001 100 PORTAL                R5 A > Conversation ID: 909935
10:00:24 DIA 001 100 PORTAL                R6 4 > CPI-C function: CMSEND(SAP)
10:26:36 DP                                      Q0 I Operating system call recv failed (error no. 10
and just now the sm37 log is different
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server
Clean_Plan:Cleaning up jobs of system PRD
Clean_Plan:finished
Database destination not found
Cannot determine operating system data for database
Buffer statistics for clusa transferred to MONI
Please suggest
Kind Regards,
Kumar
Edited by: kumar9 on Oct 21, 2010 12:30 PM
Edited by: kumar9 on Oct 21, 2010 2:37 PM

St03N not collecting all data

HI
does anyone know why would st03n not collect all proper data, we found out recently that a user had scheduled a program as a background job to run and it ran successfully but when we look on that date we don't see that it had run and even that user doesn't come out in the history
any ideas why?
regards

Sorry Sujit that I wasn't clear
the job i was referring to was a z program that was run be a user in the background.
that is how we started knowing that there were missing data in st03n
we were trying to see how many time that program ran and who ran it
so we went to see in st03n but we found out that there was no history for that program in there or any history for the user who ran the z program in the background.
there is no connection to SAP_COLLECTOR_FOR_PERFMONITOR background job. this job is running successful in our system and all other data is being collected
so the data that was missing was on the 14th of march and then we found out that there is no entry of any sort in st03n for 15th of march, but we have data for 16th of march.
so now we want to know what happened
i hope this is clear now
regards

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.

On ST03N "RFC problems: No data available"

Hi,
Can anyone tell me I am getting an error on T code ST03N as "RFC problems: No data available" when I am clicking on last minute load.
Checked the RFC it is working well.
Thanks
Hari Mohan

Hi Hari,
check whether below job running in your system.
SAP_COLLECTOR_FOR_PERFMONITOR
This job should run in client 000 under user DDIC with periodic of one hour.
The program is RSCOLL00
IF cancelled rerun it or if not scheduled sechedule it.
Regards
Ashok

ST03N noentries - SAP_COLLECTOR_FOR_PERFMONITOR running

Similar Messages

Maybe you are looking for