DB2 - Problembeschreibung
Problem IT00884 | Status: Geschlossen |
POSSIBLE MEMORY LEAK WHEN USING 'INPUT ARRAY' AND THERE IS A FATAL ERROR WHILE EXECUTING THE STATEMENT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
This problem can lead to very huge leaks but needs the following to be true: - Statement must use 'input array' (SQL_ATTR_PARAMSET_SIZE in CLI) - Statement must use 'non atomic' type (SQL_ATTR_PARAMOPT_ATOMIC in CLI) With those attributes any time one row in the array fails to insert/update/delete a new 'sqlca' is allocated for that row. At the end of the 'execute' the 'sqlca' should be freed. This is true EXCEPT if at some point while we are dealing with rows in the array one of them fails with a 'fatal' error like for example running out of log space. In that case we internally perform a 'rollback' and the 'sqlca' allocated for each rows will be left not freed until the connection is closed. A 'db2pd -db <dbname> -memb -appl' will should blocks in '1582738789' each one the size of a 'sqlca' structure. The following is sample output for db2pd -memblocks -appl. Address DataAddress PoolID PoolName BlkAge Size(Bytes) I LOC File 0x000007FAAF5A8EE8 0x000007FAAF5A8F00 1 apph 28583 136 1 4150 1582738789 ... | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 10 * **************************************************************** | |
Local-Fix: | |
Terminate connection or restart db2 instance | |
Lösung | |
First fixed in Version 9.7 Fix Pack 10. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 08.04.2014 17.11.2014 17.11.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP10 | |
Problem behoben lt. FixList in der Version | |
9.7.0.10 |