Error map
ORA-01722 ORA-01722: invalid number
SQL · layer 5, Data
Centre: this error. First ring: errors it is linked with (8). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (8)
SQL Server: Arithmetic overflow error converting expression to data type int. (Msg 8115)
A value or calculation exceeds the target data type’s range.
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
DDL or a NOWAIT lock couldn’t get the lock because another session holds it.
SQL Server: String or binary data would be truncated in table 'x', column 'y'. (Msg 2628)
A value is longer than the column allows.
SQL Server: Conversion failed when converting the varchar value 'x' to data type int. (Msg 245)
SQL Server tried to convert text to a number (often implicitly) and hit a non-numeric value.
ORA-00001: unique constraint (SCHEMA.PK_X) violated
An insert/update duplicated a value in a unique or primary key constraint.
ORA-00904: "X": invalid identifier
A column name in the statement doesn’t exist (or is misquoted).
ORA-00933: SQL command not properly ended
Oracle found extra clauses or syntax it doesn’t support at the end of a statement.
API Error: Invalid type — expected integer, received string
A request field has the wrong data type — a string where the API expects a number, a number where it expects a boolean, an object…
Two steps away (24)
ERROR: numeric field overflow — A field with precision 5, scale 2 must round to an absolute value less than 10^3
A number doesn’t fit the column’s numeric(precision, scale) or integer range.
SQL Server: Login failed for user 'x'. (Error 18456)
SQL Server rejected the login — wrong password, wrong authentication mode, or a disabled/missing login.
SQL Server: Invalid object name 'x'. (Msg 208)
The table/view doesn’t exist in the current database or schema.
Deadlock found when trying to get lock; try restarting transaction
Two transactions waited on each other’s locks; the database killed one so the other could continue.
Lock wait timeout exceeded; try restarting transaction (MySQL 1205)
A query waited too long for a row lock held by another transaction and gave up.
MySQL ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
MySQL detected a deadlock between two transactions and rolled one back.
MySQL ERROR 1406: Data too long for column
The value is longer than the column allows (e.g. 300 characters into VARCHAR(255)), and strict mode rejects it instead of truncat…
ERROR: value too long for type character varying(255)
A string exceeds the column’s varchar length.
SQL Server: Cannot insert explicit value for identity column in table 'x' when IDENTITY_INSERT is set to OFF.
An INSERT supplied a value for an IDENTITY column.
ERROR: invalid input syntax for type integer: "abc"
A string couldn’t be converted to the column’s type (integer, numeric, boolean, date…).
SQL Server: Invalid column name 'x'. (Msg 207)
SQL Server can’t find the column — typo, missing migration, or a string in double quotes with QUOTED_IDENTIFIER ON.
SQL Server: Violation of PRIMARY KEY constraint 'x'. Cannot insert duplicate key in object 'y'. (Msg 2627)
An insert duplicated a primary key or unique constraint value.
MySQL ERROR 1062 (23000): Duplicate entry for key
An INSERT/UPDATE would create a duplicate value in a PRIMARY or UNIQUE key.
sqlite3.IntegrityError: UNIQUE constraint failed: users.email
An insert/update duplicated a value in a UNIQUE or PRIMARY KEY column in SQLite.
sqlite3.IntegrityError: NOT NULL constraint failed: table.column
A NULL went into a NOT NULL column in SQLite.
MySQL ERROR 1054 (42S22): Unknown column in 'field list'
The query references a column that doesn’t exist in the table (or an unquoted string being read as a column).
sqlite3.OperationalError: no such column: x
SQLite can’t find the column — missing migration, typo, or a string written in double quotes.
ORA-00942: table or view does not exist
Oracle can’t see the table — it doesn’t exist, is in another schema, or you lack privileges on it.
MySQL ERROR 1064 (42000): You have an error in your SQL syntax
MySQL couldn’t parse the query. The text after “near” shows where parsing failed.
Column reference is ambiguous / Column 'id' in field list is ambiguous (MySQL 1052)
A column name exists in more than one joined table, so the database doesn’t know which one you mean.
Column must appear in the GROUP BY clause / isn't in GROUP BY (MySQL 1055 only_full_group_by)
You selected a column that is neither grouped nor aggregated, so the result would be ambiguous.
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
HTTP 422 Unprocessable Content
The request is well-formed, but the data fails validation (e.g. invalid email, missing required field).
java.lang.NumberFormatException: For input string: "x"
A string couldn’t be parsed as a number — it’s empty, has spaces/commas, is too large, or isn’t numeric.
Map another error
Popular: 403500400TypeErrorCritical error0xC000007BNullPointerException404