42 JZN-00000 to JZN-00665
- JZN-00000: Normal, successful completion
-
Cause: The operation completed successfully.
- JZN-00001: End of input
-
Cause: Processing has reached the end of available input.
- JZN-00002: Invalid argument
-
Cause: The input argument was not a buffer, file, or stream.
- JZN-00003: Input not specified
-
Cause: A parse or decode operation was requested without specifying input.
- JZN-00004: Cannot open input file
-
Cause: The requested input file could not be found, or was not readable.
- JZN-00005: Syntax error
-
Cause: The JavaScript Object Notation (JSON) parser encountered syntactically invalid JSON.
- JZN-00006: Invalid escape sequence
-
Cause: The JavaScript Object Notation (JSON) parser encountered an invalid sequence of characters following a backslash character.
- JZN-00007: Object member key is not unique
-
Cause: The JavaScript Object Notation (JSON) parser detected a duplicate member key.
- JZN-00008: Parse already in progress
-
Cause: An attempt was made to begin parsing an input while a parsing operation was already in progress.
- JZN-00009: Unsupported encoding
-
Cause: The requested character encoding was not supported by JavaScript Object Notation (JSON).
- JZN-00010: Invalid byte sequence in character data
-
Cause: The parser encountered a sequence of bytes that were invalid for the specified character set.
- JZN-00011: Error reading input
-
Cause: An I/O error was encountered while reading input for parsing or decoding.
- JZN-00012: Premature end of input
-
Cause: The parser or decoder encountered the end of the input source while still expecting more data.
- JZN-00013: Stack overflow
-
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.
- JZN-00014: Stack underflow
-
Cause: An event sequence to render the JavaScript Object Notation (JSON) included a closing event for an unknown object or array.
- JZN-00015: Name too long
-
Cause: The JavaScript Object Notation (JSON) parser encountered a member key name that exceeded the internal maximum.
- JZN-00016: Serializer stream error
-
Cause: An I/O error was encountered while writing to the output stream.
- JZN-00017: Serializer buffer error
-
Cause: The data overflowed the fixed-size output buffer.
- JZN-00018: Input to serializer is too large
-
Cause: The data overflowed the fixed-size output buffer.
- JZN-00019: Cannot print without array wrapper
-
Cause: The result of the JavaScript Object Notation (JSON) expression could not be rendered without an array wrapper.
- JZN-00020: Empty result
-
Cause: The path expression resulted in a null result.
- JZN-00021: Value to be printed was not scalar
-
Cause: An operation requested a scalar value, but the selected value was an object, array, or sequence and could not be returned.
- JZN-00022: Extra data after end of input
-
Cause: Additional data bytes were encountered after the expected end of input.
- JZN-00023: Length does not match data
-
Cause: The binary decoder encountered a data length that exceeded or did not match the actual data value.
- JZN-00024: Unrecognized data type or code
-
Cause: The binary decoder encountered an unrecognized operation code.
- JZN-00025: Invalid binary data
-
Cause: The binary decoder encountered invalid or inconsistent data while reading the input.
- JZN-00026: Too many levels of nesting
-
Cause: The internal depth limit on the JavaScript Object Notation (JSON) hierarchy of containers (which may be objects, arrays, or both) was exceeded.
- JZN-00027: Internal error
-
Cause: An internal error occurred in the code.
- JZN-00028: Out of memory
-
Cause: The operating system ran out of memory.
- JZN-00029: Data member too large
-
Cause: A data value in a Document Object Model (DOM) was too large to be encoded in binary form.
- JZN-00030: NULL pointer for required context
-
Cause: A NULL pointer was detected as an internal error condition.
- JZN-00031: Invalid path expression
-
Cause: The JavaScript Object Notation (JSON) path expression could not be successfully parsed.
- JZN-00032: Invalid array position in path expression
-
Cause: The specified array position was invalid.
- JZN-00033: Invalid order of array indexes
-
Cause: In a comma-delimited set of array indexes, the array indexes were in descending order.
- JZN-00034: Field name too long
-
Cause: The field name exceeded 256 bytes.
- JZN-00035: Total field names too long
-
Cause: The total length of all field names exceeded the 65536 byte limit.
- JZN-00036: Array position out of bounds
-
Cause: An attempt was made to access an element outside of the array bounds.
- JZN-00037: Invalid number
-
Cause: The string could not be interpreted as a numeric value.
- JZN-00038: Invalid date/time
-
Cause: The string could not be interpreted as a date or date/time.
- JZN-00039: Size overflow for JSON set encoding
-
Cause: The total size of the JavaScript Object Notation (JSON) objects exceeded the maximum allowed for JSON set-oriented storage.
- JZN-00040: Invalid specification
-
Cause: The Query-By-Example (QBE) specification was invalid.
- JZN-00041: JSON Patch operation could not be completed
-
Cause: The JavaScript Object Notation (JSON) Patch operation encountered an infeasible operation and could not be completed.
- JZN-00042: Modification not allowed on read-only object
-
Cause: Read-only JavaScript Object Notation (JSON) objects could not be modified by Document Object Model (DOM) operations.
- JZN-00043: Feature not implemented
-
Cause: This feature was not implemented yet.
- JZN-00044: Type conversion failed
-
Cause: A type conversion requested for JavaScript Object Notation (JSON) Path output could not be performed.
- JZN-00045: Invalid sequence of events
-
Cause: The JavaScript Object Notation (JSON) serializer encountered an incorrect event sequence and could not serialize the result.
- JZN-00046: Requested key does not exist
-
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.
- JZN-00047: Cyclic reference to DOM node is not allowed
-
Cause: A Document Object Model (DOM) node could not be inserted below one of its own descendant nodes.
- JZN-00048: Multiple references to DOM node are not allowed
-
Cause: A Document Object Model (DOM) node could not be inserted because it is already present in the document node tree.
- JZN-00049: Input to JSON parser is empty
-
Cause: The input provided to the JSON parser was empty.
- JZN-00050: Character set conversion failed
-
Cause: The string could not be converted to or from UTF-8.
- JZN-00051: Invalid regular expression
-
Cause: The string supplied to 'eq_regex' or 'like_regex' could not be interpreted as a regular expression.
- JZN-00052: no cached value found for this column
-
Cause: Internal code signals that a call to get a JSON_TABLE column value found no pre-generated value in the cache.
- JZN-00053: target of DOM operation must be an object node
-
Cause: A DOM operation that requires an object node was given an array or scalar node as the target.
- JZN-00054: target of DOM operation must be an array node
-
Cause: A DOM operation that requires an array node was given an object or scalar node as the target.
- JZN-00055: target of DOM operation is not scalar
-
Cause: A DOM operation that requires a scalar node was given an object object or array node as the target.
- JZN-00056: numeric overflow
-
Cause: A string representaion of a number was too large to be converted to an Oracle number.
- JZN-00057: cannot convert BOOLEAN value to number
-
Cause: An attempt was made to convert a BOOLEAN value that was selected by a JavaScript Object Notation (JSON path) expression to a number with a number() or numberOnly() function.
- JZN-00058: JavaScript Object Notation (JSON) value is scalar
-
Cause: A scalar JavaScript Object Notation value was encountered where a non-scalar value (JSON object or JSON array) was expected.
- JZN-00059: invalid scalar data type
-
Cause: The input scalar data type could not be processed by the JSON operator.
- JZN-00060: The specified node is a freed node.
-
Cause: The input node to a Document Object Model (DOM) operation was previously freed and could be used again.
- JZN-00061: operation not allowed
-
Cause: The Document Object Model (DOM) operation was not allowed. Operations that remove, unlink, rename, replace, or move DOM nodes were not allowed.
- JZN-00062: ~u duplicate element(s) in array
-
Cause: Items in the document array were not unique.
- JZN-00063: non-object element in array for sort or pivot operation
-
Cause: Some items in the target array were not JSON objects.
- JZN-00064: name element not found or not a string
-
Cause: The name needed for a pivot operation was not found or not a JSON string.
- JZN-00065: value element not found
-
Cause: The value needed for a pivot operation was not found.
- JZN-00066: invalid cast operation requested
-
Cause: An invalid cast operation was requested.
- JZN-00070: comma not preceded or followed by field or item
-
Cause: An unexpected or superfluous comma was encountered while parsing an object or array.
- JZN-00071: missing comma in object or array
-
Cause: A comma was expected between members of an object, or between items in an array.
- JZN-00072: object member is missing value
-
Cause: An object member name and colon was not followed by a member value.
- JZN-00073: missing colon in member:value pair
-
Cause: An object member name was not followed by a colon.
- JZN-00074: member name not enclosed in double quotation marks
-
Cause: An object member name was not enclosed in double quotation marks, and either contained or started with a character that was not allowed.
- JZN-00075: string value not enclosed in double quotation marks
-
Cause: A string value was not enclosed in double quotation marks.
- JZN-00076: number could not be parsed
-
Cause: A JavaScript Object Notation (JSON) number was encountered that
- JZN-00077: invalid ASCII control character
-
Cause: An invalid byte value was read from the JavaScript Object Notation (JSON) input. ASCII control characters are not allowed in JSON text.
- JZN-00078: Invalid JSON keyword '~s'
-
Cause: A literal value was encountered that could not be interpreted as a JSON literal. Allowed JSON literals are 'true', 'false', and 'null'.
- JZN-00079: missing quotation mark at end of string
-
Cause: A member name or string value beginning with a quotation mark did not have a closing quotation mark.
- JZN-00081: invalid hexadecimal string
-
Cause: A string was encountered that could not be interpreted as a hexadecimal representation of a binary value.
- JZN-00082: unexpected JSON syntax character '~s'
-
Cause: An unexpected or superfluous syntactic character was encountered while parsing an object or array.
- JZN-00083: unclosed array
-
Cause: An array was not closed with a ']'.
- JZN-00084: unclosed object
-
Cause: An object was not closed with a '}'.
- JZN-00085: JSON unintelligible
-
Cause: A JSON contained invalid or unexpected characters and could not be interpreted.
- JZN-00086: missing next item
-
Cause: An array or object contained a comma but no subsequent element or member was found.
- JZN-00087: unexpected characters
-
Cause: Unexpected non-whitespace characters were encountered follwing the end of the JSON document.
- JZN-00090: Invalid binary JSON (~s)
-
Cause: The binary JSON image was invalid or corrupt.
- JZN-00091: Binary JSON encoding ended prematurely
-
Cause: The binary JSON image was incomplete or corrupt.
- JZN-00092: JSON too large for binary encoding
-
Cause: The binary JSON exceeded the maximum supported size.
- JZN-00200: (line ~1s, position ~2s)
-
Cause: This is the location of the error within the JSON document.
- JZN-00201: Unquoted punctuation in step
-
Cause: A path step contained punctuation characters.
- JZN-00202: Escape sequence must be in quotation marks
-
Cause: A backslash escape sequence was not enclosed in quotation marks.
- JZN-00203: Invalid escape sequence
-
Cause: An escape sequence beginning with a backslash contained invalid characters.
- JZN-00204: Invalid surrogate pair
-
Cause: The surrogate pair was invalid. A surrogate pair must consist of a high surrogate followed by a low surrogate.
- JZN-00205: Array subscript too long
-
Cause: A subscript within an array step was too long to be interpreted.
- JZN-00206: Array subscript invalid range
-
Cause: An array range subscript was missing a start or end position.
- JZN-00207: Variable name is invalid
-
Cause: The variable name was invalid. A variable name must be alphanumeric and cannot start with a number.
- JZN-00208: Path must start with a dollar sign ($) character
-
Cause: A path did not start with a dollar sign ($) character.
- JZN-00209: Unexpected characters after end of path
-
Cause: Trailing characters followed the end of the path.
- JZN-00210: Empty array subscript
-
Cause: An array step was empty.
- JZN-00211: Invalid array subscript
-
Cause: The specified array position was invalid.
- JZN-00212: Array wildcard must be used alone
-
Cause: The array wildcard (*) character was not specified by itself in an array subscript.
- JZN-00213: Object key wildcard must be used alone
-
Cause: The key wildcard (*) character did not appear by itself in a key step.
- JZN-00214: Missing square bracket in array step
-
Cause: An array step had mismatching square bracket ([]) charaters.
- JZN-00215: Array step contains unexpected characters
-
Cause: An array step contained invalid characters and could not be interpreted.
- JZN-00216: Unclosed quoted step
-
Cause: A step beginning with a quotation mark did not have a closing quotation mark.
- JZN-00217: Key step contains unexpected characters
-
Cause: A key step contained invalid characters and could not be interpreted.
- JZN-00218: Invalid JSON literal
-
Cause: A JavaScript Object Notation (JSON) literal must be 'true', 'false', or 'null'.
- JZN-00219: Literal contains unexpected characters
-
Cause: A JavaScript Object Notation (JSON) literal must be 'true', 'false', or 'null'.
- JZN-00220: Invalid number
-
Cause: The value could not be interpreted as a number.
- JZN-00221: Numeric overflow
-
Cause: The numeric value could not be converted to binary because of an overflow.
- JZN-00222: Invalid regular expression
-
Cause: The expression supplied to 'eq_regex' or 'like_regex' was not a valid regular expression.
- JZN-00223: Unsupported operator
-
Cause: The 'not_in' operator was specified in an expression.
- JZN-00224: Unexpected characters in comparison operator
-
Cause: Unexpected characters were present in the expression.
- JZN-00225: Comparison with expression must involve a path
-
Cause: A comparison operation with an expression did not involve a path.
- JZN-00226: Not operator must be followed by parenthetical expression
-
Cause: The expression after a not operator was not enclosed in parentheses.
- JZN-00227: Comparison must be against 'true' or 'false'
-
Cause: The comparison was not against a JavaScript Object Notation (JSON) 'true' or 'false' literal.
- JZN-00228: Question mark must be followed by parenthetical expression
-
Cause: A question mark introduced a filter that was enclosed in parentheses.
- JZN-00229: Missing parenthesis in parenthetical expression
-
Cause: A parenthetical expression was missing a closing parenthesis.
- JZN-00230: Unexpected characters in expression
-
Cause: Unexpected characters were present in the expression.
- JZN-00231: Unquoted Unicode character
-
Cause: A Unicode character appeared outside of quotation marks.
- JZN-00232: Expected a '.' following step
-
Cause: After a path step, a '.' separator was expected.
- JZN-00233: Invalid character at start of step
-
Cause: The next path step started with an invalid character.
- JZN-00234: Invalid '@' outside of predicate
-
Cause: An '@' character appeared in the path outside of a predicate clause.
- JZN-00235: Invalid '$' inside of predicate
-
Cause: A '$' appeared in the path inside of a predicate clause.
- JZN-00236: missing or invalid function or operator
-
Cause: A predicate expression was missing an operator or specified a function that was not valid.
- JZN-00237: invalid comparison of two path expressions
-
Cause: A predicate expression contained a path expression on both the left and right sides of the operator.
- JZN-00238: path expression has more than one predicate
-
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.
- JZN-00239: predicate expression before final path step
-
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.
- JZN-00240: invalid characters in array range subscript
-
Cause: The specified array range contained invalid characters. Array ranges are specified using the keyword 'to' between the start and end of the range.
- JZN-00241: invalid function at the end of path
-
Cause: The specified function is not valid.
- JZN-00242: parentheses nested too deeply
-
Cause: A path expression contained too many levels of nested parentheses.
- JZN-00243: type incompatibility for comparison
-
Cause: The domain of a type comparison cannot be determined because the types are incompatible and cannot be converted.
- JZN-00244: wrong argument data type for function call
-
Cause: The argument to a function call does not have the correct data type and cannot be converted to the correct data type.
- JZN-00245: can not convert literal to the required data type
-
Cause: The JSON literal value cannot be converted to the data type required by the operation or comparison.
- JZN-00246: expression types used by in/not_in sequence must be uniform
-
Cause: The values used for an in or not_in sequence must be of a uniform data type.
- JZN-00247: Array subscript or range out of order
-
Cause: An array subscript appeared in a comma-separated list after a higher subscript or range.
- JZN-00248: Character not escaped
-
Cause: A character appeared in a quoted path step or literal string without being escaped as required.
- JZN-00249: Unquoted empty step not allowed
-
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.
- JZN-00250: JSON Patch specification must be an array of operations
-
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.
- JZN-00251: JSON Patch operations must be objects
-
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.
- JZN-00252: No 'op' code for patch operation
-
Cause: An object in a JavaScript Object Notation (JSON) Patch specification was missing an 'op' code.
- JZN-00253: Invalid path for patch operation
-
Cause: The 'path' or 'from' clause in a patch operation could not be parsed.
- JZN-00254: Invalid 'op' code for patch operation
-
Cause: The 'op' code could not be interpreted.
- JZN-00255: Unknown key name in patch operation
-
Cause: The operation contained a key that is not specified by JavaScript Object Notation (JSON) Patch.
- JZN-00256: Patch operation requires a path
-
Cause: The target path for an operation was not specified.
- JZN-00257: 'path' or 'from' key must have a string value
-
Cause: The path specified for a 'path' or 'from' field was not a string.
- JZN-00258: From path not allowed for operation
-
Cause: The 'from' path was specified for an operation that does not allow it. 'from' is only allowed in the 'move' and 'copy' operations.
- JZN-00259: 'value' is not allowed for operation
-
Cause: A 'value' was specified for an operation that does not allow it. A 'value' is not allowed in 'remove', 'move', and 'copy'.
- JZN-00260: 'from' path is required for operation
-
Cause: A 'move' or 'copy' operation was missing a 'from' path.
- JZN-00261: 'value' is required for operation
-
Cause: An 'add', 'replace', or 'test' operation was missing a target value.
- JZN-00262: Cyclic 'move' requested
-
Cause: The target 'path' specified is a child of the 'from' path.
- JZN-00280: Invalid comparison to root path in predicate
-
Cause: A predicate used a disallowed comparison operator for a path beginning with root ('$'). Root paths cannot be used with 'in' statements and cannot be used with string matching operators such as 'like', 'starts with', 'has substring', and regular expression patterns.
- JZN-00281: unexpected arithmetic expression
-
Cause: An arithmetic expression was encountered where a boolean expression was expected.
- JZN-00282: expression is not a comparison
-
Cause: A path, variable, or literal expression was encountered where a boolean expression was expected.
- JZN-00283: unexpected parenthesis
-
Cause: A parenthesis character was encountered in an unexpected position.
- JZN-00284: expression is not a variable or literal
-
Cause: An 'in' or 'not in' list contained an expression that was not a literal or variable.
- JZN-00285: parentheses were expected
-
Cause: The expression after an 'in' or 'not in' operator was not enclosed in parentheses.
- JZN-00286: invalid inequality expression
-
Cause: A comparison expression involving boolean arguments was not '==' or '!='.
- JZN-00287: duplicate predicate identifier
-
Cause: A predicate identifier was used more than once in a filter expression.
- JZN-00288: unknown predicate identifier
-
Cause: A context item was followed by an identifier that did not match any predicate identifier in the surrounding filter expression.
- JZN-00300: Conflicting inclusion or exclusion rules
-
Cause: The including rule for a parent node conflicted with the explicit rule asserted for a child node. The projection specification is invalid.
- JZN-00301: Projection specification must be an object
-
Cause: A projection specification was an array or JavaScript Object
- JZN-00302: Include or exclude rule could not be interpreted
-
Cause: The rule did not use 'true', 'false', 1, 0, "include", or "exclude".
- JZN-00303: NULL or invalid path
-
Cause: A path was either invalid or NULL.
- JZN-00304: Keys must be numbers or strings
-
Cause: An argument to $id was not a number or string.
- JZN-00305: Array of values was empty
-
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.
- JZN-00306: Array must contain only scalar values
-
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.
- JZN-00307: $between must have two values in array
-
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.
- JZN-00308: Spatial operators must be at the outermost level
-
Cause: The $near, $within, and $intersect operators were not used at the outermost level of the Query-By-Example (QBE).
- JZN-00309: Spatial operators must specify $geometry
-
Cause: The $near, $within, and $intersect operators were not given a GeoJSON object as the value of the $geometry key.
- JZN-00310: $distance parameter is not allowed
-
Cause: The $distance parameter was used with an operator other than $near. Only the $near operator may include values for $distance and $unit.
- JZN-00311: $distance parameter must be numeric
-
Cause: The $distance parameter was specified with a value that was not a JavaScript Object Notation (JSON) number.
- JZN-00312: $unit parameter must be a string
-
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.
- JZN-00313: Unknown key found in spatial operator
-
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.
- JZN-00314: $distance parameter is required
-
Cause: The $near operator did not specify a value for $distance.
- JZN-00315: Empty objects not allowed
-
Cause: An empty object was found in the filter specification. An empty object is meaningless and not allowed in the filter specification.
- JZN-00316: Object with at least one field object must follow modifier
-
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.
- JZN-00317: Target of spatial operation must be an object
-
Cause: A $near, $within, or $intersect operator was not followed by an object containing the spatial parameters.
- JZN-00318: Invalid operator within modifier
-
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.
- JZN-00319: Value of string matching operator must be a string
-
Cause: The value supplied to the $regex, $hasSubstring, $startsWith, or $like operators was not a JavaScript Object Notation (JSON) string.
- JZN-00320: Value of comparison operator must be a scalar
-
Cause: The value supplied to an operator was not a JavaScript Object Notation (JSON) scalar value.
- JZN-00321: Value of the operator must be a string or number
-
Cause: The value supplied to $eq, $ne, or $exists was not a JavaScript Object Notation (JSON) string or number.
- JZN-00322: Value of set comparison operator must be an array
-
Cause: The value supplied to $in, $all, $id, or $between was not an array.
- JZN-00323: Elements in a conjunction array must be objects
-
Cause: An element of an array for $and, $or, or $nor was not an object.
- JZN-00324: $id operator must be at the outermost level
-
Cause: The $id operator supplying document keys was not used at the outermost level of the Query-By-Example (QBE).
- JZN-00325: Cannot combine sub-expression with other filters
-
Cause: A downscoped sub-expression was used in the same scope as a normal filter condition.
- JZN-00326: Values for $orderby conditions must be integers
-
Cause: An order by condition did not give an integer value. Objects, arrays, strings, and other literals are not allowed to specify ordering criteria.
- JZN-00327: Query specification must be an object
-
Cause: The query specification root was an array or scalar. A query specification must be an object.
- JZN-00328: Order by specification must be an object or array
-
Cause: A $orderby specification was not an object or array. It may not be a JavaScript Object Notation (JSON) scalar.
- JZN-00329: Order by field must specify a path
-
Cause: A field of a $orderby array must specify a path.
- JZN-00330: Order by array contained invalid item
-
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'.
- JZN-00331: $sqlJson operator must be at the outermost level
-
Cause: The $sqlJson was not used at the outermost level of the Query-By-Example (QBE).
- JZN-00332: Value of $sqlJson operator must be an object
-
Cause: The value supplied to $sqlJson was not an object.
- JZN-00333: Items in a $sqlJson object must be field paths
-
Cause: The fields of a $sqlJson operator must all be path strings.
- JZN-00334: $id operator cannot appear more than once
-
Cause: The $id operator supplying document keys was used multiple times in the Query-By-Example (QBE).
- JZN-00335: Parameter '~s' must be a boolean
-
Cause: The parameter value was not a JSON literal 'true' or 'false'.
- JZN-00336: Parameters '~1s' and '~2s' conflict
-
Cause: Two parameters were used together that are either disallowed in combination, or had conflicting values specified.
- JZN-00337: Logical operator '~s' must have at least one target
-
Cause: An array of target values for the logical operator was empty.
- JZN-00338: Order by path must not have array steps
-
Cause: A path used in an order by path expression used an array step. Order by path expressions use lax semantics and must not have explicit array steps.
- JZN-00339: Invalid array element match clause
-
Cause: An array element matching clause for a path was specified incorrectly. The critria must follow a path and be followed by an object. The criteria must appear by itself and may not be nested under another array element matching clause.
- JZN-00350: invalid transformation
-
Cause: The transformation specification was invalid and could not be interpreted.
- JZN-00351: did not have exactly one of '$keep', '$remove', or '$modify'
-
Cause: A transformation block does not have a single projection or modification operation. The block has no target operation or has multiple conflicting operations.
- JZN-00352: specification of '~s' was a scalar
-
Cause: A scalar value was provided as the specification of an operation that requires an object or array specification.
- JZN-00353: specification of '~s' was empty
-
Cause: An empty object or array was provided as the specification an operation that must have at least one entry.
- JZN-00354: specification of '~s' was not an object
-
Cause: An array or scalar was provided for an operation that requires an object.
- JZN-00355: path for operation '~s' was not a string
-
Cause: One or more paths for an operation was not a scalar string. Projection and selection paths cannot be objects, arrays, or other scalar types.
- JZN-00356: path reference expression for '~s' was not a string
-
Cause: The value of a path reference in an update expression was not a scalar string.
- JZN-00357: path step cannot start with a '$'
-
Cause: A path step string started with an unquoted '$' character. The leading '$' character is reserved for update operators and modifiers.
- JZN-00358: argument must be a scalar
-
Cause: An argument to a calculation expression was not a scalar value.
- JZN-00359: argument must be an array
-
Cause: The calculation was not followed by an operand array.
- JZN-00360: invalid projection
-
Cause: The projection contained a modification operation or calculation that is only valid for updating documents.
- JZN-00361: unknown operator '~s'
-
Cause: The expression could not be interpreted as an operator for a calculation, modifier, or conversion function.
- JZN-00362: match condition must be a Query By Example (QBE)
-
Cause: A scalar comparison was used when a full Query By Example (QBE) clause was required.
- JZN-00363: required field '~s' missing
-
Cause: A required field was missing from a query, update, or aggregation specification.
- JZN-00364: node of type '~1s' is not allowed for '~2s'
-
Cause: A node of an incorrect type was found for a field in a query, update, or aggregation specification.
- JZN-00365: too many fields or elements for '~s'
-
Cause: A node with too many member fields or array elements was found in a query, update, or aggregation specification.
- JZN-00366: not enough fields or elements for '~s'
-
Cause: A node with insufficient member fields or array elements was found in a query, update, or aggregation specification.
- JZN-00367: no match for '~1s' referenced from list '~2s'
-
Cause: An unknown column alias appeared on a reference list and could not be matched to a defined column.
- JZN-00368: column alias '~1s' used too many times on list '~2s'
-
Cause: A column alias appeared more than once on a reference list.
- JZN-00369: column '~1s' cannot be used for operation '~2s'
-
Cause: An invalid column was used for a $group or $distinct operation. Constant columns, aggregation results, and non-scalar columns may not be used for $group or $distinct.
- JZN-00370: value of '~s' expression must be a number
-
Cause: The value of an expression was expected to be a number.
- JZN-00371: scalar type mismatch for '~s'
-
Cause: The set of scalar values for an expression contained some values that were not of compatible types.
- JZN-00372: literal value '~1s' not allowed for '~2s'
-
Cause: The JSON literal value was not allowed as a value for a comparison operator.
- JZN-00373: operation '~1s' cannot be used on '~2s'
-
Cause: An operation was specified againt an incompatible target expression.
- JZN-00374: value of field name for '~s' was not a string
-
Cause: The value of a field name reference must be a string matching a defined $fields source column.
- JZN-00375: '~s' operator must be at the outermost level
-
Cause: A disallowed operator was used at a nested level in a Query-By-Example (QBE).
- JZN-00376: invalid combination of '$textContains' with ~s
-
Cause: The $textContains operator could not be used with the other operator or query construct.
- JZN-00377: aggregation is missing '$sort'
-
Cause: An aggregation used '$first' or '$last' without a '$sort'.
- JZN-00378: unknown aggregation operator '~s'
-
Cause: The aggregation specification contained an unknown operator.
- JZN-00379: aggregation stage is indeterminant
-
Cause: A stage in an aggregation pipeline specification could not be determined from the specified fields.
- JZN-00380: invalid use of ~s at nested query level
-
Cause: A geo-spatial, full text, or key match operation was attempted within a nested query scope.
- JZN-00381: unclosed quotation mark
-
Cause: An input column value began with an opening quotation mark but had no closing quotation mark.
- JZN-00382: unescaped quotation mark
-
Cause: An unquoted input column value contains a quotation mark.
- JZN-00383: missing delimiter
-
Cause: A column value contained a quoted value and another quoted or unquoted value, but had no delimiter separating the values.
- JZN-00384: unquoted spaces
-
Cause: A quoted column value had space characters before the opening quotation mark or after the closing quotation mark.
- JZN-00390: path reference not allowed in value
-
Cause: An expression used in an unordered transformation block contained a path reference to a node within the target document.
- JZN-00391: argument to function '~s' was not a number
-
Cause: An argument to a function was not a scalar constant number.
- JZN-00392: variable name is invalid
-
Cause: A variable name used disallowed characters.
- JZN-00400: JSON_TRANSFORM operation encountered missing field
-
Cause: A JSON_TRANSFORM operation did not find a field value where one was expected.
- JZN-00401: JSON_TRANSFORM operation encountered an existing field
-
Cause: A JSON_TRANSFORM operation encountered an existing field where none was expected.
- JZN-00402: JSON_TRANSFORM operation did not match JSON array
-
Cause: A JSON_TRANSFORM operation that expected an array did not match an array.
- JZN-00403: field name existing in JSON_TRANSFORM operation
-
Cause: A JSON_TRANSFORM operation could not be executed because a field name already existed.
- JZN-00404: field name missing in JSON_TRANSFORM operation
-
Cause: A JSON_TRANSFORM operation could not be executed because a field name was missing.
- JZN-00405: JSON_TRANSFORM cannot remove root value
-
Cause: An attempt was made to remove the root value of the JSON data.
- JZN-00406: JSON_TRANSFORM operation not supported
-
Cause: An attempt was made to use a JSON_TRANSFORM operation that was not supported.
- JZN-00407: JSON_TRANSFORM operation cannot select multiple values
-
Cause: A path expression was used that selected more than one value in an operation where only one value can be modified.
- JZN-00408: JSON_TRANSFORM operation called with NULL input
-
Cause: A JSON_TRANSFORM operation was called with an input value that was NULL and the operation had ERROR ON NULL handling specified.
- JZN-00409: JSON_TRANSFORM cannot update root value
-
Cause: An attempt was made to update the root value of the JSON data.
- JZN-00410: JSON_TRANSFORM operation did not match JSON object
-
Cause: A JSON_TRANSFORM operation that expected an object did not match an object.
- JZN-00411: JSON_TRANSFORM invalid append operation
-
Cause: An attempt was made to append to an array that did not exist.
- JZN-00412: JSON_TRANSFORM invalid key name
-
Cause: An attempt was made to rename an object node using an empty key string.
- JZN-00413: JSON_TRANSFORM called with '..' path step
-
Cause: An attempt was made to evaluate the '..' descendant axis on the target side of a JSON_TRANSFORM operation. The descendant axis was not allowed because its use may lead to target nodes that are not disjoint subtrees of the document being modified.
- JZN-00414: JSON_TRANSFORM operation with no target path
-
Cause: An attempt was made to evaluate an operation without specifying a path to the target of the operation.
- JZN-00415: JSON_TRANSFORM operation with disallowed target variable
-
Cause: An attempt was made to perform an operation against a prohibited target variable.
- JZN-00450: not found
-
Cause: Evaluation returned no value. This is an advisory status and not a hard error.
- JZN-00451: JSON calculation references a missing field
-
Cause: A path expression in a calculation could not be evaluated to a node in the instance document.
- JZN-00452: JSON calculation reference matches too many values
-
Cause: A path expression in a calculation matched more than one node in the instance document.
- JZN-00453: JSON calculation reference is not a number
-
Cause: A path expression in a calculation matched a node in the instance document that was an object, array, or a non-numeric scalar.
- JZN-00454: JSON calculation reference is not a string
-
Cause: A path expression in a calculation matched a node in the instance document that was an object, array, or a non-numeric scalar.
- JZN-00455: JSON calculation literal is of the wrong type
-
Cause: A calculation literal value was not of a suitable type for the calculation operator.
- JZN-00456: JSON calculation failed
-
Cause: A calculation failed or could not be performed. A value of an incorrect scalar value was referenced or produced.
- JZN-00457: JSON calculation type conversion failed
-
Cause: A calculation attempted a type conversion that failed or could not be performed.
- JZN-00458: numeric calculation attempted on non-numeric value
-
Cause: A numeric calculation could not be performed because the operand was not a number and could not be converted to a number.
- JZN-00459: computation attempted on value of wrong type
-
Cause: A computation could not be performed because the operand was of the incorrect type and conversion is not allowed.
- JZN-00499: wrong number or types of arguments to function
-
Cause: A trailing function was passed an incorrect number of arguments, or arguments of the wrong scalar type.
- JZN-00500: invalid JSON schema document
-
Cause: An invalid JavaScript Object Notation (JSON) schema document was used.
- JZN-00501: JSON schema validation failed
-
Cause: The input JSON document instance failed schema validation.
- JZN-00502: JSON boolean schema was false
-
Cause: The input JavaScript Object Notation (JSON) boolean schema was false.
- JZN-00503: invalid type found, actual: ~1s, expected: ~2s
-
Cause: The type of the element was not valid.
- JZN-00504: invalid type found, actual: ~1s, expected one of: ~2s
-
Cause: The type of the element was not valid.
- JZN-00505: element was not equal to any of the enumerated values
-
Cause: The element was not equal to any of the enumerated values.
- JZN-00506: element was not equal to specified constant value
-
Cause: The element was not equal to the specified constant value in the schema.
- JZN-00507: value less than minimum value, actual: ~1s, expected: ~2s
-
Cause: The specified value was neither greater than nor equal to the expected minimum value specified in the schema.
- JZN-00508: value greater than maximum value, actual: ~1s, expected: ~2s
-
Cause: The specified value was neither greater than nor equal to the expected maximum value specified in the schema.
- JZN-00509: value not greater than minimum value, actual: ~1s, expected: ~2s
-
Cause: The specified value was not greater than the expected minimum value specified in the schema.
- JZN-00510: value not less than maximum value, actual: ~1s, expected: ~2s
-
Cause: The specified value was not less than the specified maximum value in the schema.
- JZN-00511: value ~1s not a multiple of ~2s
-
Cause: The specified value was not a multiple of the specified value in the schema.
- JZN-00512: string length shorter, actual: ~1s, expected: ~2s
-
Cause: The specified string value was shorter than expected.
- JZN-00513: string length longer, actual: ~1s, expected: ~2s
-
Cause: The specified string value was longer than expected.
- JZN-00514: invalid properties: ~s
-
Cause: The specified properties in the document object were not valid.
- JZN-00515: required properties not found: ~s
-
Cause: The required properties in the document object were not found.
- JZN-00516: fewer than required properties found: actual: ~1s, expected ~2s
-
Cause: Fewer than the required properties were found in the document object.
- JZN-00517: more than required properties found: actual: ~1s, expected ~2s
-
Cause: More than the required properties were found in the document object.
- JZN-00518: invalid additional properties: ~s
-
Cause: The additional properties in the document object were not valid.
- JZN-00519: invalid items at index: ~s
-
Cause: Items in the document array were not valid.
- JZN-00520: duplicate items at index: ~1u, ~2u
-
Cause: Items in the document array were not unique.
- JZN-00521: valid item not found
-
Cause: Items in the document array were all invalid.
- JZN-00522: fewer than required items found: actual: ~1s, expected ~2s
-
Cause: Fewer than the required number of items were found in the document array.
- JZN-00523: more than required items found: actual: ~1s, expected ~2s
-
Cause: More than the required items were found in the document array.
- JZN-00524: invalid additional items at index: ~s
-
Cause: The additional items in the document array were not valid.
- JZN-00525: element was valid
-
Cause: The element succeeded the schema validation.
- JZN-00526: element was not valid against any of the schemas
-
Cause: The element failed validation against all of the schemas.
- JZN-00527: element was not valid against schema at index: ~s
-
Cause: The element failed validation against some of the schemas.
- JZN-00528: element was valid against more than one schema at index: ~s
-
Cause: The element was valid against more than one schema.
- JZN-00529: invalid property names: ~s
-
Cause: The property names in the document object were not valid against the schema.
- JZN-00530: fewer than required items valid: actual: ~1s, expected ~2s
-
Cause: Fewer than the required number of items were valid.
- JZN-00531: more than required items valid: actual: ~1s, expected ~2s
-
Cause: More than the required number of items were valid.
- JZN-00532: invalid unevaluated properties: ~s
-
Cause: Unevaluated properties in the document object were not valid.
- JZN-00533: invalid unevaluated items at index: ~s
-
Cause: Unevaluated items in the document array were not valid.
- JZN-00534: required properties for dependents not found: ~s
-
Cause: The required properties for dependents in the document object were not found.
- JZN-00535: schema validation for dependent properties failed: ~s
-
Cause: The schema validation for dependent properties in the document object failed.
- JZN-00536: conditional schema validation for the 'then' condition failed
-
Cause: The schema validation for the "then" condition failed.
- JZN-00537: conditional schema validation of both 'if' and 'else' failed
-
Cause: The schema validation for both "if" and "else" conditions failed.
- JZN-00538: value did not match the expected pattern
-
Cause: The string value did not match the specified pattern.
- JZN-00539: invalid '~s' format value
-
Cause: The specified string value was not in an expected format.
- JZN-00600: the object view is invalid: ~s
-
Cause: The object view specification is invalid.
- JZN-00601: unknown table number '~d'
-
Cause: The table specified does not exist or is invalid.
- JZN-00602: invalid empty column list for '~s'
-
Cause: The specified list of columns is empty.
- JZN-00603: more than '~d' columns in list for '~s'
-
Cause: The number of columns in a list exceeded the maximum allowed.
- JZN-00604: '~s' does not have '~d' columns in list
-
Cause: The number of columns in a list did not match a covariant list.
- JZN-00605: column position '~d' invalid for list of size '~d'
-
Cause: The column specified did not exist or was invalid.
- JZN-00606: unable to find column '~s' for table '~s'
-
Cause: The column name did not match any column of the specified table.
- JZN-00607: nested links must have a key name
-
Cause: A nested link must have a key name specified for the JSON array.
- JZN-00608: property '~s' already specified
-
Cause: The property was already specified for the target object.
- JZN-00609: property '~s' has invalid value '~s'
-
Cause: The value of a property was out of range or invalid.
- JZN-00610: property '~s' has invalid value '~d'
-
Cause: The value of a property was out of range or invalid.
- JZN-00611: field '~s' is not specified
-
Cause: The required field was not specified.
- JZN-00612: unnesting link specification is invalid
-
Cause: The link for an unnesting operation had an invalid specification.
- JZN-00613: field '~s' is not an array
-
Cause: The field was specified using an incorrect node type.
- JZN-00614: field '~s' is not an object
-
Cause: The field was specified using an incorrect node type.
- JZN-00615: field '~s' is not a scalar
-
Cause: The field was specified using an incorrect node type.
- JZN-00616: field '~s' is not a string
-
Cause: The field was specified using an incorrect data type.
- JZN-00617: field '~s' is not a number
-
Cause: The field was specified using an incorrect data type.
- JZN-00618: field '~s' is not a boolean
-
Cause: The field was specified using an incorrect data type.
- JZN-00620: element of '~s' is not an object
-
Cause: The array element was specified using an incorrect node type.
- JZN-00621: element of '~s' is not a scalar
-
Cause: The array element was specified using an incorrect node type.
- JZN-00622: element of '~s' is not a string
-
Cause: The array element was specified using an incorrect data type.
- JZN-00623: too many links to target table
-
Cause: A table was specified as the target of more than one link.
- JZN-00624: target of link is the root table
-
Cause: A link specified the root table as the target table.
- JZN-00625: column is used in multiple structures
-
Cause: A column was used in more than one structure definition.
- JZN-00626: invalid empty JSON object specification
-
Cause: The specified list of fields for a JSON object was empty.
- JZN-00627: conflicting usage of table '~1s' in schema '~2s'
-
Cause: A table was used inconsistently in a business object view.
- JZN-00628: column mapped to array with key name
-
Cause: A column with a key name was mapped to an array. Key names must be contained with object mappings.
- JZN-00640: table names do not match
-
Cause: A pair of Business Object View definitions failed to match because they reference different tables at the same location.
- JZN-00641: table properties do not match
-
Cause: A pair of Business Object View definitions failed to match because the tables have different properties at the same location.
- JZN-00642: table columns do not match
-
Cause: A pair of Business Object View definitions failed to match because the tables have different sets of columns at the same location.
- JZN-00643: table descendants do not match
-
Cause: A pair of Business Object View definitions failed to match because the tables have different child table references.
- JZN-00644: columns do not match
-
Cause: A pair of Business Object View definitions failed to match because the columns have different data types or other properties.
- JZN-00645: column lists do not match
-
Cause: A pair of Business Object View definitions failed to match because the columns listed for a primary key, eTag, order by, unique key, or linking relationship were not identical.
- JZN-00646: key names do not match
-
Cause: A pair of Business Object View definitions failed to match because the key names used for columns or descendants were not identical.
- JZN-00650: element is not an object
-
Cause: An element of the JSON required to be an object was not an array or scalar.
- JZN-00651: field '~s' is unknown or undefined
-
Cause: A field was read that was not defined in the business object specification.
- JZN-00652: field '~s' is not an object
-
Cause: A field required to be a nested sub-object was found to be a scalar or array.
- JZN-00653: field '~s' is not an array
-
Cause: A field required to be a nested array of objects was found to be a scalar or object.
- JZN-00654: field '~s' is not a scalar
-
Cause: A field mapped to a column was found to be an object or array. Fields mapped to a column must be JSON scalars.
- JZN-00655: field '~s' is not the correct data type
-
Cause: A field mapped to a column was found to be a scalar of an invalid or unconvertible type.
- JZN-00656: field '~s' not found
-
Cause: A field defined in the business object specification was not found, leaving a required column undefined.
- JZN-00657: field '~s' is too large
-
Cause: A field mapped to a string or binary column is too large for the column.
- JZN-00658: array object has duplicate key
-
Cause: An object element in an array had a primary key that is identical to another object element in the same array.
- JZN-00659: table column has no match
-
Cause: A duplicate table definition had a column that could not be matched to a column of the original table definition.
- JZN-00660: table row has conflicting writable state
-
Cause: A duplicate table row had a writable state that conflicted with the writable state of the original table row.
- JZN-00661: link rows have conflicting column values
-
Cause: A row had a value for a link column that did not match the corresponding column in the linked row.
- JZN-00662: business object contains no root row
-
Cause: A business object row set did not have a root row.
- JZN-00663: array element is not a scalar
-
Cause: An array element mapped to a column was found to be an object or array. Elements mapped to a column must be JSON scalars.
- JZN-00664: array element not mapped to column
-
Cause: An array contained more elements than the available column mappings.
- JZN-00665: row not present in all nested contexts
-
Cause: A row was missing from a parent row where the linking columns had matching values.