MaxCompute:SQL error codes (ODPS-01CCCCX)

ODPS-0110011: Authorization exception

Module: META | Severity: 1

Cause: Insufficient permissions.

Fix: Contact the project owner to grant the required permission. See MaxCompute permissions.

ODPS-0110021: Invalid parameters

Module: META | Severity: 1

Cause: The input parameters are invalid.

Fix: Review the input parameters and correct any values that do not meet requirements.

ODPS-0110031: Invalid object type

Module: META | Severity: 1

Cause: The object type is invalid.

Fix: Review the input object and correct it to match the required object type.

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

Module: META | Severity: 1

Cause: MaxCompute has no locking mechanism. Concurrent read and write operations on the same partition cause metadata contention.

Fix: Avoid running multiple operations on the same table simultaneously.

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

Module: META | Severity: 1

Cause: MaxCompute has no locking mechanism. Concurrent read and write operations on the same partition cause metadata contention.

Fix: Avoid running multiple operations on the same table simultaneously.

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

Module: META | Severity: 1

Cause: The same partition is being added in batches simultaneously. MaxCompute executes only the first ADD PARTITION command and ignores subsequent requests.

Fix: Avoid adding the same partition concurrently.

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

Module: META | Severity: 1

Cause: When using dynamic data masking, running install package aegis.aegis_package; fails if the MaxCompute project requiring data masking has not been added to the masking project.

Fix: Add the MaxCompute project to the masking project before running install package aegis.aegis_package;. 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

Cause: MaxCompute has no concurrency control. When multiple tasks modify the same table simultaneously, a concurrency conflict during the final META operation can cause an execution failure. This applies to both ALTER and INSERT operations.

Fix: Convert the table to a partitioned table and write each SQL statement's output to a separate partition. This allows concurrent operations without conflict.

ODPS-0120011: Authorization exception

Module: PROCESSOR | Severity: 1

Cause: Insufficient permissions.

Fix: Contact the project owner to grant the required permission. See MaxCompute permissions.

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

Module: PROCESSOR | Severity: 1

Cause: All separators within the same group must be identical.

Fix: Use a consistent separator across the entire group.

ODPS-0120031: Instance has been cancelled

Module: PROCESSOR | Severity: 1

Cause: The instance was canceled.

Fix: Run status <instance_id>; in the MaxCompute client to check the instance status.

ODPS-0121011: Invalid regular expression pattern

Module: PROCESSOR | Severity: 1

Cause: A built-in function received a regular expression pattern it does not support.

Fix: Replace the pattern with one that the function recognizes. See RLIKE character matching.

ODPS-0121021: Regexec call failed

Module: PROCESSOR | Severity: 1

Cause: An error occurred during regular expression matching.

Fix: Verify that the regular expression is valid. See RLIKE character matching.

ODPS-0121035: Illegal implicit type cast

Module: PROCESSOR | Severity: 5

Cause: An unsupported implicit type conversion violated the conversion rules.

Fix: See Implicit type conversion and its scope.

ODPS-0121045: Unsupported return type

Module: PROCESSOR | Severity: 5

Cause: The return value type is not supported.

Fix: Change to a supported return type.

ODPS-0121055: Empty argument value

Module: PROCESSOR | Severity: 5

Cause: The parameter is empty or NULL.

Fix: Provide a valid non-null value for the parameter.

ODPS-0121065: Argument value out of range

Module: PROCESSOR | Severity: 5

Cause: The parameter value falls outside the allowed range.

Fix: Correct the parameter value to fall within the allowed range.

ODPS-0121075: Invalid number of arguments

Module: PROCESSOR | Severity: 5

Cause: The number of arguments is invalid.

Fix: Correct the number of arguments.

ODPS-0121081: Illegal argument type

Module: PROCESSOR | Severity: 1

Cause: The primitive data type of the argument is incorrect.

Fix: Correct the argument type.

ODPS-0121095: Invalid arguments

Module: PROCESSOR | Severity: 5

Cause: The input arguments are incorrect.

Fix: Correct the input arguments.

ODPS-0121105: Constant argument value expected

Module: PROCESSOR | Severity: 5

Cause: A constant is expected, but a column name was provided.

Fix: Replace the column name with a constant.

ODPS-0121115: Column reference expected

Module: PROCESSOR | Severity: 5

Cause: A column name is expected, but a constant was provided.

Fix: Replace the constant with a column name.

ODPS-0121125: Unsupported function or operation

Module: PROCESSOR | Severity: 5

Cause: The user-defined function (UDF) or operation is not supported.

Fix: Update the UDF or change to a supported operation.

ODPS-0121145: Data overflow

Module: PROCESSOR | Severity: 5

Cause: The data exceeds the value range of its data type. Common causes include aggregate functions that overflow (such as a SUM producing an out-of-range value) and division where the DECIMAL divisor is 0 (for example, SELECT 1BD / 0BD;).

Fix: Update the operation that causes the overflow to handle the boundary condition.

ODPS-0123049: buffer overflow

Module: PROCESSOR | Severity: 9

Cause: Memory overflow. A common cause is a JOIN operation where too many rows share the same key.

Fix: Check the data for issues. For example, there might be too much data that has the same key in a JOIN operation.

ODPS-0123055: Script exception

Module: PROCESSOR | Severity: 5

Cause: A script exception occurred.

Fix: If the error originates from a UDF, see Class or dependency issues in the UDF FAQ to troubleshoot.

ODPS-0123065: Join exception

Module: PROCESSOR | Severity: 5

Cause: An exception occurred during the JOIN operation.

Fix: Review and correct the JOIN operation.

ODPS-0123081: Invalid datetime string

Module: PROCESSOR | Severity: 1

Cause: The DATETIME string is invalid.

Fix: Correct the DATETIME string format.

ODPS-0123091: Illegal type cast

Module: PROCESSOR | Severity: 1

Cause: An invalid explicit type conversion was attempted.

Fix: Correct the type conversion. See Data type conversions.

ODPS-0123105: Job got killed

Module: PROCESSOR | Severity: 5

Cause: The job was aborted.

Fix: Run status <instance_id>; in the MaxCompute client to check the instance status.

ODPS-0123111: Format string does not match datetime string

Module: PROCESSOR | Severity: 1

Cause: The date format in the SQL statement does not meet MaxCompute's requirements, or a DATETIME-related built-in function was used incorrectly.

Fix: Correct the date format to match MaxCompute's expected format.

ODPS-0123121: Mapjoin exception

Module: PROCESSOR | Severity: 1

Cause: A MAPJOIN exception occurred. The most common cause is that the small table in the MAPJOIN exceeds the 512 MB system limit.

Fix: Review the MAPJOIN operation and make sure the small table is within the 512 MB limit.

ODPS-0123131: User defined function exception

Module: PROCESSOR | Severity: 1

Cause: An exception occurred in a user-defined function (UDF).

Fix: Review and correct the UDF.

ODPS-0130013: Authorization exception

Module: PARSER | Severity: 3

Cause: Insufficient permissions. The security check failed.

Fix: Contact the project owner to grant the required permission. See MaxCompute permissions.

ODPS-0130031: Failed to drop table

Module: PARSER | Severity: 1

Cause: The source table was not found when dropping it.

Fix: Run show tables; in the MaxCompute client to confirm that the table exists and that the name is correct.

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

Module: PARSER | Severity: 1

Cause: The column name is incorrect or the referenced column does not exist.

Fix: Run desc <table_name>; in the MaxCompute client to get the correct column name.

ODPS-0130071: Semantic analysis exception - Invalid column reference

Module: PARSER | Severity: 1

Cause: A column reference error occurred. The referenced column does not exist.

Fix: Run desc <table_name>; in the MaxCompute client to get the correct column name.

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

Module: PARSER | Severity: 1

Cause: The columns in the SELECT clause do not exactly match the columns in the GROUP BY clause.

Fix: Update the SELECT statement so its column list matches the GROUP BY clause. See GROUP BY query (col_list).

ODPS-0130071: Semantic analysis exception - Partition not found

Module: PARSER | Severity: 1

Cause: No partition with the specified partition value was found.

Fix: Run show partitions <table_name>; in the MaxCompute client to list existing partitions, then update the statement to reference 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: DISTINCT and GROUP BY cannot appear in the same SELECT clause.

Fix: Remove either DISTINCT or GROUP BY from the statement.

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

Module: PARSER | Severity: 1

Cause: The number or types of columns in the source table do not match those in the destination table.

Fix: Update the statement so the source and destination tables have matching column counts and types.

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: 1

Cause: Full table scans on partitioned tables are disabled for the project. A partition predicate is required.

Fix: Add a partition predicate to the query. If a full table scan is required, prepend set odps.sql.allow.fullscan=true; to the SQL statement and submit them together.

A full table scan increases input data volume and therefore increases costs.

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

Module: PARSER | Severity: 1

Cause: The number of instances in a single job exceeds the limit of 100,000.

Fix: Adjust the split size to reduce concurrency. Prepend set odps.sql.mapper.split.size=4096; to the SQL statement and submit them together. This setting controls how much data (in MB) each Mapper reads, which reduces the total number of Map tasks.

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

Symptom:

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 SQL statement uses a MaxCompute 2.0 data type (such as TINYINT, SMALLINT, INT, FLOAT, VARCHAR, TIMESTAMP, or BINARY), but the 2.0 data type feature is not enabled for the project.

Fix: Enable the MaxCompute 2.0 data type feature in the MaxCompute client using one of the following methods:

• Session level: Prepend set odps.sql.type.system.odps2=true; to the SQL statement and submit them together.

• Project level: The project owner can run the following command. The change takes effect within 10 to 15 minutes.

  setproject odps.sql.type.system.odps2=true;

  For more information about setproject, see Project operations. For considerations when enabling the project-level 2.0 data type switch, see Data type version guide.

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

Module: PARSER | Severity: 1

Cause: The number of columns in the external table does not match the number of columns in the mapped source table.

Fix: Review the external table creation statement and make sure the column count matches the source table. 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: 1

Cause: A column's data type in the external table does not match the type of the mapped column in the source table.

Fix: Review the external table creation statement and make sure each column's data type matches the corresponding column in the source table. See Foreign tables.

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

Module: PARSER | Severity: 1

Cause: The arithmetic expression is too deeply nested. The number of nodes in the expression tree exceeds the limit of 5,000.

Fix: Simplify the arithmetic expression by breaking it into smaller sub-expressions.

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

Symptom:

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

Cause: The function name is incorrect or the function is missing required parameters.

Fix: Check the function name and its required parameters. Correct the name or add missing parameters, then run the SQL statement again.

ODPS-0130081: Invalid UDF reference

Module: PARSER | Severity: 1

Cause: The UDF method signature is invalid.

Fix: Correct the signature in the UDF code.

ODPS-0130091: Invalid parameters

Module: PARSER | Severity: 1

Cause: The UDF input parameters are invalid.

Fix: Correct the UDF input parameters to meet requirements.

ODPS-0130101: Ambiguous data type

Module: PARSER | Severity: 1

Cause: The data type is ambiguous or invalid.

Fix: Correct the data type.

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

Module: PARSER | Severity: 1

Cause: The dataset contains more than one row, but exactly one row is required.

Fix: Update the dataset or query so it returns exactly one row.

ODPS-0130111: Subquery partition pruning exception

Module: PARSER | Severity: 1

Cause: An exception occurred during dynamic partition pruning for a subquery in an IN conditional statement.

Fix: Review and correct the IN conditional statement.

ODPS-0130121: Invalid argument type

Module: PARSER | Severity: 1

Cause: The argument type is incorrect. The built-in function received a type it does not support.

Fix: Correct the argument type.

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

Symptom:

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

Cause: The input argument type does not meet the function's syntax requirements.

Fix: Update the input arguments to match the function's expected types, then run the SQL statement again.

ODPS-0130131: Table not found

Module: PARSER | Severity: 1

Cause: The table does not exist. The DDL or DML statement references a table that cannot be found.

Fix: Run show tables; in the MaxCompute client to confirm the table name.

ODPS-0130141: Illegal implicit type cast

Module: PARSER | Severity: 1

Cause: An implicit type conversion that is not allowed was attempted.

Fix: See Implicit type conversion and its scope.

ODPS-0130151: Illegal data type

Module: PARSER | Severity: 1

Cause: The data type is invalid.

Fix: Correct the data type.

ODPS-0130161

Module: PARSER | Severity: 1

Cause: SQL syntax parsing error.

Fix: Verify that the SQL syntax is correct and that only supported features are used. For specific scenarios, see:

• Handle errors for the compact command

• Handle circular reference errors in WITH clauses

• Handle errors with INTERVAL input parameters

• Handle bad.escape errors from incompatible SQL rewrites

ODPS-0130171: Creating view exception

Module: PARSER | Severity: 1

Cause: An exception occurred when creating the view.

Fix: Review and correct the view creation statement. See Create or update a view.

ODPS-0130181: Window function exception

Module: PARSER | Severity: 1

Cause: A window function exception occurred.

Fix: Verify that the window function syntax is correct.

ODPS-0130191: Invalid column or partition key

Module: PARSER | Severity: 1

Cause: The column or partition key is invalid.

Fix: Run desc <table_name>; or show partitions <table_name>; in the MaxCompute client to verify the column or partition key.

ODPS-0130201: View not found

Module: PARSER | Severity: 1

Cause: The view does not exist.

Fix: Run show tables; in the MaxCompute client to confirm the view name.

ODPS-0130211: Table or view already exists

Module: PARSER | Severity: 1

Cause: A table or view with the same name already exists.

Fix: Change the name of the table or view to be created.

ODPS-0130221: Invalid number of arguments

Module: PARSER | Severity: 1

Cause: The number of arguments is invalid.

Fix: Correct the number of input arguments.

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

Symptom:

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

Cause: The number of input arguments does not match what the function requires.

Fix: Add or remove arguments to match the function's expected count, then run the SQL statement again.

ODPS-0130231: Invalid view

Module: PARSER | Severity: 1

Cause: The view is invalid.

Fix: Run show tables; in the MaxCompute client to confirm the view name is correct.

ODPS-0130241: Illegal union operation

Module: PARSER | Severity: 1

Cause: The UNION operation is invalid. The most common cause is a mismatch in column count or types on either side of the UNION.

Fix: Update the UNION statement so both sides have matching column counts and types. See UNION.

ODPS-0130252: Cartesian product is not allowed

Module: PARSER | Severity: 2

Cause: A Cartesian product was produced. MaxCompute does not support non-equi expressions in JOIN conditions.

Fix: Rewrite the JOIN to use an equi-join condition.

ODPS-0130261: Invalid schema

Module: PARSER | Severity: 1

Cause: The schema is invalid.

Fix: Correct the schema.

ODPS-0130271: Partition does not exist

Module: PARSER | Severity: 1

Cause: The specified partition does not exist.

Fix: Run show partitions <table_name>; in the MaxCompute client to list existing partitions, then update the statement to reference an existing partition.

ODPS-0140011: Illegal type cast

Module: PLANNER | Severity: 1

Cause: An explicit type conversion that is not allowed was attempted.

Fix: Correct the type conversion. See Explicit type conversion.

ODPS-0140021: Illegal implicit type cast

Module: PLANNER | Severity: 1

Cause: An implicit type conversion that is not allowed was attempted.

Fix: Correct the type conversion. See Implicit type conversion and its scope.

ODPS-0140031: Invalid column reference

Module: PLANNER | Severity: 1

Cause: The column name is invalid.

Fix: Run desc <table_name>; in the MaxCompute client to get the correct column name.

ODPS-0140041: Invalid UDF reference

Module: PLANNER | Severity: 1

Cause: The referenced UDF does not exist.

Fix: Run list functions; in the MaxCompute client to verify the UDF name.

ODPS-0140051: Invalid function

Module: PLANNER | Severity: 1

Cause: The function is invalid.

Fix: Run show functions; or list functions; in the MaxCompute client to verify the function name.

ODPS-0140061: Invalid parameters

Module: PLANNER | Severity: 1

Cause: The input parameters are invalid.

Fix: Correct the input parameters.

ODPS-0140071: Unsupported operator

Module: PLANNER | Severity: 1

Cause: The operator is not supported.

Fix: Replace it with a supported operator. See Operators.

ODPS-0140081: Unsupported join type

Module: PLANNER | Severity: 1

Cause: A small table (left) is outer-joining a large table, or a large table (right) is outer-joining a small table. This join order is not supported.

Fix: Change the join order.

ODPS-0140105: Invalid multiple I/O

Module: PLANNER | Severity: 5

Cause: Multi-path output conflict.

Fix: Restructure the job to avoid multi-path output conflicts.

ODPS-0140111: Unsupported col type in EXTRACT now

Module: PLANNER | Severity: 1

Cause: The column type is not supported by the EXTRACT function.

Fix: Change the column to a supported type.

ODPS-0140133: Invalid structure

Module: PLANNER | Severity: 3

Cause: The data structure cannot be recognized.

Fix: Verify that the data structure is valid.

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

Module: PLANNER | Severity: 1

Cause: The execution stages do not form a directed acyclic graph (DAG), causing the topological sort to fail.

Fix: Check that the sorting algorithm is correct.

ODPS-0140178: Internal system failure

Module: PLANNER | Severity: 8

Cause: A system exception occurred.

Fix: Retry the operation.

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

Cause: This error occurs when all of the following conditions are met: Java Database Connectivity (JDBC) is used to connect to MaxCompute, tasks run on subscription resources with the MaxCompute Query Acceleration (MCQA) feature enabled, and the number of concurrent jobs exceeds 500.

Fix: In the JDBC configuration for MCQA, set the alwaysFallback parameter to true. See FAQ.