The COLLECTOR_FOR_PERFORMANCEMONITOR or SAP_COLLECTOR_FOR_PERFMONITOR job (Report RSCOLL00) does not collect all the performance statistics data required or does not reorganize the entries in the MONI table.
Other termsTable TCOLL
Reason and PrerequisitesThe entries in the TCOLL table differ from the specifications below, or RSCOLL00 report is not run hourly as a background job.
SolutionBasis Release 6.40: Note 970449 describes the contents of table TCOLL for Release 6.40.
Basis Release 7.00: Note 966309 describes the contents of table TCOLL for Release 7.00.
Basis Release 7.10: Note 966631 describes the contents of table TCOLL for Release 7.10.
The SAP standard job SAP_COLLECTOR_FOR_PERFMONITOR must be scheduled hourly in each SAP system. The job must always be scheduled in client 000 with user DDIC or with a user with the same authorization (see Note 16083 for more information).
Each entry in the TCOLL table corresponds to a report that is run when executing the RSCOLL00 report (the COLLECTOR_FOR_PERFORMANCEMONITOR or the SAP_COLLECTOR_FOR_PERFMONITOR job). The reports are run at the specified times on the specified weekdays. The entry in the 'System' field controls where the report is to be executed. The following values are possible for
the 'System' field:
up to Basis Release 6.20:
- 'C' : The report is started on the host with the database.
- 'E': The report is started on the instance with the enqueue process.
- '*': The report is run on all instances.
The following indicators must be displayed in the 'System' field for reports that should only be started once for each collector run:
'C' - If there is only one SAP instance on the database server, that is, the report is executed on this instance.
'E' - If there are several SAP instances running on the database server and an SAP instance runs on the ENQ server, that is, the report is executed on the ENQ server.
If there is no SAP instance on either the database server or the ENQ server, then the 'System' field must contain the indicator '%' and the 'Alternative System' must contain a server on which an SAP instance runs.
The TCOLL table is maintained by using Transaction ST03 or ST03N
(ST03 > Environment > Data collector > Collector frequency, or
ST03N > 'Expert' mode > Collector & Database perf. > Monitor-collector perf.
All of the entries in the TCOLL table are listed below.
----------------------------------------------------------------------
I Report I Repeat factor I
I I System I
I I Altern. system I
I I Day of week I
I I Time of day I
----------------------------------------------------------------------
I RSDBPREV I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I X: :X: :X: :X: :X: :X: :X: :X: :X: :X: :X: :X: I
----------------------------------------------------------------------
I RSHOSTDB I 1 I
I I * I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
I RSHOSTPH I 1 I
I I * I
I I I
I I X:X:X:X:X:X:X I
I I : : : : : : : : :X: : :X: : : : : : :X: : : : I
----------------------------------------------------------------------
I RSORA811 I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I : : : : : : : : : : : :X: : : : : : :X: : : : I
----------------------------------------------------------------------
I RSORAPAR I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I : : : : : : : :X: : : : :X: : : : : :X: : : : I
----------------------------------------------------------------------
I RSORATDB I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I : : : : : : :X: : : : : : : : : : : : :X: : : I
----------------------------------------------------------------------
I RSSTAT60 I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I : : :X: : :X: : :X: :X: : :X: :X: : :X: : :X: I
----------------------------------------------------------------------
I RSSTAT80 I 1 I
I (up to Rel.I * I
I <4.6C) I X:X:X:X:X:X:X I
I s.u. I X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
I RSSTATPH I 1 I
I I * I
I I I
I I X:X:X:X:X:X:X I
I I : : : : : : : : :X: : :X: : : : : :X: : : : : I
----------------------------------------------------------------------
I RSTUNE80 I 1 I
I I * I
I I I
I I X:X:X:X:X:X:X I
I I : : : : : : : : :X: : : : :X: : : : : : : :X: I
----------------------------------------------------------------------
The entries for RSORAPAR and RSORATDB no longer exist as of Basis Release 6.10. They are replaced by the corresponding RSDB_PAR and RSDB_TDB entries.
In addition, entries of the following type CAN exist:
----------------------------------------------------------------------
I RSEFA350 I 1 I
I I C I
I I I
I I - as desired - I
I I - as desired - I
----------------------------------------------------------------------
I RSCUECRM I 1 I
I I C I
I I I
I I : :X: : : : I
I I : : : : :X: : : : : : : : : : : : : : : : : : I
----------------------------------------------------------------------
I RSXRPM I 1 I
I I C I
I I I
I I : :X: : : : I
I I : : : : :X: : : : : : : : : : : : : : : : : : I
----------------------------------------------------------------------
I RSRFCDLT I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
----------------------------------------------------------------------
I RSRFCDMN I 1 I
I I * I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
Report RSEFA350 is no longer required as of the introduction of the new EarlyWatch alert.
The entry can be removed from TCOLL.
As of Release 3.0C, the following entry is also needed:
----------------------------------------------------------------------
I RSSTAT98 I 1 I
I I * I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
I For systems on database platform DB2/6000, the following entry is also necessary as of Release 3.0C:
----------------------------------------------------------------------
I RSORAWDB I 1 I
I I C I
I I I
I I : : : : : :X I
I I : : : : : : : : : : :X: : : : : : : : : : : : I
----------------------------------------------------------------------
This entry no longer exists as of Basis Release 6.10 and will be replaced with the entry of the RSDB_WDB report.
As of SAP Release 3.0D, the following entry is also necessary:
----------------------------------------------------------------------
I RSSTAT90 I 1 I
I I * I
I I I
I I X:X:X:X:X:X:X I
I I X: :X: :X: :X: :X: :X: :X: :X: :X: :X: :X: :X: I
----------------------------------------------------------------------
As of Release 4.0, there could be the following additional entries:
----------------------------------------------------------------------
I RSHOSTDC I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I X: :X: :X: :X: :X: :X: :X: :X: :X: :X: :X: :X: I
----------------------------------------------------------------------
This entry is only required if there is no R/3 Instance on the database server.
----------------------------------------------------------------------
I RSAMON40 I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
The entry for RSAMON40 does not exist by default; it is used to create ST07 history data. If you want to use the ST07 history, add the following entry:
As of Release 4.0:
either ----------------------------------------------------------------------
I RSSTAT80 I 1 I
I I * I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
---------------------------------------------------------------------- or (Exclusive!),
----------------------------------------------------------------------
I RSSTAT83 I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X: :X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
If for Release 4.0B you did not apply Hot Package 10 or the new version of RSSTAT83 from a transport from Note 127642, we recommend you use RSSTAT80 (this means delete the entry for RSSTAT83). Otherwise it would be better to use RSSTAT83 as it has a higher performance (this means delete the entry for RSSTAT80). For this subject also refer to Notes 127642 and 118956.
As of Release 4.6C, you can only use RSSTAT83. It is no longer possible to schedule RSSTAT80 as of Release 4.6C!
As of Release 4.5B (RSSTAT82 also for earlier releases when using Note 127642) there could also be the following entries:
----------------------------------------------------------------------
I RSSTAT82 I 1 I
I (only I C I
I Rel. I I
I <4.6C) I X:X:X:X:X:X:X I
I I : : :X: : : : : : : : : : : : : : : : : : : : I
----------------------------------------------------------------------
I RSSTAT89 I 1 I
I I * I
I I I
I I X:X:X:X:X:X:X I
I I X: :X: :X: :X: :X: :X: :X: :X: :X: :X: :X: :X: I
----------------------------------------------------------------------
This entry for RSSTAT82 is only required when the TOTAL server of the workload analysis is not set up by RSSTAT80 (ST03 > Goto > Parameters > Performance Database: 'Cumulate server statistics to a systemwide total statistic' is turned off, or if the RSSTAT83 runs instead of RSSTAT80).
The entry for RSSTAT82 is only necessary and only possible up to Release 4.6B. As of Release 4.6C, the calculation of the TOTAL data is performed by the RSSTAT83.
The RSSTAT89 entry is only useful if the application statistic is activated: that is, profile parameter stat/as_level = 1. Alternatively, instead of the RSSTAT89, the RSSTAT88 can also then be scheduled as follows (also refer to Note 127642):
----------------------------------------------------------------------
I RSSTAT88 I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X: :X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
As of Release 4.6A:
Furthermore, you have the option, to move the load generated by the application collector to a later point in time (compared to the 'normal' workload collector). To do this, you have to enter the following report instead of RSSTAT88 or RSSTAT89:
----------------------------------------------------------------------
I RSSTAT87 I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X: :X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
You may only enter one of the three reports RSSTAT87, RSSTAT88 or RSSTAT89! (For more information about load reduction also refer to Note 127642).
As of Release 4.6C:
only the parallel collector RSSTAT83 can be used, it is no longer possible to schedule RSSTAT80.
----------------------------------------------------------------------
I RSSTAT83 I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
If you want to create the TOTAL server of the workload analysis, this is automatically initiated from RSSTAT83. Therefore, it is no longer possible (and no longer necessary) to schedule RSSTAT82).
As of Basis Release 6.10:
there is an additional entry in the TCOLL Table for R/3 systems with the Oracle database.
This is scheduled as follows:
(This entry also exists in systems (>= 40B and <=46D), in
which the basic transport for remote services (refer to Note 91488)
was implemented.
Delete the entry for the RSORAVSH report from the TCOLL table.)
If you have imported the plug-in, the entry in
table TCOLL triggers an error message. Delete the entry
for report RSORAVSH from table TCOLL.)
If, due to the fixed values in the domain COLL_RNAME, you cannot
implement this entry in the table TCOLL,
proceed according to Note 113270 and maintain
the fixed value for the report RSORAVSH in this
domain.
----------------------------------------------------------------------
I RSORAVSH I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
There are also the following new entries that were generated due to the renaming of the
reports RSORAPAR, RSORATDB and RSORAWDB. These reports have been renamed to indicate that they can perform database-released activities for all database platforms.
----------------------------------------------------------------------
I RSDB_PAR I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I : : : : : : : :X: : : : :X: : : : : :X: : : : I
----------------------------------------------------------------------
I RSDB_TDB I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I : : : : : : :X: : : : : : : : : : : : :X: : : I
----------------------------------------------------------------------
I RSDB_WDB I 1 I
I I C I
I I I
I I : : : : : :X I
I I : : : : : : : : : : :X: : : : : : : : : : : : I
----------------------------------------------------------------------
As of Support Package 55, the following entry exists in Release 6.20:
----------------------------------------------------------------------
I RSORACOL I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
If you import the Support Packages described in Note 549174 into a sysstem that runs on a DB2/390 platform, you must delete the reports RSORAPAR (or RSDB_PAR as of Release 6.10), RSHOSTPH and RSSTATPH from table TCOLL. Otherwise, the collector terminates with the error DYNPRO_SEND_IN_BACKGROUND.
As of Releases 4.6C Support Package 47, 4.6D Support Package 36, 6.10 Support Package 39, 6.20 Support Package 39:
New monitor functions are available for systems on the Oracle database platform (see Notes 705608 and 716000). For this, you must enter the RSORAHCL report:
----------------------------------------------------------------------
I RSORAHCL I 1 I
I I C I
I I I
I I X:X:X:X:X:X:X I
I I X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X:X I
----------------------------------------------------------------------
The reports listed in the TCOLL table perform the following tasks:
- Report RSDBPREV: Reads the current database status and stores it in the MONI table.
- Report RSEFA350: On Informix systems, an Update Statistics is executed on tables that have changed greatly. On Oracle platforms, a size analysis is performed on ALL R/3 tables. This takes a long time and loads the system heavily, and should only be executed when absolutely necessary.
- Report RSCUECRM: (Prepared) Triggers the collection of statistical application data in CRM systems.
- Report RSHOSTDB: Reads the system load from an operating system perspective and stores this data in the MONI table.
- Report RSHOSTDC: Reads the system load from an operating system perspective on a database server without an R/3 instance, and stores this data in the MONI table.
- Report RSHOSTPH: Reads the operating system kernel parameters and stores this data in the PAHI table.
- Report RSORA811: Reorganizes the BRBACKUP and BRARCHIVE logs.
- Report RSORAHCL: Updates Oracle monitor history data. The report is only relevant for systems with Oracle Release 9i or higher.
- Report RSORAPAR: Reads the database parameters and stores them in the PAHI table. As of Release 6.10, this report has been renamed RSDB_PAR.
- Report RSORATDB: Analyzes the tables and indexes and saves the results to the MONI table: As of Release 6.10, this report has been renamed RSDB_TDB.
- Report RSORAVSH: Analyzes wait situations on the Oracle database and stores this data in the MONI table (Oracle only).
- Report RSORAWDB: Analyzes the database on DB2/6000 platforms. As of Release 6.10, this report has been renamed RSDB_WDB.
- Report RSORACOL: This is only relevant for ORACLE databases.
- Reads the ORA_MON_DBCON table in databases to be monitored.
- Reads the DB02_COLL_PLAN table to process the functions that are to be executed.
- Executes the selected collector module.
- It is available for Release 6.20 as of Basis Support Package 55, for 6.40 as of Basis Support Package 14, and for 7.00 as of Basis Support Package 5.
- Report RSSTAT60: Reorganizes table MONI.
- As of Release 6.40, report RSSTAT61 replaces report RSSTAT60.
- Report RSSTAT62 enhances report RSSTAT61 as of Release 6.40. The report checks the MONI cluster table for defective entries.
- Report RSSTAT80 Reads the statistics records and then summarizes and stores this data in the MONI table.
- Report RSSTAT83: As RSSTAT80, but it starts multiple parallel processes. For more information, refer to Note 127642.
- Report RSSTAT82: Structures the TOTAL statistics of the workload analysis, if report RSSTAT80 does not do so, and stores them in table MONI.
- Report RSSTAT89: Reads the application statistical records, aggregates and stores them in table MONI.
- Report RSSTAT88: As RSSTAT89, but it starts multiple parallel processes. For more information, refer to Note 127642.
- Report RSSTAT87: Schedules a job that starts the RSSTAT88 report approximately 30 minutes after the SAP_COLLECTOR_FOR_PERFMONITOR.
- Report RSSTAT90: Reads the table access statistics and stores this data in the MONI table.
- Report RSSTAT98: Logs active instances in the SAPWLSERV table.
- Report RSSTATPH: Reads the SAP profile parameters and stores this data in the PAHI table.
- Report RSTUNE80: Reads the buffer statistics and stores this data in the MONI table.
- Report RSRFCDLT: Reorganizes the RFC statistics table. In Releases 6.20 and 6.30, this report performs the tasks of RSICFDMN.
- Report RSRFCDMN: Reads the RFC statistics data from the file system and saves it to the database. Reorganizes the files in the file system.
- Report RSICFDLT: Reorganizes the ICF recorder entries in the database.
- Report RSICFDMN: Deletes the obsolete entries and deactivates the ICF analysis tool.
- Report RSICFJOB: Schedules a background job to execute RSICFDLT in 30 minutes.
- Report RSAMON40: Creates ST07 data.
- Report RSDB_PAR: Reads the database parameters and stores them in the PAHI table. This report replaces report RSORAPAR as of Release 6.10
- Report RSDB_TDB: Analyzes the tables and indexes and saves the results to the MONI table: This report replaces report RSORATDB as of Release 6.10
- Report RSDB_WDB: Analyzes the database on DB2/6000 platforms. This report replaces report RSORAWDB as of Release 6.10
- Report RSXRPM: Triggers the collection of statistical application data in xRPM systems.
No comments:
Post a Comment