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 IT28326 Status: Closed

DB2CKBKP -E MAY RESULT IN A TRAP IF THE USER INPUT A NON-EXISTING OBJECT
TYPE IN EXTRACTPAGE.IN

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
The db2ckbkp tool may crash when issued with option -e to
extract pages from backup or load copy image.

The db2ckbkp has following syntax that one can use to extract
pages from backup or load image:

db2ckbkp -e BACKUP_IMAGE extractPage.in

The extractPage.in file allows user to specify input for
db2ckbkp tool.

For example following line allows user to extract 1 page 8136927
from table space 4 from load copy image (D).
The value of 12 indicates data type. This 12 means that the page
is normal data or index page,
not LOB for which we need to use 14 or LONG for which we need to
specify 15

D 12 4 8136927 1

If one specifies wrong, non existing value for data type then
db2ckbkp may crash and produce the core file.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.03.2019
16.01.2020
16.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)