DB2 FOR LUW / DB2FORLUW / B10 - DB2

An online backup that includes tablespaces that have LOB pages
might fail with the following errors in the db2diag.log :

FUNCTION: DB2 UDB, buffer pool services, sqlbDirectRead,
probe:820
RETCODE :
ZRC=0x8402001E=-2080243682=SQLB_CONTAINER_NOT_ACCESSIBLE
"Container not accessible"
...
FUNCTION: DB2 UDB, database utilities, sqlubReadDMS, probe:364
MESSAGE :
ZRC=0x8402001E=-2080243682=SQLB_CONTAINER_NOT_ACCESSIBLE
"Container not accessible"
DATA #1 : Pool ID, PD_TYPE_POOL_ID, 2 bytes
335   ------> Tablespace ID
DATA #2 : unsigned integer, 4 bytes
47021952
DATA #3 : unsigned integer, 4 bytes
4096
DATA #4 : unsigned integer, 4 bytes
2364192  --- > Page that produced failure

....

FUNCTION: DB2 UDB, database utilities, sqlubReadDMS, probe:367
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
-293
DATA #2 : Hexdump, 8 bytes
0x00007FCE0105BD90 : 1E00 0284 1E00 0000 ........


This error can only occur when DB2_BCKP_PAGE_VERIFICATION=TRUE

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************

Depending on the data inside the LOB pages a reorg with
LONGBLOBDATA
of the table will resolve the problem, alternatively set the
following registry variable:
DB2_BCKP_PAGE_VERIFICATION=FALSE

not known / see Local fix

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

17.08.2018
27.11.2018
27.11.2018