SAP Note 20097 - SE30: Runtime measurement error (Multi-processor machine), O.

Symptom

The analysis of a measurement
- shows a "runtime measurement error",
- ends with an OVERFLOW runtime error.

Reason and Prerequisites

This message may have the following causes:

1. The application server is a multi-processor machine on which the clocks of the individual processors are not sufficiently synchronized. With high time resolution of the measuring clock, this leads to time leaps in case of a processor change so that negative time readings may occur.

2. The kernel release is lower than 4.0A, the application server is either a single-processor machine or a multi-processor machine where the individual processor clocks are not fully synchronized (see the platform list in the 'Solution' section).

Solution

1.

-> For shorter transactions, it is often sufficient to repeat the
measurement (no processor swap).

-> Large transactions should be measured

- on a single processor machine
- on the following platforms:
- AS/400 with OS/400
- IBM with AIX
- SNI with SINIX
- SUN with SUN-OS
- Windows NT

If such a platform does not exist, measure again using a low
measuring accuracy. The measuring accuracy can be set using
the following menu function:
Runtime analysis -> Settings -> Measuring accuracy...

-> As of Release 4.5A, the user can set the measuring accuracy from
high to low. For this, refer to the ABAP online
documentation on the statement SET RUN TIME CLOCK RESOLUTION.

2. Ignore the message. The data displayed are correct.

Other terms

ABAP, SE30, ATRA, time measurement error, multi-processor machine,
BCD_FIELD_OVERFLOW