DB2 - Problem description
Problem IC74696 | 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 / 970 - 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: * * DB2 file access not using DIO when CIO is not available. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.7 Fix Pack 5 * **************************************************************** | |
Local Fix: | |
n/a | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
The problem has first been fixed in V9.7 Fix Pack 5 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC74760 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.02.2011 22.12.2011 22.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |