Fixes are available
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
Closed as program error.
When you SELECT from Microsoft SQL Server nickname's char/varchar column, if remote table contains some multibyte encoded string, and those string's character-length exceeds certain value, SELECT statement will fail with following error message: SQL0901N The SQL statement failed because of a non-severe system error. Subsequent SQL statements can be processed. (Reason "Negative output data length".) SQLSTATE=58004 You can reproduce it by the following steps. 1) Insert some multibyte encoded string into remote SQL Server table's char/varchar column, by SQL Server Management Studio. CREATE TABLE [dbname].[schemaname].[tablename](ID int, MESSAGE char(10)); INSERT INTO [dbname].[schemaname].[tablename] VALUES(1, '?????'); 2) Create nickname for remote table at Federation Server. Then select from the nickname with char/varchar column CREATE NICKNAME nickname FOR servername.username.tablename; SELECT * FROM nickname; The reason of this error is that, when SQL Server Wrapper retrieves data length of character type column , ODBC driver returns SQL_NO_TOTAL indicator, whose value is -4, in following two scenarios: 1) the local data buffer is inadequate for remote data. 2) The driver cannot determine the number of bytes of long data that still available to return in an output buffer. (http://msdn.microsoft.com/en-us/library/ms713532(VS.85).aspx) SQL Server incorrectly treats this indicator as a length value.
Users affected: Users of the MS SQL Server wrapper in InfoSphere Federation Server Problem description and summary: See error description.
Problem was first fixed in Version 9.5 FixPak 6 (s100805 ). This fix should be applied on Federation Server.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
19 September 2010