DB2 - Problem description
Problem IT07170 | Status: Closed |
BLOBS ARE NOT HANDLED CORRECTLY WHEN FETCHING THE DATA FROM CURSORS OPENED WHEN CALLING THE PROCEDURE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - 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 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to v10.5 FP7 or later fixpacks * **************************************************************** | |
Local Fix: | |
Solution | |
Problem fixed in db2 v10.5 FP7 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.02.2015 19.01.2016 28.04.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |