|
Problem IC68403
|
Status: Closed |
A RE-STARTED RECOVER COMMAND CAUSES DB2 TO ENTER INFINITE LOOP. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
If a RECOVER command was interrupted and then restarted, the
restarted RECOVER command can hang. Taking a callstack, will
show something similar to this:
<StackTrace>
-------Frame------ ------Function + Offset------
0x09000000004B61F0 _p_nsleep + 0x10
0x090000000005A2D0 nsleep + 0xB0
0x090000000010A32C nanosleep + 0x140
0x09000000182D1B40 ossSleep + 0x80
0x09000000197AD630 sqlorest + 0x68
0x090000001B5536D0 sqlpALR_LoadActive__FP9SQLP_DBCBP10SQLP_ALRCB
+ 0x54
0x090000001B552D48
sqlpALR_ReloadActive__FP9SQLP_DBCBP10SQLP_ALRCB + 0x40
0x090000001A960490
sqlpAgentReadLogAndAction__FP8sqeAgentPFP8sqeAgentP17SQLP_LOG_RE
C_DESC_iP9SQLP_LSN8T3
+ 0x20C
0x090000001A97EF6C
@109@sqlpIsRecoverContinuable__FP9SQLP_DBCBP8sqeAgentUi + 0x400
0x090000001A97C37C
sqlpCallRestore__FP9SQLP_DBCBP8sqeAgentPcP13sqlpRecoverCBP5sqlca
+ 0x800
0x090000001AAEBF84 sqlpPdbRfwRouter__FP8sqeAgent + 0xBAC
0x090000001A9EC104 sqleSubRequestRouter__FP8sqeAgentPUiT2 +
0x86C
0x090000001A9E8AC0 sqleProcessSubRequest__FP8sqeAgent + 0x22BC
0x0900000018F2E63C RunEDU__8sqeAgentFv + 0x2E8
0x09000000197CEB54 EDUDriver__9sqzEDUObjFv + 0xE4
0x09000000197D549C sqloEDUEntry + 0x268
------- |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of RECOVER command *
****************************************************************
* PROBLEM DESCRIPTION: *
* A restarted RECOVER command may hang. *
****************************************************************
* RECOMMENDATION: *
* Apply v9.7.2. *
**************************************************************** |
| Local Fix: |
|
| Solution |
Fix is first available in v9.7.2. With the fix the RECOVER
command will complete successfully |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.05.2010
04.05.2010
04.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.2
|
| Problem solved according to the fixlist(s) of the following version(s) |
