Informix - Problem description
Problem IT04556 | Status: Closed |
THE OS_MEM_FREE COLUMN FROM SYSMASTER:SYSMACHINEINFO IS MISLEADING ON AIX | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
Take for example the following query: select os_mem_free from sysmaster:sysmachineinfo; This returns the amount of free memory on the OS in bytes. We appear to get this information from the same function that gathers that info for OAT (via the SMI query) and onstat -g osi. The system call being used appears to be grabbing what is seen in svmon -G's "free" column. (see below) While this does tend to be showing a true value for free memory on the system, it is not an accurate representation of the real available free memory. That's because this free value incorporates a lot of memory reserved/cached by the OS. Yet this memory can be redistributed to new shared memory segments and process heap memory if needed. > svmon -G size inuse free pin virtual mmode memory 65404928 65258049 9272929 11308121 Ded pg space 5373952 28131 work pers clnt other pin 7337054 0 1123 1934752 in use 11308121 0 53949928 ... A more accurate value for free memory on the system (i.e. memory that could be available if needed) would be the (memory->size) - (memory->virtual). Or (memory->size) - (in use->work). | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * AIX users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IDS-12.10.xC5 * **************************************************************** | |
Local Fix: | |
Solution | |
Problem Fixed In IDS-12.10.xC5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.09.2014 16.10.2015 16.10.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
12.10.xC5 | |
12.10.xC5.W1 |