Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC98107 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
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

Lösung
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4).
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.12.2013
13.10.2014
13.10.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList