SODA Restrictions (Reference)

Restrictions that apply across SODA implementations are described.

• Document size:

  • 26ai JSON collection tables and views have an individual document size limit of 32 MB.

  Note: You must ensure that you have sufficient RAM to support your workload.

• JSON document content:

  In SODA, JSON content must conform to the JSON RFC 8259 standard, if database initialization parameter compatible is at least 20, or to the RFC 4627 standard, if compatible is less than 20. RFC 8259 support includes RFC 4627 support (and RFC 7159 support).

  In Oracle Database release 19c and prior, only RFC 4627 was supported. RFC 4627 allows only a JSON object or an array, not a scalar, at the top level of a JSON document. For example, according to RFC 8259, the string value "hello" is, by itself, valid JSON content; but according to RFC 4627, it is not.

  In addition, SODA JSON content can be UTF-8 or UTF-16 (big endian (BE) or little endian (LE)). Although RFC 4627 also allows UTF-32 (BE and LE) encodings, SODA does not support them. Some implementations may support additional, non-Unicode, encodings.

  See Also:

  • IETF RFC 8259 for the JSON RFC 8259 standard

  • IETF RFC 4627 for the JSON RFC 4627 standard