ORA-30000 to ORA-49999

ORA-30002: SYS_CONNECT_BY_PATH function is not allowed here

• OceanBase error code: 5768

• SQLSTATE: HY000

• Cause: The SYS_CONNECT_BY_PATH function is called beyond the SELECT list and ORDER BY clause.

• Solution: Delete the calls of the SYS_CONNECT_BY_PATH function except those in the SELECT list and ORDER BY clause.

ORA-30003: illegal parameter in SYS_CONNECT_BY_PATH function

• OceanBase error code: 5769

• SQLSTATE: HY000

• Cause: The SYS_CONNECT_BY_PATH function contains invalid arguments.

ORA-30003: illegal parameter in SYS_CONNECT_BY_PATH function

• OceanBase error code: 5927

• SQLSTATE: HY000

• Cause: The SYS_CONNECT_BY_PATH function contains invalid arguments.

ORA-30004: A column value contained the string that the SYS_CONNECT_BY_PATH function was to use to separate column values

• OceanBase error code: 5770

• SQLSTATE: HY000

• Cause: The string used by the SYS_CONNECT_BY_PATH function to separate column values is included in a column value.

• Solution: Specify another separator that is not included in any column value for the SYS_CONNECT_BY_PATH function, and try again.

ORA-30005: missing or invalid WAIT interval

• OceanBase error code: 5495
• SQLSTATE: HY000
• Cause: When you run the WAIT command, the specified wait time parameter is invalid or missing.
• Solution: Check the syntax of the WAIT command and make sure that the wait time parameter is correctly specified.

ORA-30006: resource busy; acquire with WAIT timeout expired

• OceanBase error code: 6003

• SQLSTATE: HY000

• Cause: The requested resource is busy.

• Solution: Try again later.

ORA-30007: CONNECT BY ROOT operator is not supported in the START WITH or in the CONNECT BY condition

• OceanBase error code: 5771

• SQLSTATE: HY000

• Cause: You are attempting to use the CONNECT BY ROOT operator in the START WITH or CONNECT BY condition.

• Solution: Delete the CONNECT BY ROOT operator from the START WITH or CONNECT BY condition.

ORA-30009: Not enough memory for CONNECT BY operation

• OceanBase error code: 5926

• SQLSTATE: HY000

• Cause: On a new engine, an error is reported if the recursion level is deeper than 2 to the 30th power. On the old engine, an error is reported if the number of all nodes and their subnodes on the path from the root node to the current node exceeds 2 to the 30th power. At present, this value is fixed. In general, this value will not be exceeded.

• Solution: No solution is available now. This issue cannot be solved by increasing the memory size. We recommend that you reduce the recursion level or the amount of data.

ORA-30076: invalid extract field for extract source

• OceanBase error code: 5686

• SQLSTATE: HY000

• Cause: The data extraction source does not contain the specified data extraction field.

ORA-30078: partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals

• OceanBase error code: 5349

• SQLSTATE: HY000

• Cause: The TIME or TIMESTAMP column does not contain TIME ZONE.

• Solution: Use the TIME or TIMESTAMP format with TIME ZONE.

ORA-30084: invalid data type for datetime primary with time zone modifier

• OceanBase error code: 5950

• SQLSTATE: HY000

• Cause: If a time zone modifier is specified, the value of the datetime parameter must be of the TIME, TIME WITH TIME ZONE, TIMESTAMP, or TIME STAMP WITH TIME ZONE type.

ORA-30088: datetime/interval precision is out of range

• OceanBase error code: 5605

• SQLSTATE: HY000

• Cause: The specified datetime or interval precision is not within the range of 0 to 9.

• Solution: Ensure that the datetime or interval precision is within the range of 0 to 9.

ORA-30175: invalid type given for an argument

• OceanBase error code: 5351

• SQLSTATE: HY000

• Cause: The argument list contains arguments of invalid types.

• Solution: Use correct data types for arguments.

ORA-30186: '\\' must be followed by four hexidecimal characters or another '\\'

• OceanBase error code: 5938

• SQLSTATE: HY000

• Cause: In the argument of the SQL function UNISTR, a pair of double backslashes (\\) must be followed by four hexadecimal characters or another pair of double backslashes (\\).

• Solution: Correct the string format.

ORA-30205: invalid Character set

• OceanBase error code: 5969

• SQLSTATE: HY000

• Cause: The specified character set is invalid.

• Solution: Check whether the character set ID is valid.

ORA-30481: GROUPING function only supported with GROUP BY CUBE or ROLLUP

• OceanBase error code: 5501
• SQLSTATE: 42000
• Cause: The GROUPING function is supported only in the GROUP BY CUBE or ROLLUP statement.
• Solution: Use the GROUPING function only in the GROUP BY CUBE or ROLLUP statement.

ORA-30482: DISTINCT not allowed here

• OceanBase error code: 5798

• SQLSTATE: HY000

• Cause: The DISTINCT option is not allowed in the function.

ORA-30485: missing ORDER BY expression in the window specification

• OceanBase error code: 5300

• SQLSTATE: HY000

• Cause: The ORDER BY expression is missing from the window function or aggregation group.

ORA-30487: ORDER BY not allowed here

• OceanBase error code: 5797

• SQLSTATE: HY000

• Cause: The ORDER BY expression is not allowed in the DISTINCT function and RATIO_TO_REPORT.

ORA-30488: argument should be a function of expressions in PARTITION BY

• OceanBase error code: 5347

• SQLSTATE: HY000

• Cause: The argument of the window function must be a constant for a partition.

ORA-30493: The percentile value should be a number between 0 and 1

• OceanBase error code: 5861

• SQLSTATE: HY000

• Cause: The percentile value specified for the PERCENTILE_CONT or PERCENTILE_DISC function is not within the specified range.

• Solution: Specify a value within the range of [0,1].

ORA-30494: The argument [%s] of WIDTH_BUCKET function is NULL or invalid

• OceanBase error code: 5925

• SQLSTATE: HY000

• Cause: The [%s] argument of the WIDTH_BUCKET function is NULL or invalid.

ORA-30495: The argument should be of numeric or date/datetime type

• OceanBase error code: 5862

• SQLSTATE: HY000

• Cause: The argument must be of the numeric or date/datetime type.

ORA-30496: Argument should be a constant

• OceanBase error code: 5852

• SQLSTATE: HY000

• Cause: The argument value is not a constant.

ORA-30553: The function is not deterministic

• OceanBase error code: 5996

• SQLSTATE: HY000

• Cause: The function on which the index is defined is not deterministic.

• Solution: If the function is deterministic, mark it DETERMINISTIC. If it is not deterministic (which depends on the package state, database state, current time, or anything other than the function inputs), do not create the index. You should never change the values returned by a deterministic function even when the function is rewritten or recompiled.

ORA-30562: SAMPLE percentage must be in the range [0.000001,100)

• OceanBase error code: 5730

• SQLSTATE: HY000

• Cause: The SAMPLE percentage should be within the range of [0.000001,100).

ORA-30563: outer join operator (+) is not allowed here

• OceanBase error code: 5626

• SQLSTATE: HY000

• Cause: You are attempting to reference + in the SELECT_LIST function or the CONNECT BY, START WITH, or ORDER BY clause.

• Solution: Do not use operators in the SELECT_LIST function or the CONNECT BY, START WITH, or ORDER BY clause.

ORA-30625: method dispatch on NULL SELF argument is disallowed

• OceanBase error code: 5847

• SQLSTATE: HY000

• Cause: A MEMBER method is called by the NULL SELF argument.

• Solution: Change the method call type so that a valid SELF argument is passed.

ORA-30665: invalid NOT NULL constraint specified on a DEFAULT ON NULL column

• OceanBase error code: 5949

• SQLSTATE: HY000

• Cause: The NOT NULL constraint is not correctly specified on the DEFAULT ON NULL column.

• Solution: If the NOT NULL constraint is specified on the DEFAULT ON NULL column, enable the constraint immediately.

ORA-30669: table can have only one identity column

• OceanBase error code: 5909

• SQLSTATE: HY000

• Cause: The operation attempted to specify multiple identity columns for a table.

• Solution: Specify only one identity column for each table.

ORA-30670: invalid NOT NULL constraint specified on an identity column

• OceanBase error code: 5910

• SQLSTATE: HY000

• Cause: The NOT NULL constraint is not properly specified on the identity column.

• Solution: If the NOT NULL constraint is specified for the identity column, enable the constraint immediately.

ORA-30671: cannot modify NOT NULL constraint on an identity column

• OceanBase error code: 5911

• SQLSTATE: HY000

• Cause: The NOT NULL constraint on the identity column cannot be modified.

• Solution: Do not modify the NOT NULL constraint on an identity column.

ORA-30672: cannot drop NOT NULL constraint on an identity column

• OceanBase error code: 5912

• SQLSTATE: HY000

• Cause: The NOT NULL constraint on the identity column cannot be deleted.

• Solution: Do not delete the NOT NULL constraint from the identity column. To delete the constraint, call the DROP IDENTITY operation in the ALTER TABLE MODIFY statement to delete the identity attribute of the column.

ORA-30673: column to be modified is not an identity column

• OceanBase error code: 5913

• SQLSTATE: HY000

• Cause: The operation attempted to modify the identity attribute of a non-identity column.

• Solution: Modify the identity attribute of only an identity column.

ORA-30674: identity column cannot have a default value

• OceanBase error code: 5914

• SQLSTATE: HY000

• Cause: The operation attempted to add a default value to an identity column.

• Solution: Do not specify a default value for an identity column.

ORA-30675: identity column must be a numeric type

• OceanBase error code: 5915

• SQLSTATE: HY000

• Cause: The operation attempted to create non-numeric values for an identity column or change the values of an identity column into non-numeric values.

• Solution: Do not assign a non-numeric data type to an identity column.

ORA-30926: unable to get a stable set of rows in the source tables

• OceanBase error code: 30926

• SQLSTATE: HY000

• Cause: A stable set of rows cannot be obtained due to a large DML activity or a non-deterministic WHERE clause.

• Solution: Delete the non-deterministic WHERE clause and re-execute the DML statement.

ORA-30929: ORDER SIBLINGS BY clause not allowed here

• OceanBase error code: 5325

• SQLSTATE: HY000

• Cause: The specified query with the ORDER SIBLINGS BY clause does not contain the CONNECT BY clause.

• Solution: Delete the ORDER SIBLINGS BY clause or add the CONNECT BY clause to the query.

ORA-30929: ORDER SIBLINGS BY clause not allowed here

• OceanBase error code: 5451
• SQLSTATE: 42000
• Cause: The ORDER SIBLINGS BY clause is specified in a query that does not have a CONNECT BY clause.
• Solution: Remove the ORDER SIBLINGS BY clause or add a CONNECT BY clause.

ORA-30929: ORDER SIBLINGS BY clause not allowed here

• OceanBase error code: 5772

• SQLSTATE: HY000

• Cause: The specified query with the ORDER SIBLINGS BY clause does not contain the CONNECT BY clause.

• Solution: Delete the ORDER SIBLINGS BY clause or add the CONNECT BY clause to the query.

ORA-30930: NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudo column

• OceanBase error code: 5773

• SQLSTATE: HY000

• Cause: CONNECT_BY_ISCYCLE is specified in a query, but this query does not contain the NOCYCLE keyword.

• Solution: Delete CONNECT_BY_ISCYCLE from the query or add the NOCYCLE keyword to the query.

ORA-30980: Invalid Input

• OceanBase error code: 5462
• SQLSTATE: 42000
• Cause: The type conversion failed due to invalid input.
• Solution: Enter data of the correct type.

ORA-31003: Parent %.*s already contains child entry %.*s

• OceanBase error code: 7433

• SQLSTATE: 42000

• Cause: The child that you attempted to insert into the XDB hierarchical resolver already exists.

• Solution: Insert a unique name into the container.

ORA-31011: XML parsing failed

• OceanBase error code: 9549

• SQLSTATE: HY000

• Cause: The XML parser returns an error when it parses a document.

• Solution: Check whether the document to be parsed is valid.

ORA-31012: Given XPATH expression not supported

• OceanBase error code: 7409
• SQLSTATE: 42000
• Cause: The specified XPath expression is not supported.
• Solution: Make sure that the specified XPath expression is valid and is supported by the current database version.

ORA-31013: invalid xpath expression

• OceanBase error code: 7404
• SQLSTATE: 42000
• Cause: The format of the XPath expression is incorrect or invalid.
• Solution: Make sure that the XPath expression and XML data are correct.

ORA-31056: The document being inserted does not conform to specified child name

• OceanBase error code: 7429

• SQLSTATE: 42000

• Cause: The inserted XML element does not conform to the registered XML schema specified by the URL.

• Solution: Insert an element that conforms to the specified XML schema.

ORA-31067: XML nodes must be updated with valid nodes and of the same type

• OceanBase error code: 7418
• SQLSTATE: 42000
• Cause: An invalid XML node or node type is used in the update.
• Solution: Make sure that the new node type matches the node type before the update.

ORA-31188: The specified printing option is invalid

• OceanBase error code: 7407
• SQLSTATE: 42000
• Cause: The specified printing option is invalid.
• Solution: Make sure that the specified printing option is valid.

ORA-31195: XML node '' (type=%s) does not support this operation

• OceanBase error code: 7430

• SQLSTATE: 42000

• Cause: The type of the specified node does not support the operation. Other unsupported operations include: adding a child node to an attribute node, or passing a document node as a child node.

• Solution: Use a node of a supported type in an operation.

ORA-31600: invalid input value %.*s for parameter %.*s in function %.*s

• OceanBase error code: 9504

• SQLSTATE: HY000

• Cause: The input parameter value is NULL or invalid.

• Solution: Specify a valid value and call the function again.

ORA-31603: object '%.*s' of type %.*s not found in schema '%.*s'

• OceanBase error code: 9503

• SQLSTATE: HY000

• Cause: The specified object cannot be found in the database.

• Solution: Modify the object configuration and try again.

ORA-32021: parameter value longer than %d characters

• OceanBase error code: 5939

• SQLSTATE: HY000

• Cause: The parameter value exceeds the maximum length, or one of the parameter values in the parameter list exceeds the maximum value.

• Solution: Reduce the length of the parameter value and try again. For the DISPATCHERS parameter, use a listener alias to reduce the value length.

ORA-32031: illegal reference of a query name in WITH clause

• OceanBase error code: 5737

• SQLSTATE: HY000

• Cause: Forward or recursive reference of a query name in the WITH clause is not allowed.

• Solution: Modify the query statement and try again.

ORA-32033: unsupported column aliasing

• OceanBase error code: 5738

• SQLSTATE: HY000

• Cause: The WITH clause does not support column aliases.

• Solution: Specify an alias in the subquery and try again.

ORA-32034: unsupported use of WITH clause

• OceanBase error code: 5739

• SQLSTATE: HY000

• Cause: The WITH clause is used improperly in either of the following ways:

  • A WITH clause is nested in another WITH clause.

  • In a set query, a WITH clause is specified for branches.

• Solution: Modify the query and try again.

ORA-32038: number of WITH clause column names does not match number of elements in select list

• OceanBase error code: 5740

• SQLSTATE: HY000

• Cause: A column alias or name list is specified for a WITH query name, but the number of elements in the list does not match the number of elements in the SELECT list of the definition query.

• Solution: Update the column alias list or SELECT list to ensure that they have the same number of elements.

ORA-32039: recursive WITH clause must have column alias list

• OceanBase error code: 5741

• SQLSTATE: HY000

• Cause: A WITH query recursively references itself, but no column alias list is specified for this query.

• Solution: Add a column alias list for the WITH query name.

ORA-32040: recursive WITH clause must use a UNION ALL operation

• OceanBase error code: 5742

• SQLSTATE: HY000

• Cause: A WITH query recursively references itself, but the UNION ALL operation is not used in the definition query.

• Solution: Rewrite the recursive WITH query so that the UNION ALL operation is used.

ORA-32041: UNION ALL operation in recursive WITH clause must have only two branches

• OceanBase error code: 5743

• SQLSTATE: HY000

• Cause: A WITH query recursively references itself but uses a UNION ALL operation with more than two branches, which is not supported.

• Solution: Rewrite the recursive WITH query so that it uses only two branches in the UNION ALL operation.

ORA-32042: recursive WITH clause must reference itself directly in one of the UNION ALL branches

• OceanBase error code: 5744

• SQLSTATE: HY000

• Cause: A WITH query recursively references itself indirectly. For example, it does so through a subquery or view.

• Solution: Rewrite the recursive WITH query so that it directly references itself in the FROM clause of a branch of the UNION ALL operation.

ORA-32043: recursive WITH clause needs an initialization branch

• OceanBase error code: 5745

• SQLSTATE: HY000

• Cause: A WITH query recursively references itself, but an initial branch that does not reference itself is absent in the UNION ALL operation.

• Solution: Rewrite the WITH query by adding an initial branch that does not reference itself to the UNION ALL operation.

ORA-32044: cycle detected while executing recursive WITH query

• OceanBase error code: 5746

• SQLSTATE: HY000

• Cause: A recursive WITH query forms a cycle, and the system stops this query to avoid an infinite cycle.

• Solution: Rewrite the recursive WITH query to stop the recursion, or use the CYCLE clause in the query.

ORA-32045: maximum level of recursion reached while executing recursive WITH query

• OceanBase error code: 5747

• SQLSTATE: HY000

• Cause: A recursive WITH query reaches the specified maximum recursion level and stops.

• Solution: Increase the maximum recursion level or use the CYCLE clause.

ORA-32046: sequence column name for SEARCH clause must not be part of the column alias list

• OceanBase error code: 5748

• SQLSTATE: HY000

• Cause: The SEARCH clause in a recursive WITH query specifies a sequence column, but this sequence column already exists in the column alias list of the WITH query.

• Solution: Specify a different name for the sequence column in the SEARCH clause, or delete this name from the column alias list.

ORA-32047: cycle mark value and non-cycle mark value must be one byte character string values

• OceanBase error code: 5749

• SQLSTATE: HY000

• Cause: The cycle mark or non-cycle mark value specified in the CYCLE clause of a recursive WITH query is not a one-byte string.

• Solution: Specify a one-byte string as the value of cycle mark or non-cycle mark in the CYCLE clause of the recursive WITH query.

ORA-32048: cycle mark column name for CYCLE clause must not be part of the column alias list

• OceanBase error code: 5750

• SQLSTATE: HY000

• Cause: The CYCLE clause in a recursive WITH query specifies a cycle mark column, but this column already exists in the column alias list of the WITH query.

• Solution: Specify a different name for the cycle mark column in the CYCLE clause, or delete this name from the column alias list.

ORA-32049: duplicate name found in column alias list for WITH clause

• OceanBase error code: 5751

• SQLSTATE: HY000

• Cause: A name appears multiple times in the column alias list of the WITH clause.

• Solution: Delete duplicate names from the column alias list.

ORA-32480: SEARCH and CYCLE clauses can only be specified for recursive WITH clause elements

• OceanBase error code: 5752

• SQLSTATE: HY000

• Cause: The SEARCH or CYCLE clause is specified for a non-recursive WITH clause element.

• Solution: Delete the SEARCH or CYCLE clause, or add recursion to the WITH clause element.

ORA-32481: cycle value for CYCLE clause must be different from the non-cycle value

• OceanBase error code: 5753

• SQLSTATE: HY000

• Cause: The CYCLE clause is specified for a recursive WITH query, but the cycle value is the same as a non-cycle value or the DEFAULT value.

• Solution: Change the cycle value or the non-cycle value to ensure that they are different.

ORA-32482: sequence column for SEARCH clause must be different from the cycle mark column for CYCLE clause

• OceanBase error code: 5754

• SQLSTATE: HY000

• Cause: The SEARCH and CYCLE clauses are specified for a recursive WITH query, but the sequence column of the SEARCH clause is the same as the cycle mark column of the CYCLE clause.

• Solution: Modify the sequence or cycle mark column to ensure that they are different.

ORA-32483: duplicate name found in sort specification list for SEARCH clause of WITH clause

• OceanBase error code: 5755

• SQLSTATE: HY000

• Cause: A SEARCH clause is specified for a recursive query, but the sort specification list in the recursive query contains duplicate names.

• Solution: Delete duplicate names from the sort specification list.

ORA-32484: duplicate name found in cycle column list for CYCLE clause of WITH clause

• OceanBase error code: 5756

• SQLSTATE: HY000

• Cause: A CYCLE clause is specified for a recursive query, but the cycle column list of the CYCLE clause contains duplicate names.

• Solution: Delete duplicate names from the cycle column list of the CYCLE clause.

ORA-32485: element in cycle column list of CYCLE clause must appear in the column alias list of the WITH clause element

• OceanBase error code: 5757

• SQLSTATE: HY000

• Cause: In the CYCLE clause specified for a recursive WITH query, the elements in the cycle column list are not included in the column alias list of the WITH clause element.

• Solution: Modify the cycle column list so that only the names included in the column alias list of the WITH clause element are used.

ORA-32486: unsupported operation in recursive branch of recursive WITH clause

• OceanBase error code: 5758

• SQLSTATE: HY000

• Cause: The recursive component of the UNION ALL operation in a recursive WITH clause element uses an unsupported operation. The recursive branch of the UNION ALL operation must not use GROUP BY, DISTINCT, MODEL, grouping sets, CONNECY BY, window functions, HAVING, or aggregate functions.

• Solution: Rewrite the query and ensure that it does not contain unsupported operations.

ORA-32487: unsupported join in recursive WITH query

• OceanBase error code: 5759

• SQLSTATE: HY000

• Cause: The recursive component in the recursive WITH clause element contains the following unsupported join operations:

  • A LEFT OUTER join with the name of the recursive query on the right side

  • A RIGHT OUTER join with the name of the recursive query on the left side

  • A FULL OUTER join that involves the name of the recursive query

• Solution: Rewrite the query and ensure that it does not contain unsupported join operations.

ORA-32488: WITH clause element did not have a column alias list

• OceanBase error code: 5760

• SQLSTATE: HY000

• Cause: A WITH clause element uses the SEARCH clause and/or the CYCLE clause but does not specify a column alias list for them.

• Solution: Add a column alias list for the WITH query name.

ORA-32489: element in sort specification list of SEARCH clause did not appear in the column alias list of the WITH clause element

• OceanBase error code: 5761

• SQLSTATE: HY000

• Cause: The elements in the sort specification list of the SEARCH clause specified for a recursive WITH query are not included in the column alias list of the WITH clause element.

• Solution: Modify the sort specification list so that only the names in the column alias list of the WITH clause element are used.

ORA-32490: recursive query name referenced more than once in recursive branch of recursive WITH clause element

• OceanBase error code: 5762

• SQLSTATE: HY000

• Cause: The recursive component of the UNION ALL operation in a recursive WITH clause element references the name of the recursive query multiple times. The recursive branch of the recursive WITH query can reference the name of the recursive query only once.

• Solution: Rewrite the query so that its recursive branch references the name of the query only once.

ORA-32575: Explicit column default is not supported for modifying views

• OceanBase error code: 5511
• SQLSTATE: 42000
• Cause: The DEFAULT keyword is used to modify the view.
• Solution: Omit column values to implicitly use the default values.

ORA-32595: DDL statement cannot be audited with BY SESSION specified

• OceanBase error code: 4364

• SQLSTATE: HY000

• Cause: You are attempting to audit a DDL statement with a specified BY SESSION clause. DDL statements can be audited only by using BY ACCESS.

• Solution: Use BY ACCESS to audit the DDL statement.

ORA-32792: prebuilt table managed column cannot be an identity column

• OceanBase error code: 5916

• SQLSTATE: HY000

• Cause: The operation attempted to create an instantiated view on a pre-built table with an identity column.

• Solution: Delete the identity attribute or delete the identity column from the instantiated view.

ORA-32793: cannot alter a system-generated sequence

• OceanBase error code: 5917

• SQLSTATE: HY000

• Cause: The operation attempted to modify a system-generated sequence.

• Solution: Do not modify sequences generated by the system, such as a sequence created for the identity column.

ORA-32794: cannot drop a system-generated sequence

• OceanBase error code: 5918

• SQLSTATE: HY000

• Cause: The operation attempted to drop a system-generated sequence.

• Solution: Do not drop sequences generated by the system, for example, a sequence created for the identity column.

ORA-32795: cannot insert into a generated always identity column

• OceanBase error code: 5919

• SQLSTATE: HY000

• Cause: The operation attempted to insert a value into an identity column created by using the GENERATED ALWAYS keyword.

• Solution: Do not directly insert a value into an identity column that is created by using the GENERATED ALWAYS keyword. Instead, the value should be provided by the associated sequence generator.

ORA-32796: cannot update a generated always identity column

• OceanBase error code: 5920

• SQLSTATE: HY000

• Cause: The operation attempted to update an identity column created by using the GENERATED ALWAYS keyword.

• Solution: Do not directly update an identity column that is created by using the GENERATED ALWAYS keyword.

ORA-32797: identity column sequence mismatch in ALTER TABLE EXCHANGE PARTITION

• OceanBase error code: 5921

• SQLSTATE: HY000

• Cause: Sequences of identity columns of two tables specified in the EXCHANGE statement are neither incremented nor decremented.

• Solution: Ensure that the sequences of the identity columns with INCREMENT BY have the same symbol.

ORA-32798: cannot rename a system-generated sequence

• OceanBase error code: 5922

• SQLSTATE: HY000

• Cause: The operation attempted to rename a system-generated sequence.

• Solution: Do not rename sequences generated by the system, such as a sequence created for the identity column.

ORA-38101: Invalid column in the INSERT VALUES Clause:'%.*s'.'%.*s'

• OceanBase error code: 5803

• SQLSTATE: HY000

• Cause: The INSERT VALUES clause references an invalid table column.

ORA-38104: Columns referenced in the ON Clause cannot be updated:'%.*s'.'%.*s'

• OceanBase error code: 38104

• SQLSTATE: HY000

• Cause: LHS in UPDATE SET contains columns referenced in the ON clause.

ORA-38778: Restore point %s already exists

• OceanBase error code: 6259 and 6261

• SQLSTATE: HY000

• Cause: The restore point name in the CREATE RESTORE POINT statement already exists. The restore point name must be unique.

• Solution: Specify another name or delete the existing restore point with the same name.

ORA-38779: cannot create restore point - too many restore points

• OceanBase error code: 6263

• SQLSTATE: HY000

• Cause: The number of created restore points has reached the maximum number allowed.

• Solution: Delete some existing restore points and try again.

ORA-38780: Restore point %s does not exists

• OceanBase error code: 6260 and 6262

• SQLSTATE: HY000

• Cause: The restore point name specified in the statement does not exist.

• Solution: Query the restore point table for the restore point.

ORA-38900: miss mandatory column %.*s of error log table

• OceanBase error code: 5385

• SQLSTATE: HY000

• Cause: The mandatory column of the error logging table is missing.

• Solution: Add the named column to the error logging table.

ORA-39956: duplicate setting for PL/SQL compiler parameter %.*s

• OceanBase error code: 5964

• SQLSTATE: HY000

• Cause: A PL/SQL compiler parameter was set more than once.

• Solution: Remove the duplicate setting of the PL/SQL compiler parameter.

ORA-39962: invalid parameter for PLSQL_CCFLAGS

• OceanBase error code: 5940

• SQLSTATE: HY000

• Cause: The value of the PLSQL_CCFLAGS parameter is invalid.

• Solution: Specify a valid value for the PLSQL_CCFLAGS parameter.

ORA-40441: JSON syntax error

• OceanBase error code: 5411
• SQLSTATE: 22032
• Cause: The syntax of the JavaScript Object Notation (JSON) data provided is invalid and cannot be parsed.
• Solution: Check the JSON data and provide the JSON data with the correct syntax.

ORA-40441: JSON syntax error

• OceanBase error code: 5412
• SQLSTATE: 22032
• Cause: The syntax of the JavaScript Object Notation (JSON) data provided is invalid and cannot be parsed.
• Solution: Check the JSON data and provide the JSON data with the correct syntax.

ORA-40441: JSON syntax error

• OceanBase error code: 5447
• SQLSTATE: 42000
• Cause: The syntax of the JavaScript Object Notation (JSON) data provided is invalid and cannot be parsed.
• Solution: Provide the JSON data with the correct syntax.

ORA-40441: This version doesn't yet support 'references in JSON Schema.

• OceanBase error code: 6284

• SQLSTATE: 42000

• Cause: OceanBase Database of the current version does not support references in JSON mode.

• Solution: Modify the design of JSON mode to avoid using references.

ORA-40442: JSON path expression syntax error ('INT')

• OceanBase error code: 5414
• SQLSTATE: 22032
• Cause: The syntax of the JSON path expression provided is invalid and cannot be parsed.
• Solution: Provide the JSON path expression with the correct syntax.

ORA-40442: JSON path expression syntax error ('INT').JSON path expression syntax error ('%s')

• OceanBase error code: 5442
• SQLSTATE: 42000
• Cause: The syntax of the JSON path expression provided is invalid and cannot be parsed.
• Solution: Provide the JSON path expression with the correct syntax.

ORA-40444: JSON processing error

• OceanBase error code: 5514
• SQLSTATE: 42000
• Cause: A JSON data processing error occurred.

ORA-40449: invalid data type for return value

• OceanBase error code: 5443
• SQLSTATE: 42000
• Cause: The data type provided for the return value is invalid or is not supported.
• Solution: Enter a supported return value.

ORA-40450: invalid '%s' clause

• OceanBase error code: 5460
• SQLSTATE: 42000
• Cause: The %s statement is invalid.
• Solution: Provide the correct %s statement.

ORA-40451: invalid default value provided

• OceanBase error code: 5486
• SQLSTATE: 42000
• Cause: The default value provided is invalid.

ORA-40452: default value not matching type defined in RETURNING clause

• OceanBase error code: 5474
• SQLSTATE: 42000
• Cause: The default value is not of the type defined in the RETURNING statement.
• Solution: Ensure that the default value is of the type defined in the RETURNING clause.

ORA-40454: path expression not a literal

• OceanBase error code: 5487
• SQLSTATE: 42000
• Cause: The path expression is not a literal.

ORA-40455: default value not a literal

• OceanBase error code: 5446
• SQLSTATE: 42000
• Cause: The default value provided is not a literal (constant).
• Solution: Provide a constant value.

ORA-40456: JSON_VALUE evaluated to non*scalar value

• OceanBase error code: 5444
• SQLSTATE: 42000
• Cause: The JSON path expression provided selected a non-scalar value.
• Solution: Correct the JSON path expression or use JSON_QUERY.

ORA-40459: output value too large (actual: %d, maximum: %d)

• OceanBase error code: 5473
• SQLSTATE: 42000
• Cause: The provided JSON operator generates a result that exceeds the maximum length specified in the RETURNING clause.
• Solution: Increase the maximum length of the data type in the RETURNING clause, or use CLOB/BLOB in the RETURNING clause.

ORA-40462: No value was found by '%.192s' on the specified path

• OceanBase error code: 5432
• SQLSTATE: 22035
• Cause: The JSON path expression provided did not select any value.
• Solution: Correct the JSON path expression.

ORA-40462: JSON_VALUE evaluated to no value

• OceanBase error code: 5445
• SQLSTATE: 42000
• Cause: The JSON path expression provided did not select any value.
• Solution: Correct the JSON path expression.

ORA-40470: More than one value was found by '%.192s' on the specified path

• OceanBase error code: 5433
• SQLSTATE: 22034
• Cause: The JSON path expression provided selected multiple values.
• Solution: Correct the JSON path expression or use JSON_QUERY.

ORA-40473: duplicate key names in JSON object

• OceanBase error code: 5453
• SQLSTATE: 42000
• Cause: The JSON data provided has a duplicate key name in an object.
• Solution: Provide JSON data with a unique key name in each JSON object.

ORA-40476: JSON key too long

• OceanBase error code: 5422
• SQLSTATE: 22032
• Cause: The JSON data provided has a key that exceeds the maximum name length.
• Solution: Provide JSON data with a shorter key name.

ORA-40480: result cannot be returned without array wrapper

• OceanBase error code: 5449
• SQLSTATE: 42000
• Cause: The result cannot be returned without an array wrapper.

ORA-40481: ASCII or PRETTY not supported for non*textual return data type

• OceanBase error code: 5469
• SQLSTATE: 42000
• Cause: An attempt was made to pretty print or escape non-ASCII characters for a non-textual output of a JSON operation.
• Solution: Change the return data type to VARCHAR2 or CLOB, or remove the PRETTY or ASCII serialization option.

ORA-40484: invalid data type for '%s' column

• OceanBase error code: 5459
• SQLSTATE: 42000
• Cause: The data type of column %s is invalid.
• Solution: Enter correct information for column %s.

ORA-40487: invalid usage of keyword EXISTS

• OceanBase error code: 5480
• SQLSTATE: 42000
• Cause: An invalid keyword exists. The syntax of the expression is incorrect.

ORA-40491: invalid input data type for JSON_TABLE

• OceanBase error code: 5481
• SQLSTATE: 42000
• Cause: The input to JSON_TABLE is of an invalid data type.

ORA-40560: JSON_TABLE nested path expressions not disjunct

• OceanBase error code: 5483
• SQLSTATE: 42000
• Cause: The JSON_TABLE expression contains duplicate path expressions at the same level.

ORA-40565: JSON path expression did not select a value

• OceanBase error code: 5468
• SQLSTATE: 42000
• Cause: The JSON path expression did not select any value.
• Solution: Correct the JSON path expression.

ORA-40566: JSON path expression selected a value of different data type

• OceanBase error code: 5467
• SQLSTATE: 42000
• Cause: The JSON path expression selected a value of a data type that is different from the requested data type.
• Solution: Use another get*method to retrieve the value selected by the JSON path expression.

ORA-40569: Unimplemented JSON feature

• OceanBase error code: 5479
• SQLSTATE: 42000
• Cause: An attempt was made to execute an unimplemented JSON feature.
• Solution: Check that the expression exists.

ORA-40570: JSON conversion failed

• OceanBase error code: 5476
• SQLSTATE: 42000
• Cause: JSON conversion failed.
• Solution: Check the type definition or the selected JSON value.

ORA-40571: JSON key name not found.", "JSON key name not found

• OceanBase error code: 5485
• SQLSTATE: 42000
• Cause: The key was not found in JSON data.

ORA-40573: Invalid use of PL/SQL JSON object type

