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

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

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
User affected: 
  Users of ODBC wrappers in InfoSphere Federation Server 
Problem description and summay: 
  See error description
Local Fix:
available fix packs:
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

Solution
Problem was fistly fixed in Version 10, FixPak 1. This 
fix should be applied on the federation Server.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
01.11.2012
01.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList