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

SQL0433N WITH UTL_MAIL.SEND_ATTACH_RAW WHEN ATTACHMENT IS LARGER THAN 1MB

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
UTL_MAIL.SEND_ATTACH_RAW can fail with an SQL0433N error when it 
is invoked with an input "attachment" argument that is greater 
than 1MB. 
 
Example: 
 
>db2 "call 
utl_mail.send_attach_raw('test@ibm.com','test@ibm.com',null,null 
,'my attachment','my message',null,null, (select blobcol from 
mytbl fetch first row only),null,'application/pdf','test.pdf')" 
 
SQL0433N  Value 
"JVBERi0xLjMNJeLjz9MNCjI5MTMgMCBvYmoNPDwgDS9MaW5lYXJpemVkIDEg" 
is too long.  SQLSTATE=22001 
 
 
This is despite the fact that our documentation states that an 
attachment can be at least 10MB in length. 
http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com. 
ibm.db2.luw.apdv.sqlpl.doc/doc/r0055178.html
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5, Fix Pack 7                      * 
****************************************************************
Local Fix:
n/a
Solution
First fixed in DB2 Version 10.5, Fix Pack 7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.06.2015
01.02.2016
01.02.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 FixList