DB2 - Problem description
Problem IC89732 | Status: Closed |
DB2CKBKP RETURNS FALSE ERRORS FOR COMPRESSED BACKUPS | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
When db2ckbkp is used to check a compressed backup it can, under some circumstances, incorrectly generate the error "ERROR: Zero table spaces detected for catalog node." This is caused by a bug in the way that db2ckbkp calculates the number of table spaces in the backup image. The message can safely be ignored. Furthermore, when db2ckbkp is run with the -a option, some of the information displayed for objects of type "LIST.OF.DATA.POOLS" will be incorrect. The table space name could be truncated or completely wrong, and the numerical values could be incorrect. This is caused by a bug in the logic that displays the contents of the LIST.OF.DATA.POOLS object in the backup image and does not indicate an error in the backup image itself. These two errors occur only for compressed backup images. | |
Problem Summary: | |
When db2ckbkp is used to check a compressed backup it can, under some circumstances, incorrectly generate the error "ERROR: Zero table spaces detected for catalog node." This is caused by a bug in the way that db2ckbkp calculates the number of table spaces in the backup image. The message can safely be ignored. Furthermore, when db2ckbkp is run with the -a option, some of the information displayed for objects of type "LIST.OF.DATA.POOLS" will be incorrect. The table space name could be truncated or completely wrong, and the numerical values could be incorrect. This is caused by a bug in the logic that displays the contents of the LIST.OF.DATA.POOLS object in the backup image and does not indicate an error in the backup image itself. These two errors occur only for compressed backup images. | |
Local Fix: | |
The errors can be safely ignored. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 10.1 FP3. | |
Workaround | |
The errors can be safely ignored. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.01.2013 01.10.2013 01.10.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |