DB2 - Problem description
Problem IT06072 | Status: Closed |
DB2PD -TABLESPACES, MON_GET_TABLESPACE NEED TO REPORT DEFAULT/UNSPECIFIED SETTING FOR FILE SYSTEM CACHING ATTRIBUTE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
By default, the file system caching attribute is "unspecified", meaning it has an automatic or default behaviour as specified in documentation. see "File System Caching Configurations". The tools which report the default file system caching attribute only report the preference DB2 has per operating system, which can be misleading. Instead of "default" it will report the file system caching is Off for AIX,Linux,Solaris, and Windows, and On for HP and Linux390. However, this will not be the correct interpretation for certain filesystems as DB2 will request the opposite behaviour (as documented). In addition, it is impossible to distinguish between the default/unspecified setting and a user-specified setting that is equivalent to the default behaviour. This APAR will change the displaying of the File System Caching attribute to include the "default" setting. It will be necessary to consult the documentation to determine the intended DB2 behaviour. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All DB2 systems are affected * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix pack 5 * **************************************************************** | |
Local Fix: | |
None. Consult documentation for expected file system caching behaviour. | |
Solution | |
Problem first fixed in DB2 Version 10.1 Fix Pack 5 | |
Workaround | |
see Local Fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.12.2014 29.07.2015 29.07.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 | |
10.5.0.7 |