Informix - Problem description
Problem IT30129 | Status: Closed |
NEGATIVE VALUES CAN BE REPORTED IN ONSTAT -G HIS (SQLTRACES IS SET) IF ONSTAT -Z IS RUN | |
product: | |
INFORMIX SERVER / 5725A3900 / E10 - | |
Problem description: | |
If you enable SQL tracing using "SQLTRACE level=high,ntraces=10000,size=4,mode=global" and then run "onstat -z" on a busy system, then you might see negative values being shown when you run "onstat -g his". e.g. Statement Statistics: Page Buffer Read Buffer Page Buffer Write Read Read % Cache IDX Read Write Write % Cache -42 -53103 0.00 0 -611 -21648 0.00 Lock Lock LK Wait Log Num Disk Memory Requests Waits Time (S) Space Sorts Sorts Sorts -5031 0 0.0000 4.29 GB 0 0 0 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of IDS prior to 14.10.xC3 * **************************************************************** * PROBLEM DESCRIPTION: * * NEGATIVE VALUES CAN BE REPORTED IN ONSTAT -G HIS (SQLTRACES * * IS SET) IF ONSTAT -Z IS RUN * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 14.10.xC3+. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of IDS prior to 14.10.xC3 * **************************************************************** * PROBLEM DESCRIPTION: * * NEGATIVE VALUES CAN BE REPORTED IN ONSTAT -G HIS (SQLTRACES * * IS SET) IF ONSTAT -Z IS RUN * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 14.10.xC3+. * **************************************************************** | |
Comment | |
Problem fixed in Informix Server 14.10.xC3+. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.08.2019 02.12.2019 02.12.2019 |
Problem solved at the following versions (IBM BugInfos) | |
14.10.xC3 | |
Problem solved according to the fixlist(s) of the following version(s) |