Cause | The statement is not a valid DML (Data Manipulation Language) statement. |
Action | Check the syntax. |
Cause | Unable to execute the DML statement. |
Action | Check if DML is executable in the current DB state. |
Cause | There is a syntax error. |
Action | Check the statement syntax. |
Cause | The identifier is too long. |
Action | Adjust the length to less than 30 characters. |
Cause | The FROM keyword is missing. |
Action | Check the statement syntax. |
Cause | A conditional expression is missing or contains syntax errors. |
Action | Check the statement syntax. |
Cause | Invalid or missing expression. |
Action | Check the expression syntax. |
Cause | There is a syntax error. |
Action | Check the statement syntax. |
Cause | INTO keyword is missing. |
Action | Check the statement syntax. |
Cause | VALUES keyword is missing. |
Action | Check the statement syntax. |
Cause | A comma is missing. |
Action | Check the statement syntax. |
Cause | SELECT keyword is missing. |
Action | Check the statement syntax. |
Cause | NULL keyword is missing. |
Action | Check the statement syntax. |
Cause | Right parenthesis is missing. |
Action | Check the statement syntax. |
Cause | BY keyword is missing after the ORDER, GROUP or CONNECT keyword. |
Action | Check the statement syntax. |
Cause | In a hierarchical query, the CONNECT BY clause should be specified. |
Action | Check the statement syntax. |
Cause | In a SET clause, an \"=\" is missing. |
Action | Check the statement syntax. |
Cause | WITH keyword is missing after a START keyword. |
Action | Check the statement syntax. |
Cause | In an UPDATE statement, a SET clause is missing. |
Action | Check the statement syntax. |
Cause | The specification of the table, view or inline view in the FROM clause uses invalid syntax. |
Action | Check the statement syntax. |
Cause | The SQL statement is invalid. |
Action | Check the statement syntax. |
Cause | Invalid qualifier specification. |
Action | Check the qualifier syntax. |
Cause | A derived column with this name already exists. |
Action | Rename the column. |
Cause | The number of derived columns does not match the number of columns in a base table, view or inline view. |
Action | Modify the query. |
Cause | Unable to interpret the column or identifier. |
Action | Check the identifier. |
Cause | Columns with the same name exist in more than one table, view or inline view. |
Action | Specify a qualifier for the column name. |
Cause | The FOR UPDATE clause was used in a SELECT query block other than the top one. |
Action | Check the query block syntax. |
Cause | The FOR UPDATE statement cannot be used in a query that uses GROUP BY, DISTINCT or set functions. |
Action | Modify the query. |
Cause | The number of expressions specified in a VALUE statement is less than the number of columns. |
Action | Ensure that the numbers match. |
Cause | The number of expressions specified in a VALUE statement is greater than the number of columns. |
Action | Ensure that the numbers match. |
Cause | The position specified in ORDER BY clause is out of range. |
Action | Specify a valid position. |
Cause | The specified schema object does not exist. |
Action | Check the schema object name. |
Cause | The sequence does not exist. |
Action | Check the sequence name. |
Cause | The synonym does not exist. |
Action | Check the synonym name. |
Cause | Procedure or function does not exist. |
Action | Check the procedure name. |
Cause | Set functions cannot be used in SELECT LIST, HAVING, or ORDER BY clauses. |
Action | Check the statement syntax. |
Cause | An expression that was not specified in a GROUP BY clause was used. |
Action | Modify the query. |
Cause | When DISTINCT is specified in a SELECT LIST clause, it must be used in an ORDER BY clause. |
Action | Modify the query. |
Cause | A column name is used more than once. |
Action | Modify the query. |
Cause | In a FROM clause, schema objects other than tables and views cannot be used. |
Action | Modify the query. |
Cause | Sub queries cannot be used along with the outer join condition. |
Action | Modify the query. |
Cause | The OR operator cannot be used along with the outer join condition. |
Action | Modify the query. |
Cause | The IN operator cannot be used along with the outer join condition. |
Action | Modify the query. |
Cause | Outer joining of two tables is not allowed. |
Action | Delete one of the outer join conditions. |
Cause | Outer joining between more than two tables is not allowed. |
Action | Modify the query. |
Cause | Outer joins cannot be used with ANSI joins. |
Action | Modify the query. |
Cause | An attempt was made to update virtual table. |
Action | Virtual table cannot be updated. |
Cause | In an ORDER BY clause in a query where SET the operator was used, invalid expressions were used. |
Action | Modify the query. |
Cause | Procedure cannot be used in DML statement. |
Action | Unable to use procedure. |
Cause | Functions cannot be used in a CALL clause which requires a procedure. |
Action | Use a valid procedure. |
Cause | The current object is disabled. |
Action | Recreate the object. |
Cause | An attempt was made to access unauthorized objects or columns. |
Action | Unable to access the object. |
Cause | Subquery cannot be used in GROUP BY clause. |
Action | Modify the query. |
Cause | The number of expressions specified in the RETURNING clause and that of columns to be updated do not match with each other. |
Action | Modify the query. |
Cause | The number of PROJECTIONs between blocks used in SET operation do not match. |
Action | Modify the query. |
Cause | The column cannot be updated. |
Action | Check whether or not the column is in a key-preserved table. |
Cause | More than two key-preserved tables cannot be updated at once. |
Action | Modify the query to update only one key preserved table. |
Cause | The view cannot be updated. |
Action | Check whether or not it is a key-preserved table. |
Cause | A key preserved table, which can be deleted, does not exist in view. |
Action | Check the definition of the view. |
Cause | Columns in USING clauses or NATURAL joins cannot have a qualifier. |
Action | Delete the qualifier. |
Cause | The nesting level of aggregation functions is too deep. |
Action | Modify the query. |
Cause | LONG type columns cannot be used. |
Action | Modify the query. |
Cause | LOB type columns cannot be used. |
Action | Modify the query. |
Cause | An invalid host variable name was used. |
Action | Ensure the host variable name uses proper syntax. |
Cause | View definition cannot reference itself. |
Action | Check the view definition. |
Cause | Invalid window range expression in analytic function. |
Action | Modify the query. |
Cause | The ORDER BY clause cannot be used in a subquery. |
Action | Modify the query. |
Cause | Columns which are not used in a GROUP BY clause are used outside aggregation functions. |
Action | Change the query. |
Cause | SELECT LIST clauses that use the nested aggregation function cannot use subqueries. |
Action | Delete the subquery. |
Cause | View cannot use partition name. |
Action | Delete the partition name. |
Cause | A subquery cannot be used in DEFAULT, CHECK or RETURNING clauses. |
Action | Delete the subquery. |
Cause | UDF cannot be used in DEFAULT or CHECK clauses. |
Action | Modify the query. |
Cause | Sequence being is used in an invalid position. |
Action | Modify the query. |
Cause | ROWNUM cannot be used in DEFAULT or CHECK clauses, or as a join condition. |
Action | Modify the query. |
Cause | LEVEL cannot be used in DEFAULT or CHECK clauses. |
Action | Modify the query. |
Cause | The bind variable cannot be used in DEFAULT or CHECK clauses. |
Action | Modify the query. |
Cause | The aggregation function cannot be used in DEFAULT or CHECK columns. |
Action | Modify the query. |
Cause | The analytic function cannot be used in DEFAULT clauses, CHECK clauses, and in index columns. |
Action | Modify the query. |
Cause | PRIOR keyword can be used only in a CONNECT BY clause. |
Action | Modify the query. |
Cause | Column cannot be used in DEFAULT or VALUES clauses. |
Action | Modify the query. |
Cause | Non-deterministic functions cannot be used in DEFAULT clauses, CHECK clauses, and in index columns. |
Action | Modify the query. |
Cause | PARTITION or SUBPARTITION keywords cannot be used in non-partitioned tables. |
Action | Modify the query. |
Cause | Unable to find the partition name. |
Action | Check the partition name and retry. |
Cause | Unable to find the sub-partition name. |
Action | Check the sub-partition name and retry. |
Cause | The syntax is not supported by the current version. |
Action | Modify the query. |
Cause | The expression in a SET clause is incomplete. |
Action | Correct the expression. |
Cause | View definition, referenced schema object or authority check has errors. |
Action | Correct the error. |
Cause | Invalid number of argument of the OVERLAP function. |
Action | Verify the use of the OVERLAP function. |
Cause | Bind variable names starting with ':SYS_B_' cannot be used. |
Action | Change the name. |
Cause | An attempt was made to execute INSERT/UPDATE/DELETE on a table with constraints in a DISABLE VALIDATE state. |
Action | Modify the constraints condition. |
Cause | SIBLINGS cannot be specified in the ORDER BY clause. |
Action | Modify the query. |
Cause | INTO and BULK COLLECT INTO clauses can be specified only in the top query block. |
Action | Modify the query. |
Cause | LEVEL, PRIOR and ROWNUM keywords cannot be used with the PRIOR operator. |
Action | Modify the query. |
Cause | Percentage in a SAMPLE clause must be between 0.000001 and 100 (must be less than 100). |
Action | Modify the value to fall within the range. |
Cause | The CONNECT_BY_ROOT operator cannot be used here. |
Action | Modify the query. |
Cause | The CONNECT_BY_ISLEAF operator cannot be used here. |
Action | Modify the query. |
Cause | The SYS_CONNECT_BY_PATH operator cannot be used here. |
Action | Modify the query. |
Cause | The CONNECT_BY_ISCYCLE operator cannot be used here. |
Action | Modify the query. |
Cause | Target of MERGE INTO statement must be a table. |
Action | Check the target object. |
Cause | The column used in an ON clause cannot be updated. |
Action | Modify the query. |
Cause | An outer join cannot be specified for a correlation column. |
Action | Change the query. |
Cause | Synonyms cannot reference themselves. |
Action | Check the definition of the synonym. |
Cause | More than 255 arguments were used. |
Action | Reduce the number of arguments in the DECODE function. |
Cause | More than 65535 arguments were used. |
Action | Reduce the number of arguments in the CASE function. |
Cause | The outer join operator can only be used in ON and WHERE clauses. |
Action | Modify the query. |
Cause | The MERGE statement attempted to process more than two DB instances. |
Action | Modify the query. |
Cause | Invalid condition expression. |
Action | Modify the condition expression. |
Cause | Only expressions with the same value in GROUP BY clauses are allowed. |
Action | Use only expressions which are used in a constant expression or GROUP BY clause. |
Cause | A single multitable insert statement contained more than 127 WHEN clauses. |
Action | Reduce the number of WHEN clauses in the statement. |
Cause | View or remote table cannot be the target of a multitable insert. |
Action | Modify the query. |
Cause | More than 10,000 arguments were used. |
Action | Reduce the number of arguments in the PSM function. |
Cause | An argument required for the function was omitted. |
Action | Specify the omitted argument again. |
Cause | The number of arguments specified for a function exceeds the number required. |
Action | Delete extraneous arguments. |
Cause | The flashback query clause was used in an invalid location. |
Action | Modify the query. |
Cause | The DISTINCT option cannot be used for this function. |
Action | Delete the DISTINCT option and try again. |
Cause | The datatype used in the function is invalid. |
Action | Check the arguments of the function. |
Cause | Unable to select rowid column from the index-organized table. |
Action | Remove the rowid column and try again. |
Cause | Failed to recompile the invalid trigger. |
Action | Modify the trigger source code and create again. |
Cause | A column required for the error log table is is missing. |
Action | Check the error log table. |
Cause | The number of arguments is incorrect. |
Action | Check the syntax and change it. |
Cause | Internal hint cannot be used. |
Action | Remove internal hint. |
Cause | The query defined in the RECURSIVE WITH clause violates an integrity constraint. |
Action | Define the query in the format of (anchor member) UNION ALL (recursive member). |
Cause | Column name aliases were not defined for the query names. |
Action | Add a column alias list for the query names in the RECURSIVE WITH clause. |
Cause | The following statement cannot be used as a recursive member to the right of UNION ALL statement within the recursive WITH query: GROUP BY, HAVING, DISTINCT, CONNECT BY, window functions, set operations, and aggregate functions. |
Action | Rewrite the recursive WITH query so that the unsupported statements are not used. |
Cause | The recursive WITH clause contains the recursive query name at one of the following positions: the right side of the LEFT OUTER JOIN, the left side of the RIGHT OUTER JOIN, the FULL OUTER JOIN, or in the subquery. |
Action | Rewrite the query with the supported join. |
Cause | An attempt was made to execute DML on a read-only table. |
Action | Read-only table cannot be updated. |
Cause | Unable to find the index name. |
Action | Check the index name and retry. |
Cause | INDEX_PARTITION or INDEX_SUBPARTITION keywords cannot be used in non-partitioned indexes. |
Action | Modify the query. |
Cause | The predicate returned by the policy function refers to the object that the policy is attached to. |
Action | Check the definition of the policy function. |
Cause | The predicate string generated by the policy function is not valid for this object. |
Action | Check the definition of the policy function. |
Cause | Association operator (=>) can only be used as an UDF argument. |
Action | Modify the query. |
Cause | Check the definition or the call of the user-defined aggregate function. |
Action | Modify the definition of the user-defined aggregate function and regenerate it. |
Cause | Check the definition of the object type. |
Action | Modify the object type definition and regenerate it. |
Cause | Check the query and the definition of the object type. |
Action | Modify the query or the definition of the object type and regenerate it. |
Cause | Check the query and the definition of the object type. |
Action | Modify the query or the definition of the object type and regenerate it. |
Cause | An index was not specified in the IGNORE_ROW_ON_DUPKEY_INDEX hint. |
Action | Specify a unique index defined in the table. |
Cause | The unique index was not found. |
Action | Specify a unique index defined in the table. |
Cause | Multiple unique indexes were specified in the index hint. |
Action | Specify a single unique index. |
Cause | The specified function argument is invalid. |
Action | Check the declaration of the function. |
Cause | In the current boot mode, this DML cannot be executed. |
Action | Change the boot mode and run the DML statement again. |
Cause | Attempted to insert a value in a virtual column. |
Action | Write insert statements except for this column. |
Cause | Attempted to update a value in a virtual column. |
Action | Remove the SET clause for this column in UPDATE statements. |
Cause | A value other than null cannot be inserted into the AUTO_INCREMENT COLUMN. |
Action | Remove AUTO_INCREMENT COLUMN or set the AUTO_INCREMENT COLUMN to null in the insert statement. |
Cause | Self reference can be used only once in a recursive node in a recursive WITH. |
Action | Rewrite the query so that a WITH query name can be used only once. |
Cause | Only expressions that return a built-in type are allowed in the current context. |
Action | Check the return type of the expression in the current context. |