DB2 - Problem description
Problem IT38006 | Status: Closed |
BACKUP FAILS WITH BAD PAGE ERRORS DUE TO MISMATCH BETWEEN THE PHYSICAL SIZE OF THE CONTAINER AND WHAT IS SAVED IN THE SPCS FILES | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
This is a bug where resize of containers on XFS fails. and Db2 fails to correctly handle the error. sqloFilePreallocationOnFSWithFastExtend() missed checking the return code and skipped resizing containers and not returning any errors. This is the reason the containers end up being mismatched - any failure to resize is not being detected. The result is that backup may end in an End of File error. posix_fallocate should not be checking errno as per https://man7.org/linux/man-pages/man3/posix_fallocate.3.html Diagnostic information: 2021-07-18-00.18.32.414083-240 E87972E1001 LEVEL: Critical PID : 6419 TID : 140023869466368 PROC : db2sysc 3 INSTANCE: NODE : 003 DB : APPHDL : APPID: AUTHID : HOSTNAME: EDUID : 4293 EDUNAME: db2bm.4292.1 () 3 FUNCTION: DB2 UDB, buffer pool services, sqlbDMSMapAndRead, probe:10 MESSAGE : ADM14001C An unexpected and critical error has occurred: "BadPage". The instance may have been shutdown as a result. "Automatic" FODC (First Occurrence Data Capture) has been invoked and diagnostic information has been recorded in directory "/..../db2dump/FODC_BadPage_2021-07-18-00.18.32.4 13949_0003/". Please look in this directory for detailed evidence about what happened and contact IBM support if necessary to diagnose the problem. 2021-07-18-00.18.32.414521-240 E88974E683 LEVEL: Warning PID : 6419 TID : 140023869466368 PROC : db2sysc 3 INSTANCE: NODE : 003 DB : APPHDL : APPID: AUTHID : HOSTNAME: EDUID : 4293 EDUNAME: db2bm.4292.1 () 3 FUNCTION: DB2 UDB, buffer pool services, sqlbDMSMapAndRead, probe:30 MESSAGE : ADM6006E The database manager encountered an error while reading page "4288" from table space "34" for object "0" (located at offset "4320" of container " "). 2021-07-18-00.18.32.414843-240 I89658E231 LEVEL: Severe PID:6419 TID:140023869466368 NODE:003 Title: SQLB_PAGE Dump File:/........./FODC_BadPage_2021-07-18-00.18.32.413949_0003/641 9.4293.003.dump.bin But in db2dart, there will be no error. The requested DB2DART processing has completed successfully! All operation completed without error; no problems were detected in the database. This issue can be confirmed by doing a comparison of `ls -l` of the container sizes with the size saved in `db2pd -tablespaces`. If they are different, this is a match for this issue. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to fixpack inclusive of this APAR fix. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to fixpack inclusive of this APAR fix. * **************************************************************** | |
Comment | |
Upgrade to Db2 v11.5m6fp0, or later. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.08.2021 01.12.2021 03.12.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |