DB2 FOR LUW / DB2FORLUW / 970 - DB2

An application that is running a Stored procedure code via 
db2fmp process might not respond to a 
force command. Application status will be likely 
"PendingRemoteRequest" 
 
1. db2pd -fmp output will show the agent being served by an FMP 
thread in the list of "Active Threads" 
 
Example: 
 
FMP Process: 
Address            FmpPid     Bit   Flags      ActiveThrd 
PooledThrd ForcedThrd Active IPCList 
0x000000020095D9C0 32585      64    0x00000006 1          24 
11         Yes    0x0000000200C3FB80 
 
   Active Threads: 
   Address            FmpPid     EduPid     ThreadId 
   0x00000002009CEFC0 32585      7843       1093683520 
 
 
... 
 
2. Agent stack will show that the Agent is waiting on FMP - note 
the stack might be different 
but the key is that the agent is  sqlccipcWaitSynch when it has 
called the sqlerInterruptThreadedFmp 
function. 
 
Stack for Agent Edu 7843: 
 
Stack #1             Signal #10        Timestamp 
2012-07-09-14.29.28.191941 
0        ossDumpStackTraceEx 
1        OSSTrapFile::dumpEx 
2        sqlo_trce 
3        sqloDumpDiagInfoHandler 
4        __invoke_dynamic_linker__ 
5        semop 
6        sqloSSemP 
7        sqlccipcWaitSynch 
8        sqlccipcinit 
9        sqlccinit 
10       sqlerInitCommsLayer 
11       sqlerMasterThreadReq 
12       sqlerInterruptThreadedFmp 
13       sqlerInterruptFmp 
14       sqlerFedInvokeFencedRoutine 
15       sqlriFedInvokeInvoker 
16       sqlqg_Call_FMP_Thread 
17       sqlqgFedStart 
18       sqlqgOpen 
19       sqlri_djx_rta 
20       sqlriSectInvoke 
21       sqlrr_dss_router 
22       sqlrr_subagent_router 
23       sqleSubRequestRouter 
24       sqleProcessSubRequest 
25       sqeAgent::RunEDU 
 
 
2. There will be "nonEDu" stack files in the db2dump directory. 
Most of them will show the function sqlo_db2fmp_sigpre. 
One file will show entries indicating who is the Master thread 
and showing a list of threads: 
</Trap> 
* Master Thread TID: 46912572395840        * 
* Waiter Thread TID: 1082132800        * 
* Number of worker threads in process 00000024   * 
* db2fmp flags 0000004b                   * 
* thread list ***************************** 
* Thread TID: 1125235008                    * 
* Thread TID: 1124182336                    * 
* Thread TID: 1123129664                    * 
* Thread TID: 1122076992                    * 
* Thread TID: 1121024320                    * 
* Thread TID: 1119971648                    * 
* Thread TID: 1118918976                    * 
* Thread TID: 1117866304                    * 
 
The normal behaviour would be the file having the following 
 
</Trap> 
* Master Thread TID: 46912572395840        * 
* Waiter Thread TID: 1082132800        * 
* Number of worker threads in process 00000024   * 
* db2fmp flags 0000004b                   * 
* thread list ***************************** 
* Thread TID: 1125235008                    * 
* Thread TID: 1124182336                    * 
* Thread TID: 1123129664                    * 
* Thread TID: 1122076992                    * 
* Thread TID: 1121024320                    * 
* Thread TID: 1119971648                    * 
* Thread TID: 1118918976                    * 
* Thread TID: 1117866304                    * 
*****************************              << Note 
"*****************************" as closing line. 
 
If the FMP threads are hung due to this APAR there will be no 
"*****************************" and the end of the list of 
threads.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 and Fix Pack 7                    * 
****************************************************************

DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 Version 9.7 and Fix Pack 7

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC88610 IT04823 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

17.07.2012
25.10.2012
25.10.2012

9.7.