In DB2 10.1 Fix Pack 2 and later DB2 10.1 fix packs a sequence
of messages like these sometimes appears in db2diag.log.
XXXX-XX-XX-XX.XX.XX.XXXXXX+XXX XXXXXXXXXXXX LEVEL: Error
PID : XXXXXXXX TID : XXXXX PROC
:db2sysc X
INSTANCE: XXXXXXXX NODE : XXX DB
:XXXXXXXX
APPHDL : XXXXXXX
APPID:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
AUTHID : XXXXXXXX
HOSTNAME:XXXXXXXXXXXXXXXXXXXXXXXXX
EDUID : XXXXX EDUNAME: db2agntp (XXXXXXXX) X
FUNCTION: DB2 UDB, routine_infrastructure,
sqlerInvokeFencedRoutine, probe:88
DATA #1 : String, 37 bytes
Routine failed with termination error
[...]
XXXX-XX-XX-XX.XX.XX.XXXXXX+XXX XXXXXXXXXXXX LEVEL:Severe
PID : XXXXXXXX TID : XXXXX PROC
:db2sysc X
INSTANCE: XXXXXXXX NODE : XXX DB
:XXXXXXXX
APPHDL : XXXXXXX
APPID:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
AUTHID : XXXXXXXX
HOSTNAME:XXXXXXXXXXXXXXXXXXXXXXXXX
EDUID : XXXXX EDUNAME: db2agntp (XXXXXXXX) X
FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool,
probe:900
DATA #1 : String, 50 bytes
Marking fmp as unstable, fmp is forced or aborted:
[...]
XXXX-XX-XX-XX.XX.XX.XXXXXX+XXX XXXXXXXXXXXX LEVEL: Event
PID : XXXXXXXX TID : XXXXX PROC
:db2sysc X
INSTANCE: XXXXXXXX NODE : XXX DB
:XXXXXXXX
APPHDL : XXXXXXX
APPID:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
AUTHID : XXXXXXXX
HOSTNAME:XXXXXXXXXXXXXXXXXXXXXXXXX
EDUID : XXXXX EDUNAME: db2agntp (XXXXXXXX) X
FUNCTION: DB2 UDB, oper system services, sqlossig, probe:10
MESSAGE : Sending SIGKILL to the following process id
DATA #1 : signed integer, 4 bytes
XXXXXXXX
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[...]
XXXX-XX-XX-XX.XX.XX.XXXXXX+XXX XXXXXXXXXXXX LEVEL: Error
PID : XXXXXXXX TID : XXXXX PROC
:db2sysc X
INSTANCE: XXXXXXXX NODE : XXX DB
:XXXXXXXX
APPHDL : XXXXXXX
APPID:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
AUTHID : XXXXXXXX
HOSTNAME:XXXXXXXXXXXXXXXXXXXXXXXXX
EDUID : XXXXX EDUNAME: db2agntp (XXXXXXXX) X
FUNCTION: DB2 UDB, routine_infrastructure,
sqlerInvokeFencedRoutine, probe:99
MESSAGE : ZRC=0xFFFFFBEC=-1044
SQL1044N Processing was cancelled due to an
interrupt.
[...]
What triggers these messages is part of normal DB2 processing,
and they do not indicate that anything abnormal has happened.
One known situation in which these messages appear is when Optim
Performance Manager (OPM) is running.
The change that this APAR introduces is to make the
sqlerInvokeFencedRoutine and subsequent sqlerReturnFmpToPool
messages just a Warning instead of Error or Severe and so only
appear when DIAGLEVEL is 3 or above. |
