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 IC98386 Status: Geschlossen

DB2CFEXP/DB2CFIMP UTILITIES FAIL TO EXPORT/IMPORT THE CORRECT SECURITY TYPE
FOR NODE CREATED WITH SSL SECURITY.

Produkt:
DB2 CONNECT / DB2CONNCT / A50 - DB2
Problembeschreibung:
If you have created a node with SSL security, the db2cfexp 
utility will fail to export the correct security type for this 
node : the generated configuration profile will contain 
security=0 instead of security=2. 
 
Then, the db2cfimp utility will create the node with the wrong 
security type, even if you manually change the parameter 
security to 2 in the configuration profile generated by the 
db2cfexp utility.
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:
n/a
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
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.12.2013
08.09.2014
27.10.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList