home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC96714 Status: Geschlossen

TABLE SPACES HAVING ONLY ONE CONTAINER CAN NOT MAKE USE OF "VECTORED
IO"

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
DB2 does not make use of "Vectored IO" when a table space has 
only one container. Applying the APAR makes it possible to take 
advantage of "Vectored IO" even if a table space has only one 
container. 
 
One of the benefits of using "Vectored IO" is: it may possibly 
avoid one ONLINE BACKUP performance issue that happens in 
pureScale environment only. 
When the performance issue is happening, following information 
can be observed in stack files of DB2 prefetchers (EDU name 
'db2pfchr'): 
=========================================== 
<StackTrace> 
thread_wait 
getConflictComplex 
getConflict 
get 
sqlbDMSDirectRead 
sqlbDirectRead 
sqlbServiceDirectReadRequest 
sqlbPFPrefetcherEntryPoint 
</StackTrace> 
 
<LatchInformation> 
Waiting on latch type: (SQLO_LT_SQLB_POOL_CB__olbRangeLotch) 
</LatchInformation> 
=========================================== 
The ONLINE BACKUP is slow because multiple prefetchers are 
competing for the 'SQLO_LT_SQLB_POOL_CB__olbRangeLotch'. 
When prefetchers are making use of "Vectored IO", there is no 
competition for the latch hence the performance issue is 
avoided.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 10.5 on Linux, Unix and Windows         * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 LUW Version 10.5 Fix Pack 4 or higher levels.  * 
****************************************************************
Local-Fix:
Change table spaces from "one container" to "multiple 
containers".
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 LUW Version 10.5 Fix Pack 4.
Workaround
Change table spaces from "one container" to "multiple 
containers".
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.10.2013
26.08.2014
26.08.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList