|
Problem IC74760
|
Status: Closed |
FOR TABLESPACES WITH "NO FILE SYSTEM CACHE" ENABLED AND NO CONCU RRENT I/O AVAILABLE, DIRECT I/O WILL NOT ALWAYS BE ATTEMPTED. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
When tablespaces are created with the "no file system cache"
attribute, then DB2 will attempt to use Concurrent I/O ( CIO )
on the containers of that tablespace. In some cases, when CIO is
not available on the system, then DB2 will incorrectly not
attempt to use Direct I/O ( DIO ) even though that may be
available in some cases.
DB2 will instead fall back to using the file system cache for
I/O on those tablespaces.
This could have an impact on performance. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* I/O performance may be suboptimal due to DB2 not choosing *
* Direct I/O as an access method even though it may be *
* available. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5 and Fix Pack 8 *
**************************************************************** |
| Local Fix: |
n/a |
| 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 |
Problem was first fixed in DB2 Version 9.5 and Fix Pack 8 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.03.2011
21.07.2011
21.07.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
