All Products
Search
Document Center

MaxCompute:ODPS-0010000

Last Updated:Jan 27, 2026

This topic describes scenarios and solutions for the error code ODPS-0010000: System internal error.

Error 1: kWorkerOutOfMemory (basic)

Error message

ODPS-0010000:System internal error - fuxi job failed, caused by: kWorkerOutOfMemory(errCode:256) at Odps/xxx/xxx. Detail error msg: KILL_NAKILL_NA: plannedResource({Memory=xxx, CPU=xxx}) usedResource({Memory=xxx, CPU=xxx})

Description

The job uses more resources than planned, causing an out-of-memory (OOM) error and job failure.

Solution

1. Identify the planned and used resource amounts from the plannedResource and usedResource fields in the error message.

2. Determine the task type from the error message:

  • M: mapper

  • R: reducer

  • J: joiner

3. Use SET operations to adjust parameters. For example:

  • odps.stage.mapper.mem

  • odps.stage.mapper.split.size

Error 2: Merge into statement not support update or delete duplicate row

Error message

ODPS-0010000:System internal error - fuxi job failed, caused by: Merge into statement not support update or delete duplicate row, please check your query, the query text location is from [line m, column n] to [line i, column j]

Description

Duplicate values exist on both sides of the equal sign (=) from row m, column n to row i, column j, causing duplicate rows due to data bloat. The MERGE INTO statement cannot update or delete duplicate rows, so the operation fails.

Solution

1. Check for duplicate values in the source data from line m, column n to line i, column j.

2. Remove duplicates before running the statement again.

Error 3: OSSRequestException (temporary service issue)

Error message

ODPS-0010000:System internal error - build/release64/common/io/oss/oss_client.cpp(99): OSSRequestException: req_id: xxxxxx, http status code: 400, error code: InvalidArgument, message: Authorization header is invalid

Description

Object Storage Service (OSS) experiences temporary service instability, making services unavailable for a short period.

Solution

Rerun the job.

Error 4: OSSRequestException (permission issue)

Error message

ODPS-0010000:System internal error - build/release64/common/io/oss/oss_client.cpp(99): OSSRequestException: req_id: xxxxx, http status code: 400, error code: InvalidArgument, message: Authorization header is invalid

Description

You do not have the required permissions to access the OSS file.

Solution

Grant the user accessing the external table the permissions to access the corresponding OSS external table.

Error 5: Shortcut optimize failed because the script is too complex

Error message

ODPS-0010000:System internal error - Shortcut optimize failed because the script is too complex

Description

The SQL statement is too complex, which causes the shortcut optimization to fail.

Solution

Optimize the SQL statement:

  • Split and simplify complex SQL statements

  • Check for:

    • Deeply nested subqueries

    • Excessive JOIN operations

    • Complex aggregate or window functions

  • Reduce data processing volume:

    • Use WHERE clauses to limit query scope

    • Query only necessary partitions of partitioned tables

Error 6: alloc too large size

Error message

ODPS-0010000:System internal error - fuxi job failed, caused by: alloc too large size: xxx

Description

The job failed because it requested too much memory during runtime. Possible causes:

  • A bug in MaxCompute

  • Abnormal user data, such as an ARRAY type field containing too many elements

Solution

1. Check for oversized ARRAY data and reduce its volume.

2. If the issue persists, submit a ticket for technical support.

Error 7: Regex compile error

Error message

ODPS-0010000:System internal error - fuxi job failed, caused by: Regex compile error

Description

The regular expression is invalid.

Solution

Fix the regular expression syntax in your SQL statement.

Error 8: failed to get error message of java exception because of outofmemoryerror

Error message

ODPS-0010000:System internal error - failed to get error message of java exception because of outofmemoryerror

Description

An out-of-memory error caused the program to fail.

Solution

Increase the memory by setting the following parameters.

SET odps.sql.mapper.cpu=400;
SET odps.sql.mapper.memory=8192;

Error 9: codeGenCallBuiltinFunction fail in CopmareBase for function

Error message

ODPS-0010000:System internal error - fuxi job failed, caused by: codeGenCallBuiltinFunction fail in CopmareBase for function: NEQ, xxx

Description

This error often occurs when you perform a NEQ operation on a field or expression of the ARRAY type, which is not supported. For example, this can happen when you use the COLLECT_SET function.

Solution

Use a function that supports the NEQ operations on ARRAY type fields or expressions, such as SIZE(ARRAY)!=0. For more information, see SIZE. Alternatively, you can upgrade MaxCompute to the latest version.

Error 10: process core dumped

Error message

ODPS-0010000:System internal error - fuxi job failed, caused by: process core dumped

Description

This error often occurs when you perform a NEQ operation on a field or expression of the ARRAY type, which is not supported. For example, this can happen when you use the COLLECT_SET function.

Solution

Use a function that supports the NEQ operations on ARRAY type fields or expressions, such as SIZE(ARRAY)!=0. For more information, see SIZE. Alternatively, you can upgrade MaxCompute to the latest version.

Error 11: kWorkerOutOfMemory (detailed)

Error message

ODPS-0010000:System internal error - fuxi job failed, caused by: kWorkerOutOfMemory(errCode:256) at Odps/autonavi_location_20230831212 329151gio81xoniqh_SQL_0_1_0_job_0/R2_1@68d01417.na62#4533.

Detail error msg: KILL_NAKILL_NA: plannedResource ({Memory=4096, CPU=100}) usedResource ({Memory=5751, CPU=164}).

Description

  • Cause: The SQL_0_1_0_job_0/R2_1 part of the error message indicates that an out-of-memory (OOM) error occurred in the R2_1 part of the Reduce stage.

  • Resource information:

    • plannedResource({Memory=4096, CPU=100}) shows the planned resources for this task

    • usedResource({Memory=5751, CPU=164}) shows the actual resources required by the task at runtime

Solution

Set memory for the stage where the OOM error occurred. For this error, configure the following settings for the Reduce stage:

  • SET odps.sql.reducer.memory=6144; -- Must be greater than the memory in usedResource

  • SET odps.sql.reducer.cpu=200; -- Must be greater than the CPU in usedResource