|
Problem IT27472
|
Status: Closed |
SELECT FROM SYSMASTER:SYSSQLHOSTS WILL LEAK OSMUTEX BLOCKS IN GLOBAL POOL
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
This problem was reported on linux x86_64 running IDS 12.10.FC10
As part of APIM monitoring, they execute many queries against
sysmaster:syssqlhosts. There appear
to be leaking memory out of the global memory pool which can be
seen accumulating in an 'onstat -g afr global'
Many of these leaked blocks are like these:
467a0dd0 64 net 3457 osmutex.c:595
467a0e78 64 net 3457 osmutex.c:595
467a0f00 64 net 3457 osmutex.c:595
467ef978 64 net 3457 osmutex.c:595
467efa08 64 net 3457 osmutex.c:595
467efae8 64 net 3457 osmutex.c:595
46b4ce00 64 net 3457 osmutex.c:595
46bf5500 64 net 3457 osmutex.c:595
Which appear to hold the csm options field in the sqlhosts file
per following mem dump of one of these blocks
$ ifx onstat -g dmp 0x467a0dd0 64
address bytes in mem
00000000467a0dd0: c91bf48c 00000000 18005302 0000810d ........
..S.....
00000000467a0de0: 100e7a46 00000000 780d7a46 00000000 ..zF....
x.zF....
00000000467a0df0: 40000000 00000000 454e4343 534d0000 @.......
ENCCSM..
00000000467a0e00: 00000000 00000000 c1020d8a 00000000 ........
........ |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC11. *
****************************************************************
* PROBLEM DESCRIPTION: *
* SELECT FROM SYSMASTER:SYSSQLHOSTS WILL LEAK OSMUTEX BLOCKS *
* IN GLOBAL POOL *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC11+. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.12.2018
04.12.2019
04.12.2019 |
| Problem solved at the following versions (IBM BugInfos) |
12.10.xC11
|
| Problem solved according to the fixlist(s) of the following version(s) |
