SQL error codes (ODPS-01CCCCX) - MaxCompute - Alibaba Cloud Documentation Center

This topic describes SQL error codes, their triggers, and their solutions.

This type of error code has the following format.

ODPS-01CCCCX:General description - Context-specific description

SQL errors originate from the META (error codes 1000-1999), PROCESSOR (error codes 2000-2999), PARSER (error codes 3000-3999), and PLANNER (error codes 4000-4999) modules. The following list describes these error codes.

ODPS-0110011:Authorization exception

Module: META.
Severity level: 1.
Trigger: Insufficient permissions.
Resolution: Contact the project owner to grant the required permissions. For more information, see MaxCompute permissions.

ODPS-0110021:Invalid parameters

Module: META.
Severity: 1.
Cause: The provided parameters are invalid.
Resolution: Check the input parameters and modify them to ensure they are valid.

ODPS-0110031:Invalid object type

Module: META.
Severity: 1.
Cause: An invalid object type was specified.
Resolution: Check the input object and modify it to a valid object type.

ODPS-0110041:Invalid meta operation - AlreadyExistsException(message:Partition already exists, existed values:)

Module: META.
Severity: 1.
Trigger condition: MaxCompute does not have a table locking mechanism. This can cause metadata contention and trigger this error if you perform multiple read and write operations on the same partition simultaneously.
Resolution: Do not perform simultaneous operations on the same partition because MaxCompute does not have a table locking mechanism.

ODPS-0110061: Failed to run ddltask - AlreadyExistsException(message:Partition already exists, existed values:)

Module: META.
Severity level: 1.
Trigger condition: MaxCompute does not provide a locking mechanism for tables. This error is caused by metadata contention and is likely to occur if you perform multiple read and write operations on the same partition simultaneously.
Resolution: Do not perform simultaneous operations on the same table. MaxCompute does not provide a locking mechanism.

ODPS-0110061:Failed to run ddltask - SimpleLock conflict failure, add partition is already on-going

Module: META.
Severity level: 1.
Trigger condition: This error occurs when you add the same partition multiple times. MaxCompute executes only the first command it receives to add the partition and ignores subsequent requests.
Resolution: Avoid performing concurrent operations on the same partition.

ODPS-0110061: Failed to run ddltask - Your project is not allowed to install the package

Module: META.
Severity level: 1.
Trigger condition: This error occurs if you use dynamic data masking and run the install package aegis.aegis_package; command without adding the MaxCompute project that requires data masking to the masking project.
Resolution: Before you run the install package aegis.aegis_package; command, add the MaxCompute project that requires data masking to the masking project. For more information, see Dynamic data masking.

ODPS-0110999: Critical! Internal error happened in commit operation and rollback failed, possible breach of atomicity - Rename directory failed during DDLTask.

Module: META.
Severity: 1.
Trigger condition: MaxCompute does not enforce concurrency control when multiple tasks modify the same table. In rare cases, a concurrency conflict may occur during the final META operation, which causes an execution exception. This can happen during ALTER and INSERT operations.
Resolution: You can convert the table to a partitioned table and write the data from each SQL statement into a separate partition. This allows for concurrent operations.

ODPS-0120011:Authorization exception

Module: PROCESSOR.
Severity: 1.
Trigger: Insufficient permissions.
Resolution: Contact the project owner to grant the required permissions. For more information, see MaxCompute permissions.

ODPS-0120021:the delimitor must be the same in wm_concat

Module: PROCESSOR.
Severity level: 1.
Trigger condition: All separators within a group must be identical.
Resolution: Use a consistent separator for the group.

ODPS-0120031:Instance has been cancelled

Module: PROCESSOR.
Severity: 1.
Trigger: The instance is canceled.
Resolution: You can run the status <instance_id>; command in the MaxCompute client to confirm the instance status.

ODPS-0121011:Invalid regular expression pattern

Module: PROCESSOR.
Severity level: 1.
Trigger condition: A built-in function received an invalid regular expression.
Resolution: Modify the regular expression to use a valid pattern. For more information about regular expressions, see RLIKE character matching.

ODPS-0121021:Regexec call failed

Module: PROCESSOR.
Severity level: 1.
Cause: An error occurred during regular expression matching.
Resolution: Ensure that the regular expression is valid. For more information about regular expressions, see RLIKE character matching.

ODPS-0121035:Illegal implicit type cast

Module: PROCESSOR.
Severity level: 5.
Trigger condition: A type conversion error occurred. This error is usually caused by an unsupported implicit type conversion that violates the conversion rules.
Resolution: For more information about implicit type conversion, see Implicit type conversion and its scope.

ODPS-0121045:Unsupported return type

Module: PROCESSOR
Severity: 5
Trigger: The return value is not supported.
Resolution: Use a supported return value.

ODPS-0121055:Empty argument value

Module: PROCESSOR
Severity: 5
Trigger condition: The value of an input parameter is empty or NULL.
Resolution: Provide a valid value for the input parameter.

ODPS-0121065:Argument value out of range

Module: PROCESSOR.
Severity level: 5.
Trigger condition: The value of a parameter is outside the allowed range.
Resolution: Change the parameter to a value within the allowed range.

ODPS-0121075:Invalid number of arguments

Module: PROCESSOR
Severity level: 5
Cause: The number of arguments is invalid.
Resolution: Correct the number of arguments.

ODPS-0121081:Illegal argument type

Module: PROCESSOR
Severity: 1
Trigger condition: The parameter has an incorrect primitive data type.
Solution: Ensure that the parameter uses a valid primitive data type.

ODPS-0121095:Invalid arguments

Module: PROCESSOR.
Severity: 5.
Trigger: The input parameters are invalid.
Resolution: Correct the input parameters.

ODPS-0121105:Constant argument value expected

Module: PROCESSOR.
Severity level: 5.
Trigger condition: This error occurs because a column name was entered where a constant is expected.
Resolution: Change the input to a constant.

ODPS-0121115:Column reference expected

Module: PROCESSOR
Severity: 5
Trigger condition: A constant was entered where a column reference is expected.
Resolution: Replace the constant with a column reference.

ODPS-0121125:Unsupported function or operation

Module: PROCESSOR.
Severity level: 5.
Cause: An unsupported User-Defined Function (UDF) or operation was used.
Resolution: Modify the UDF or use a supported operation.

ODPS-0121145:Data overflow

Module: PROCESSOR.
Severity level: 5.
Trigger condition: A data overflow occurs when a value exceeds the range of its data type. This can be caused by an aggregate function, such as `sum`, or a division operation in which the divisor is a DECIMAL type with a value of 0, such as SELECT 1BD / 0BD;.
Resolution: Modify the operation that causes the data overflow.

ODPS-0123049: buffer overflow

Module: PROCESSOR.
Severity level: 9.
Trigger: Memory overflow.
Resolution: Check the data for issues. For example, a Join operation may contain too much data with the same key.

ODPS-0123055:Script exception

Module: PROCESSOR.
Severity level: 5.
Trigger condition: A script exception occurred.
Resolution: If a User-Defined Function (UDF) error occurs, see Class or dependency issues in the UDF FAQ.

ODPS-0123065:Join exception

Module: PROCESSOR.
Severity: 5.
Trigger: An exception occurred during a JOIN operation.
Resolution: Modify the JOIN operation.

ODPS-0123081:Invalid datetime string

Module: PROCESSOR.
Severity level: 1.
Trigger condition: The DATETIME string is invalid.
Resolution: Correct the DATETIME string.

ODPS-0123091:Illegal type cast

Module: PROCESSOR.
Severity level: 1.
Trigger condition: This error is triggered by an invalid type conversion, which is usually an invalid explicit type conversion.
Resolution: Modify the type conversion mechanism. For more information about data type conversion, see Data type conversion.

ODPS-0123105:Job got killed

Module: PROCESSOR.
Severity level: 5.
Trigger condition: The job was aborted.
Resolution: You can run the status <instance_id>; command in the MaxCompute client to confirm the instance status.

ODPS-0123111:Format string does not match datetime string

Module: PROCESSOR.
Severity level: 1.
Trigger condition: The date format specified in the SQL statement does not meet the format requirements of MaxCompute, or a DATETIME-related built-in function is used incorrectly.
Resolution: Correct the date format in the SQL statement or the usage of the built-in function.

ODPS-0123121:Mapjoin exception

Module: PROCESSOR.
Severity level: 1.
Trigger condition: An exception occurs during a MAPJOIN operation. This is usually because the small table in the operation exceeds the system limit of 512 MB.
Resolution: Modify the MAPJOIN operation.

ODPS-0123131:User defined function exception

Module: PROCESSOR.
Severity level: 1.
Trigger condition: An exception occurred in the user-defined function.
Resolution: Modify the user-defined function.

ODPS-0130013:Authorization exception

Module: PARSER.
Severity: 3.
Cause: The security check failed because you do not have the required permissions.
Resolution: Contact the project owner to request the required permissions. For more information about permissions, see MaxCompute permissions.

ODPS-0130031:Failed to drop table

Module: PARSER.
Severity: 1.
Cause: This error occurs when you try to drop a source table that does not exist.
Resolution: You can run the show tables; command in the MaxCompute client to confirm that the source table name is correct and that the table exists.

ODPS-0130071:Semantic analysis exception - Invalid table alias or column reference

Module: PARSER.
Severity level: 1.
Trigger condition: A syntax parsing error occurs because an invalid column name is specified, and the column cannot be found.
Resolution: You can run the desc <table_name>; command in the MaxCompute client to retrieve the correct column name.

ODPS-0130071:Semantic analysis exception - Invalid column reference

Module: PARSER.
Severity level: 1.
Trigger condition: A syntax parsing exception occurs because the statement references a column that does not exist.
Resolution: You can run the desc <table_name>; command in the MaxCompute client to retrieve the correct column name.

ODPS-0130071:Semantic analysis exception - Expression not in GROUP BY key

Module: PARSER.
Severity level: 1.
Trigger condition: A non-aggregated column that is read in the SELECT clause is not included in the GROUP BY clause.
Resolution: Modify the SELECT statement to ensure that it is compliant with the GROUP BY clause. For more information, see GROUP BY clause (col_list).

ODPS-0130071:Semantic analysis exception - Partition not found

Module: PARSER.
Severity: 1.
Trigger: This error occurs during semantic analysis when the specified partition value cannot be found.
Resolution: You can run the show partitions <table_name>; command in the MaxCompute client to query the existing partition values. Then, modify the statement to use an existing partition.

ODPS-0130071:Semantic analysis exception - SELECT DISTINCT and GROUP BY can not be in the same query

Module: PARSER
Severity: 1
Cause: The DISTINCT keyword and a GROUP BY clause are used in the same SELECT statement.
Resolution: Modify the statement to remove either the DISTINCT keyword or the GROUP BY clause.

ODPS-0130071:Semantic analysis exception - Cannot insert into target table because column number/types are different

Module: PARSER.
Severity: 1.
Cause: This error is reported when an `insert` statement is run, and the number or types of columns in the source table do not match those in the target table.
Resolution: Modify the `insert` statement to ensure that the number and types of columns in the source table match those in the target table.

ODPS-0130071:Semantic analysis exception - physical plan generation failed: java.lang.RuntimeException: Table(xxxx) is full scan with all partitions, please specify partition predicates

Module: PARSER.
Severity level: 1.
Trigger condition: Full table scans on partitioned tables are disabled for the project that contains the table. You must specify partition predicates.
Resolution: If you must perform a full table scan, add set odps.sql.allow.fullscan=true; before your SQL statement and submit them together. Be aware that a full table scan increases the amount of input data and leads to higher costs.

ODPS-0130071:Semantic analysis exception - physical plan generation failed: com.aliyun.odps.lot.cbo.FailFastException: instance count exceeds limit 99999

