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

COPY PROCEDURE IN DBMS_LOB MODULE MIGHT FAIL AFTER 32KB DATA, ALTHOUGH
DBMS_LOB MODULE SUPPORTS LOB DATA UP TO 10MB.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
COPY procedure in DBMS_LOB module might fail after 32K bytes 
data, although DBMS_LOB module supports LOB data up to 10M 
bytes. 
 
In this situation, it gives the error: 
SQL0171N The data type, length or value of the argument for the 
parameter in position "3" of routine "DBMS_LOB.COPY_BLOB" is 
incorrect. Parameter name: "AMOUNT". 
 
Note that this error can also be seen if the parameter is wrong 
data type. So, it wouldn't pin point this exact issue.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 Fix Pack 4                           * 
****************************************************************
Local Fix:
Not available.
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.5 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.02.2014
08.09.2014
08.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList