MaxCompute error codes identify which component failed, how severe the failure is, and what went wrong — so you can locate and fix issues without guessing.
Error message format
Every MaxCompute error message follows this structure:
Error code:General description - Context-related description| Component | Description |
|---|---|
| Error code | Identifies the module, error type, and severity. Format: ODPS-MMCCCCX |
| General description | A short, human-readable explanation of the error. Each error code maps to exactly one general description. |
| Context-related description | Runtime details that help you pinpoint the root cause. |
Example: In ODPS-0130131:Table not found - "myproject" "mytable", the error code is ODPS-0130131, the general description is Table not found, and "myproject" "mytable" is the context that identifies the missing table.
Error code structure
The error code ODPS-MMCCCCX consists of three fields:
| Field | Description | Values |
|---|---|---|
MM | Module number — identifies which component raised the error | 00–14 (see table below) |
CCCC | Error code — a four-digit integer that identifies the specific error | See Error reference |
X | Severity — a one-digit integer. Higher means more severe. | 1 (minor, e.g., invalid user input) to 9 (major, e.g., atomicity error) |
Module numbers
Module (MM) | Component |
|---|---|
00 | Common errors — failures in underlying components such as Tablestore, Apsara Distributed File System, or Job Scheduler |
01 | SQL jobs |
02 | Procedural language (PL) jobs |
03 | Data Tunnel (DT) — MaxCompute Tunnel jobs |
04 | API |
05 | Xlib jobs — the data mining module in MaxCompute |
07 | MapReduce jobs |
08 | ODPS SDK or client jobs |
09 | Streaming jobs |
10 | Replication jobs |
11 | xFlow jobs |
12 | AlgoTask jobs — Machine Learning Platform for AI (PAI) jobs |
13 | PAI Server (PS) |
14 | Galaxy jobs |
Resolve an error
From the error message, identify the module (
MM), severity (X), and error number (CCCC) to determine the cause of the error.Fix the error based on the context-related description. For complex failures, use LogView V2.0 to inspect job logs. See Use LogView V2.0 to view job information.
Errors
For trigger conditions and solutions for each error type, see the corresponding reference: