Common SQL Error Codes

Indicates that a timeout has occurred while trying to access a specific resource. This can happen when a connection to a database is not closed properly or when a SQL statement takes too long to execute.

Indicates that a deadlock has occurred. This can happen when two or more transactions are trying to access the same resource at the same time.

Indicates that a deadlock or timeout has occurred while trying to access a specific resource.

Indicates that a specific resource is unavailable. This can happen when a database is not running or when a specific database object is in a state that prevents it from being used.

Indicates that a deadlock or timeout has occurred while trying to access a specific resource.

Indicates that a resource is currently unavailable. This can happen when a database is not running or when a specific database object is in a state that prevents it from being used.

Indicates that a deadlock or timeout has occurred while trying to access a specific resource.

Indicates that more than one row has been returned in response to a single row request.

Indicates that a timestamp or date value is not valid. This is a specific error code related to IBM DB2 database.

Indicates that a deadlock or timeout has occurred while trying to access a specific resource.

Indicates that an error occurred while accessing a specific resource. The specific cause of the error would need to be investigated further, by looking at the error message and the system's logs.

Indicates that a deadlock or timeout has occurred while trying to access a specific resource.

Indicates that a specific integrity constraint has been violated. It could be a unique constraint, primary key constraint or a referential integrity constraint.

Indicates that a specific resource is unavailable. This can happen when a database is not running or when a specific database object is in a state that prevents it from being used.

Unique constraint violated. This occurs when trying to insert a duplicate value in a column with a unique index.

Invalid identifier. This error occurs when a column name or table name is misspelled or doesn't exist.

Invalid username/password; logon denied. This error occurs when attempting to connect to the database with incorrect credentials.

Cannot insert NULL. This error occurs when trying to insert a NULL value into a column that is defined as NOT NULL.

No data found. This error occurs when a SELECT statement returns no rows, but at least one row was expected.

Exact fetch returns more than requested number of rows. This error occurs in situations where only one row is expected, but multiple rows are returned.

Value too large for column. This error occurs when trying to insert or update a value that is too large for the defined column size.

You have an error in your SQL syntax. This is a general MySQL error for syntax issues in your SQL statement.

Table doesn't exist. This MySQL error occurs when you try to query a table that doesn't exist in the current database.

Cannot delete or update a parent row: a foreign key constraint fails. This MySQL error occurs when trying to delete or update a row that is referenced by another table.

Relation (table) does not exist. This PostgreSQL error occurs when you try to query a table that doesn't exist.

Column does not exist. This PostgreSQL error occurs when you reference a column that doesn't exist in the table.

Unique violation. This PostgreSQL error occurs when trying to insert a duplicate value in a column with a unique constraint.