DB2 - Problem description
Problem IT09945 | Status: Closed |
MEMORY USAGE CAN INCREASE WHEN RUNNING SQL ON OBJECT WITH XML COLUMN. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Memory usage can increase WHEN RUNNING SQL on object with XML column. It can also result in an instance crash if we run out of memory on the instance/machine. Requirements to see this APAR: - Database is created with Collating using UCA500R1_LEN_AN_CX_EX_FX_HX_NX_S1. - SQL uses a table that has an XML column. - Table may also require XML Indexes. - The SQL uses XMLTABLE and/or XMLNAMESPACES. Can check for this by running the following during or just after the SQL: syscpid=`db2pd -edu | grep "db2sysc PID:" | awk '{ print $3}'` db2pd -memblocks sort pid=${syscpid} |head -20 The output will show the following: Address DataAddress PoolID PoolName BlkAge Size(Bytes) I LOC File Total set size: 0 bytes Memory blocks sorted by size: PoolID PoolName TotalSize(Bytes) TotalCount LOC File 0 205489369 295026 110 sqlnlsICUcallback.C | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW v10.5 Fixpack 7 or Later. * **************************************************************** | |
Local Fix: | |
Solution | |
First Fixed in DB2 LUW v10.5 Fixpack 7. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.07.2015 21.01.2016 21.01.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |