home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC74016 Status: Closed

ONLINE BACKUP HANGS UP ON DEADLATCH CONDITION BETWEEN DB2BM AND PREFETCHERS

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
The online backup can hang up with the following stacks under 
very stressful conditions for prefetching resources and those 
stacks are the eye-catchers of this issue. 
 
db2bm is waiting in sqloCSemP : 
 
 
0x0900000000248358 msgrcv + 0xD8 
0x0900000007D4EB5C sqloCSemP + 0x194 
0x09000000060ED278 
sqlbpfParallelDirectReadV__FP14SQLB_pfParIoCbP17SQLB_DIRECT_IO_C 
B 
+ 0x1488 
0x09000000060E8FE4 
sqlbDirectReadBlock__FP17SQLB_DIRECT_IO_CBP14SQLB_pfParIoCbUiPUi 
T4 
+ 0xC50 
0x09000000060E70E0 sqlubReadDMS__FP14SQLU_BUFMAN_CB + 0x8D0 
0x0900000005B4B4C0 sqlubBMCont__FP14SQLU_BUFMAN_CB + 0x1C0 
0x09000000060E1284 sqlubbuf__FP8sqeAgent + 0x590 
0x09000000047F1890 sqleSubCoordProcessRequest__FP8sqeAgent + 
0x1F4 
 
 
Some db2pfchrs are waiting on the range latch as follows : 
 
 
0x09000000000EAC18 thread_wait + 0x98 
0x0900000007D80104 getConflictComplex__17SQLO_SLATCH_CAS64FCUl + 
0x3DC 
0x0900000007D7F724 getConflict__17SQLO_SLATCH_CAS64FCUl + 0x58 
0x0900000007F758DC 
getConflict__17SQLO_SLATCH_CAS64FCUl@glueF7@clone1 + 0x74 
0x0900000007DBE968 
sqloltch_track__FCP10sqlo_latchCUlCPCcT2P16SQLO_LATCH_TABLECbC14 
SQLO_LT_VALUES@glue9B7 
+ 0x128 
0x0900000007C60080 
sqlbLatchPoolRange__FP12SQLB_GLOBALSUsUiT3PiT5ib + 0x224 
0x0900000004BD3278 
sqlbReadAndReleaseBuffers__FP16SQLB_OBJECT_DESCUiUlN23P11SQLB_pf 
Misc 
+ 0x448 
0x0900000007D5037C sqlbServiceRangeRequest__FP11SQLB_pfMisc + 
0x1D0
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see ERROR DESCRIPTION                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 8.                       * 
****************************************************************
Local Fix:
- increase NUM_IOSERVERS settings and it much reduces the 
    problem risk. 
- db2set DB2BPVARS=<path to config file> 
    in the config file, have this line: 
    NOREADVBCKUP=1 
  this will revert to the pre-V9.5FP6 behaviour
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.5 Fix Pack 8.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.01.2011
01.07.2011
01.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList