Fixes are available
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod4 Fix Pack4 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 4 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows
APAR status
Closed as program error.
Error description
Db2adutl Extract will show errors which might point to a corrupt image, when actually the image is perfectly valid. Example: db2adutl extract db TEST taken at 20150929060717 Query for database TEST Retrieving FULL DATABASE BACKUP information. Please wait. FULL DATABASE BACKUP image: ./TEST.0.itest.DBPART002.20150929060717.001, DB Partition Number: 2 ./TEST.0.itest.DBPART002.20150929060717.002, DB Partition Number: 2 ./TEST.0.itest.DBPART002.20150929060717.003, DB Partition Number: 2 Do you wish to extract ALL of these images? (Y/N) Y ./TEST.0.itest.DBPART002.20150929060717.001 Warning: backup object already exists. Overwrite? (Y/N) Y Writing to file: ./TEST.0.itest.DBPART002.20150929060717.001 ./TEST.0.itest.DBPART002.20150929060717.002 Warning: backup object already exists. Overwrite? (Y/N) Y Writing to file: ./TEST.0.itest.DBPART002.20150929060717.002 Error unexpected data seen at the end of the sequence, image maybe corrupt. ./TEST.0.itest.DBPART002.20150929060717.003 Warning: backup object already exists. Overwrite? (Y/N) Y Writing to file: ./TEST.0.itest.DBPART002.20150929060717.003 Error unexpected data seen at the end of the sequence, image maybe corrupt. The images that have got failures are 4k in size: -rw-r----- 1 itest db2tadm 295804928 Nov 05 16:49 TEST.0.itest.DBPART002.20150929060717.001 -rw-r----- 1 itest db2tadm 4096 Nov 05 16:49 TEST.0.itest.DBPART002.20150929060717.002 -rw-r----- 1 itest db2tadm 4096 Nov 05 16:49 TEST.0.itest.DBPART002.20150929060717.003 The reason for this size is that when backing up a database with multiple sessions, some sessions are "hard" workers and back up majority of data, some sessions are "lazy" workers and might not have a chance to back up any data. For each backup image, 4K in space will be reserved for the media header. These are valid images.
Local fix
Run db2adutl verify and confirm the images are fine. Add up the size of the image files in bytes. This should match with the size of the backup reported in the db2diag.log "MESSAGE : Actual size of backup in bytes:"
Problem summary
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Check with DB2 support if your DB2 Version 11 Fix Pack * * includes this fix * ****************************************************************
Problem conclusion
Problem will be fixed in future DB2 Version 11 (not GA)
Temporary fix
Comments
APAR Information
APAR number
IT12449
Reported component name
DB2 FOR LUW
Reported component ID
DB2FORLUW
Reported release
A50
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-11-26
Closed date
2016-12-22
Last modified date
2016-12-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 FOR LUW
Fixed component ID
DB2FORLUW
Applicable component levels
RA50 PSN
UP
Document Information
Modified date:
04 May 2022