In the Workload monitor (Transaction ST03), after pressing the pushbutton "Performance database," a dialog box appears in which you enter the date to which the Workload statistics are available for a specific server. If you start the workload monitor on different system servers, for some reason, different dates are output in the dialog boxes for the same server.
Other termsJob COLLECTOR_FOR_PERFORMANCEMONITOR
Job SAP_COLLECTOR_FOR_PERFMONITOR
The workload statistics are stored centrally in the database after reading the local statistics files for every server so that any system server can be analyzed by any other system server. This implies that the same statistics status should be found on every server. However, this is generally not the case. The reason for this is that the statistics are not only read for the local server in the database, but the statistical data from the local statistics file is added to it. Therefore, it is not the time of the last update of data in the database that exists on every server for the local server, but rather the current time, as the incorrect (in comparison to the current database status) statistical data is looked up.
ExampleSnapshot in a system with 3 servers at approximately 16:47. #Server B# has only recently been started after it was shut down on October 10, at approximately 22:00.
Server A Server B Server C
-------- -------- --------
Server A Today, 16:47 Server A Today, 15:05 Server A Today, 15:05
Server B 10.10, 21:05 Server B Today, 16:47 Server B 10.10, 21:05
Server C Today, 15:10 Server C Today, 15:10 Server C Today, 16:47
Transaction ST03N is available as of Release 4.6C (also see Note 403039). Transaction ST03 therefore becomes obsolete.
Transaction ST03N reads the aggregated data from the database only. This data is no longer added to the current data from the statistic file, and so the inconsistencies described in this note no longer occur.
No comments:
Post a Comment