Informix - Problem description
Problem IT10352 | Status: Closed |
MEMORY LEAK IN DATA DICTIONARY WHEN ENTRIES FOR TABLES WITH FOREIGN KEYS ARE RECREATED | |
product: | |
INFORMIX SERVER / 5725A3900 / B70 - IDS 11.70 | |
Problem description: | |
When using tables with referential integrity, memory in the heap associated with the data dictionary entry for the table with the primary key will be temporarily lost when the entries are recreated for tables that have a foreign key relationship. This memory will be made available again when the dictionary entry for the table with the primary key is recreated, such as when update statistics is run. However, depending on the frequency of updates to these tables the size of the memory pool associated with the data dictionary may grow substantially and cause the server to allocate additional shared memory segments. The amount of memory allocated to the data dictionary may be determined with the command "onstat -g mem | grep dictpool." One reason that may lead to this behaviour is when the data dictionary is undersized for the number of tables in use. This may lead to entries for the tables with foreign keys being pushed out of the cache. When these tables are accessed again the cache entry will be rebuilt resulting in the additional memory allocation for the primary key table. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users having detached index and referential constraints * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 11.70.xC9 * **************************************************************** | |
Local Fix: | |
Solution | |
Problem Fixed In IBM Informix Server 11.70.xC9 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.07.2015 09.06.2017 09.06.2017 |
Problem solved at the following versions (IBM BugInfos) | |
11.70.xC9 | |
Problem solved according to the fixlist(s) of the following version(s) |