public Class ErrorCode

The error with code 90134 is thrown when trying to load a Java class that is not part of the allowed classes.

The error with code 90132 is thrown when trying to drop a user-defined aggregate function that doesn't exist.

The error with code 22034 is thrown when an attempt is made to read non-existing element of an array.

The error with code 90137 is thrown when trying to assign a value to something that is not a variable.

The error with code 90107 is thrown when trying to drop an object because another object would become invalid.

The error with code 90084 is thrown when trying to drop the last column of a table.

The error with code 90123 is thrown when trying mix regular parameters and indexed parameters in the same statement.

The error with code 23514 is thrown when evaluation of a check constraint resulted in an error.

The error with code 90086 is thrown when a class can not be loaded because it is not in the classpath or because a related class is not in the classpath.

The error with code 90094 is thrown when trying to connect to a clustered database that runs together with a different cluster node setting than what is used when trying to connect.

The error with code 90156 is thrown when trying to create a view or a table from a select and some expression doesn't have a column name or alias when it is required by a compatibility mode.

The error with code 21002 is thrown when the number of columns does not match.

The error with code 90083 is thrown when trying to drop a column that is part of a constraint.

The error with code 42122 is thrown when referencing an non-existing column.

The error with code 90104 is thrown when the data can not be de-compressed.

The error with code 90067 is thrown when the client could not connect to the database, or if the connection was lost.

The error with code 90115 is thrown when trying to drop a constant that does not exists.

The error with code 90152 is thrown when trying to manually drop a unique or primary key constraint that is referenced by a foreign key constraint without a CASCADE clause.

The error with code 90148 is thrown when trying to access the current value of a sequence before execution of NEXT VALUE FOR sequenceName in the current session.

The error with code 90020 is thrown when trying to open a database in embedded mode if this database is already in use in another process (or in a different class loader).

The error with code 90098 is thrown when the database has been closed, for example because the system ran out of memory or because the self-destruction counter has reached zero.

The error with code 90126 is thrown when trying to call the BACKUP statement for an in-memory database.

The error with code 90013 is thrown when when trying to access a database object with a catalog name that does not match the database name.

The error with code 40001 is thrown when the database engine has detected a deadlock.

The error with code 22012 is thrown when trying to divide a value by zero.

The error with code 90120 is thrown when trying to drop a domain that doesn't exist.

The error with code 42121 is thrown when trying to create a table or insert into a table and use the same column name twice.

The error with code 90066 is thrown when the same property appears twice in the database URL or in the connection properties.

The error with code 22032 is thrown when an attempt is made to add or modify an ENUM-typed column so that one or more of its enumerators would be empty.

The error with code 90111 is thrown when an exception occurred while accessing a linked table.

The error with code 90044 is thrown when an exception or error occurred while calling the triggers fire method.

The error with code 90099 is thrown when an error occurred trying to initialize the database event listener.

The error with code 90061 is thrown when trying to start a server if a server is already running at the same port.

The error with code 90030 is thrown when the database engine has detected a checksum mismatch in the data or index.

The error with code 90025 is thrown when a file could not be deleted, because it is still in use (only in Windows), or because an error occurred when deleting.

The error with code 90124 is thrown when trying to access a file that doesn't exist.

The error with code 90048 is thrown when the file header of a database files (*.db) does not match the expected version, or if it is corrupted.

The error with code 90076 is thrown when trying to create a function alias for a system function or for a function that is already defined.

The error with code 90000 is thrown when a function that does not return a result set was used in the FROM clause.

The error with code 50000 is thrown when something unexpected occurs, for example an internal stack overflow.

The error with code 90155 is thrown when trying to create a referential constraint that can update a referenced generated column.

The error with code 90003 is thrown when trying to convert a String to a binary value.

The error with code 42131 is thrown when identical expressions should be used, but different expressions were found.

The error with code 90085 is thrown when trying to manually drop an index that was generated by the system because of a unique or referential constraint.

The error with code 90125 is thrown when PreparedStatement.setBigDecimal is called with object that extends the class BigDecimal.

The error with code 22007 is thrown when a text can not be converted to a date, time, or timestamp constant.

The error with code 7001 is thrown when trying to call a function with the wrong number of parameters.

The error with code 90010 is thrown when trying to format a timestamp or number using TO_CHAR with an invalid format.

The error with code 90005 is thrown when trying to create a trigger with invalid combination of flags.

The error with code 90008 is thrown when trying to use a value that is not valid for the given operation.

The error with code 90151 is thrown when trying to use an invalid scale or fractional seconds precision.

The error with code 90031 is thrown when an input / output error occurred.

The error with code 22025 is thrown when using an invalid escape character sequence for LIKE or REGEXP.

The error with code 90039 is thrown when trying to access a CLOB or BLOB object that timed out.

The error with code 90147 is thrown when trying to execute a statement which closes the transaction (such as commit and rollback) and autocommit mode is on.

The error with code 90001 is thrown when Statement.executeUpdate() was called for a SELECT statement.

The error with code 90002 is thrown when Statement.executeQuery() was called for a statement that does not return a result set (for example, an UPDATE statement).

The error with code 90016 is thrown when a column was used in the expression list or the order by clause of a group or aggregate query, and that column is not in the GROUP BY clause.

The error with code 2000 is thrown when the result set is positioned before the first or after the last row, or not on a valid row for the given operation.

The error with code 90096 is thrown when trying to perform an operation with a non-admin user if the user does not have enough rights.

The error with code 23502 is thrown when trying to insert NULL into a column that does not allow NULL.

The error with code 22003 is thrown when a value is out of range when converting to another data type.

The error with code 90007 is thrown when trying to call a JDBC method on an object that has been closed.

The error with code 90108 is thrown when not enough heap memory was available.

The error with code 90014 is thrown when trying to parse a date with an unsupported format string, or when the date can not be parsed.

The error with code 23503 is thrown when trying to delete or update a row when this would violate a referential constraint, because there is a child row that would become an orphan.

The error with code 90117 is thrown when trying to connect to a TCP server from another machine, if remote connections are not allowed.

The error with code 90128 is thrown when trying to call a method of the ResultSet that is only supported for scrollable result sets, and the result set is not scrollable.

The error with code 90140 is thrown when trying to update or delete a row in a result set if the statement was not created with updatable concurrency.

The error with code 90074 is thrown when trying to grant a role that has already been granted.

The error with code 90070 is thrown when trying to drop or grant a role that does not exists.

The error with code 90143 is thrown when trying to fetch a row from the primary index and the row is not there.

The error with code 90063 is thrown when trying to rollback to a savepoint that is not defined.

The error with code 90064 is thrown when Savepoint.getSavepointName() is called on an unnamed savepoint.

The error with code 90078 is thrown when trying to create a schema if an object with this name already exists.

The error with code 90080 is thrown when trying to rename a object to a different schema, or when trying to create a related object in another schema.

The error with code 90017 is thrown when trying to define a second primary key constraint for this table.

The error with code 90009 is thrown when trying to create a sequence with an invalid combination of attributes (min value, max value, start value, etc).

The error with code 90006 is thrown when trying to get a value from a sequence that has run out of numbers and does not have cycling enabled.

The error with code 90026 is thrown when an object could not be serialized.

The error with code 90142 is thrown when trying to set zero for step size.

The error with code 90052 is thrown when a single-column subquery is expected but a subquery with other number of columns was specified.

The error with code 42000 is thrown when trying to execute an invalid SQL statement.

The error with code 42101 is thrown when trying to create a table or view if an object with this name already exists.

The error with code 42104 is thrown when trying to query, modify or drop a table or view that does not exists in this schema and database but it is empty anyway.

The error with code 54011 is thrown when too many columns were specified in a table, select statement, or row value.

The error with code 90034 is thrown when writing to the trace file failed, for example because the there is an I/O exception.

The error with code 90041 is thrown when trying to create a trigger and there is already a trigger with that name.

The error with code 90110 is thrown when trying to compare or combine values of incomparable data types.

The error with code 50004 is thrown when creating a table with an unsupported data type, or when the data type is unknown because parameters are used.

The error with code 90055 is thrown when trying to open a database with an unsupported cipher algorithm.

The error with code 90102 is thrown when trying to use unsupported options for the given compression algorithm.

The error with code 90113 is thrown when the database URL contains unsupported settings.

The error with code 90046 is thrown when trying to open a connection to a database using an unsupported URL format.

The error with code 90033 is thrown when trying to create a user or role if a user with this name already exists.

The error with code 90071 is thrown when trying to grant or revoke if no role or user with that name exists.

The error with code 90038 is thrown when trying to create a view if a view with this name already exists.

The error with code 90037 is thrown when trying to drop or alter a view that does not exist.

The error with code 90122 is thrown when WITH TIES clause is used without ORDER BY clause.

The error with code 28000 is thrown when there is no such user registered in the database, when the user password does not match, or when the database encryption password does not match (if database encryption is used).