suche 36x36
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 IT30782 Status: Closed

FALSE POSITIVE AGAINST BACKUP WITH REGISTRY DB2_BCKP_PAGE_VERIFICATION

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
False positive page corruption could be experienced when
registry
variable DB2_BCKP_PAGE_VERIFICATION is enabled for the
backup.

One of the observations could be backup failure with
SQL0980

2019-05-06-22.15.53.504558+000 I31885E651            LEVEL:
Severe
PID     : 5263                 TID : 140674221467392 PROC :
db2sysc 0
INSTANCE: db2inst1               NODE : 000            DB   :
MYDB
APPHDL  : 0-49851              APPID: 
AUTHID  : MYAUTH              HOSTNAME: host1
EDUID   : 1056                 EDUNAME: db2bm.299.28 (MYDB) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbpfParallelDirectReadV, probe:7361
MESSAGE : ZRC=0x86020019=-2046689255=SQLB_CSUM "Bad Page,
Checksum Error"
          DIA8426C A invalid page checksum was found for page
"".
DATA #1 : String, 26 bytes

2019-05-06-22.15.53.505474+000 E33290E590            LEVEL:
Severe
PID     : 5263                 TID : 140674221467392 PROC :
db2sysc 0
INSTANCE: db2inst1               NODE : 000            DB   :
MYDB
APPHDL  : 0-49851              APPID: *LOCAL.db2qr1.190506220508
AUTHID  : MYAUTH              HOSTNAME: host1
EDUID   : 1056                 EDUNAME: db2bm.299.28 (MYDB) 0
FUNCTION: DB2 UDB, database utilities, sqlubReadDMS, probe:367
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
-980
DATA #2 : Hexdump, 8 bytes
0x00007FFE37DA92D0 : 1900 0286 1900 0000
........

There might exist a stale page header in LOB/LF extents and can
cause the false positive checksum error to the backup.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* db2 registry ENV_DB2_BCKP_PAGE_VERIFICATION is enabled       *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 Version 11.1 m4fp5                            *
****************************************************************
Local Fix:
Issue db2dart /ts against the problematic table space, and run
backup with db2set DB2_BCKP_PAGE_VERIFICATION=false if the
inspect runs successfully.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* db2 registry ENV_DB2_BCKP_PAGE_VERIFICATION is enabled       *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 Version 11.1 m4fp5                            *
****************************************************************
Comment
Problem first fixed in DB2 Version 11.1 m4fp5
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
31.10.2019
31.10.2019
31.10.2019
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)