home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT01036 Status: Geschlossen

NORMAL DPF QUERY PROCESSING ON DPF TRIGGERING UNNECESSARY FMP TERMINATION

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
In version 10.1 Fix Pack 2 and higher, and version 10.5 GA and 
higher, a change was made to allow db2fmp processing to be 
interruptible when using the DPF feature (Database Partitioning 
Feature).  For non-threaded fenced routines, this requires 
terminating the db2fmp process, which generates a large number 
of db2diag.log entries. 
 
In some cases, the db2fmp termination is unnecessarily triggered 
when there are no errors or external interrupts. While there is 
no effect on applicaition processing as the SQL execution is 
unaffected (expected results are returned with no error), an 
excessive amount of db2diag.log messages are generated, and 
db2fmp processes are being unnecessarily terminated. 
 
This may be seen commonly on systems where OPM is used in 
conjunction with DPF.  OPM makes use of the reg_list_variables 
table function, which is one of the routines which can trigger 
this behavior.  In addition, the FMP termination may trigger a 
buildup of memory usage as documented in APAR IT00784 . 
 
db2diag.log entries (snippets): 
(note these entries may be present in scenario other than the 
"normal" DPF Processing targeted by this APAR) 
 
EDUID   : 9513                 EDUNAME: db2agntp (SAMPLE) 0 
FUNCTION: DB2 UDB, routine_infrastructure, 
sqlerInvokeFencedRoutine, probe:88 
DATA #1 : String, 37 bytes 
Routine failed with termination error 
 
EDUID   : 9513                 EDUNAME: db2agntp (SAMPLE) 0 
FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, 
probe:900 
DATA #1 : String, 50 bytes 
Marking fmp as unstable, fmp is forced or aborted: 
 
... 
 
EDUID   : 9513                 EDUNAME: db2agntp (SAMPLE) 0 
FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, 
probe:2000 
DATA #1 : String, 55 bytes 
Sending a signal to clean up NOT THREADED FMP process: 
 
EDUID   : 9513                 EDUNAME: db2agntp (SAMPLE) 0 
FUNCTION: DB2 UDB, oper system services, sqlossig, probe:10 
MESSAGE : Sending SIGKILL to the following process id
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all systems                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4                       * 
****************************************************************
Local-Fix:
None.  however, see APAR IT00784 if db2fmp processes are 
accumulating and the scenario in this APAR applies
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem first fixed in DB2 Version 10.5 Fix Pack 4
Workaround
see Local Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.04.2014
22.09.2014
22.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList