My Oracle Support Banner

Primary Note for Oracle JSON DB (Doc ID 2339484.1)

Last updated on JUNE 06, 2021

Applies to:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.

Details

 This primary note provides information for DBA's on Oracle JSON DB.

 

Ask Questions, Get Help, And Share Your Experiences With This Article

Would you like to explore this topic further with other Oracle Customers, Oracle Employees, and Industry Experts?
(Click here to join the discussion where you can ask questions, get help from others, and share your experiences with this specific article.)

Discover discussions about other articles and helpful subjects by clicking here to access the main My Oracle Support Community page for Oracle XDB.

Actions

General Concepts

  What is JSON?

JSON stands for JavaScript Object Notation. Even though JSON is based on a subset of the JavaScript Programming Language, it's a language-independent data format and like XML its relatively easy for humans to read and write, and easy for software to parse and generate. It is often used for serializing structured data and exchanging it over a network, typically between a server and web applications. Its widely used in web browsers and web servers.

 

 JSON DB Simple Definition

Oracle database provides a comprehensive implemention of SQL, for both analytics and batch processing. JSON held in the Oracle Database can be directly accessed via SQL, without the need to convert it into an intermediary form. JSON collections can be joined to other JSON collections or to relational tables using standard SQL queries.

Please refer to the following document for any of the Frequently Asked Questions (FAQ) on JSON DB:

Best Practices

 

 

Known issues

 

 

                    { "foo" : .0123 }

                    { "foo" : 0.0123 }

 

 

 

                    SQL> SELECT jt.* FROM j_purchaseorder, json_table(po_document, '$' COLUMNS (requestor VARCHAR2(32 CHAR) FORMAT JSON)) as "JT";

 

 

    1. Note that if you aren't receiving any rows it could be that no error is recorded and instead no rows are returned. The return an error ensure the "ERROR on ERROR" syntax like in the example: SQL> select json_value(po_document, '$.PONumber'
      RETURNING NUMBER ERROR ON ERROR) from purchaseOrder;
    2. If you are on 12.1.0.2, be sure you are on the latest Database Proactive Bundle Patch as this includes many wrong result issues.
    3. If (1) or (2) don't help to resolve your issue, please create an SR with Support providing a simple reproducible testcase with a README.txt with step by step instructions for reproducing the issue on a fresh new in-house database.

JSON Patch Bundles

 

 

 

Verify JSON/SODA Installation

 

 

JSON/SODA DEMOS/SCRIPTS/DOCUMENTATION/BLOGS:

JSON Demo Scripts

JSON DB documentation

JSON and SODA OTN which includes videos and technical briefs

SQL/JSON standard

JSON Blogs

SODA Blogs

 

 

Contacts

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Details
Actions
 General Concepts
 Best Practices
 Known issues
 JSON Patch Bundles
 Verify JSON/SODA Installation
 JSON/SODA DEMOS/SCRIPTS/DOCUMENTATION/BLOGS:
 JSON Demo Scripts
 JSON DB documentation
 JSON and SODA OTN which includes videos and technical briefs
 SQL/JSON standard
 JSON Blogs
 SODA Blogs
Contacts
References

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