Kbase P119202: Negative values being returned in promon
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/22/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.0x
SYMPTOM(s):
Negative value returned for VST
Negative value returned in promon
Cannot 'zero' the VST counters while databases are online
CAUSE:
The VST _ActBILog._BiLog-BytesWrtn for example cycles through positive and negative values after about every 2 billion.
Unfortunately, this is expected. Due to the current construction of Progress (32-Bit) the data types for many Progress data structures are limited to the max number sizes for 32-bit architectures which is 4 billion (unsigned). If it is a signed integer then it will be 2 billion positive and 2 billion negative. Therefore as the values increase to the maximum positive of 2 billion the values roll-over and begin decreasing from the maximum negative values.
FIX:
In OpenEdge 10.1A, proutil -C zerostats has been introduced to combat exactly this, eg.: it will zero out all shared memory (promon and VST) counters online when a database has been left running so long that counters overflow to negative numbers - or at any other time a baseline is needed.
Prior to this release, the VST's can only be re-set by restarting that instance of the database.
OpenEdge 10.1B has implemented 64-bit counters.