Subscribe to this APAR
By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.
| APAR (Authorized Program Analysis Report) |
Abstract
LIC-DB-OTHER ALLOW DUPLICATE KEYS IN JSON_OBJECT AND
JSON_OBJECTAGG
Error Description
Allow duplicate keys in JSON_OBJECT and JSON_OBJECTAGG.
When the result of the JSON_OBJECT or JSON_OBJECTAGG function is
a JSON object string having identical keys, the result is
considered invalid and the query will fail with SQL State
22030.
An example of an invalid JSON string would be
{"key1":"a","key1":"b"}.
Problem Summary
Please see the ERROR DESCRIPTION section.
Problem Conclusion
Application of this fix will change the default behavior of the
JSON_OBJECT and JSON_OBJECTAGG functions for duplicate keys.
When a duplicate key is generated, no error will be signaled and
the query will complete successfully. To revert to the previous
behavior and generate an error under these conditions, apply fix
XXXXXXX and use the WITH UNIQUE KEYS clause.
Temporary Fix
Comments
Circumvention
PTFs Available
R720 MF65142 9123
R730 MF65146 9116
Affected Modules
Affected Publications
Summary Information
| Status............................................ | CLOSED PER |
| HIPER........................................... | No |
| Component.................................. | 9400DG3DBMF6 |
| Failing Module.......................... | RCHMGR |
| Reported Release................... | R720 |
| Duplicate Of.............................. |
IBM i Support
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information
Document Information
Modified date:
08 September 2021