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

CHANGE TO REVERT BACK DB2AUTOSTART REGISTRY VARIABLE BEHAVIOUR WITHIN
DB2ICRT AS WAS IN DB2 VERSION 9.7

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
This APAR is to revert default db2icrt behavior in DB2 version 
10, where DB2AUTOSTART registry variable was set by default to 
DB2AUTOSTART=YES. 
Once APAR is implemented, DB2AUTOSTART registry variable is not 
set by default when running db2icrt. 
 
This change is to stay consistent with the previous releases.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 10.5 FixPack 3                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 10.5 FixPack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.07.2013
04.03.2014
04.03.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList