Cause: The operation completed successfully.

Cause: Processing has reached the end of available input.

Cause: The input argument was not a buffer, file, or stream.

Cause: A parse or decode operation was requested without specifying input.

Cause: The requested input file could not be found, or was not readable.

Cause: The JavaScript Object Notation (JSON) parser encountered syntactically invalid JSON.

Cause: The JavaScript Object Notation (JSON) parser encountered an invalid sequence of characters following a backslash character.

Cause: The JavaScript Object Notation (JSON) parser detected a duplicate member key.

Cause: An attempt was made to begin parsing an input while a parsing operation was already in progress.

Cause: The requested character encoding was not supported by JavaScript Object Notation (JSON).

Cause: The parser encountered a sequence of bytes that were invalid for the specified character set.

Cause: An I/O error was encountered while reading input for parsing or decoding.

Cause: The parser or decoder encountered the end of the input source while still expecting more data.

Cause: The internal depth limit on the JavaScript Object Notation (JSON) hierarchy of containers (which may be objects, arrays, or both) was exceeded during a Document Object Model (DOM) read or write operation.

Cause: An event sequence to render the JavaScript Object Notation (JSON) included a closing event for an unknown object or array.

Cause: The JavaScript Object Notation (JSON) parser encountered a member key name that exceeded the internal maximum.

Cause: An I/O error was encountered while writing to the output stream.

Cause: The data overflowed the fixed-size output buffer.

Cause: The data overflowed the fixed-size output buffer.

Cause: The result of the JavaScript Object Notation (JSON) expression could not be rendered without an array wrapper.

Cause: The path expression resulted in a null result.

Cause: An operation requested a scalar value, but the selected value was an object, array, or sequence and could not be returned.

Cause: Additional data bytes were encountered after the expected end of input.

Cause: The binary decoder encountered a data length that exceeded or did not match the actual data value.

Cause: The binary decoder encountered an unrecognized operation code.

Cause: The binary decoder encountered invalid or inconsistent data while reading the input.

Cause: The internal depth limit on the JavaScript Object Notation (JSON) hierarchy of containers (which may be objects, arrays, or both) was exceeded.

Cause: An internal error occurred in the code.

Cause: The operating system ran out of memory.

Cause: A data value in a Document Object Model (DOM) was too large to be encoded in binary form.

Cause: A NULL pointer was detected as an internal error condition.

Cause: The JavaScript Object Notation (JSON) path expression could not be successfully parsed.

Cause: The specified array position was invalid.

Cause: In a comma-delimited set of array indexes, the array indexes were in descending order.

Cause: The field name exceeded 256 bytes.

Cause: The total length of all field names exceeded the 65536 byte limit.

Cause: An attempt was made to access either an element outside of the array bounds, or an object member outside of the list of members.

Cause: The string could not be interpreted as a numeric value.

Cause: The string could not be interpreted as a date or date/time.

Cause: The total size of the JavaScript Object Notation (JSON) objects exceeded the maximum allowed for JSON set-oriented storage.

Cause: The Query-By-Example (QBE) specification was invalid.

Cause: The JavaScript Object Notation (JSON) Patch operation encountered an infeasible operation and could not be completed.

Cause: Read-only JavaScript Object Notation (JSON) objects could not be modified by Document Object Model (DOM) operations.

Cause: This feature was not implemented yet.

Cause: A type conversion requested for JavaScript Object Notation (JSON) Path output could not be performed.

Cause: The JavaScript Object Notation (JSON) serializer encountered an incorrect event sequence and could not serialize the result.

Cause: An attempt was made to read a key from a Document Object Model (DOM) object node, but the key was not present in the DOM object node.

Cause: A Document Object Model (DOM) node could not be inserted below one of its own descendant nodes.

Cause: A Document Object Model (DOM) node could not be inserted because it is already present in the document node tree.

Cause: The input provided to the JSON parser was empty.

Cause: The string could not be converted to or from UTF-8.

Cause: The string supplied to 'eq_regex' or 'like_regex' could not be interpreted as a regular expression.

Cause: Internal code signals that a call to get a JSON_TABLE column value found no pre-generated value in the cache.

Cause: A DOM operation that requires an object node was given an array or scalar node as the target.

Cause: A DOM operation that requires an array node was given an object or scalar node as the target.

Cause: A DOM operation that requires a scalar node was given an object object or array node as the target.

Cause: A string representaion of a number was too large to be converted to an Oracle number.

Cause: An unexpected or superfluous comma was encountered while parsing an object or array.

Cause: A comma was expected between members of an object, or between items in an array.

Cause: An object member name and colon was not followed by a member value.

Cause: An object member name was not followed by a colon.

Cause: An object member name was not enclosed in double quotation marks, and either contained or started with a character that was not allowed.

Cause: A string value was not enclosed in double quotation marks.

Cause: A JavaScript Object Notation (JSON) number was encountered that

Cause: An invalid byte value was read from the JavaScript Object Notation (JSON) input. ASCII control characters are not allowed in JSON text.

Cause: A literal value was encountered that could not be interpreted as a JSON literal. Allowed JSON literals are 'true', 'false', and 'null'.

Cause: A member name or string value beginning with a quotation mark did not have a closing quotation mark.

Cause: A path step contained punctuation characters.

Cause: A backslash escape sequence was not enclosed in quotation marks.

Cause: An escape sequence beginning with a backslash contained invalid characters.

Cause: The surrogate pair was invalid. A surrogate pair must consist of a high surrogate followed by a low surrogate.

Cause: A subscript within an array step was too long to be interpreted.

Cause: An array range subscript had a start position greater than the end position.

Cause: The variable name was invalid. A variable name must be alphanumeric and cannot start with a number.

Cause: A path did not start with a dollar sign ($) character.

Cause: Trailing characters followed the end of the path.

Cause: An array step was empty.

Cause: The specified array position was invalid.

Cause: The array wildcard (*) character was not specified by itself in an array subscript.

Cause: The key wildcard (*) character did not appear by itself in a key step.

Cause: An array step had mismatching square bracket ([]) charaters.

Cause: An array step contained invalid characters and could not be interpreted.

Cause: A step beginning with a quotation mark did not have a closing quotation mark.

Cause: A key step contained invalid characters and could not be interpreted.

Cause: A JavaScript Object Notation (JSON) literal must be 'true', 'false', or 'null'.

Cause: A JavaScript Object Notation (JSON) literal must be 'true', 'false', or 'null'.

Cause: The value could not be interpreted as a number.

Cause: The numeric value could not be converted to binary because of an overflow.

Cause: The expression supplied to 'eq_regex' or 'like_regex' was not a valid regular expression.

Cause: The 'not_in' operator was specified in an expression.

Cause: Unexpected characters were present in the expression.

Cause: A comparison operation with an expression did not involve a path.

Cause: The expression after a not operator was not enclosed in parentheses.

Cause: The comparison was not against a JavaScript Object Notation (JSON) 'true' or 'false' literal.

Cause: A question mark introduced a filter that was enclosed in parentheses.

Cause: A parenthetical expression was missing a closing parenthesis.

Cause: Unexpected characters were present in the expression.

Cause: A Unicode character appeared outside of quotation marks.

Cause: After a path step, a '.' separator was expected.

Cause: The next path step started with an invalid character.

Cause: An '@' character appeared in the path outside of a predicate clause.

Cause: A '$' appeared in the path inside of a predicate clause.

Cause: A predicate expression was missing an operator or specified a function that was not valid.

Cause: A predicate expression contained a path expression on both the left and right sides of the operator.

Cause: A path expression had more than one predicate expression at the top level. At most, one predicate expression is allowed at the top level.

Cause: A path expression contained a predicate expression prior to the final step in the path. If an expression has a predicate at the top level, it must be the final step in the path.

Cause: The specified array range contained invalid characters. Array ranges are specified using the keyword 'to' between the start and end of the range.

Cause: The specified function is not valid.

Cause: A path expression contained too many levels of nested parentheses.

Cause: The domain of a type comparison cannot be determined because the types are incompatible and cannot be converted.

Cause: The argument to a function call does not have the correct data type and cannot be converted to the correct data type.

Cause: The JSON literal value cannot be converted to the data type required by the operation or comparison.

Cause: The values used for an in or not_in sequence must be of a uniform data type.

Cause: An array subscript appeared in a comma-separated list after a higher subscript or range.

Cause: A character appeared in a quoted path step or literal string without being escaped as required.

Cause: A zero length step appeared in a path without being enclosed in quotes. The sequence '..' implies a descendant that may not be an immediate child of the previous step.

Cause: The JavaScript Object Notation (JSON) Patch specification was not an array. A JSON Patch specification must be an array, listing an ordered series of operations to be performed.

Cause: The JavaScript Object Notation (JSON) Patch specification array contained some non-object members. Each element of the JavaScript Object Notation (JSON) Patch specification array must be an object describing a patch operation to be performed.

Cause: An object in a JavaScript Object Notation (JSON) Patch specification was missing an 'op' code.

Cause: The 'path' or 'from' clause in a patch operation could not be parsed.

Cause: The 'op' code could not be interpreted.

Cause: The operation contained a key that is not specified by JavaScript Object Notation (JSON) Patch.

Cause: The target path for an operation was not specified.

Cause: The path specified for a 'path' or 'from' field was not a string.

Cause: The 'from' path was specified for an operation that does not allow it. 'from' is only allowed in the 'move' and 'copy' operations.

Cause: A 'value' was specified for an operation that does not allow it. A 'value' is not allowed in 'remove', 'move', and 'copy'.

Cause: A 'move' or 'copy' operation was missing a 'from' path.

Cause: An 'add', 'replace', or 'test' operation was missing a target value.

Cause: The target 'path' specified is a child of the 'from' path.

Cause: The including rule for a parent node conflicted with the explicit rule asserted for a child node. The projection specification is invalid.

Cause: A projection specification was an array or JavaScript Object

Cause: The rule did not use 'true', 'false', 1, 0, "include", or "exclude".

Cause: A path was either invalid or NULL.

Cause: An argument to $id was not a number or string.

Cause: An array of values for $in, $nin, $all, or $id did not any values. The array of values must have at least one value.

Cause: An array of values for $in, $nin, $all, or $id contained object or array members. The array of values must contain only scalar values.

Cause: A minimum and maximum value were not specified for the $between operator. The $between operator must be given an array with a minimum and a maximum value.

Cause: The $near, $within, and $intersect operators were not used at the outermost level of the Query-By-Example (QBE).

Cause: The $near, $within, and $intersect operators were not given a GeoJSON object as the value of the $geometry key.

Cause: The $distance parameter was used with an operator other than $near. Only the $near operator may include values for $distance and $unit.

Cause: The $distance parameter was specified with a value that was not a JavaScript Object Notation (JSON) number.

Cause: The $unit parameter was not a JavaScript Object Notation (JSON) string. The $unit parameter should be a string specifying a unit of measure such as 'mile'. It may not be a number or JSON literal, nor an object or array.

Cause: The spatial operator contained a key that did not match the expected values. All spatial operators must have a $geometry value, and the $near operator may have $distance and $unit values. Other keys are not allowed.

Cause: The $near operator did not specify a value for $distance.

Cause: An empty object was found in the filter specification. An empty object is meaningless and not allowed in the filter specification.

Cause: A modifier operator was not followed by an object, or was followed by an object with no fields. Modifiers include $not, datatype casts such as $number, simple conversions such as $upper, and structural operators such as $type.

Cause: A $near, $within, or $intersect operator was not followed by an object containing the spatial parameters.

Cause: A modifier operator (such as $not) was used around a $and, $or, $nor, $id, or another modifier operator. Modifiers may not be used around those operators.

Cause: The value supplied to the $regex, $hasSubstring, $startsWith, or $like operators was not a JavaScript Object Notation (JSON) string.

Cause: The value supplied to an operator was not a JavaScript Object Notation (JSON) scalar value.

Cause: The value supplied to $eq, $ne, or $exists was not a JavaScript Object Notation (JSON) string or number.

Cause: The value supplied to $in, $all, $id, or $between was not an array.

Cause: An element of an array for $and, $or, or $nor was not an object.

Cause: The $id operator supplying document keys was not used at the outermost level of the Query-By-Example (QBE).

Cause: A downscoped sub-expression was used in the same scope as a normal filter condition.

Cause: An order by condition did not give an integer value. Objects, arrays, strings, and other literals are not allowed to specify ordering criteria.

Cause: The query specification root was an array or scalar. A query specification must be an object.

Cause: A $orderby specification was not an object or array. It may not be a JavaScript Object Notation (JSON) scalar.

Cause: A field of a $orderby array must specify a path.

Cause: The items in a $orderby array must be sort field specification objects. The objects must contain only fields for 'path', 'datatype', 'maxLength', and 'order'.

Cause: The $sqlJson was not used at the outermost level of the Query-By-Example (QBE).

Cause: The value supplied to $sqlJson was not an object.

Cause: The fields of a $sqlJson operator must all be path strings.

Cause: The $id operator supplying document keys was used multiple times in the Query-By-Example (QBE).

Cause: The parameter value was not a JSON literal 'true' or 'false'.

Cause: Two parameters were used together that are either disallowed in combination, or had conflicting values specified.

Cause: An array of target values for the logical operator was empty.

Cause: An input column value began with an opening quotation mark but had no closing quotation mark.

Cause: An unquoted input column value contains a quotation mark.

Cause: A column value contained a quoted value and another quoted or unquoted value, but had no delimiter separating the values.

Cause: A quoted column value had space characters before the opening quotation mark or after the closing quotation mark.