Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC86927 Status: Closed

DB2 SERVER TERMINATES ABNORMALLY COMPILING A SQL STATEMENT UNDER LOW MEMORY
CONDITIONS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
An out-of-memory condition may result in the DB2 server 
terminating 
abnormally while compiling a SQL statement.   The stack includes 
these 
functions: 
 
0x00002AAAB080FAAD sqlo_md_mset + 0x00df 
0x00002AAAAF78F17D _ZN9sqlnq_ftb14constab_addfldEiPKhl + 0x03e3
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 fix pack 2                       * 
****************************************************************
Local Fix:
Ensure there is enough statement heap to compile the statement
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 version 10.1 fix pack 2
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC86930 IC86931 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.10.2012
17.12.2012
17.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList