suche 36x36
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 IT29206 Status: Geschlossen

SQLSETCONNECTATTRW() WITH SQL_ATTR_SESSION_GLOBAL_VAR ATTRIBUTEIS NOT
WORKING AS EXPECTED

Produkt:
DB2 CONNECT / DB2CONNCT / B10 - DB2
Problembeschreibung:
When application has SQLSetConnectAttrW() API call with
SQL_ATTR_SESSION_GLOBAL_VAR  attribute, it is working as
designed.  Client is not sending the attribute list to server
and resulting in unexpected error.

  memcpy(membuf, "SQL_COMPAT='NPS'", 17);
  membuf[17] = '';

  toWideChar(membuf, szAttribBuf);
  sql_rc = SQLSetConnectAttrW(hdbc, SQL_ATTR_SESSION_GLOBAL_VAR,
szAttribBuf, SQL_NTS);

When application calls like this, client is not sending the
SQL_COMPAT='NPS' to server.

In DRDA trace we see empty set statement flowing to server:
DDM Format: d0 SEND(AR) OBJDSS - Object Data Stream Structure
LL: 23 CORR: 0003 CHAINED: y CONT ON ERR: n SAME CORR FOR NEXT
DSS: n

NM: SQLSTT - SQL Statement
LL: 17 CP: 2414
DATA: (ASCII) (EBCDIC)
0000000007534554 20203D20FF .....SET = . .............

DDM Format: d0 SEND(AR) RQSDSS - Request Data Stream Structure
LL: 78 CORR: 0004 CHAINED: y CONT ON ERR: n SAME CORR FOR NEXT
DSS: y
Problem-Zusammenfassung:
****************************************************************
* USERS AFFECTED:                                              *
* DB2 CLI/ODBC Unicode API users                               *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 version 11.1.4.5                              *
****************************************************************
Local-Fix:
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.05.2019
23.02.2020
23.02.2020
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version