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

DEFAULT VALUE FOR SHEAPTHRES_SHR DATABASE CONFIGURATION PARAMETER
IS NOT AUTOMATIC

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The SHEAPTHRES_SHR database configuration parameter is not set 
to AUTOMATIC by default.  Hence, when resetting the database 
configuration file (using RESET DB CONFIG command for example), 
or when creating a database with AUTOCONFIGURE APPLY NONE 
specified, SHEAPTHRES_SHR is not automatic, though it should be. 
 
For more information about how this configuration parameter can 
affect your environment, look it up in Information Center.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 for Linux, Unix and Windows Version 9.7 GA servers   * 
* through to Version 9.7 Fix Pack 2 relying on SHEAPTHRES_SHR  * 
* being automatic by default according to the documentation.   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The SHEAPTHRES_SHR database configuration parameter logic is * 
* not setting the value to automatic by default.               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 Version 9.7 Fix Pack 3 or manually update          * 
* SHEAPTHRES_SHR parameter to automatic.                       * 
****************************************************************
Local Fix:
Update SHEAPTHRES_SHR database configuration parameter to 
automatic.
available fix packs:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 9.7 Fix Pack 3 and all 
subsequent Fix Packs.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC69081 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.06.2010
23.09.2010
23.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList