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 IT37375 Status: Closed

IN DPF SQL USING EARLY CLOSE MAY INCREASE FCM BUFFERS UNTIL APPLICATION
TERMINATION

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
In a DPF environment, SQL that makes use of EARLY CLOSE may
increase some FCM buffers when that SQL ends (eg. at CURSOR
CLOSE time).
Such buffers remain associated with the application and are get
freed up when the application terminates.

If any such applications remain connected to the database for a
long time FCM buffer usage may increase and could result in "out
of FCM buffer heap" errors and probes. such as the following
occur:

2021-06-25-19.17.31.297696     I257831E755           LEVEL:
Severe
PID     : 6200                 TID : 121099857008320 PROC :
db2sysc 5
INSTANCE: instance              NODE : 005            DB   :
DBNAME
APPHDL  : 1-6832               APPID:
X.X.X.X.0000.210619000516
UOWID   : 56126                ACTID: 2
AUTHID  : USER01              HOSTNAME: hostname
EDUID   : 29213                EDUNAME: db2agntp (DBNAME) 5
FUNCTION: DB2 UDB, fast comm manager,
sqkfBufferManager::DynAdjustBuffers, probe:16
RETCODE : ZRC=0x8B0F000D=-1961951219=SQLO_NOMEM_FCM_BUFFER_HEAP
          "No memory available in 'FCMBP Heap'"
          DIA8300C A memory heap error has occurred.

2021-06-25-19.17.31.501726     I249952E613           LEVEL:
Error
PID     : 6200                 TID : 121099857008320 PROC :
db2sysc 5
INSTANCE: instance              NODE : 005            DB   :
DBNAME
APPHDL  : 1-6832               APPID:
X.X.X.X.0000.210619000516
UOWID   : 56126                ACTID: 2
AUTHID  : USER01              HOSTNAME: hostname
EDUID   : 29213                EDUNAME: db2agntp (DBNAME) 5
FUNCTION: DB2 UDB, fast comm manager,
sqkfBufferManager::AllocBuffer,
probe:55
MESSAGE : Ran out low priority buffers. Total=472476; Num in
freelist=92482;
          med thres=75195; hi thres=25143
DATA #1 : Hexdump, 4 bytes
0x00007F6B731FC6C8 : 0A00 0000



This behavior will be modified in the future releases.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* User using DPF.                                              *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Code change will not be provided for V11.1.                  *
* Please try the local fix.                                    *
****************************************************************
Local Fix:
For JCC applications, set queryCloseImplicit property to 2 for
the connections.
For, CLI and ODBC applications, set SQL_ATTR_EARLYCLOSE property
to SQL_EARLYCLOSE_OFF for the statements.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* User using DPF.                                              *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Code change will not be provided for V11.1.                  *
* Please try the local fix.                                    *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.06.2021
18.03.2022
29.03.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)