|
Problem IC87844
|
Status: Closed |
DPF CATALOG NODE FAIL DEACT APP HUNG IN LOCALDEACTIVATE IN TERM LOG SYNC. SIMILAR TO APAR IC75211 (9.5) and IC74901 (9.7) |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Similar to APARs fixed in 9.5FP8 (IC75211) and also included in
9.7FP5 (IC74901).
In DPF, when the catalog node fails, a CNF deact app is spawned
to deactivate the database and clean up the database. If it is
the last app, it will send a term log sync to the catalog node.
This term log sync is hung waiting for a reply from the catalog
node when it should have failed with -1229.
On Version 9.7FP5, DB2 might experience a partition hang with
the following symptoms:
There is an agent thread that is in in the process of
deactivating the database in the hung partition (likely -1229
errors will be received on attempting to connect to that
partition)
Database partition is hung with
2012-02-20-08.44.32.282395+000 I116452A437 LEVEL: Info
PID : 18546904 TID : 41576 PROC : db2sysc
28
INSTANCE: xxxx NODE : 0028
APPHDL : 0-42
EDUID : 41576 EDUNAME: db2agntp 28
FUNCTION: DB2 UDB, base sys utilities,
sqeDBMgr::LocalDeactivate, probe:25
Stack shows:
<StackTrace>
-------Frame------ ------Function + Offset------
0x09000000000EED78 thread_wait + 0x98
0x0900000009C4678C sqloWaitEDUWaitPost + 0x1E8
0x090000000B556344 WaitRecvReady__11sqkfChannelFiT1 + 0xFAC
0x090000000B5528BC ReceiveBuffer__11sqkfChannelFPP10sqkfBufferi
+ 0x7B0
0x090000000B55109C
getNextBuffer__18sqkdBdsBufferTableFPP10sqkfBufferP8SQLKD_CB +
0xFD4
0x090000000B54FF68
@128@sqlkd_rcv_buffer__FP8SQLKD_CBPP10sqkfBuffer + 0x44
0x090000000B54FCA4 @128@sqlkd_rcv_get_next_buffer__FP8SQLKD_CB +
0x50
0x090000000B222E6C @128@sqlkd_rcv_init__FP8SQLKD_CBiT2 + 0x104
0x09000000098B4D64 sqlkdReceiveReply__FP16sqlkdRqstRplyFmt +
0x838
0x090000000972EC3C
sqlpLSrequestor__FP8sqeAgentP9SQLP_DBCBi13SQLP_LOG_INFOT4P8SQLP_
VTSP5sqlca + 0x450
0x09000000096A2D7C
@108@sqlpPerformTermLogSync__FP8sqeAgentP9SQLP_DBCB + 0x23C
0x09000000097544E0 sqlpTermLogSync__FP8sqeAgentP9SQLP_DBCB +
0x27C
0x090000000999B45C
sqlpterm__FP16sqeLocalDatabaseP8sqeAgentP5sqlcab + 0x18C
0x0900000009997DA4 CleanDB__16sqeLocalDatabaseFP5sqlca + 0x408
0x0900000009A6CD54
TermDbConnect__16sqeLocalDatabaseFP8sqeAgentP5sqlcai + 0x4F8
0x0900000009A33BB8
AppStopUsing__14sqeApplicationFP8sqeAgentUcP5sqlca + 0xDA8
0x090000000A326484
AppStopUsing__14sqeApplicationFP8sqeAgentUcP5sqlca@glue164 +
0x7C
0x0900000009E9D74C
sqleSubAgentStartUsing__FP8sqeAgentP16SQLE_CLIENT_INFO + 0x270
0x090000000971260C
AppSecondaryStartUsing__14sqeApplicationFP8sqeAgentP16SQLE_CLIEN
T_INFOP5sqlca + 0x574
0x09000000098EFE84 LocalDeactivate__8sqeDBMgrFP8sqeAgentPCci +
0x920
0x09000000098EA8E4 sqleSubRequestRouter__FP8sqeAgentPUiT2 +
0x5EC
0x09000000094C77D4 sqleProcessSubRequest__FP8sqeAgent + 0x2F90
0x0900000009E4D84C RunEDU__8sqeAgentFv + 0x2F4
0x0900000009A2AAD4 EDUDriver__9sqzEDUObjFv + 0xF8
0x0900000009A5C7E4 sqloEDUEntry + 0x278
</StackTrace>
This thread will hold the SQLO_LT_sqeLocalDatabase__dblatch |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 and Fix Pack 2 *
**************************************************************** |
| Local Fix: |
A restart of the partition will be needed to clear the hang |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2012
17.12.2012
17.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
