Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC74921 Status: Closed

db2dart does not print out sufficient details when it encounters a
non-corruption read errors.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Currently, db2dart only returns general error message when it 
encounters a non-corruption related error i.e. 
 
  Error: Unable to read pool page XXXXXXX, object page XXXX, 
from pool X, 
  Error: parent pool X, object ID X, object type Index. 
  Error: extent map anchor page of object is XX. 
 
 
For example, db2dart could encounter a non-corruption error due 
to insufficient system resource (i.e. SQLO_NORES). 
 
db2diag.log will return the following entry, e.g. 
 
XXXX-0X-XX-XX.XX.XX.XXX000-XXX XXXXXXXXXXXXX      LEVEL: Error 
PID     : XXXX                 TID  : XXXX        PROC : db2dart 
INSTANCE: DB2                  NODE : 000 
FUNCTION: DB2 UDB, buffer pool services, sqlbFixDataEMP, 
probe:820 
MESSAGE : ZRC=0x870F00F2=-2029059854=SQLO_NORES 
          "no resources to create process or thread" 
 
and db2dart returns the following errors, e.g. 
 
  Data inspection phase start. Data obj: XXX  In pool: X 
  Error: Unable to determine pool relative page number for obj 
rel page 0 (Obj ID:XXX, Pool ID:X) 
  Error: Unable to read pool page XXXXXXXXXX, object page X, 
from pool X, 
  Error: parent pool X, object ID XXX, object type Data. 
  Error: extent map anchor page of object is XXXXXX. 
  Error: This object page does not exist. 
 
Instead of returning a general error message, db2dart will 
include the return code (RC) of the error (in hex value).
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2dart users.                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Without this APAR, customer is exposed to the issue as       * 
* described in the "ERROR DESCRIPTION" section.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5, Fixpack 8.                       * 
****************************************************************
Local Fix:
n/a
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.5, Fixpack 8.
Workaround
n/a
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.03.2011
06.07.2011
06.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.