Module: PARSER.
Severity level: 1.
Trigger condition: The number of instances in a single job exceeds the limit of 99,999.
Resolution: Adjust the split size to reduce concurrency. You can add the set odps.sql.mapper.split.size=4096; statement before the SQL statement and submit them together. This setting adjusts the amount of table data each Mapper reads. The default unit is MB. You can use this variable to manage the input for the Map phase.

ODPS-0130071:Semantic analysis exception - X type is not enabled in current mode

Symptom: When you call a built-in function, an error message similar to the following is returned.

FAILED: ODPS-0130071:[1,27] Semantic analysis exception - TIMESTAMP type is not enabled in current mode. Please set odps.sql.type.system.odps2=true to use it.

Cause: The built-in function used in the SQL statement uses a Data Type 2.0 data type (such as TINYINT, SMALLINT, INT, FLOAT, VARCHAR, TIMESTAMP, or BINARY), but Data Type 2.0 is not enabled for the project. This prevents MaxCompute from processing the statement.
Resolution: In the MaxCompute client, you can enable Data Type 2.0 in one of the following ways:
- Session level: Add the set odps.sql.type.system.odps2=true; statement before your SQL statement and submit them together.
- Project level: The project owner can run the following command. The configuration takes effect in 10 to 15 minutes.
```
setproject odps.sql.type.system.odps2=true;
```
  After the configuration takes effect, run the SQL statement again.
  For more information about setproject, see Project operations. For more information about enabling Data Type 2.0 at the project level, see Data type editions.

ODPS-0130071:Semantic analysis exception - wrong columns count X in data source, requires Y columns (includes dynamic partitions if any)

Module: PARSER.
Severity: 1.
Trigger: The number of columns in the foreign table does not match the number of columns in the mapped source table.
Resolution: Check the statement for creating the foreign table. Ensure that the number of columns in the foreign table is the same as the number of columns in the mapped source table. For more information about the syntax for creating foreign tables, see Foreign tables.

ODPS-0130071:Semantic analysis exception - column X in source has incompatible type A with destination column Y, which has type B

Module: PARSER.
Severity level: 1.
Trigger condition: The creation of the foreign table fails because the data type of a column in the foreign table is inconsistent with the data type of the corresponding column in the mapped source table.
Resolution: Check the statement that you use to create the foreign table. Ensure that the data type of each column in the foreign table is consistent with the data type of the corresponding column in the mapped source table. For more information about the syntax for creating foreign tables, see Foreign tables.

ODPS-0130071:Semantic analysis exception - max depth of expression is xxxx, which exceeds limit of 5000

Module: PARSER.
Severity: 1.
Trigger condition: This error occurs because the expression is too complex. The number of nodes in the tree constructed from the expression exceeds the 5,000-node limit.
Resolution: Optimize the expression.

ODPS-0130071:Semantic analysis exception - function or view Y cannot be resolved

Symptom: When you call a built-in function, an error message similar to the following is returned.

FAILED: ODPS-0130071:[1,8] Semantic analysis exception - function or view 'row_number' cannot be resolved

Cause: The name of the built-in function in the SQL statement is incorrect, or the function is missing parameters. As a result, MaxCompute cannot process the statement.
Resolution: Check the function name and its parameters. Add the required input parameters according to the function syntax. After you verify that the function name and syntax are correct, run the SQL statement again.

ODPS-0130081:Invalid UDF reference

Module: PARSER.
Severity: 1.
Trigger: The method signature of the user-defined function (UDF) is invalid.
Resolution: You can modify the method signature in the UDF code.

ODPS-0130091:Invalid parameters

Module: PARSER.
Severity: 1.
Trigger: Invalid input parameters were provided for a User-Defined Function (UDF).
Resolution: Correct the input parameters to meet the UDF requirements.

ODPS-0130101:Ambiguous data type

Module: PARSER.
Severity: 1.
Cause: The data type is invalid.
Resolution: Correct the data type.

ODPS-0130111: Fuxi job failed - Data Set should contains exactly one row

Module: PARSER.
Severity level: 1.
Trigger condition: The dataset being read does not contain exactly one record.
Resolution: Modify the dataset to ensure it contains only one record.

ODPS-0130111:Subquery partition pruning exception

Module: PARSER.
Severity level: 1.
Trigger condition: An exception occurred during the dynamic partition pruning optimization for a subquery in an IN statement.
Resolution: Modify the IN statement.

ODPS-0130121:Invalid argument type

Module: PARSER
Severity level: 1
Cause: The parameter type is invalid. This error occurs when a built-in function is called with a parameter of an incorrect type.
Solution: Correct the parameter type.

ODPS-0130121:Invalid argument type- invalid type X of argument m for function Y

Symptom: When you call a built-in function, an error message similar to the following is returned.

FAILED: ODPS-0130121:[1,18] Invalid argument type - invalid type STRING of argument 1 for function all_match, expect ARRAY<T>

Cause: The data type of an input parameter for the built-in function in the SQL statement does not meet the syntax requirements. As a result, MaxCompute fails to process the statement.
Resolution: Modify the input parameters to comply with the function's syntax requirements. After you ensure that the data types are correct, run the SQL statement again.

ODPS-0130131:Table not found

Module: PARSER.
Severity: 1.
Trigger: This error is reported when a DDL or DML statement references a table that does not exist.
Resolution: You can run the show tables; command in the MaxCompute client to confirm the table name.

ODPS-0130141:Illegal implicit type cast

Module: PARSER.
Severity: 1.
Cause: An illegal implicit type conversion was attempted.
Resolution: For more information about implicit type conversion, see Implicit type conversion and its scope.

ODPS-0130151:Illegal data type

Module: PARSER
Severity: 1
Trigger: An invalid data type is specified.
Resolution: Correct the data type.

ODPS-0130161

Module: PARSER.
Severity level: 1.
Trigger condition: SQL syntax parsing error.
Resolution: Ensure that the SQL syntax is correct and uses only supported features. For more information about specific scenarios, see Handle errors for the compact command, Handle circular reference errors for the WITH clause, Handle errors for INTERVAL input parameters, and Handle bad.escape errors for incompatible SQL rewrites.

ODPS-0130171:Creating view exception

Module: PARSER.
Severity level: 1.
Trigger condition: An exception occurred during view creation.
Resolution: Check and modify the view creation statement. For more information about the view creation syntax, see Create or update a view.

ODPS-0130181:Window function exception

Module: PARSER.
Severity: 1.
Trigger: An error occurred in a window function.
Resolution: Check that the syntax of the window function is correct.

ODPS-0130191:Invalid column or partition key

Module: PARSER.
Severity: 1.
Trigger: This error occurs if an invalid column or partition key is specified.
Resolution: You can run the desc <table_name>; or show partitions <table_name>; command in the MaxCompute client to confirm the column or partition key.

ODPS-0130201:View not found

Module: PARSER.
Severity level: 1.
Cause: The specified view does not exist.
Resolution: Run the show tables; command in the MaxCompute client to verify that the view name is correct.

ODPS-0130211:Table or view already exists

Module: PARSER
Severity level: 1
Trigger condition: You tried to create a table or view using a name that already exists.
Resolution: Change the name of the new table or view.

ODPS-0130221:Invalid number of arguments

Module: PARSER.
Severity level: 1.
Description: The number of arguments is invalid.
Resolution: Correct the number of arguments.

ODPS-0130221:Invalid number of arguments - function Y needs m parameters, actually have n

Symptom: When you call a built-in function, an error message similar to the following is returned.

FAILED: ODPS-0130221:[1,8] Invalid number of arguments - function from_utc_timestamp needs 2 parameters, actually have 1

Cause: The number of input parameters provided for the built-in function in the SQL statement does not meet the function's syntax requirements. As a result, MaxCompute cannot process the statement.
Resolution: Check the number of input parameters for the built-in function. Adjust the parameters to match the function's syntax, and then rerun the SQL statement.

ODPS-0130231:Invalid view

Module: PARSER.
Severity: 1.
Cause: The specified view is invalid.
Resolution: You can run the show tables; command in the MaxCompute client to verify that the view name is correct.

ODPS-0130241:Illegal union operation

Module: PARSER.
Severity: 1.
Description: This error indicates an invalid UNION operation. It is usually caused by an inconsistent number or type of columns on both sides of the UNION operator.
Resolution: Modify the UNION statement to comply with the syntax requirements. For more information, see Union.

ODPS-0130252:Cartesian product is not allowed

Module: PARSER.
Severity: 2.
Description: Cartesian product operations are not supported.
Resolution: MaxCompute does not support non-equi join expressions in the conditions of a JOIN operation.

ODPS-0130261:Invalid schema

Module: PARSER
Severity level: 1
Trigger condition: Invalid schema
Resolution: Modify the schema

ODPS-0130271:Partition does not exist

Module: PARSER.
Severity level: 1.
Trigger condition: The specified partition does not exist.
Resolution: You can run the show partitions <table_name>; command in the MaxCompute client to query the existing partitions. Then, modify the statement to specify an existing partition.

ODPS-0140011:Illegal type cast

Module: PLANNER.
Severity level: 1.
Trigger: An explicit type conversion is not allowed.
Resolution: Modify the type conversion logic. For more information, see Explicit type conversion.

ODPS-0140021:Illegal implicit type cast

Module: PLANNER.
Severity level: 1.
Trigger condition: An unsupported implicit type conversion was attempted.
Resolution: Correct the type conversion in your statement. For more information about implicit type conversion, see Implicit type conversion and its scope.

ODPS-0140031:Invalid column reference

Module: PLANNER
Severity: 1
Cause: An invalid column name is specified.
Resolution: Run the desc <table_name>; command in the MaxCompute client to obtain the correct column name.

ODPS-0140041:Invalid UDF reference

Module: PLANNER.
Severity level: 1.
Trigger condition: The specified UDF does not exist.
Resolution: You can run the list functions; command in the MaxCompute client to view the correct UDF name.

ODPS-0140051:Invalid function

Module: PLANNER
Severity: 1
Cause: An invalid function is specified.
Resolution: You can run the show functions; or list functions; command in the MaxCompute client to view a list of valid functions.

ODPS-0140061:Invalid parameters

Module: PLANNER.
Severity level: 1.
Cause: An invalid input parameter was provided.
Resolution: Correct the input parameters.

ODPS-0140071:Unsupported operator

Module: PLANNER
Severity: 1
Cause: The operator is not supported.
Resolution: Use a supported operator. For more information about operators, see Operators.

ODPS-0140081:Unsupported join type

Module: PLANNER.
Severity: 1.
Trigger condition: This error occurs when you perform a LEFT OUTER JOIN from a small table to a large table, or a RIGHT OUTER JOIN from a large table to a small table.
Resolution: Modify the join order.

ODPS-0140105:Invalid multiple I/O

Module: PLANNER.
Severity: 5.
Cause: A conflict occurred among multiple outputs.
Resolution: Adjust the job to resolve the conflict.

ODPS-0140111:Unsupported col type in EXTRACT now

Module: PLANNER.
Severity level: 1.
Trigger: The specified column type is not supported by the EXTRACT function.
Resolution: Change the column to a supported type.

ODPS-0140133:Invalid structure

Module: PLANNER
Severity: 3
Cause: The specified data structure is not recognized.
Solution: Ensure that the specified data structure is valid.

ODPS-0140151:Can not do topologic sort, the stages is not a DAG

Module: PLANNER.
Severity level: 1.
Trigger condition: An error occurred in the sorting algorithm.
Resolution: Verify the correctness of the sorting algorithm.

ODPS-0140178: Internal system failure

Module: PLANNER.
Severity: 8.
Cause: This error is triggered by a system exception.
Resolution: Retry the operation.

ODPS-1800001: Session exception - Failed to submit sub-query in session because:Prepaid project run out of free query quota

Module: Not applicable.
Severity level: Not applicable.
Trigger condition: This error occurs if you use Java Database Connectivity (JDBC) to connect to MaxCompute to run tasks on subscription resources using the MCQA feature, and the number of jobs exceeds 500.
Resolution: Modify the JDBC configuration for the MCQA feature. Set the alwaysFallback parameter to true. For more information, see FAQ.