home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC77456 Status: Closed

VALUES ON "INCSIZE" AND "MAXSIZE" COLUMNS OF
"DB2PD -TABLESPACE"OUTPUT MAY BE INCORRECT.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
In "Tablespace Autoresize Statistics" section of the "db2pd 
-tablespace" output, values on "IncSize" and "MaxSize" columns 
may be incorrect. 
A typical symptom is that the values remain as 0.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.1 on 64-bits OS platforms.            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In "Tablespace Autoresize Statistics" section of the "db2pd  * 
* -tablespace" output, values on "IncSize" and "MaxSize"       * 
* columns may be incorrect.                                    * 
* A typical symptom is that the values remain as 0.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.1 FixPak 11 or higher levels.   * 
****************************************************************
Local Fix:
Use "get snapshot for tablespaces" command as an alternative.
available fix packs:
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
First fixed in DB2 UDB Version 9.1 FixPak 11.
Workaround
Use "get snapshot for tablespaces" command as an alternative.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.07.2011
19.01.2012
19.01.2012
Problem solved at the following versions (IBM BugInfos)
9.1.
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.11 FixList