• OceanBase error code: 5470
• SQLSTATE: 42000
• Cause: An attempt was made to use a PL/SQL JSON object type in an invalid context.
• Solution: Use PL/SQL JSON object types only inside PL/SQL.

ORA-40576: Invalid use of bind variable in SQL/JSON path

• OceanBase error code: 5484
• SQLSTATE: 42000
• Cause: A bind variable in the SQL/JSON path is used improperly.

ORA-40587: invalid JSON type

• OceanBase error code: 5441
• SQLSTATE: 42000
• Cause: The JSON type is invalid. The JSON text is invalid.

ORA-40595: Name input to JSON generation function cannot be null

• OceanBase error code: 5429
• SQLSTATE: 22032
• Cause: The name input given to the JSON generation function was null.
• Solution: Ensure that the input has a valid value.

ORA-40597: JSON path expression syntax error ('%.*s')

• OceanBase error code: 5454
• SQLSTATE: 42000
• Cause: The specified JSON path expression had invalid syntax ("%.*s").

ORA-40600: JSON_EQUAL used outside predicate

• OceanBase error code: 5448
• SQLSTATE: 42000
• Cause: JSON_EQUAL is used outside the predicate.
• Solution: Use JSON_EQUAL in the predicate. For example, embed it in a CASE expression.

ORA-40629: Patch specification is not valid JSON

• OceanBase error code: 5450
• SQLSTATE: 42000
• Cause: The patch specification was not expressed in valid JSON.
• Solution: Ensure that the patch specification is expressed in valid JSON.

ORA-40654: Input to JSON generation function has unsupported data type

• OceanBase error code: 7420

• SQLSTATE: HY000

• Cause: The input parameter of the JSON generation function contains an unsupported data type.

• Solution: Use supported data types or use a conversion function to convert the data types of the input parameters to supported ones.

ORA-40654: Input to JSON generation function has unsupported data type

• OceanBase error code: 7431

• SQLSTATE: HY000

• Cause: The input parameter of the JSON generation function contains an unsupported data type.

• Solution: Use supported input or use a conversion function to convert the input to supported data types.

ORA-40656: Variable in JSON path expression has no value in PASSING clause

• OceanBase error code: 5456
• SQLSTATE: 42000
• Cause: The JSON path expression contained a variable that had no value in the PASSING clause.
• Solution: Add the variable to the external PASSING clause and ensure that the variable names match.

ORA-40664: cannot add additional IS jSON check constraint

• OceanBase error code: 5464
• SQLSTATE: 42000
• Cause: An attempt was made to add an IS JSON check constraint to a column that already had an IS JSON check constraint.
• Solution: Check the IS JSON constraint.

ORA-40688: date or time stamp string value does not conform to ISO 8601 format

• OceanBase error code: 5472
• SQLSTATE: 42000
• Cause: The date or timestamp string value did not conform to the ISO 8601 format.
• Solution: Provide a proper date or timestamp string value conforming to the ISO 8601 format for conversion.

ORA-40750: Patch specification is not valid JSON

• OceanBase error code: 5452
• SQLSTATE: 42000
• Cause: The specified sorting condition includes LOB columns, such as CLOB, BLOB, or JSON columns.
• Solution: Ensure that the sorting column data type is not a large object, such as CLOB, BLOB, or JSON.

ORA-40779: Truncation is not supported with data type in RETURNING clause

• OceanBase error code: 5478
• SQLSTATE: 42000
• Cause: The data type in the RETURNING statement does not support truncation.

ORA-40783: invalid binary JSON data\nstring

• OceanBase error code: 5413
• SQLSTATE: 22032
• Cause: The provided binary JSON data is invalid.
• Solution: Provide valid binary JSON data.

ORA-40796: invalid comparison operation involving JSON type value

• OceanBase error code: 5461
• SQLSTATE: 42000
• Cause: An attempt was made to compare JSON type values.
• Solution: Add a JSON tail type conversion function to compare the JSON type value with the scalar value. Use JSON_EQUAL to compare two JSON type values.

ORA-40799: cannot convert Boolean value to number

• OceanBase error code: 5475
• SQLSTATE: 42000
• Cause: An attempt was made to convert a Boolean value selected by a JSON path expression with a number() or numberOnly() function to a number.
• Solution: Remove the number()/numberOnly() function from the JSON path expression.

ORA-40833: empty input to JSON operator

• OceanBase error code: 5463
• SQLSTATE: 42000
• Cause: An empty input, such as an empty CLOB, was provided to a JSON operator that expects a non-empty input.
• Solution: Check and correct the input.

ORA-40876: invalid JSON schema document

• OceanBase error code: 6285

• SQLSTATE: 22032

• Cause: The JSON mode is invalid.

• Solution: Use the correct JSON mode.

ORA-42399: cannot perform a DML operation on a read-only view

• OceanBase error code: 5723

• SQLSTATE: HY000

• Cause: You are attempting to insert, delete, or update rows in a read-only view, which is not allowed.

• Solution: Execute required DML operations on the base table of the view, or use the ALTER VIEW ... READ WRITE statement to make the view operable.