FORCE APPLICATION will not force sub-agents that are handling external routine requests.

Problem(Abstract)

FORCE APPLICATION will not force sub-agents that are handling external routine requests even though tried to force them using FORCE APPLICATION command.

FORCE APPLICATION command will return successful but applications which are hang will still remain in the system.

Symptom

procstack output may show something like below:

0x0900000000251e80 semop(??, ??, ??) + 0xc0 
0x090000001535c9d4 semop@glue11(??, ??, ??) + 0x78 
0x090000001535c85c sqloSSemP__fdpr_3(??, ??, ??, ??) + 0x24 
0x09000000152981b0 sqlccipcrecv(SQLCC_COMHANDLE_T*,SQLCC_COND_T*)(??, ??) + 0xd8 
0x0900000014f579e0 sqlccrecv__fdpr_1(0x700000040000370, 
0x780000007078780, 0xf0000000f000, 0x1, 0x9000000188bcc38, 
0x8d0000000000008d, 0x0, 0x0) + 0x370 
0x0900000015a931b4sqljsDrdaAsNonCoordSPDrive(db2UCconHandle*,sqlerFmpCommInfo*)(??,
??) + 0x1b0

Cause

Some sub-agents still remain in database. These can't be forced. This is a current designed behavior of DB2 V9.5 and DB2 V9.7.

Note : DB2 V10.1 has design enhancements which will allow to force such sub-agents using the command.

Resolving the problem

Either of the following can be used to force the hanging application.

1) Recycle the instance. i.e Issue db2stop and db2start. Incase, recycling the instance is not possible then,

2) Terminate the active FMP processes which will wake up sub-agents.

For Example : Issue db2pd -fmp to find the active FMP processes. You can see output as shown below:

db2pd -fmp shows:

Database Partition 203 -- Active -- Up 3 days 23:55:01 -- Date 2012-09-27-11.34.33.831054

FMP:
Pool Size: 0
Max Pool Size: 200
Keep FMP: YES
Initialized: YES
Trusted Path: /db2home/db2inst1/sqllib/function/unfenced
Fenced User: bifenc
Shared Memory: 0x0780000000290420
IPC Pool: 0x0780000000290480

FMP Process:
Address FmpPid Bit Flags ActiveThrd PooledThrd ForcedThrd Active IPCList
0x07800000077BD000 38732016 64 0x00000002 2 1 0 Yes 0x0780000006FD1600

Active Threads:
Address FmpPid EduPid ThreadId
0x0780000006D3FDC0 38732016 13369 1029
0x0780000006FD0A80 38732016 20027 1286

Pooled Threads:
Address FmpPid ThreadId
0x07800000077BDA80 38732016 772

Forced Threads:
Address FmpPid ThreadId
No forced threads.

The active FMP threads should each have an associated edu. In the above example they are 13369 and 20027. Make sure these two edu's are indeed hanging. If yes, then FMP id to be terminated would be 38732016

db2pd -apinfo 옵션등을 통해 해당 어플리케이션의 EduPid를 추적, 이후에 db2fmpterm 명령으로 FMP 종료

Once you find the FMP id to be terminated, issue "db2fmpterm <fmp_id>" command to terminate the active FMP.

For Example : db2fmpterm 38732016

This way you can avoid recycling your instance to kill such hang applications

http://www-01.ibm.com/support/docview.wss?uid=swg21612984