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 |
