DB2 - Problem description
Problem IC99625 | Status: Closed |
DB2LOOK -L COLLECTS CONTAINER INFORMATION FOR AUTOMATIC STORAGE TABLESPACES WHICH IS NOT NEEDED BUT COULD CAUSE SLOWNESS ON DPF | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
db2look -l can generate DDL statements for user-defined table spaces. For table spaces managed by AUTOMATIC STORAGE, db2look -l still collects container information internally while these information is not needed. And this might lead to the slowness if there are a large number of table spaces in DPF environment. For table spaces managed by database or system on DPF, db2look -l needs the container information. And it is normal that db2look -l might take a long time to complete if there are a large number of table spaces in DPF environment. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users on DB2 V10.1 FixPack 3 or below * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10.1 Fix Pack 4. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 V10.1 Fix Pack 4. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC99668 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.02.2014 09.06.2014 09.06.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |