SQL error codes (ODPS-01CCCCX)-MaxCompute(MaxCompute)-阿里云帮助中心

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

This type of error code uses the following format:

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

The following sections detail each error code.

ODPS-0110011: Authorization exception

Module: META
Severity: 1
Cause: You do not have the required permissions.
Solution: Contact the project owner to grant the permission specified in the error message. For more information about permissions, see MaxCompute permissions.

ODPS-0110021: Invalid parameters

Module: META
Severity: 1
Cause: An invalid parameter was provided.
Solution: Check and modify the input parameters to ensure they meet the requirements.

ODPS-0110031: Invalid object type

Module: META
Severity: 1
Cause: An invalid object type was provided.
Solution: Check and modify the input object to ensure it meets the object type requirements.

ODPS-0110041: Invalid meta operation - partition already exists

Module: META
Severity: 1
Cause: MaxCompute lacks a lock mechanism for the target table. This error is caused by a metadata race condition, which can occur when you perform multiple read and write operations on the same partition concurrently.
Solution: Because MaxCompute lacks a lock mechanism, avoid concurrent operations on the same table.

ODPS-0110061: DDL task failed - partition already exists

Module: META
Severity: 1
Cause: MaxCompute lacks a lock mechanism for the target table. This error is caused by a metadata race condition, which can occur when you perform multiple read and write operations on the same partition concurrently.
Solution: Because MaxCompute lacks a lock mechanism, avoid concurrent operations on the same table.

ODPS-0110061: DDL task failed - lock conflict on partition add

Module: META
Severity: 1
Cause: This error occurs if you attempt to add the same partition multiple times at once. MaxCompute executes only the first add partition command it receives and ignores subsequent requests.
Solution: Avoid performing concurrent operations on the same partition.

ODPS-0110061: DDL task failed - project not allowed to install package

Module: META
Severity: 1
Cause: This error occurs if you run the install package aegis.aegis_package; command for dynamic data masking without first adding the target MaxCompute project to the masking project.
Solution: Before you run the install package aegis.aegis_package; command, add the MaxCompute project that contains the data to be masked to the masking project. For more information, see Dynamic data masking.

ODPS-0110999: Critical internal error - DDL task rename failed

Module: META
Severity: 1
Cause: MaxCompute lacks concurrency control. This error can occur if multiple jobs attempt to modify the same table simultaneously. In rare cases, this can lead to a concurrency conflict during the final metadata operation, causing the job to fail. This issue can happen with both ALTER and INSERT operations.
Solution: Convert the table to a partitioned table. This allows you to write data for each SQL statement into a separate partition, which enables concurrent operations.

ODPS-0120011: Authorization exception

Module: PROCESSOR
Severity: 1
Cause: You do not have the required permissions.
Solution: Contact the project owner to grant the permission specified in the error message. For more information about permissions, see MaxCompute permissions.

ODPS-0120021: Inconsistent delimiter in wm_concat

Module: PROCESSOR
Severity: 1
Cause: The delimiters used within the same group are not consistent.
Solution: Use a consistent delimiter format.

ODPS-0120031: Instance has been canceled

Module: PROCESSOR
Severity: 1
Cause: The instance has been canceled.
Solution: You can run the status <instance_id>; command 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 an unrecognized regular expression pattern.
Solution: Modify the regular expression to a recognizable pattern. For more information about regular expressions, see RLIKE character matching.

ODPS-0121021: Regexec call failed

Module: PROCESSOR
Severity: 1
Cause: An error occurred during regular expression matching.
Solution: Verify 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: 5
Cause: An unsupported implicit type cast occurred, violating casting rules.
Solution: For more information about implicit type casts, see Implicit type casts and their scopes.

ODPS-0121045: Unsupported return type

Module: PROCESSOR
Severity: 5
Cause: The return type is not supported.
Solution: Modify the operation to use a supported return type.

ODPS-0121055: Empty argument value

Module: PROCESSOR
Severity: 5
Cause: An argument is empty or NULL.
Solution: Modify the input argument.

ODPS-0121065: Argument value out of range

Module: PROCESSOR
Severity: 5
Cause: The argument value is outside the allowed range.
Solution: Modify the argument value.

ODPS-0121075: Invalid number of arguments

Module: PROCESSOR
Severity: 5
Cause: The number of arguments is invalid.
Solution: Modify the number of arguments.

ODPS-0121081: Illegal argument type

Module: PROCESSOR
Severity: 1
Cause: An argument has an invalid underlying data type.
Solution: Modify the argument type.

ODPS-0121095: Invalid arguments

Module: PROCESSOR
Severity: 5
Cause: An invalid input argument was provided.
Solution: Modify the input argument.

ODPS-0121105: Constant argument value expected

Module: PROCESSOR
Severity: 5
Cause: The operation expected a constant value but received a column name.
Solution: Change the input to a constant.

ODPS-0121115: Column reference expected

Module: PROCESSOR
Severity: 5
Cause: A column name is expected, but a constant value was provided.
Solution: Change the input to a column name.

ODPS-0121125: Unsupported function or operation

Module: PROCESSOR
Severity: 5
Cause: The user-defined function (UDF) or other operation is not supported.
Solution: Modify the UDF or use a different operation.

ODPS-0121145: Data overflow

Module: PROCESSOR
Severity: 5
Cause: A data overflow occurred because the data exceeds the value range of its data type. This can be caused by an aggregate function or a division operation where the divisor is a DECIMAL type with a value of 0. For example, a SUM() function or an expression like SELECT 1BD / 0BD; can cause a data overflow.
Solution: Modify the operation that is causing the data overflow.

ODPS-0123049: Buffer overflow

Module: PROCESSOR
Severity: 9
Cause: A buffer overflow occurred.
Solution: Check for issues with your data. For example, a JOIN operation may have too many records with the same key, which can lead to a buffer overflow.

ODPS-0123055: Script exception

Module: PROCESSOR
Severity: 5
Cause: A script exception occurred.
Solution: If you encounter an error with a user-defined function (UDF), see Class or dependency issues in UDF FAQ to troubleshoot the issue.

ODPS-0123065: Join exception

Module: PROCESSOR
Severity: 5
Cause: A JOIN operation exception occurred.
Solution: Modify the JOIN operation.

ODPS-0123081: Invalid datetime string

Module: PROCESSOR
Severity: 1
Cause: The DATETIME string is invalid.
Solution: Modify the DATETIME string.

ODPS-0123091: Illegal type cast

Module: PROCESSOR
Severity: 1
Cause: An invalid explicit type cast was attempted.
Solution: Modify the type cast logic. For more information about data type casts, see Data type conversions.

ODPS-0123105: Job got killed

Module: PROCESSOR
Severity: 5
Cause: The job was terminated.
Solution: You can run the status <instance_id>; command in the MaxCompute client to check the instance status.

ODPS-0123111: Format string does not match datetime string

Module: PROCESSOR
Severity: 1
Cause: The format string does not match the date string. This can occur if the date format you entered in the SQL statement does not meet MaxCompute requirements, or if a DATETIME-related built-in function is used incorrectly.
Solution: Modify the date format.

ODPS-0123121: Mapjoin exception

Module: PROCESSOR
Severity: 1
Cause: A MAPJOIN exception occurred. This is typically because the small table in the MAPJOIN operation exceeds the system limit of 512 MB.
Solution: Modify the MAPJOIN operation.

ODPS-0123131: User-defined function exception

Module: PROCESSOR
Severity: 1
Cause: A user-defined function exception occurred.
Solution: Modify the user-defined function.

ODPS-0130013: Authorization exception

Module: PARSER
Severity: 3
Cause: You do not have the required permissions. The security check failed.
Solution: Contact the project owner to grant the permission specified in the error message. For more information about permissions, see MaxCompute permissions.

ODPS-0130031: Failed to drop table

Module: PARSER
Severity: 1
Cause: The specified source table does not exist.
Solution: Run the show tables; command in the MaxCompute client to verify that the source table name is correct and that the table exists.

ODPS-0130071: Semantic analysis exception - invalid alias or column

Module: PARSER
Severity: 1
Cause: A syntax parsing exception occurred. The specified column name is invalid or could not be found.
Solution: Run the desc <table_name>; command in the MaxCompute client to retrieve the correct column names.

ODPS-0130071: Semantic analysis exception - invalid column reference

Module: PARSER
Severity: 1
Cause: A syntax parsing exception occurred. The column reference is invalid or the column could not be found.
Solution: Run the desc <table_name>; command in the MaxCompute client to retrieve the correct column names.

ODPS-0130071: Semantic analysis exception - expression not in GROUP BY

Module: PARSER
Severity: 1
Cause: A syntax parsing exception occurred. A column in the SELECT list is not included in the GROUP BY clause.
Solution: Modify the SELECT statement to ensure it meets the syntax requirements. For more information about GROUP BY, see GROUP BY grouping query (col_list).

ODPS-0130071: Semantic analysis exception - partition not found

Module: PARSER
Severity: 1
Cause: A syntax parsing exception occurred. The specified partition was not found.
Solution: Run the show partitions <table_name>; command in the MaxCompute client to view existing partitions. Then, modify the statement to specify an existing partition.

ODPS-0130071: Semantic analysis exception - DISTINCT and GROUP BY conflict

Module: PARSER
Severity: 1
Cause: DISTINCT and GROUP BY were used in the same SELECT clause.
Solution: Modify the statement to use either DISTINCT or GROUP BY, but not both in the same clause.

ODPS-0130071: Semantic analysis exception - column mismatch on insert

Module: PARSER
Severity: 1
Cause: The column count or data types in the source table do not match the target table.
Solution: Modify the statement to ensure the column count and types match between the source table and target table.

ODPS-0130071: Semantic analysis exception - full scan on partitioned table is disallowed

Module: PARSER
Severity: 1
Cause: The project containing the table prohibits full table scans on partitioned tables. You must specify partition predicates in your query.
Solution: If a full table scan is necessary, you can enable it for the current session by adding set odps.sql.allow.fullscan=true; before your SQL statement and submitting them together. Note that performing a full table scan increases the amount of data processed, which can lead to higher costs.

ODPS-0130071: Semantic analysis exception - instance count exceeds limit

Module: PARSER
Severity: 1
Cause: The number of instances in a single job exceeds the limit of 99,999.
Solution: Reduce the concurrency by adjusting the split size. You can add the statement set odps.sql.mapper.split.size=4096; before your SQL query and submit them together. This setting adjusts the amount of data in megabytes (MB) that each mapper reads from the table, allowing you to control the input for the map stage.

ODPS-0130071: Semantic analysis exception - data type not enabled

Symptom: When you call a built-in function, an error message similar to the following one 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 SQL statement uses a built-in function that involves a 2.0 data type, such as TINYINT, SMALLINT, INT, FLOAT, VARCHAR, TIMESTAMP, or BINARY. However, this feature is not enabled for the project.
Solution: Enable the 2.0 data type feature in the MaxCompute client by using one of the following methods:
- Session level: Add the set odps.sql.type.system.odps2=true; statement before your SQL query and submit them together.
- Project level: A project owner can enable this feature for the entire project. The change takes effect in 10 to 15 minutes. Run the following command:
```
setproject odps.sql.type.system.odps2=true;
```
  After the command takes effect, run the SQL statement again.
  For more information about the setproject command, see Project operations. For more information about considerations when you enable the 2.0 data type feature at the project level, see Data type editions.

ODPS-0130071: Semantic analysis exception - incorrect column count in data source

Module: PARSER
Severity: 1
Cause: The external table could not be created because its column count does not match that of the source table.
Solution: Check the CREATE EXTERNAL TABLE statement and ensure that the number of columns in the external table matches the number of columns in the mapped source table. For more information about the syntax for creating an external table, see External tables.

ODPS-0130071: Semantic analysis exception - incompatible column types

Module: PARSER
Severity: 1
Cause: The external table could not be created because the data type of a column in the external table is inconsistent with the data type of the corresponding column in the mapped source table.
Solution: Check the CREATE EXTERNAL TABLE statement and ensure that the data type of each column in the external table matches the data type of the corresponding column in the mapped source table. For more information about the syntax for creating an external table, see External tables.

ODPS-0130071: Semantic analysis exception - expression depth exceeds limit

Module: PARSER
Severity: 1
Cause: The expression is too complex. The number of nodes in the tree constructed from the expression exceeds the limit of 5,000.
Solution: Simplify the expression.

ODPS-0130071: Semantic analysis exception - cannot resolve function or view

Symptom: When you call a built-in function, an error message similar to the following one 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 is incorrect or the function is missing parameters.
Solution: Check the function and parameter names. Add input parameters as required by the function's syntax. Ensure all names and syntax are correct, and then run the SQL statement again.

ODPS-0130081: Invalid UDF reference

Module: PARSER
Severity: 1
Cause: The UDF method signature is invalid.
Solution: Modify the signature information in the UDF code.

ODPS-0130091: Invalid parameters

Module: PARSER
Severity: 1
Cause: A UDF input parameter is invalid.
Solution: Modify the UDF input parameters to ensure they meet the requirements.

ODPS-0130101: Ambiguous data type

Module: PARSER
Severity: 1
Cause: The data type is invalid.
Solution: Modify the data type.

ODPS-0130111: Fuxi job failed - dataset must contain one row

Module: PARSER
Severity: 1
Cause: The dataset being read does not meet the requirement of containing exactly one record.
Solution: Modify the dataset to ensure it contains only one record.

ODPS-0130111: Subquery partition pruning exception

Module: PARSER
Severity: 1
Cause: An exception occurred during the dynamic partition optimization for the subquery in an IN condition.
Solution: Modify the IN condition statement.

ODPS-0130121: Invalid argument type

Module: PARSER
Severity: 1
Cause: An invalid argument type was provided. This is typically because a built-in function received a parameter of the wrong type.
Solution: Modify the argument type.

ODPS-0130121: Invalid argument type

Symptom: When you call a built-in function, an error message similar to the following one 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 actual data type of an input parameter for a built-in function does not meet the function's syntax requirements, which causes MaxCompute to fail.
Solution: Modify the input parameter to match the data type required by the function's syntax, and then run the SQL statement again.

ODPS-0130131: Table not found

Module: PARSER
Severity: 1
Cause: The specified table does not exist.
Solution: Run the show tables; command in the MaxCompute client to verify the table name.

ODPS-0130141: Illegal implicit type cast

Module: PARSER
Severity: 1
Cause: An unsupported implicit type cast was attempted.
Solution: For more information about implicit type casts, see Implicit type casts and their scopes.

ODPS-0130151: Illegal data type

Module: PARSER
Severity: 1
Cause: The data type is invalid.
Solution: Modify the data type.

ODPS-0130161: SQL syntax error

Module: PARSER
Severity: 1
Cause: An SQL syntax parsing error occurred.
Solution: Ensure that the SQL syntax is correct and that you are using supported features. For more information about specific scenarios, see Troubleshoot compact command errors, Troubleshoot WITH clause circular reference errors, Troubleshoot INTERVAL argument errors, and Troubleshoot incompatible SQL rewrite bad.escape errors.

ODPS-0130171: View creation exception

Module: PARSER
Severity: 1
Cause: An exception occurred while creating a view.
Solution: Check and modify the CREATE VIEW statement. For more information about the syntax for creating a view, see Create or update a view.

ODPS-0130181: Window function exception

Module: PARSER
Severity: 1
Cause: A window function exception occurred.
Solution: Check whether the window function meets the syntax requirements.

ODPS-0130191: Invalid column or partition key

Module: PARSER
Severity: 1
Cause: The column or partition key is invalid.
Solution: Run the desc <table_name>; or show partitions <table_name>; command in the MaxCompute client to verify the validity of the column or partition.

ODPS-0130201: View not found

Module: PARSER
Severity: 1
Cause: The view does not exist.
Solution: Run the show tables; command in the MaxCompute client to verify the view name.

ODPS-0130211: Table or view already exists

Module: PARSER
Severity: 1
Cause: The table or view already exists.
Solution: Change the name of the table or view you are trying to create.

ODPS-0130221: Invalid number of arguments

Module: PARSER
Severity: 1
Cause: The number of arguments is invalid.
Solution: Modify the number of input arguments.

ODPS-0130221: Invalid number of arguments

Symptom: When you call a built-in function, an error message similar to the following one 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 for the built-in function is incorrect.
Solution: Correct the number of input parameters to match the function's syntax, and then rerun the SQL statement.

ODPS-0130231: Invalid view

Module: PARSER
Severity: 1
Cause: The view is invalid.
Solution: Run the show tables; command in the MaxCompute client to verify the view name.

ODPS-0130241: Illegal union operation

Module: PARSER
Severity: 1
Cause: The UNION operation is invalid. This is typically because the number and types of columns on both sides of the UNION operator are inconsistent.
Solution: Modify the UNION statement to meet the syntax requirements. For more information about UNION, see Union.

ODPS-0130252: Cartesian product is not allowed

Module: PARSER
Severity: 2
Cause: Cartesian product is not supported.
Solution: MaxCompute does not support non-equality expressions in the join conditions of a JOIN operation.

ODPS-0130261: Invalid schema

Module: PARSER
Severity: 1
Cause: The schema is invalid.
Solution: Modify the schema.

ODPS-0130271: Partition does not exist

Module: PARSER
Severity: 1
Cause: The partition does not exist.
Solution: Run the show partitions <table_name>; command in the MaxCompute client to view existing partitions. Then, modify the statement to specify an existing partition.

ODPS-0140011: Illegal type cast

Module: PLANNER
Severity: 1
Cause: An unsupported explicit type cast was attempted.
Solution: Modify the type cast logic. For more information about explicit type casts, see Explicit type casts.

ODPS-0140021: Illegal implicit type cast

Module: PLANNER
Severity: 1
Cause: An unsupported implicit type cast was attempted.
Solution: Modify the type cast logic. For more information about implicit type casts, see Implicit type casts and their scopes.

ODPS-0140031: Invalid column reference

Module: PLANNER
Severity: 1
Cause: The column name is invalid.
Solution: Run the desc <table_name>; command in the MaxCompute client to retrieve the correct column names.

ODPS-0140041: Invalid UDF reference

Module: PLANNER
Severity: 1
Cause: The specified UDF does not exist.
Solution: Run the list functions; command in the MaxCompute client to view the correct UDF names.

ODPS-0140051: Invalid function

Module: PLANNER
Severity: 1
Cause: The function is invalid.
Solution: Run the show functions; or list functions; command in the MaxCompute client to view the correct function names.

ODPS-0140061: Invalid parameters

Module: PLANNER
Severity: 1
Cause: An input parameter is invalid.
Solution: Modify the input parameter.

ODPS-0140071: Unsupported operator

Module: PLANNER
Severity: 1
Cause: The operator is not supported.
Solution: Replace the operator with a supported one. For more information about operators, see Operators.

ODPS-0140081: Unsupported join type

Module: PLANNER
Severity: 1
Cause: An OUTER JOIN was performed between a small table and a large table in an unsupported order.
Solution: Modify the join order.

ODPS-0140105: Invalid multiple I/O

Module: PLANNER
Severity: 5
Cause: A multi-output conflict occurred.
Solution: Adjust the job to avoid multi-output conflicts.

ODPS-0140111: Unsupported column type in EXTRACT

Module: PLANNER
Severity: 1
Cause: The column type is not supported by EXTRACT.
Solution: Change to a supported column type.

ODPS-0140133: Invalid structure

Module: PLANNER
Severity: 3
Cause: The data structure cannot be recognized.
Solution: Verify that the data structure is valid.

ODPS-0140151: Topological sort failed

Module: PLANNER
Severity: 1
Cause: An error occurred in the sorting algorithm.
Solution: Check that the sorting algorithm is correct.

ODPS-0140178: Internal system failure

Module: PLANNER
Severity: 8
Cause: An internal system error occurred.
Solution: Retry the operation.

ODPS-1800001: Session exception - free query quota exceeded

Module: N/A
Severity: N/A
Cause: This error occurs when you use a JDBC connection to run jobs on subscription resources in MaxCompute with the MCQA feature enabled, and the number of jobs exceeds 500.
Solution: Modify the JDBC configuration for the MCQA feature by setting the alwaysFallback parameter to true. For more information, see FAQ.

ODPS-0130071: Semantic analysis exception - inference quota check failed

Symptom: When you call a public model supported by the model inference service, you see the following error message.

FAILED: ODPS-0130071:[1,8] Semantic analysis exception - inference quota status check failed, error message: region cn-shanghai not found in inference quota

Cause: The model inference service is not activated in your project's region, such as cn-shanghai. As a result, you cannot call AI inference resources.

Solution: Go to the Alibaba Cloud console to activate the model inference service for your project's region. For detailed instructions, see Purchase and use the MaxCompute model inference service.