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

SQLCONNECT SETS DBNAME INTO DATA SOURCE NAME EVEN IF USER SPECIFIES
DBALIAS, THIS CAUSES -842/-1024 IN SUBSEQUENT API.

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
SQLConnect sets dbname into data source name even if user 
specifies dbalias, this causes SQL0842N or SQL1024N in 
subsequent API calls. 
 
The following scenario would fail if a database has more than 
one alias. 
NOTE: where dbAlias is an alias for dbName. 
 
Case 1: Subsequesnt connection request fails with SQL0842N 
(Already connected) 
 
SQLConnect(hDbc, dbName..); 
SQLConnect(hDbc, dbAlias..); 
 
Case 2: DB2 API (db2CfgGet in this case) reports SQL1024N (No 
connection) 
 
SQLConnect(hDbc, dbAlias..); 
cfgStruct.dbname = dbAlias; 
db2CfgGet(db2Version970, (void *)&cfgStruct, &sqlca);
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use CLI application against a database which has   * 
* more than one database alias(es).                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQLConnect sets dbname into data source name even if user    * 
* specifies dbalias, this causes SQL0842N or SQL1024N in       * 
* subsequent API calls.                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V9.8 FixPack 5 or later.               * 
****************************************************************
Local-Fix:
please remove dbalias.
Lösung
This problem was first fixed in DB2 V9.8 FixPack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.10.2011
19.06.2012
19.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.FP5
Problem behoben lt. FixList in der Version
9.8.0.5 FixList