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 IC73205 Status: Closed

DB2 ATTEMPTS TO USE DIRECT IO ON SOLARIS ZFS FILE SYSTEM, WHILE ZFS HAS NO
DIRECT IO SUPPORT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
(1) During opening log files, the message in db2diag.log looks 
like the following: 
 
xxxx-xx-xx-xx.xx.xx.xxxxxx+xxx xxxxxxxxxx         LEVEL: Warning 
 
PID     : 26579                TID  : 13          PROC : db2sysc 
0 
INSTANCE: db2             NODE : 000         DB   : sample 
 
EDUID   : 13                   EDUNAME: db2loggr (sample) 0 
 
FUNCTION: DB2 UDB, oper system services, 
 
sqlo_enable_dio_cio_using_ioctl, probe:30 
 
MESSAGE : Unsupported file system type %s for Direct I/O. 
 
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 
 
0x870F00B7 
 
DATA #2 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes 
 
  File Handle              = 9 
 
  File System Block Size   = 512 bytes 
 
  File System Type         = zfs 
 
  File Handle Flags : 
 
    Require Sector Align   = No 
 
    DIO/CIO Mode           = No 
 
    Raw Block Device       = No 
 
    Reserved Handle        = No 
 
    Flush On Close         = No 
 
    Thread-Level Lock      = No 
 
    Write-through Mode     = Yes 
 
    File Not Tracked       = No 
 
Please note that the EDU name is db2loggr or db2loggw. 
 
The workaround would be to set: 
db2set DB2_LOGGER_NON_BUFFERED_IO=OFF 
 
2. Some customer might notice the following message in 
db2diag.log during opening tablespace containers: 
 
 
xxxx-xx-xx-xx.xx.xx.xxxxxx+xxx xxxxxxxxxx         LEVEL: Warning 
 
PID     : 5351                 TID  : 10          PROC : db2sysc 
INSTANCE: db2              NODE : 000         DB   : sample 
APPHDL  : 0-46                 APPID: xxxxxxxxxx 
AUTHID  : xxx 
EDUID   : 10                   EDUNAME: db2agent (sample) 
FUNCTION: DB2 UDB, oper system services, 
sqlo_enable_dio_cio_using_ioctl, probe:30 
MESSAGE : Unsupported file system type %s for Direct I/O. 
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 
0x870F00B7 
DATA #2 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes 
  File Handle              = 27 
  File System Block Size   = 512 bytes 
  File System Type         = zfs 
  File Handle Flags : 
    Require Sector Align   = No 
    DIO/CIO Mode           = No 
    Raw Block Device       = No 
    Reserved Handle        = No 
    Flush On Close         = No 
    Thread-Level Lock      = No 
    Write-through Mode     = Yes 
    File Not Tracked       = No 
 
The workaround would be altering the definition of a tablespace 
for using the file system caching. 
 
To check if a file system caching is enabled on any tablespace 
of the 
database : 
 
db2 "SELECT substr(TBSP_NAME,1,40) as TBSP_NAME, TBSP_TYPE, 
TBSP_CONTENT_TYPE, FS_CACHING FROM TABLE(SNAP_GET_TBSP(CAST(NULL 
AS 
VARCHAR(1)),-1)) AS T" 
 
The customer needs to find a tablespace with containers that are 
located on a file system that doesn't support Direct IO ( like 
Solaris ZFS ) . 
( the Direct IO , or DIO and CIO are technical terms used in the 
file systems to describe I/O with no file system caching ) 
For tablespaces like that the customer shouldn't use "NO FILE 
SYSTEM CACHING" option. 
 
To enable file system caching on a tablespace : 
 
db2 alter tablespace table_space_name file system caching
Problem Summary:
Fixed
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fixed
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.12.2010
16.12.2011
16.12.2011
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.