|
Problem IC96703
|
Status: Closed |
UNDER RARE CONDITIONS, LOAD CANNOT BE FORCED OFF DURING A FORCE APPLICATION PROCESSING IN A DPF ENVIRONMENT. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Under rare conditions, load cannot be forced off during a force
attempt via force application or db2stop force command,
in a DPF environment. After the force attempt, only the main
db2 coordinator agent and the db2lcata EDU remain.
The db2lcata edu is only active at the beginning of load
processing. Hence, if the force attempt is during the beginning
of the load processing when db2lcata edu is active, one may run
into this situation.
The stack tracebacks for dblcata edu and db2agent process would
show as follows:
db2agent edu
-----------
Stack:
======================
0x09000000000FFBD8 thread_wait + 0x98
0x0900000007815704 sqloWaitEDUWaitPost + 0x1CC
0x0900000007EB4494 WaitRecvReady__11sqkfChannelFiT1 + 0x598
0x0900000007EB01D4
ReceiveBuffer__11sqkfChannelFPP10sqkfBufferi + 0xB1C
0x0900000007EAEC08
getNextBuffer__18sqkdBdsBufferTableFPP10sqkfBufferP8SQLKD_CB +
0xF04
0x0900000007EAD8C8
@128@sqlkd_rcv_buffer__FP8SQLKD_CBPP10sqkfBuffer + 0x44
0x0900000007EAD608 @128@sqlkd_rcv_get_next_buffer__FP8SQLKD_CB
+ 0x50
0x090000000829189C @128@sqlkd_rcv_init__FP8SQLKD_CBiT2 + 0x104
0x09000000081D4ED4 sqlkdReceiveReply__FP16sqlkdRqstRplyFmt +
0xDC
0x09000000086D7198
sqleReceiveAndMergeReplies__FP24SQLE_RECEIVE_MERGE_INPUTP25SQLE_
RECEIVE_MERGE_OUTPUTP5sqlcaP8sqlrr_cb + 0x7D0
0x09000000081DE780
sqlkdInterrupt__FP22SQLKD_INTERRUPT_FORMATP5sqlcaP8sqlrr_cb +
0x610
0x0900000007CB9DDC
iInterrupt__16sqlusCBDSChannelFPUcT1UiP5sqlca + 0x798
0x0900000007CBFA90
zHandleInterrupt__26sqlucCLoadInterruptHandlerFP16sqlusCBDSChann
eliP5sqlca + 0x650
0x090000000824AD18
iReceiveReplies__16sqlusCBDSChannelFPP17sqluCSerializableUiP21sq
lusCBDSReplyHandlerP22sqlucCInterruptHandlerP5sqlcaP18SQLU_QRY_N
ODE_INFOPs + 0x224
0x0900000009E3A8D8
iSetupAtCatalogNode__24sqlusCLoadMPPCoordinatorFiPi + 0x6A8
0x0900000009E3590C
sqluPerformCatalogTasks__FP8sqeAgentP26sqluCLoadRequestDescripto
rP20sqlu_loadapi_load_cbP24sqlusCLoadMPPCoordinatorP16sqluCCatal
ogInfo + 0xC68
0x0900000008B49DDC
sqlu_register_table_load__FP26sqluCLoadRequestDescriptorP24sqlus
CLoadMPPCoordinatorP15sql_static_dataPb + 0x5A0
0x0900000008B4879C iRun__24sqlusCLoadMPPCoordinatorFv + 0x50
0x0900000007AA4A8C
sqlu_register_table_load_MPP__FP26sqluCLoadRequestDescriptorP15s
ql_static_dataPb + 0x1A8
0x0900000007F94E64 sqluvtld_route_in__FP12SQLE_DB2RA_T +
0x3188
db2lcata edu
-------------
Stack:
======================
0x09000000000FFBD8 thread_wait + 0x98
0x0900000007815704 sqloWaitEDUWaitPost + 0x1CC
0x0900000007EB4494 WaitRecvReady__11sqkfChannelFiT1 + 0x598
0x0900000007EB01D4
ReceiveBuffer__11sqkfChannelFPP10sqkfBufferi + 0xB1C
0x0900000007EB1EF8
getNextReply__18sqkdBdsBufferTableFP8SQLKD_CB + 0xB4
0x0900000007EAECA8
getNextBuffer__18sqkdBdsBufferTableFPP10sqkfBufferP8SQLKD_CB +
0xFA4
0x0900000007EAD8C8
@128@sqlkd_rcv_buffer__FP8SQLKD_CBPP10sqkfBuffer + 0x44
0x0900000007EAD608 @128@sqlkd_rcv_get_next_buffer__FP8SQLKD_CB
+ 0x50
0x090000000829189C @128@sqlkd_rcv_init__FP8SQLKD_CBiT2 + 0x104
0x09000000081D315C sqlkdReceiveReply__FP16sqlkdRqstRplyFmt +
0x31C
0x09000000065AFFC0
iAction__16sqlusCBDSChannelFiP13sqluCLinkListP13sqluCCacheMgr +
0x4E8
0x0900000007F85D80
iSendReceive__17sqluCSerializableFP22sqluISerializableMediai +
0x3F0
0x090000000824AC40
iReceiveReplies__16sqlusCBDSChannelFPP17sqluCSerializableUiP21sq
lusCBDSReplyHandlerP22sqlucCInterruptHandlerP5sqlcaP18SQLU_QRY_N
ODE_INFOPs + 0x14C
0x0900000007CBC514
iAcquireResources__21sqlusCCatalogSubAgentFUl + 0x1108
0x0900000007CBA39C iRun__21sqlusCCatalogSubAgentFv + 0x48C
0x0900000007FC3378 sqlusSubAgentRouter__FP8sqeAgenti + 0x31C
0x0900000007BFF448 sqleSubRequestRouter__FP8sqeAgentPUiT2 +
0x4B0
0x09000000065C4280 sqleProcessSubRequest__FP8sqeAgent + 0x2C84
0x0900000006742840 RunEDU__8sqeAgentFv + 0x2EC
0x0900000007637C8C EDUDriver__9sqzEDUObjFv + 0xD8 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 V10.1 on LUW users. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.1 Fix Pack 4 or above. *
**************************************************************** |
| Local Fix: |
Only way around it would be to recycle db2. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 V10.1 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2013
09.06.2014
09.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
