suche 36x36
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 IT36891 Status: Closed

MON_GET_LOCKS FAILS IN SINGLE MEMBER WITH "NO MEMORY AVAILABLE".

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
When the MON_GET_LOCKS table function needs to report a large
number of locks, this table function can fail with a "no memory
available" message.  When this occurs a probe can be found in
the db2diag.log file that looks like this:

2020-07-09-08.57.39.412079+000 I17880199E1028    LEVEL: Error
PID   : 55912        TID : 139650073093888 PROC : db2sysc 0
INSTANCE: db2inst1       NODE : 000      DB  : XXXX
APPHDL : 0-9227        APPID: 172.30.61.113.50388.200709085337
UOWID  : 1          ACTID: 1       AUTHID : DSADM
HOSTNAME: XXXX
EDUID  : 10971        EDUNAME: db2agent (METADB) 0
FUNCTION: DB2 UDB, WLM, sqlrwGetLocks, probe:10
MESSAGE : ZRC=0x8B0F0000=-1961951232=SQLO_NOMEM "No Memory
Available"
     DIA8300C A memory heap error has occurred.
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA   sqlcabc: 136  sqlcode: 0  sqlerrml: 0
 sqlerrmc:
 sqlerrp : SQL11052
 sqlerrd : (1) 0x00000000   (2) 0x00000000   (3) 0x00000000
      (4) 0x00000000   (5) 0x00000000   (6) 0x00000000
 sqlwarn : (1)   (2)   (3)   (4)    (5)    (6)
      (7)   (8)   (9)   (10)    (11)
 sqlstate:
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.5 FP7 or later                                 *
****************************************************************
Local Fix:
Set INSTANCE_MEMORY and LOCKLIST to fixed values.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.5 FP7 or later                                 *
****************************************************************
Comment
Upgrade to 11.5 FP7 or later
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.05.2021
22.11.2021
22.11.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)