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

NO ERROR MESSAGE IS RETURNED WHEN THE DATA EXCEEDS JSON ARRAY SIZE.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When data/projection is larger than JSON array size, no error 
message is returned notifying the user, rather the command line 
returns silently: 
 
This is the output when trying to fetch data > 32K which is the 
max size of JSON array: 
 
nosql>db.testsize1000.find({"_id":"PWXXXXXXXXXXXX"},{"v.linkedEn 
tities.v.v.entityId":1}) 
nosql>Row 1: 
nosql> { 
"_id":"PWXXXXXXXXXXX" 
} 
nosql>CDJSN1206I "1" row(s) returned in "30" milliseconds. 
 
With this defect fix, the following error message will be 
returned: 
 
nosql>DB2 SQL Error: SQLCODE=-443, SQLSTATE=38553, 
SQLERRMC=JSON_BINARY2;jsonBinaryOrNull2;33675:Selected JSON data 
is too long, DRIVER=3.70.4 
nosql>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 10.5 Fix Pack 9 or higher                     * 
****************************************************************
Local Fix:
No Local Fix
Solution
First fixed in Db2 10.5 Fix Pack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.03.2017
29.09.2017
29.09.2017
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)