JSON Database Patch Bundle Details (Doc ID 1992767.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Details

• This article is intended to provide the latest information about the Oracle JSON Merge Patch Bundles. This note will be constantly updated to reflect the latest patch bundle as they become available.

• The JSON bundle patches contain a number of required functional and performance fixes. It should be noted that JSON Patch Bundles are cumulative. This means that JSON Patch Bundle 2 for example, includes patches from JSON Patch Bundle 1 and also additional JSON patch fixes.

• The JSON patches are included in DBBP starting with DBBP13. It is recommended that JSON customers upgrade to the latest version which is 12.1.0.2.160419, or apply the latest Oracle JSON merge patch for releases earlier than DBBP13.

• It should be noted, that each 12.1.0.2 Bundle Patches for Engineered Systems and DB In-Memory include fixes for both Engineered Systems and for DB In-Memory. They can be used on both Exadata and non-Exadata systems, and can be used for both RAC and non-RAC configurations.

• This note only focuses on DBBP and not Database Patch Set Updates(DBPSU). DBPSU's don't include JSON Patch Bundles, whereas DBBP do include JSON Patch Bundles. The JSON Patch Bundles must be applied on top of DBPSU's. It should be noted, that customer's should be on DBBP if they are using the functionality of JSON Database and not DBPSU's.

• Many of the JSON patches listed below are unpublished so further details cannot be seen when clicking on the hyperlinks.

Patch 20080249: JSON Patch Bundle 1

The following are the bugs fixed by this patch:

Bug 18727933: NOT OPERATOR IS NOT SUPPORTED FOR JSON PATH PREDICATE
Bug 18758877: REDEFINITION ERROR IN FILE JZNENG.H
Bug 18778801: DATA GUIDE CALLBACK HOOK IN JZNENGRUN IS EXECUTED BEFORE ERROR CHECK
Bug 18803726: MISSING MULTIMATCH FLAG SET IN JZNP.C
Bug 18810904: JSON PATH WITH PREDICATE INCORRECT RESULTS FOR ARRAY OF SCALARS
Bug 18895170: JSON_QUERY WITH ASIS OPTION RETURNING NULL WHEN JSON VALUE IS TRUE
Bug 18952766: BSON DECODER FAILS ON BIG-ENDIAN PLATFORMS
Bug 18999568: PRESENCE OF  WITHIN A KEY CAUSES JSON_VALUE TO FAIL DURING QUERY
Bug 19130152: NESTED PREDICATES NOT WORKING
Bug 19131386: CAST UB1 to from QJSNGFORMAT
Bug 19131607: IS JSON SHOULD USE JZNEVENTSOURCEVALIDATE INSTEAD OF MORE COSTLY JZNENGRUN
Bug 19146474: CRASH IN QJSNTGETQBCDEF
Bug 19168167: ORA 600 WHEN USING KEYWORD IN COLUMN NAME
Bug 19248279: MAKE PREDICATE PARSER ALWAYS ON
Bug 19313563: JSON SERIALIZER REQUIRES NULL TERMINATED STRINGS FOR NUMBER EVENTS
Bug 19317646: MOVE JSON PL/SQL COLLECTION API TO RDBMS-ADMIN
Bug 19327391: EXPRESSION == FALSE NOT WORKING WITH PREDICATES
Bug 19364502: BSON DECODER NEEDS INTERNAL VALIDATOR FOR IS JSON
Bug 19440520: JZUNNUMTOSTRING REQUIRES NULL TERMINATED STRING
Bug 19448499: JSON_TEXTCONTAINS TURNS OFF WILDCARD MATCH
Bug 19461428: CHECK FOR JSON DURING DOWNGRADE
Bug 19468612: DEFAULT LEXERS FOR JSON REST SERVICES
Bug 19547774: NEED TO SWITCH OFF END PAIR
Bug 19566592: WRONG RESULT WITH NEW PATH PARSER
Bug 19571055: PERF ENHANCEMENTS IN JZNENG.C
Bug 19571082: LRGISM2C ORA 20000 DRG-10700
Bug 19590877: BIND VARIABLES DO NOT WORK IN CERTAIN CASES
Bug 19632912: LIKE_REGEX DOES NOT WORK WITH BIND VARIABLES
Bug 19647503: TESTING THE RESULT OF AN EXPRESSION FOR TRUE/FALSE DOESN'T PARSE
Bug 19680796: CHECK FOR COMPATIBILITY IN JSON OPERATORS
Bug 19701015: JSON PATH ENGINE PRODUCES WRONG RESULTS FOR JSON_EXISTS
Bug 19705781: JSON_EXISTS REGULAR EXPRESSIONS WRONG RESULTS
Bug 19769625: JSON_EXISTS PREDICATES FAIL WITH BIND VARIABLE FROM IN STATEMENT
Bug 19784751: LIKE_REGEX IN PREDICATE PATH EXPRESSION CAUSED QUERY TO CRASH
Bug 19799847: INCONSISTENT RESULTS FOR QUERY W PREDICATE EXPR W JSON-ENABLED TEXT IDX
Bug 19811709: JZNENG.C SHOULD NOT USE LXREGEXEC2
Bug 19817386: JSON_EXISTS IN OPERATOR WRONG RESULTS - BEHAVES LIKE STARTSWITH
Bug 19824871: JSON_EXISTS PRODUCES WRONG RESULTS WITH SUPPOSEDLY EQUIVALENT EXPRESSIONS
Bug 19859472: REMOVE JSON STUFF FROM KOKU.C
Bug 19880190: JSON_VALUE DATE AND TIMESTAMP RETURNS DON'T WORK PROPERLY
Bug 19886165: JSON COLLECTION PL SQL APIS HAVE AN INCORRECT LIMIT FOR VARCHAR2 CONTENT
Bug 19889230: JSON_TABLE NOT USING LAX MODE
Bug 20011897: SYNC SODA SQL FILES WITH XDK
Bug 20052269: DEFAULT FOR FORMAT JSON CLAUSE SHOULD BE 'TEXT'

Patch 20885778: JSON Patch Bundle 2

• JSON Patch Bundle 2 includes all patches from JSON Patch Bundle 1 plus the following are the bugs fixed by this patch:

Bug 19313563:   JSON SERIALIZER REQUIRES NULL TERMINATED STRINGS FOR NUMBER EVENTS
Bug 19440520:   JZUNNUMTOSTRING REQUIRES NULL TERMINATED STRING
Bug 19448499:   JSON_TEXTCONTAINS() TURNS OFF WILDCARD MATCH
Bug 18952766:   BSON DECODER FAILS ON BIG-ENDIAN PLATFORMS
Bug 19364502:   BSON DECODER NEEDS INTERNAL VALIDATOR FOR IS JSON
Bug 18727933:   NOT OPERATOR(!) IS NOT SUPPORTED FOR JSON PATH PREDICATE
Bug 18758877:   REDEFINITION ERROR IN FILE JZNENG.H
Bug 18778801:   DATA GUIDE CALLBACK HOOK IN JZNENGRUN IS EXECUTED BEFORE ERROR CHECK
Bug 18803726:   MISSING MULTIMATCH FLAG SET IN JZNP.C
Bug 18810904:   JSON PATH WITH PREDICATE INCORRECT RESULTS FOR ARRAY OF SCALARS
Bug 18895170:   48759: JSON_QUERY WITH ASIS OPTION RETURNING NULL WHEN JSON VALUE IS 'TRUE'
Bug 18999568:   48759:PRESENCE OF $ WITHIN A KEY CAUSES JSON_VALUE TO FAIL DURING QUERY
Bug 19130152:   NESTED PREDICATES NOT WORKING
Bug 19131386:   CAST UB1 <-> QJSNGFORMAT
Bug 19131607:   IS JSON SHOULD USE JZNEVENTSOURCEVALIDATE INSTEAD OF MORE COSTLY JZNENGRUN
Bug 19146474:   CRASH IN QJSNTGETQBCDEF
Bug 19168167:   48759:ORA 600 WHEN USING KEYWORD IN COLUMN NAME  
Bug 19248279:   48759: MAKE PREDICATE PARSER ALWAYS ON
Bug 19317646:   48759: MOVE JSON PL/SQL COLLECTION API TO /RDBMS/ADMIN/
Bug 19327391:   EXPRESSION == FALSE NOT WORKING WITH PREDICATES
Bug 19461428:   CHECK FOR JSON DURING DOWNGRADE
Bug 19468612:   DEFAULT LEXERS FOR JSON REST SERVICES
Bug 19547774:   NEED TO SWITCH OFF END PAIR
Bug 19566592:   WRONG RESULT WITH NEW PATH PARSER
Bug 19571055:   PERF ENHANCEMENTS IN JZNENG.C  
Bug 19571082:   LRGISM2C: ORA-20000/ DRG-10700
Bug 19590877:   BIND VARIABLES DO NOT WORK IN CERTAIN CASES
Bug 19632912:   LIKE_REGEX DOES NOT WORK WITH BIND VARIABLES
Bug 19647503:   TESTING THE RESULT OF AN EXPRESSION FOR TRUE/FALSE DOESN'T PARSE
Bug 19680796:   CHECK FOR COMPATIBILITY IN JSON OPERATORS
Bug 19701015:   JSON PATH ENGINE PRODUCES WRONG RESULTS FOR JSON_EXISTS
Bug 19705781:   JSON_EXISTS REGULAR EXPRESSIONS WRONG RESULTS
Bug 19769625:   JSON_EXISTS PREDICATES FAIL WITH BIND VARIABLE FROM IN STATEMENT
Bug 19784751:   47322:LIKE_REGEX IN PREDICATE PATH EXPRESSION CAUSED QUERY TO CRASH
Bug 19799847:   47322:INCONSISTENT RESULTS FOR QUERY W/ PREDICATE EXPR W/ JSON-ENABLED TEXT IDX
Bug 19811709:   JZNENG.C SHOULD NOT USE LXREGEXEC2
Bug 19817386:   JSON_EXISTS IN OPERATOR WRONG RESULTS:   BEHAVES LIKE STARTSWITH
Bug 19824871:   JSON_EXISTS PRODUCES WRONG RESULTS WITH SUPPOSEDLY EQUIVALENT EXPRESSIONS
Bug 19859472:   REMOVE JSON STUFF FROM KOKU.C
Bug 19880190:   JSON_VALUE DATE AND TIMESTAMP RETURNS DON'T WORK PROPERLY
Bug 19886165:   JSON COLLECTION PL/SQL APIS HAVE AN INCORRECT LIMIT FOR VARCHAR2 CONTENT
Bug 19889230:   JSON_TABLE NOT USING LAX MODE
Bug 20011897:   SYNC SODA SQL FILES WITH XDK
Bug 20052269:   DEFAULT FOR FORMAT JSON CLAUSE SHOULD BE 'TEXT'
Bug 20577490:   ORA-40441 ON COMPRESSION AL32UTF JSON_TABLE
Bug 19583624:   48759:JSON_TABLE QUERIES DO NOT WORK WHEN PQ IS ENFORCED IN SESSION
Bug 19933147:   JSON_VALUE RETURNING TIMESTAMP DOES NOT WORK
Bug 19952975:   PARFAIT ISSUES IN XDKC SOURCE CODE.
Bug 19982584:   JZNTOK.C AND JZNP.C CONTAIN HARD-WIRED LIMITS
Bug 19988852:   (FXD) JSON_EXISTS INEQUALITIES WORK STRANGELY FOR JSON LITERALS
Bug 20009569:   JSON C DEAD CODE SHOULD BE ELIMINATED
Bug 20011646:   JSON_TABLE INCORRECT RESULTS AND FORMATTING
Bug 20061399:   (FXD) JSON_EXISTS FAILS WITH NON-ZERO/NON-WILDCARD ARRAY STEPS
Bug 20233181:   THE EVALUATION OF REGULAR EXPRESSION FAILED IN JSON QUERY
Bug 20703629:   SYNC SODA SQL FILES WITH XDK
Bug 20707932:   JSON_TABLE DEFAULT VALUE IS CORRUPTED
Bug 20717091:   MOST QUERIES WITH EMPTY PATH STEPS GIVE ERROR WHEN JSON TEXT INDEX IS USED
Bug 20800890:   JSON_TABLE WITH NUMBER(3,2) COLUMN RETURN WRONG RESULT.
Bug 20801783:   DATE AND TIMESTAMP NEEDS TO BE SUPPORTED IN JSON_TABLE
Bug 20565112:   (FXD) INCORRECT RESULTS FOR JSON_EXISTS(...) QUERY
Bug 20565133:   (FXD) INCORRECT RESULTS FOR JSON_EXISTS(...) QUERY

Patch 24836374: JSON Patch Bundle 3

• JSON Patch Bundle 3 includes all patches from JSON Patch Bundle 1 and 2 plus the following are the bugs fixed by this patch:

Bug 22351417: 47322:JSON DATA CORRUPTED DURING LOAD BY DIRECT PATH SQL LOADER
Bug 22460450: 47322:INSERT FAILS FOR JSON CLOB COLUMN WHEN COMPRESSION ENABLED
Bug 20700049: Memory corruption / ORA-7445 [LpxMemAlloc] from JSON query
Bug 20884085: Memory corruption / ORA-600 / ORA-7445 from SQL using JSON_VALUE on nested arrays
Bug 21186638: JSON_QUERY on NUMBER / DATE are not rendered properly with PRETTY flag
Bug 21275387: JSON_EXISTS(...) with "!" operator can produce wrong results

•  Patch 24968615 DATABASE PROACTIVE BUNDLE PATCH 12.1.0.2.170117

Actions

 Specifics on 12.1.0.2.8 and 12.1.0.2.10

• It should be noted that 12.1.0.2.8 and 12.1.0.2.10 Bundle Patch 10 for Engineered Systems and DB In-Memory can be used on both Exadata and non-Exadata systems. There are instructions in the README.txt, on how to install this on a database.

 Details on 12.1.0.2.13 Database Bundle Patch

• If you plan to use json functionality with DBBP13, an additional <Bug:22030856> must be applied and is mandatory for the JSON functionality to work correctly.
• JSON Bundled Patch 2 is included in DBBP13
• DBBP13 will include the json bundled patch 1 and patch 2.
• JSON functionality in 12.1.0.2.13 and above has a dependency on Oracle Text.
  • If the user plans to use the JSON functionality in DBBP13, then the user must make sure Oracle Text is installed before installing DBBP13. Please note, it is only supported to install Oracle Text by using DBCA. Manual installation/deinstallation of Oracle Text is not supported in 12.1.0.x. You now have to use the Database Configuration Assistant (DBCA) to add Oracle Text.
  • If the user plans to use the JSON functionality in DBBP13, and the user already has DBBP13 installed but not Oracle Text. Then they must install Oracle Text first. And then rerun the datapatch.sql script included in DBBP13 to complete the installation of JSON support with DBBP13.
  • If they do not plan to use JSON functionality, they can proceed with installing DBBP13 without installing Oracle Text.

 Details on 12.1.0.2.160419 Database Bundle Patch

• JSON Bundle Patch 2 is included in DBBP160119.
• DBBP160119 will include the JSON bundled patch 1 and patch 2.
• Note, starting from April 2016 the bundle name has been changed to "Database Proactive Bundle Patch" from "Database Patch for Engineered Systems and Database In-Memory".

• JSON functionality in 12.1.0.2.160119 has a dependency on Oracle Text. For further information on this refer to details listed above from 12.1.0.2.13.

Details on 12.1.0.2.160719 Database Bundle Patch

• JSON Bundle Patch 3 is included in DBBP160719.
• DBBP160719 will include the JSON bundled patch 1, patch 2 and patch 3.
• It should be noted that JSON Bundle Patch 3 cannot be downloaded individually. You must install DBBP160719 or higher version to get JSON Bundle Patch 3.

Details on 12.1.0.2.170531 WINDBBP

• JSON Bundle Patch 2 is included in WINDBBP170531.
• WINDBBP170531 will include the JSON bundled patch 1 and patch 2.
• It should noted that WINDBBP170531 is cumulative. This means that higher versions of WINDBBP will include JSON bundle patch 2 fixes.

 Current Recommended Oracle JSON Merge Patch

• V 12.1.0.2 Recommended JSON Merge Patches. As seen in the table below, that shows the JSON Patch Bundle numbers and associated patches, JSON Patch Bundle 1 can be applied on top of 12.1.0.2.0 whereas JSON Patch Bundle 2 needs to be applied on top of 12.1.0.2.8 and/or 12.1.0.2.10 DATABASE PATCH FOR ENGINEERED SYSTEMS AND DB IN-MEMORY.

How to get a Oracle JSON Merge Patch?

1. Login to My Oracle Support (MOS)
2. Go to Patches & Updates TAB ==>Under Oracle Server/Tools, use the Hyperlink : Latest Patchsets
3. Select "Simple Search"
4. Search by "Patch Number(s)"
5. Patch # ==> enter the Merge Patch number
6. Platform or Language ==> enter your Platform
7. Click GO

Contacts

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.