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

CONNECTION FROM DB2FMP TO THE ENGINE IS NOT CLEANED UP AFTER AN INTERRUPT

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
During the execution of a fenced routine, when the execution is
interrupted or canceled(due to timeout or any kind of interrupt)
at the middle, the connection and agent associated to the db2fmp
might not be cleaned up properly. The leaked connections or
agents may finally cause SQL1226N when the number of connections
or agents reaches the MAX_CONNECTIONS / MAX_COORDAGENTS.
The issue was observed when executing the following
administrative routines and views, which are fenced routines and
are deprecated:
SYSIBMADM.SNAPAPPL
SYSIBMADM.SNAPAPPL_AP
SNAPAPPL_INFO
SNAP_GET_APPL_INFO

When the issue is happening, what the user should be seeing is
an increase in agents where the client is the db2fmp:
$ db2pd -agents -member all   | grep -c  db2fmp
126

$ db2pd -agents -member all   | grep -c  db2fmp
130

additionally, the following error messages can be found from
db2diag.log:
2022-04-04-19.20.00.552099-420 I3066E510             LEVEL:
Severe
PID     : 21426                TID : 139983435175680 PROC :
db2fmp (
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
APPID   : X.X.X.X.65371.220405031903
HOSTNAME: MYHOST1
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpSendFini,
probe:3372
RETCODE : ZRC=0xFFFFFB95=-1131
          SQL1131N  A stored procedure process has been
terminated abnormally.
          Routine name: "". Specific name: "".


2022-04-04-19.20.00.631675-420 I3577E507             LEVEL: Info
PID     : 21426                TID : 139983435175680 PROC :
db2fmp (
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
APPID   : X.X.X.X.65371.220405031903
HOSTNAME: MYHOST1
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpListener,
probe:350
RETCODE : ZRC=0xFFFFFB95=-1131
          SQL1131N  A stored procedure process has been
terminated abnormally.
          Routine name: "". Specific name: "".


2022-04-04-19.20.00.633355-420 I4085E612             LEVEL: Info
PID     : 21426                TID : 139983435175680 PROC :
db2fmp (
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
APPID   : X.X.X.X.65371.220405031903
HOSTNAME: MYHOST1
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpListener,
probe:1999
MESSAGE : ZRC=0xFFFFFB95=-1131
          SQL1131N  A stored procedure process has been
terminated abnormally.
          Routine name: "". Specific name: "".

DATA #1 : String, 46 bytes
FMP exiting with error. Last agent registered:
DATA #2 : EDUID, 4 bytes
1042

2022-04-04-19.20.00.635276-420 I4698E517             LEVEL:
Warning
PID     : 21426                TID : 139983435175680 PROC :
db2fmp (
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
APPID   : X.X.X.X.65371.220405031903
HOSTNAME: MYHOST1
FUNCTION: DB2 UDB, routine_infrastructure,
sqlerWorkerThreadEntry, probe:1025
MESSAGE : ZRC=0xFFFFFB95=-1131
          SQL1131N  A stored procedure process has been
terminated abnormally.
          Routine name: "". Specific name: "".
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* The users are executing the following administrative         *
* routines and views, which are fenced routines.               *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 for LUW v11.5.6.0 or later versions.          *
****************************************************************
Local Fix:
1) Used the MON_GET_xxx routines are NOT FENCED and so wouldn't
use db2fmp's.
OR
2) Use db2fmpterm to terminate the db2fmp process in problem:
db2fmpterm
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* The users are executing the following administrative         *
* routines and views, which are fenced routines.               *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 for LUW v11.5.6.0 or later versions.          *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.04.2022
21.04.2022
08.09.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)