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

DB2ADUTL FAILS WITH SQL1019 WHEN ACQUIRING INSTANCE CONNECTION T O
DETERMINE NODE NUMBER WHEN INSTANCE NAME IS LESS THAN 8 CHARAC

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
sqlegins API - which is used to acquires the current instants 
returns an illegal (space padded) instance name when the 
instance name is less than 8 characters. This causes db2adutl to 
fails to acquire an instance connection needed to determine the 
node number and  and automatically acquire the TSM password.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2ADUTL FAILS WITH SQL1019 WHEN ACQUIRING INSTANCE          * 
* CONNECTION TO DETERMINE NODE NUMBER WHEN INSTANCE NAME IS    * 
* LESS THAN 8 CHARACTERS                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10 fixpack FP4                               * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Fixed fixed in DB2 V10 FP4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.10.2013
09.06.2014
09.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList