DB2 FOR LUW / DB2FORLUW / B10 - DB2

During database creation with DMS tablespaces (the default in
V95 and above) or during the creation of a DMS tablespace on a
storage array that is defined with a Sector Size that is not 512
bytes, it will fail with a "Error accessing a table space
container" error.

This is due to a combination of the default of NO FILESYSTEM
CACHE for DMS tablespace creation and the current expectation in
the code that the Sector Size for Direct I/O devices is defined
as 512.

To diagnose the problem, run blockdev --report  and
determine the SSZ value. A value other than 512 under the SSZ
column for a device that you are using for DB2 tablespaces
indicates exposure.

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to v11.1.1.2 or later                                *
****************************************************************

Reconfigure the volume or device to use a Sector Size of 512

not known / see Local fix

forerunner  : IT16353 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

03.08.2017
16.10.2017
16.10.2017