home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT07116 Status: Closed

BLOBS ARE NOT HANDLED CORRECTLY WHEN FETCHING THE DATA FROM CURSORS OPENED
WHEN CALLING THE PROCEDURE.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Blob columns are not handled correctly in the output of queries 
called from inside procedures 
 
CLP example below can be used to reproduce the bug: 
 
create table myTable (blobCol blob(10)); 
insert into myTable values (blob(x'1122334455')), 
(blob(x'112233')), (blob(x'11')), (blob(x'667788')), 
(blob(x'66')), (blob(x'AABBCCDDEEFF')), (blob(x'AABBCC')); 
 
create or replace procedure myProc() 
  dynamic result sets 1 
  begin 
    declare txt varchar(30) default 'select blobCol from 
myTable' ;-- 
    declare cur cursor with return to client for stmt ;-- 
    prepare stmt from txt ;-- 
    open cur ;-- 
  end ; 
 
-- call query from inside procedure => wrong results 
call myProc(); 
 
  Result set 1 
  -------------- 
 
  BLOBCOL 
  ------------------------------------------- 
  x'1122334455' 
  x'112233'455' 
  x'11'233'455' 
  x'667788'455' 
  x'66'788'455' 
  x'AABBCCDDEEFF' 
  x'AABBCC'DEEFF' 
 
  7 record(s) selected. 
 
  Return Status = 0 
 
-- expected results from same query 
select blobCol from myTable; 
 
BLOBCOL 
----------------------- 
x'1122334455' 
x'112233' 
x'11' 
x'667788' 
x'66' 
x'AABBCCDDEEFF' 
x'AABBCC' 
 
  7 record(s) selected. 
 
drop table myTable;
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 CLP users using db2 V10.1                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1.5 and later                             * 
****************************************************************
Local Fix:
Solution
Problem fixed from DB2 V10.1.5 onwards
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.02.2015
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList