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

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

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Fixed fixed in DB2 V10 FP4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.10.2013
09.06.2014
09.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList