DB2 FOR LUW / DB2FORLUW / A10 - DB2

The SQL1643 message - Insufficient Instance Memory - was 
introduced in DB2 Version 10.1.  However, it is not being 
returned when database activation fails due to encountering an 
Instance Memory limit.  Instead, the pre-existing SQL1084 sql 
code is still being returned, which provides incorrect guidance 
on resolving the issue. 
 
If SQL1084 is being received on database activation, check the 
db2diag.log to determine the actual cause of the failure.  If a 
message similar to the following immediately precedes the error, 
the Instance Memory limit is being encountered, and the guidance 
associated with SQL1643 should be followed. 
 
FUNCTION: DB2 UDB, SQO Memory Management, 
SqloMemController::requestMemory, probe:50 
MESSAGE : ZRC=0x8B0F0000=-1961951232=SQLO_NOMEM "No Memory 
Available" 
          DIA8300C A memory heap error has occurred. 
DATA #1 : String, 28 bytes 
Attempt to get memory failed

**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems with an enforced Instance Memory limit are affected  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Consult db2diag.log for more details about error conditions, * 
* monitor Instance Memory usage with db2pd -dbptnmem           * 
****************************************************************

See guidance for SQL1643 if appropriate

Problem first fixed in DB2 Version 10.1 Fix Pack 5

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

03.11.2014
03.07.2015
03.07.2015