home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC84532 Status: Geschlossen

CAN NOT CREATE NICKNAME FOR CLASSIC FEDERATION OBJECT BY USING ODBC WRAPPER
IN V95FP9

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Classic Federation Server ODBC driver doesn't support ODBC 3.0 
type SQL_C_SBIGINT, so it 
block creating nickname for Classic Federation Server like this: 
 
You may meet the following error when creating nickname for a 
classic federation object by using odbc wrapper: 
create nickname nick1 for <your_server>.<schema>.<table1> 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL1822N  Unexpected error code "HY003" received from data 
source "<your_server>". 
Associated text and tokens are " SQLBindCol - Error code: 
x00560051. Message 
look-up f".  SQLSTATE=560BD 
 
The x00560051 error means Classic Federation Server SQLBindCol 
doesn't support SQL_C_SBIGINT ODBC C type. 
 
You may be also failed to create nickname with such kind of ODBC 
drivers which is not totally abide by ODBC 3.x specification.
Problem-Zusammenfassung:
User affected: 
  Users of ODBC wrappers in InfoSphere Federation Server 
Problem description and summay: 
  See error description
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem was fistly fixed in Version 10, FixPak 1. This 
fix should be applied on the federation Server.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.06.2012
01.11.2012
01.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList