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

STMT_CONC PARAMETER IS NOT REPORTED BY A SELECT STATEMENT ON THE
SYSIBMADM.DBCFG VIEW OR SYSPROC.DB_GET_CFG TABLE FUNCTION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In version 9.7 some new database configuration parameters 
were  added. Amongst them the STMT_CONC statement 
concentrator parameter. Though its value is reported from a 
GET DB CFG command, it is not returned against a query on 
the SYSIBMADM.DBCFG view or 
SYSPROC.DB_GET_CFG table function. 
 
USERS AFFECTED: version 9.7 GA
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Only version 9.7 GA is affected                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In version 9.7 some new database configuration parameters    * 
* were  added. Amongst them the STMT_CONC statement            * 
* concentrator parameter. Though its value is reported from a  * 
* GET DB CFG command, it is not returned against a query on    * 
* the SYSIBMADM.DBCFG view or                                  * 
* SYSPROC.DB_GET_CFG table function.                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* You can get the current value of STMT_CONC using "db2 get db * 
* cfg"                                                         * 
****************************************************************
Local Fix:
Get the value of STMT_CONC using "db2 get db cfg"
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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
First fixed in version 9.7  Fixpak 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.08.2009
02.02.2010
02.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList