|
Problem IC69560
|
Status: Closed |
VALUES ON "INCSIZE" AND "MAXSIZE" COLUMNS OF "DB2PD -TABLESPACE"OUTPUT MAY BE INCORRECT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - 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.5 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.5 FixPak 7 or higher levels. *
**************************************************************** |
| Local Fix: |
Use "get snapshot for tablespaces" command as an alternative. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
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 UDB Version 9.5 FixPak 7. |
| Workaround |
Use "get snapshot for tablespaces" command as an alternative. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC71090 IC71091 IC77456
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.06.2010
02.11.2010
02.11.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.7
|
 |
| 9.5.0.7
|
|
