Error Class X0 - Execution exceptions

Error Class X0: Execution exceptions
SQLSTATE Message Text
X0A00.S The select list mentions column '<columnName>' twice. This is not allowed in queries with GROUP BY or HAVING clauses. Try aliasing one of the conflicting columns to a unique name.
X0X02.S Table '<tableName>' cannot be locked in '<mode>' mode.
X0X03.S Invalid transaction state - held cursor requires same isolation level
X0X05.S Table/View '<tableName>' does not exist.
X0X07.S Cannot remove jar file '<fileName>' because it is on your derby.database.classpath '<classpath>'.
X0X0D.S Invalid column array length '<columnArrayLength>'. To return generated keys, column array must be of length 1 and contain only the identity column.
X0X0E.S Table '<columnPosition>' does not have an auto-generated column at column position '<tableName>'.
X0X0F.S Table '<columnName>' does not have an auto-generated column named '<tableName>'.
X0X10.S The USING clause returned more than one row; only single-row ResultSets are permissible.
X0X11.S The USING clause did not return any results so no parameters can be set.
X0X13.S Jar file '<fileName>' does not exist in schema '<schemaName>'.
X0X14.S The file '<fileName>' does not exist.
X0X57.S An attempt was made to put a Java value of type '<type>' into a SQL value, but there is no corresponding SQL type. The Java value is probably the result of a method call or field access.
X0X60.S A cursor with name '<cursorName>' already exists.
X0X61.S The values for column '<columnName>' in index '<indexName>' and table '<schemaName>.<tableName>' do not match for row location <location>. The value in the index is '<value>', while the value in the base table is '<value>'. The full index key, including the row location, is '<indexKey>'. The suggested corrective action is to recreate the index.
X0X62.S Inconsistency found between table '<tableName>' and index '<indexName>'. Error when trying to retrieve row location '<rowLocation>' from the table. The full index key, including the row location, is '<indexKey>'. The suggested corrective action is to recreate the index.
X0X63.S Got IOException '<value>'.
X0X67.S Columns of type '<type>' may not be used in CREATE INDEX, ORDER BY, GROUP BY, UNION, INTERSECT, EXCEPT or DISTINCT statements because comparisons are not supported for that type.
X0X81.S <value> '<value>' does not exist.
X0X85.S Index '<indexName>' was not created because '<indexType>' is not a valid index type.
X0X86.S 0 is an invalid parameter value for ResultSet.absolute(int row).
X0X87.S ResultSet.relative(int row) cannot be called when the cursor is not positioned on a row.
X0X95.S Operation '<operationName>' cannot be performed on object '<objectName>' because there is an open ResultSet dependent on that object.
X0X99.S Index '<indexName>' does not exist.
X0Y16.S '<value>' is not a view. If it is a table, then use DROP TABLE instead.
X0Y23.S Operation '<operationName>' cannot be performed on object '<objectName>' because VIEW '<viewName>' is dependent on that object.
X0Y24.S Operation '<operationName>' cannot be performed on object '<objectName>' because STATEMENT '<statement>' is dependent on that object.
X0Y25.S Operation '<operationName>' cannot be performed on object '<objectName>' because <value> '<value>' is dependent on that object.
X0Y26.S Index '<indexName>' is required to be in the same schema as table '<tableName>'.
X0Y28.S Index '<indexName>' cannot be created on system table '<tableName>'. Users cannot create indexes on system tables.
X0Y29.S Operation '<operationName>' cannot be performed on object '<objectName>' because TABLE '<tableName>' is dependent on that object.
X0Y30.S Operation '<operationName>' cannot be performed on object '<objectName>' because ROUTINE '<routineName>' is dependent on that object.
X0Y32.S <value> '<value>' already exists in <value> '<value>'.
X0Y38.S Cannot create index '<indexName>' because table '<tableName>' does not exist.
X0Y41.S Constraint '<constraintName>' is invalid because the referenced table <tableName> has no primary key. Either add a primary key to <tableName> or explicitly specify the columns of a unique constraint that this foreign key references.
X0Y42.S Constraint '<constraintName>' is invalid: the types of the foreign key columns do not match the types of the referenced columns.
X0Y43.S Constraint '<constraintName>' is invalid: the number of columns in <value> (<value>) does not match the number of columns in the referenced key (<value>).
X0Y44.S Constraint '<constraintName>' is invalid: there is no unique or primary key constraint on table '<tableName>' that matches the number and types of the columns in the foreign key.
X0Y45.S Foreign key constraint '<constraintName>' cannot be added to or enabled on table <tableName> because one or more foreign keys do not have matching referenced keys.
X0Y46.S Constraint '<constraintName>' is invalid: referenced table <tableName> does not exist.
X0Y54.S Schema '<schemaName>' cannot be dropped because it is not empty.
X0Y55.S The number of rows in the base table does not match the number of rows in at least 1 of the indexes on the table. Index '<indexName>' on table '<schemaName>.<tableName>' has <number> rows, but the base table has <number> rows. The suggested corrective action is to recreate the index.
X0Y56.S '<value>' is not allowed on the System table '<tableName>'.
X0Y57.S A non-nullable column cannot be added to table '<tableName>' because the table contains at least one row. Non-nullable columns can only be added to empty tables.
X0Y58.S Attempt to add a primary key constraint to table '<tableName>' failed because the table already has a constraint of that type. A table can only have a single primary key constraint.
X0Y59.S Attempt to add or enable constraint(s) on table '<tableName>' failed because the table contains <rowName> row(s) that violate the following check constraint(s): <constraintName>.
X0Y63.S The command on table '<tableName>' failed because null data was found in the primary key or unique constraint/index column(s). All columns in a primary or unique index key must not be null.
X0Y63.S.1 The command on table '<tableName>' failed because null data was found in the primary key/index column(s). All columns in a primary key must not be null.
X0Y66.S Cannot issue commit in a nested connection when there is a pending operation in the parent connection.
X0Y67.S Cannot issue rollback in a nested connection when there is a pending operation in the parent connection.
X0Y68.S <value> '<value>' already exists.
X0Y69.S <value> is not supported in trigger <triggerName>.
X0Y70.S INSERT, UPDATE and DELETE are not permitted on table <tableName> because trigger <triggerName> is active.
X0Y71.S Transaction manipulation such as SET ISOLATION is not permitted because trigger <triggerName> is active.
X0Y72.S Bulk insert replace is not permitted on '<value>' because it has an enabled trigger (<value>).
X0Y77.S Cannot issue set transaction isolation statement on a global transaction that is in progress because it would have implicitly committed the global transaction.
X0Y78.S Statement.executeQuery() cannot be called with a statement that returns a row count.
X0Y78.S.1 <value>.executeQuery() cannot be called because multiple result sets were returned. Use <value>.execute() to obtain multiple results.
X0Y78.S.2 <value>.executeQuery() was called but no result set was returned. Use <value>.executeUpdate() for non-queries.
X0Y79.S Statement.executeUpdate() cannot be called with a statement that returns a ResultSet.
X0Y80.S ALTER table '<tableName>' failed. Null data found in column '<columnName>'.
X0Y83.S WARNING: While deleting a row from a table the index row for base table row <rowName> was not found in index with conglomerate id <id>. This problem has automatically been corrected as part of the delete operation.
X0Y84.T Too much contention on sequence <sequenceName>. This is probably caused by an uncommitted scan of the SYS.SYSSEQUENCES catalog. Do not query this catalog directly. Instead, use the SYSCS_UTIL.SYSCS_PEEK_AT_SEQUENCE function to view the current value of a query generator.
X0Y85.S The Splice property '<propertyName>' identifies a class which cannot be instantiated: '<className>'. See the next exception for details.
X0Y86.S Splice could not obtain the locks needed to release the unused, preallocated values for the sequence '<schemaName>'.'<sequenceName>'. As a result, unexpected gaps may appear in this sequence.
X0Y87.S There is already an aggregate or function with one argument whose name is '<schemaName>'.'<aggregateOrFunctionName>'.