Informix - Problem description
Problem IT31368 | Status: Closed |
INCREASE THE SIZE OF THE NAME WITHIN ONSTAT -G MEM | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
The output of "onstat -g mem" will print a name but this can be truncated, which can be an issue when you have many readahead entries as you cannot easily match these to the appropriate session/thread. Pool Summary: name class addr totalsize freesize #allocfrag #freefrag aqtpool V 45ac0040 8192 1128 6 2 â ¦ RA_req_3030 V 53cf7040 40960 784 3 1 RA_req_3030 V 54af7040 40960 782 4 1 The readahead entry has a prefix of "RA_req_" followed by a thread id and a request id. On a busy system, the thread id's can quickly and easily exceed 9999 and so you see many duplicate entries. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 12.10.xC15 and 14.10.xC4. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC15 (when available) or * * 14.10.xC4. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 12.10.xC15 and 14.10.xC4. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC15 (when available) or * * 14.10.xC4. * **************************************************************** | |
Comment | |
Fixed in Informix Server 12.10.xC15 and 14.10.xC4. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.12.2019 10.12.2020 10.12.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |