
You can use update statistics to get an overview of update activities since the system was started.
, or from the menu choose
Goto
Administration of Update System
.
. The statistics contain all of the data collected as of the last reset or server restart.The statistics are divided into the following sections:
Update requests
You can see how many update requests have been generated on this server (field Gen.), and how many have been processed (field Executed (V1).
Background: The update request is sent from a dialog or batch work process (client) on the application server you are working on to the update work process (server), which may be running on a different application server.
Fields Started (V2) and Executed (V2) provide the same information for V2 updates.
If you call up the statistics on a server on which no update work process is running, 0 always appears alongside executed (V1), started (V2), and executed (V2).
Field Canceled shows how many update requests have been canceled on the client side. Field Deleted shows how many update requests have been deleted by the server side.
Database accesses
Database accesses caused by the update are recorded here. Sum of written and read bytes, the smallet batch, the largest batch and the average batch size. This is the data that is written to update tables VBHDR, VBMOD, VBDATA, and VBERROR.
Times
Here you can see two tables.
The top one shows how much time is needed for the update requests: The number of executed V1 and V2 update requests, and the number of write and read operations (from the update tables in the database).
The bottom table shows the time intervals required for the different work steps (minimum, maximum, and average values). Update table updates (column 1), commits and delete operations in the update update work processes.
Edit
Statistics
Reset
Local
or Global. Local resets the statistics on the instance, Global in the entire system.