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

DB2IUPDT MAY SET DB2AUTOSTART TO YES.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The instance registry variable, DB2AUTOSTART may be set to 
YES unexpectedly after running db2iupdt command 
even though DB2AUTOSTART is set to NO or it is not set 
explicitly before running db2iupdt.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 users.                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 3.  * 
****************************************************************
Local Fix:
Set DB2AUTOSTART manually with db2iauto command after running 
db2iupdt command.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 3.
Workaround
Set DB2AUTOSTART manually with db2iauto command after running 
db2iupdt command.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95486 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.05.2013
02.12.2013
02.12.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList