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

DATABASE MANAGER PARAMETERS ARE RESET TO DEFAULT AFTER INSTANCE UPDATE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
After running db2iupdt all database manager parameters are reset 
to default
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 and Fix Pack 1                   * 
****************************************************************
Local Fix:
Use db2cfexp to store the settings before instance update and 
restore them using db2cfimp afterwards. 
Note: because of  APAR IC94404, parameters which were set to 
AUTOMATIC might need to be adjusted manually after the 
procedure.
available fix packs:
DB2 Version 10.5 Fix Pack 2 for Linux, UNIX, and Windows
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 DB2 Version 10.5 and Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.07.2013
26.08.2013
26.08.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.1 FixList