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

PARAMETERS STORED AS STRINGS ARE NOT APPLIED BY DB2CFIMP (ERROR -5060)

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Configuration parameters stored as strings by db2cfexp utility 
are not applied properly by db2cfimp on the target instance. 
Affected parameters are: 
 
SYSADM_GROUP 
DFT_MON_UOW 
DFT_MON_STMT 
DFT_MON_TABLE 
DFT_MON_BUFPOOL 
DFT_MON_LOCK 
DFT_MON_SORT 
DFT_MON_TIMESTAMP 
TRUST_ALLCLNTS 
SVCENAME 
 
For those parameters SQL5060N error messages are logged in 
db2diag.log
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix    * 
* Pack 4) or higher.                                           * 
****************************************************************
Local Fix:
Apply affected parameters manually.
available fix packs:
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
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4).
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.12.2013
13.10.2014
13.10.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList