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

STORAGE MANAGEMENT STORED PROCEDURE DOESN'T RETURN VALUES FOR INDEXES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Here is the sample test case 
 
db2 connect to sample 
db2 "create table shashi.t1(col1 int)" 
db2 "create index shashi.idx on shashi.t1(col1)" 
db2 "call create_storagemgmt_tables('USERSPACE1')" 
 
db2 "call capture_storagemgmt_info(5,'SHASHI','IDX')" 
 
  Return Status = 0 
 
db2 "select * from systools.stmg_index" 
 
Returns 0 records
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All user of capture_storagemgmt_info procedure who try to    * 
* capture storagemanagement data for a particular index from   * 
* CLP                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* No records were  returned when systools.stmg_index is        * 
* queried                                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to any any of the following versions db2_v91fp8,     * 
* db2_v95fp5 & db2_v97fp1                                      * 
****************************************************************
Local Fix:
Please run the Stored Procedure with database info first and 
then Index. Please see the below example 
 
db2 "call capture_storagemgmt_info(0,'SHASHI','SAMPLE')" 
 
  Return Status = 0 
 
db2 "call capture_storagemgmt_info(5,'SHASHI','IDX')" 
 
  Return Status = 0 
 
 
db2 "select * from systools.stmg_index"  Will now return the 
values.
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fix exists in db2_v91fp8, db2_v95fp5 & db2_v97fp1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
17.02.2010
17.02.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList