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

THE TABLE FUNCTIONS SYSPROC.ADMIN_GET_INDEX_COMPRESS_INFO AND SY CAUSE DB
MARKED BAD IN DATA PRATITIONED ENV.

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
The table functions SYSPROC.ADMIN_GET_INDEX_COMPRESS_INFO and 
SYSPROC.ADMIN_GET_INDEX_INFO do not have a check to skip in caes 
of nicknames. 
If the table is data partitioned, the table functions cause the 
database got marked bad. 
 
The function sqlrlAdminGetIndexInfo does not have a similar 
check of sqlrlAdminGetTabInfo (which is used to process the 
table functions SYSPROC.ADMIN_GET_TAB_COMPRESS_INFO_V97 and 
SYSPROC.ADMIN_GET_TAB_INFO_V97)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The table functions                                          * 
* SYSPROC.ADMIN_GET_INDEX_COMPRESS_INFOandSYSPROC.ADMIN_GET_INDE 
* do not have a check to skip incaesof nicknames.If the table  * 
* is data partitioned, the table functions causethedatabase    * 
* got marked bad.The function sqlrlAdminGetIndexInfo does not  * 
* have a similarcheck of sqlrlAdminGetTabInfo (which is used   * 
* to process thetable functions                                * 
* SYSPROC.ADMIN_GET_TAB_COMPRESS_INFO_V97                      * 
* andSYSPROC.ADMIN_GET_TAB_INFO_V97)                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.8 Fix Pack 3                        * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
Problem was first fixed in DB2 Version 9.8 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.03.2010
10.01.2011
10.01.2011
Problem solved at the following versions (IBM BugInfos)
9.8.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.3 FixList