SAP Note 91488 - SAP Support Services - Central preparatory note (Part - III)

Collectors and Monitors

5. Performance Collector In order to provide data for peformance analysis in service sessions, the performance collector must run, and must store data correctly. The data for each instance must be stored in folder 'week' in ST03. The following SAP Notes assist in starting the setup of the performance collector:SAP Note 12103   Contents of the TCOLL table  [ releases < 640]SAP Note 970449  Contents of TCOLL table in SAP_BASIS 640SAP Note 966631  Contents of TCOLL table in SAP_BASIS 710SAP Note 966309  Contents of table TCOLL in SAP_BASIS 700 If more assistance is needed a message can be opened in BC-CCM-MON-TUN. Further information on service relevant settings can also be found in SAP Note 144864.

6. Hardware utilization A number of SAP services require information about the hardware utilization of each system in the landscape. To enable a meaningful analysis it is important that the monitoring and recording of this data is set up correctly. Most services need ca 2 weeks worth of data. Ensure that data for all servers is being collected and can be viewed in ST06N, or ST06 -> Detailed analysis -> Compare recent days. This is required also for servers without SAP instance (e.g. standalone servers, Java). Ideally this should be carefully reviewed 4-6 weeks prior to the agreed session date. Where problems exist this ensures that they can be recognised and fixed, in time to then still record the required amount of data correctly. If assistance is needed a message can be opened in BC-CCM-MON-OS. Where the OS Collector is used please bear in mind the following :

a) The OS collector version should be kept up to date. You can find the newest version following SAP Note 19227.

b) If you need to monitor a non SAP system (Java, standalone database) you can find more information in SAP Note 450741.

c) Where agents and/or connections are used to monitor and record data please ensure that they are set up correctly, and that the set up is reflected in transactions OS07 and AL15.

d) If you are using IBM Logical Partitions with SPLPARS you need to take extra steps to configure monitoring correctly. Please refer to SAP Notes 895816 and then 994025 for more information.

           Many services have a preparation phase during which SAP colleagues perform a brief review of the preparation steps. Where complex set ups are being used it can be useful to prepare a high level description which explains the relationship between logical and physical servers.
If hardware is shared between several SAP systems or a form of virtualization is used please inform the person delivering the session as this can affect the analysis.
Recommendations given in the service will depend on the description of the exact hardware setup.

7. Database Monitor The Database Monitor provides a snapshot of databuffer, cache quality, SQL cache catalog, I/O activity and other values used for the analysis of database performance. As of SAP NetWeaver 7.0 SPS 13, a new platform-independent tool called DBA Cockpit (transaction DBACOCKPIT) is available for all supported databases. This tool replaces many of the old database monitors and transactions. Should there be any issues with these tools (e.g. no data, negative values), a customer message under component BC-DB-<DB type>-CCM should be created (example: BC-DB-ORA-CCM). To ensure the counters have enough information for analysis (1 full working day) a restart of the database just before the agreed session date should be avoided. If the required information is not available, we will not be able to perform a detailed database analysis. For further details please refer to the following SAP Notes: In case you use central monitoring system (CEN) for databases: SAP Note 1068204 New monitor template for database monitoring. Up to SAP Basis 4.6D only: SAP Note 73945 Missing statistical data in database monitor.

8. Central Performance History (CPH) SAP Services are evaluating data from various sources. One source is the central performance history of the CCMS. In order to activate the collection of this data for the SAP Services, please proceed as described in SAP Note 1373735.

9. Traces To enable the safe use of SQL Traces please ensure that the requirements described in SAP Note 1076804 and SAP Note 1132350 are met.

10. To enable the safe use of ABAP Traces please ensure that the requirements described in SAP Note 981919 are met.

11. Profile parameters In order to activate the recording of the required performance data, you need to set the ABAP instance profile parameters as follows:             stat/level   = 1             rsdb/staton  = 1 For an Oracle database system, you need to set the following parameter in configuration file "init<SID>.ora":             timed_statistics  = true For an Informix database system, you need to set the following parameter in configuration file "/informix/<SID>/etc/onconfig.<dbhost>.<sid>":             WSTATS = 1

12. Data Protection When an SAP Support Service session is executed, no data is changed; data is only displayed according to the user's authorizations, so that service related system analyses can be carried out. Detailed information on data protection in connection with remote connections is available in SAP Note 46902. Where SAP employees come into contact with customers' personal/secret data these employees are bound to secrecy by §5 according to the German Data Protection Act. More information can be found in SAP Note 35493.

13. Authorizations To execute a service session, SAP requires users who are equipped with suitable authorization profiles. A user RSDUSER has been constructed, which is described in SAP Note 1405975. The SAP Note also describes which products and session types RSDUSER can be used for.