|
Problem IT21921
|
Status: Closed |
NO ERROR MESSAGE IS RETURNED WHEN THE DATA EXCEEDS JSON ARRAY SIZE. |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - 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 11.1 Mod 3 Fix Pack 3 or higher *
**************************************************************** |
| Local Fix: |
No Local Fix |
| available fix packs: |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Db2 11.1 Mod 3 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.08.2017
19.03.2018
19.03.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
