This topic describes SQL errors, their trigger conditions, and relevant solutions.

Format of SQL error messages:
ODPS-01CCCCX: General description - Context-related description
SQL errors are related to the following modules: META (CCCC ranges from 1000 to 1999), PROCESSOR (CCCC ranges from 2000 to 2999), PARSER (CCCC ranges from 3000 to 3999), and PLANNER (CCCC ranges from 4000 to 4999). The following table describes SQL errors.
Error message Module Severity Trigger condition Solution
ODPS-0110005:Unknown exception from metadata operation META 5 The error message returned because an internal error has occurred. Submit a ticket to contact MaxCompute technical support.
ODPS-0110011:Authorization exception META 1 The error message returned because you are not authorized to perform this operation. Complete authorization.
ODPS-0110021:Invalid parameters META 1 The error message returned because the parameters are invalid. Check and modify the parameters.
ODPS-0110031:Invalid object type META 1 The error message returned because the object type is invalid. Change the object type to a valid type.
ODPS-0110041:Invalid meta operation - AlreadyExistsException(message:Partition already exists, existed values:) META 1 The error message returned because MaxCompute does not have the lock mechanism on the table. This error is caused by competition for metadata. Multiple read/write operations on a partition at the same time are prone to this type of error. If the lock mechanism is unavailable in MaxCompute, we recommend that you do not perform multiple read/write operations on a table at the same time.
ODPS-0110061: Failed to run ddltask - AlreadyExistsException(message:Partition already exists, existed values:) META 1 The error message returned because MaxCompute does not have the lock mechanism on the table. This error is caused by competition for metadata. Multiple read/write operations on a partition at the same time are prone to this type of error. If the lock mechanism is unavailable in MaxCompute, we recommend that you do not perform multiple read/write operations on a table at the same time.
ODPS-0110061:Failed to run ddltask - SimpleLock conflict failure, add partition is already on-going META 1 The error message returned because you run multiple commands to add the same partition at the same time. MaxCompute runs only the first command to add the partition and ignores the subsequent commands. Do not run multiple commands to add the same partition at the same time.
ODPS-0110071:OTS initialization exception META 1 The error message returned because an exception occurs when Tablestore is initialized. Submit a ticket to contact MaxCompute technical support.
ODPS-0110081:OTS transaction exception META 1 The error message returned because the transaction of Tablestore is abnormal.
ODPS-0110091:OTS filtering exception META 1 The error message returned because the conditional filtering of Tablestore is abnormal.
ODPS-01100101:OTS processing exception META 1 The error message returned because the processing of Tablestore is abnormal.
ODPS-01100111:OTS invalid data object META 1 The error message returned because the data of Tablestore is invalid.
ODPS-01100121:Unknown OTS exception META 1 The error message returned because an unknown error of Tablestore has occurred.
ODPS-0110131:StorageDescriptor compression exception META 1 The error message returned because the storage descriptor compression is abnormal. Perform the compression operation again.
ODPS-0110141:Data version exception META 1 The error message returned because the database version is abnormal. Confirm the correct database version.
ODPS-0110999:Critical! Internal error happened in commit operation and rollback failed, possible breach of atomicity META 9 The error message returned because the rollback has failed. Submit a ticket to contact MaxCompute technical support.
ODPS-0120005:Unknown exception from processor PROCESSOR 5 The error message returned because an internal error has occurred.
ODPS-0120011:Authorization exception PROCESSOR 1 The error message returned because you are not authorized to perform this operation. Complete authorization.
ODPS-0120021:the delimitor must be the same in wm_concat PROCESSOR 1 The error message returned because the delimiters in a group are different. Use the same delimiter in a group.
ODPS-0120031:Instance has been cancelled PROCESSOR 1 The error message returned because the instance is canceled. Check the instance status.
ODPS-0121011:Invalid regular expression pattern PROCESSOR 1 The error message returned because the regular expression processing function of built-in functions has received a regular expression that cannot be identified. Modify the regular expression to an identifiable regular expression.
ODPS-0121021:Regexec call failed PROCESSOR 1 The error message returned because the regular expression fails to be matched. Confirm that the regular expression meets the specifications.
ODPS-0121035:Illegal implicit type cast PROCESSOR 5 The error message returned because the data type conversion is invalid. This error is usually caused by a violation of implicit data type conversion rules. Change the data type conversion mechanism.
ODPS-0121045:Unsupported return type PROCESSOR 5 The error message returned because the type of the return value is not supported. Change the type of the return value.
ODPS-0121055:Empty argument value PROCESSOR 5 The error message returned because the input parameter is empty or NULL. Modify the input parameter.
ODPS-0121065:Argument value out of range PROCESSOR 5 The error message returned because the parameter value is invalid. Change the parameter value to a valid value.
ODPS-0121075:Invalid number of arguments PROCESSOR 5 The error message returned because the number of parameters is invalid. Change the number of parameters.
ODPS-0121081:Illegal argument type PROCESSOR 1 The error message returned because the basic type of the parameter is invalid. Change the basic type of the parameter to a valid type.
ODPS-0121095:Invalid arguments PROCESSOR 5 The error message returned because the input parameter is invalid. Change the input parameter to a valid parameter.
ODPS-0121105:Constant argument value expected PROCESSOR 5 The error message returned because you have specified column names instead of the required constants. Change the column names to constants.
ODPS-0121115:Column reference expected PROCESSOR 5 The error message returned because you have specified constants instead of the required column names. Change the constants to column names.
ODPS-0121125:Unsupported function or operation PROCESSOR 5 The error message returned because the user-defined function (UDF) or operation is not supported. Modify the UDF or change the operation.
ODPS-0121135:Malloc memory failed PROCESSOR 5 The error message returned because memory allocation is abnormal. Adjust the memory allocation.
ODPS-0121145:Data overflow PROCESSOR 5 The error message returned because data overflow has occurred. The value is invalid for the current data type. Data overflow is usually caused by an aggregate function, such as SUM. Modify the operation that causes data overflow.
ODPS-0123019:Distributed file operation exception PROCESSOR 9 The error message returned because the read or write operation on the disk is abnormal. Submit a ticket to contact MaxCompute technical support.
ODPS-0123023:Unsupported reduce type PROCESSOR 3 The error message returned because the Reduce type is not supported. Change the Reduce type to the one that is supported.
ODPS-0123031:Partition exception PROCESSOR 1 The error message returned because a partition exception has occurred. Submit a ticket to contact MaxCompute technical support.
ODPS-0123043:buffer overflow PROCESSOR 3 The error message returned because cache overflow has occurred.
ODPS-0123049: buffer overflow PROCESSOR 9 The error message returned because memory overflow has occurred. Check whether a data issue exists. For example, a large amount of data with duplicate keys is used in a JOIN operation.
ODPS-0123055:Script exception PROCESSOR 5 The error message returned because the script is abnormal. Submit a ticket to contact MaxCompute technical support.
ODPS-0123065:Join exception PROCESSOR 5 The error message returned because the JOIN operation is abnormal. Modify the JOIN operation.
ODPS-0123075:Hash exception PROCESSOR 5 The error message returned because a hash exception has occurred. Submit a ticket to contact MaxCompute technical support.
ODPS-0123081:Invalid datetime string PROCESSOR 1 The error message returned because the DATETIME string is abnormal. Modify the DATETIME string.
ODPS-0123091:Illegal type cast PROCESSOR 1 The error message returned because the data type conversion is invalid. In most cases, this error is caused by invalid explicit data type conversions. Change the data type conversion mechanism.
ODPS-0123105:Job got killed PROCESSOR 5 The error message returned because the job has been stopped. Check the job status.
ODPS-0123111:Format string does not match datetime string PROCESSOR 1 The error message returned because the format string does not match the DATETIME string. The format of the date that you entered in the SQL statement does not meet the MaxCompute format requirements, or DATETIME-related built-in functions are improperly used. Modify the date format.
ODPS-0123121:Mapjoin exception PROCESSOR 1 The error message returned because the MAPJOIN operation is abnormal. In most cases, this error occurs because the size of the small table on which the MAPJOIN operation is performed exceeds 512 MB. Modify the MAPJOIN operation.
ODPS-0123131:User defined function exception PROCESSOR 1 The error message returned because the UDF is abnormal. Modify the UDF.
ODPS-0123141:Exstore exception PROCESSOR 1 The error message returned because extreme storage is abnormal. Submit a ticket to contact MaxCompute technical support.
ODPS-0130005:Unknown exception from parser PARSER 5 The error message returned because an internal error has occurred.
ODPS-0130013:Authorization exception PARSER 3 The error message returned because you are not authorized to perform this operation and the security check has failed. Complete authorization.
ODPS-0130025:Failed to I/O PARSER 5 The error message returned because an I/O exception has occurred. Submit a ticket to contact MaxCompute technical support.
ODPS-0130031:Failed to drop table PARSER 1 The error message returned because the source table does not exist when you try to delete the table. Check the name of the source table.
ODPS-0130041:Statistics exception PARSER 1 The error message returned because a statistics exception has occurred. Submit a ticket to contact MaxCompute technical support.
ODPS-0130051:Exception in sub query PARSER 1 The error message returned because a subquery exception has occurred.
ODPS-0130061:Invalid table PARSER 1 The error message returned because the table is invalid. Modify the table.
ODPS-0130071:Semantic analysis exception - Invalid table alias or column reference PARSER 1 The error message returned because the column name is invalid and the required column cannot be found. Confirm the correct column name.
ODPS-0130071:Semantic analysis exception - Invalid column reference PARSER 1 The error message returned because the column reference is invalid and the required column cannot be found. Confirm the correct column name.
ODPS-0130071:Semantic analysis exception - Expression not in GROUP BY key PARSER 1 The error message returned because a syntax parsing exception has occurred. In the SELECT statement, the columns from which you read data are not exactly consistent with the columns that are specified in GROUP BY. Modify the statement to ensure that it meets the syntax requirements.
ODPS-0130071:Semantic analysis exception - Partition not found PARSER 1 The error message returned because a syntax parsing exception has occurred. The partition specified by the value of the partition key column is not found. Change the value of the partition key column in the statement to specify an existing partition.
ODPS-0130071:Semantic analysis exception - SELECT DISTINCT and GROUP BY can not be in the same query PARSER 1 The error message returned because DISTINCT and GROUP BY appear in the same SELECT statement. Modify the statement and make sure that DISTINCT and GROUP BY do not appear in the same SELECT statement.
ODPS-0130071:Semantic analysis exception - Cannot insert into target table because column number/types are different PARSER 1 The error message returned because the number or data types of the columns in the source table are different from those in the destination table when you try to insert data into the destination table. Modify the statement to ensure that the number or data types of the columns in the source table are the same as those in the destination 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. PARSER 1 The error message returned because a full table scan is disabled for a partitioned table of the project to which the table belongs. To address this issue, you must specify the partition that you want to scan. To scan a full table by using the current SQL statement, you can add set odps.sql.allow.fullscan=true to the current SQL statement and submit the command with the SQL statement. A full table scan increases data inputs and costs.
ODPS-0130071:Semantic analysis exception - xxxx type is not enabled in current mode PARSER 1 The error message returned because the feature for using new data types is disabled. Enable the feature for using new data types when you use the MaxCompute V2.0 data type edition.
  • Session level: set odps.sql.type.system.odps2=true;

    This setting must be committed with the SQL statement. This setting is valid only for the current session.

  • Project level: setproject odps.sql.type.system.odps2=true;
ODPS-0130081:Invalid UDF reference PARSER 1 The error message returned because the UDF signature is invalid. Modify the UDF signature.
ODPS-0130091:Invalid parameters PARSER 1 The error message returned because the UDF parameters are invalid. Modify the UDF parameters.
ODPS-0130101:Ambiguous data type PARSER 1 The error message returned because the data type is invalid. Change the data type to a valid type.
ODPS-0130111:Subquery partition pruning exception PARSER 1 The error message returned because dynamic partition optimization in the subquery in the IN conditional statement is abnormal. Modify the IN conditional statement.
ODPS-0130121:Invalid argument type PARSER 1 The error message returned because the parameter type is invalid. In most cases, this error occurs because an invalid parameter type has been received by built-in functions. Change the parameter type to a valid type.
ODPS-0130131:Table not found PARSER 1 The error message returned because the table you want to manage does not exist when you execute a data definition language (DDL) or data manipulation language (DML) statement. Check the name of the table.
ODPS-0130141:Illegal implicit type cast PARSER 1 The error message returned because the implicit data type conversion is not supported. Modify the data type conversion mechanism.
ODPS-0130151:Illegal data type PARSER 1 The error message returned because the data type is invalid. Change the data type to a valid type.
ODPS-0130161:Parse exception PARSER 1 The error message returned because syntax parsing has failed. Submit a ticket to contact MaxCompute technical support.
ODPS-0130171:Creating view exception PARSER 1 The error message returned because an exception has occurred when you create a view. Check the view creation statement and modify it.
ODPS-0130181:Window function exception PARSER 1 The error message returned because the window function is abnormal. Confirm that the window function meets the syntax requirements.
ODPS-0130191:Invalid column or partition key PARSER 1 The error message returned because the column or partition key is invalid. Confirm that the column or partition meets related requirements.
ODPS-0130201:View not found PARSER 1 The error message returned because the view does not exist. Check the name of the view.
ODPS-0130211:Table or view already exists PARSER 1 The error message returned because the table or view that you want to create already exists. Change the name of the table or view that you want to create.
ODPS-0130221:Invalid number of arguments PARSER 1 The error message returned because the number of input parameters is invalid. Change the number of input parameters.
ODPS-0130231:Invalid view PARSER 1 The error message returned because the view is invalid. Check the view.
ODPS-0130241:Illegal union operation PARSER 1 The error message returned because the UNION operation is invalid. In most cases, this error occurs because the numbers or data types of columns on both sides of the UNION clause are inconsistent. Modify the UNION statement to meet the UNION syntax requirements.
ODPS-0130252:Cartesian product is not allowed PARSER 2 The error message returned because Cartesian products are not supported. MaxCompute does not support non-equi joins for ON conditions in JOIN clauses.
ODPS-0130261:Invalid schema PARSER 1 The error message returned because the table schema is invalid. Modify the table schema.
ODPS-0130271:Partition does not exist PARSER 1 The error message returned because the partition does not exist. Check whether the partition exists.
ODPS-0140005:Unknown exception from planner PLANNER 5 The error message returned because an internal error has occurred. Submit a ticket to contact MaxCompute technical support.
ODPS-0140011:Illegal type cast PLANNER 1 The error message returned because the explicit data type conversion is not supported. Modify the data type conversion mechanism.
ODPS-0140021:Illegal implicit type cast PLANNER 1 The error message returned because the implicit data type conversion is not supported. Modify the data type conversion mechanism.
ODPS-0140031:Invalid column reference PLANNER 1 The error message returned because the column name or table name reference is invalid. Modify the column name or table name reference.
ODPS-0140041:Invalid UDF reference PLANNER 1 The error message returned because the UDF does not exist. Check the name of the UDF.
ODPS-0140051:Invalid function PLANNER 1 The error message returned because the function is invalid. Select a valid function.
ODPS-0140061:Invalid parameters PLANNER 1 The error message returned because the input parameters are invalid. Modify the input parameters.
ODPS-0140071:Unsupported operator PLANNER 1 The error message returned because the operator is not supported. Change the operator to the one that is supported.
ODPS-0140081:Unsupported join type PLANNER 1 The error message returned because the left table in the LEFT OUTER JOIN operation is a small table but the right table in this operation is a large table, or the left table in the RIGHT OUTER JOIN operation is a large table but the right table in this operation is a small table. Modify the join sequence.
ODPS-0140091:Unsupported stage type PLANNER 1 The error message returned because the type of the execution plan is not supported. Submit a ticket to contact MaxCompute technical support.
ODPS-0140105:Invalid multiple I/O PLANNER 5 The error message returned because multiple outputs have caused a conflict. Adjust the job to avoid multiple output conflicts.
ODPS-0140111:Unsupported col type in EXTRACT now PLANNER 1 The error message returned because the column type is not supported by EXTRACT. Change the column type to a type that is supported by EXTRACT.
ODPS-0140125:The path need to read has different storage type PLANNER 5 None. Submit a ticket to contact MaxCompute technical support.
ODPS-0140133:Invalid structure PLANNER 3 The error message returned because the data structure cannot be identified. Confirm that the data structure meets the standards.
ODPS-0140141:Can not remove operator with more than one children PLANNER 1 None. Submit a ticket to contact MaxCompute technical support.
ODPS-0140151:Can not do topologic sort, the stages is not a DAG PLANNER 1 The error message returned because an error has occurred in the sorting algorithm. Check the accuracy of the sorting algorithm.
ODPS-0140171:Sandbox violation exception PLANNER 1 The error message returned because the security sandbox model is abnormal. Submit a ticket to contact MaxCompute technical support.
ODPS-0140178: Internal system failure PLANNER 8 The error message returned because an exception has occurred in the system. Retry the operation.
ODPS-0140181:Sql plan exception PLANNER 1 The error message returned because an SQL job cannot generate an execution plan. Resubmit the job. If the job fails to be submitted multiple times,submit a ticket to contact MaxCompute technical support.