Exception Messages and SQL States

The JDBC driver returns SQLExceptions for all errors from GemFire XD. If the exception originated in a user type but is not itself a SQLException, it is wrapped in a SQLException. GemFire XD-specific SQLExceptions use SQLState class codes starting with X. Standard SQLState values are returned for exceptions where appropriate.

Unimplemented aspects of the JDBC driver return a SQLException with a SQLState starting with 0A. If your application runs on JDK 1.6 or higher, then the exception class is java.sql.SQLFeatureNotSupportedException. These unimplemented parts are for features not supported by GemFire XD.

GemFire XD supplies values for the message and SQLState fields. In addition, GemFire XD sometimes returns multiple SQLExceptions using the nextException chain. The first exception is always the most severe exception, with SQL-92 Standard exceptions preceding those that are specific to GemFire XD.

Table 1. Class 01: Warning
SQLState Message text
01001 An attempt to update or delete an already deleted row was made: No row was updated or deleted.
01003 Null values were eliminated from the argument of a column function.
01006 Privilege not revoked from user {0}.
01007 Role {0} not revoked from authentication id {1}.
01008 WITH ADMIN OPTION of role {0} not revoked from authentication id {1}.
0100E XX Attempt to return too many result sets.
01500 The constraint {0} on table {1} has been dropped.
01501 The view {0} has been dropped.
01502 The trigger {0} on table {1} has been dropped.
01503 The column {0} on table {1} has been modified by adding a not null constraint.
01504 The new index is a duplicate of an existing index: {0}.
01505 The value {0} may be truncated.
01506 The index {0} on table {1} has been dropped due to {2}.
01507 The GatewaySender/AsyncEventListener {0} on table {1} is not created on this member. Existing {2} : {3}.
01508 Attempt to start AsyncEventQueue {0} which is already running.
01522 The newly defined synonym '{0}' resolved to the object '{1}' which is currently undefined.
01J01 Database '{0}' not created, connection made to existing database instead.
01J02 Scroll sensitive cursors are not currently implemented.
01J04 The class '{0}' for column '{1}' does not implement java.io.Serializable or java.sql.SQLData. Instances must implement one of these interfaces to allow them to be stored.
01J05 Database upgrade succeeded. The upgraded database is now ready for use. Revalidating stored prepared statements failed. See next exception for details of failure.
01J06 ResultSet not updatable. Query does not qualify to generate an updatable ResultSet.
01J07 ResultSetHoldability restricted to ResultSet.CLOSE_CURSORS_AT_COMMIT for a global transaction.
01J08 Unable to open resultSet type {0}. ResultSet type {1} opened.
01J10 Scroll sensitive result sets are not supported by server; remapping to forward-only cursor
01J12 Unable to obtain message text from server. See the next exception. The stored procedure SYSIBM.SQLCAMESSAGE is not installed on the server. Please contact your database administrator.
01J13 Number of rows returned ({0}) is too large to fit in an integer; the value returned will be truncated.
01J14 SQL authorization is being used without first enabling authentication.
Table 2. Class 07: Dynamic SQL Error
SQLState Message text
07000 Parameter at position {0} (1 based) to the current statement '{1}' is uninitialized.
07004 Parameter {0} is an {1} procedure parameter and must be registered with CallableStatement.registerOutParameter before execution.
07009 No input parameters.
Table 3. Class 08: Connection Exception
SQLState Message text
08000 Connection closed by unknown interrupt.
08000.S.1 Cannot close a connection with an active transaction. The transaction remains open and the connection was not closed.
08001.C.10 A connection could not be established because the security token is larger than the maximum allowed by the network protocol.
08001.C.11 A connection could not be established because the user id has a length of zero or is larger than the maximum allowed by the network protocol.
08001.C.12 A connection could not be established because the password has a length of zero or is larger than the maximum allowed by the network protocol.
08001.C.1 Required GemFireXD DataSource property {0} not set.
08001.C.2 {0} : Error connecting to server {1} on port {2} with message {3}.
08001.C.3 SocketException: '{0}'
08001.C.4 Unable to open stream on socket: '{0}'.
08001.C.5 User id length ({0}) is outside the range of 1 to {1}.
08001.C.6 Password length ({0}) is outside the range of 1 to {1}.
08001.C.7 User id can not be null.
08001.C.8 Password can not be null.
08001.C.9 A connection could not be established because the database name '{0}' is larger than the maximum length allowed by the network protocol.
08003 No current connection.
08003.C.1 getConnection() is not valid on a closed PooledConnection.
08003.C.2 Lob method called after connection was closed
08003.C.3 The underlying physical connection is stale or closed.
08004 Connection refused : {0}
08004.C.1 Connection authentication failure occurred. Reason: {0}.
08004.C.2 The connection was refused because the database {0} was not found.
08004.C.3 Database connection refused.
08004.C.4 User '{0}' cannot shut down database '{1}'. Only the database owner can perform this operation.
08004.C.5 User '{0}' cannot (re)encrypt database '{1}'. Only the database owner can perform this operation.
08004.C.6 User '{0}' cannot hard upgrade database '{1}'. Only the database owner can perform this operation.
08004.C.7 Connection refused to database '{0}' because it is in replication slave mode.
08004.C.8 User '{0}' cannot issue a replication operation on database '{1}'. Only the database owner can perform this operation.
08004.C.9 Missing permission for user '{0}' to shutdown system [{1}].
08004.C.10 Cannot check system permission to create database '{0}' [{1}].
08004.C.11 Missing permission for user '{0}' to create database '{1}' [{2}].
08004.S.12 Failed with old password passed for user '{0}': {1}
08006.C A network protocol error was encountered and the connection has been terminated: {0}
08006.C.1 An error occurred during connect reset and the connection has been terminated. See chained exceptions for details.
08006.C.2 SocketException: '{0}'
08006.C.3 A communications error has been detected: {0}.
08006.C.4 An error occurred during a deferred connect reset and the connection has been terminated. See chained exceptions for details.
08006.C.5 Insufficient data while reading from the network - expected a minimum of {0} bytes and received only {1} bytes. The connection has been terminated.
08006.C.6 Attempt to fully materialize lob data that is too large for the JVM. The connection has been terminated.
08006.D Database '{0}' shutdown.
Table 4. Class 0A: Feature not supported
SQLState Message text
0A000.S Feature not implemented: {0}.
0A000.C.6 The DRDA command {0} is not currently implemented. The connection has been terminated.
0A000.S.1 JDBC method is not yet implemented.
0A000.S.2 JDBC method {0} is not supported by the server. Please upgrade the server.
0A000.S.3 resultSetHoldability property {0} not supported
0A000.S.4 cancel() not supported by the server.
0A000.S.5 Security mechanism '{0}' is not supported.
0A000.S.7 The data type '{0}' is not supported.
0A000.S.8 The query cannot be executed as the partitioned table '{0}' is not having any colocation defined, and this version of GemFireXD does not support joins/subqueries on non-colocated tables.
0A000.S.9 The query cannot be executed as the table '{0}' is not colocated with '{1}', and this version of GemFireXD does not support joins/subqueries on non-colocated tables.
0A000.S.10 The query cannot be executed as it does not have all the required colocation equijoin conditions, and this version of GemFireXD does not support joins/subqueries on non-colocated table columns. Reason: {0}.
0A000.S.11 The query cannot be executed as atleast one Partitioned Table involved is having multiple nodes.
0A000.S.12 The delete rules, CASCADE and SET NULL, on foreign keys are not supported.
0A000.S.13 Statement cannot continue execution as overflowing to disk is unsupported. Try limiting the sort size or the join size.
0A000.S.14 Correlated query with outer query on replicated table and inner on partitioned table is unsupported in this version of GemFireXD.
0A000.S.15 A distributed member with given ID '{0}' could not be found.
0A000.S.16 Correlated, non primary key type subquery on partitioned based table not supported in this version of GemFireXD.
0A000.S.17 Subqueries with more than one level of nesting not supported in this version of GemFireXD.
0A000.S.18 Updatable resultset supported only in read committed and repeatable read transaction isolation levels in this version of GemFireXD.
0A000.S.19 Only TYPE_FORWARD_ONLY resultsets supported in this version of GemFireXD.
0A000.S.20 Nesting level more than 1 not supported for subqueries in this version of GemFireXD.
0A000.S.21 GENERATED BY DEFAULT AS IDENTITY clause specified for column '{0}' not implemented in this version of GemFireXD.
0A000.S.22 UPDATABLE concurrency is unsupported with SCROLL_INSENSITIVE result set type in GemFireXD.
0A000.S.23 Internal error: cannot apply OR list optimization.
0A000.S.24 Index of type '{0}' cannot be case-insensitive.
0A000.S.25 Alter Table {0} add Foreign Key constraint failed , because it is not colocated with the table {1}. For a Foreign Key relationship defined on unique column(s) of master table with those columns also forming the partitioning columns, it is necessary for the FK table to be colocated using FK columns, with the master.
0A000.S.26 CHANGE_PASSWORD not allowed for current authentication scheme '{0}'.
0A000.S.27 Local index '{0}' can only be created on table '{1}' using HDFSStore when the table uses EVICTION BY CRITERIA or uses OVERFLOW. The eviction action for the table is '{2}'.
0A000.S.28 LRU eviction is not supported for HDFS tables.
0A000.S.29 HDFS Store cannot be used for REPLICATED TABLE.
0A000.S.30 Foreign key constraint is not supported with custom eviction criteria for HDFS tables.
Table 5. Class 0P: Invalid role specification
SQLState Message text
0P000 Invalid role specification, role does not exist: '{0}'.
0P000.S.1 Invalid role specification, role not granted to current user or PUBLIC: '{0}'.
Table 6. Class 21: Cardinality Violation
SQLState Message text
21000 Scalar subquery is only allowed to return a single row.
Table 7. Class 22: Data Exception
SQLState Message text
22001 A truncation error was encountered trying to shrink {0} '{1}' to length {2}.
22003 The resulting value is outside the range for data type '{0}' column '{1}'.
22003.S.1 Year ({0}) exceeds the maximum '{1}'.
22003.S.2 Decimal may only be up to 127 digits.
22003.S.3 Overflow occurred during numeric data type conversion of '{0}' to {1}.
22004.S.4 The length ({0}) exceeds the maximum length for the data type ({1}).
22005.S.1 Unable to convert a value of type '{0}' to type '{1}' for column '{2}': the encoding is not supported.
22005.S.2 The required character converter is not available.
22005.S.3 Unicode string cannot convert to Ebcdic string
22005.S.4 Unrecognized JDBC type. Type: {0}, columnCount: {1}, columnIndex: {2}.
22005.S.5 Invalid JDBC type for parameter {0}.
22005.S.6 Unrecognized Java SQL type {0}.
22005 An attempt was made to get a data value of type '{0}' from a data value of type '{1}' for column '{2}'.
22007.S.180 The string representation of a datetime value is out of range for reason '{0}'.
22007.S.181 The syntax of the string representation of a datetime value '{0}' is incorrect.
22008.S '{0}' is an invalid argument to the {1} function.
2200L Values assigned to XML columns must be well-formed DOCUMENT nodes.
2200M Invalid XML DOCUMENT: {0}
2200V Invalid context item for {0} operator; context items must be well-formed DOCUMENT nodes.
2200W XQuery serialization error: Attempted to serialize one or more top-level Attribute nodes.
22011 The second or third argument of the SUBSTR function is out of range.
22012 Attempt to divide by zero.
22013 Attempt to take the square root of a negative number, '{0}'.
22014 The start position for LOCATE is invalid; it must be a positive integer. The index to start the search from is '{2}'. The string to search for is '{0}'. The string to search from is '{1}'.
22015.S.1 Invalid data conversion: requested conversion would result in a loss of precision of {0}
22015 The '{0}' function is not allowed on the following set of types. First operand is of type '{1}'. Second operand is of type '{2}'. Third operand (start position) is of type '{3}'.
22018 Invalid character string format for type '{0}' column '{1}'.
22019 Invalid escape sequence, '{0}'. The escape string must be exactly one character. It cannot be a null or more than one character.
22020 Invalid trim string, '{0}'. The trim string must be exactly one character or NULL. It cannot be more than one character.
22025 Escape character must be followed by escape character, '_', or '%'. It cannot be followed by any other character or be at the end of the pattern.
22027 The built-in TRIM() function only supports a single trim character. The LTRIM() and RTRIM() built-in functions support multiple trim characters.
22028 The string exceeds the maximum length of {0}.
22501 An ESCAPE clause of NULL returns undefined results and is not allowed.
2201X Invalid row count for OFFSET, must be >= 0.
2201W Invalid row count for FIRST/NEXT, must be >= 1.
2201Z NULL value not allowed for {0} argument.
Table 8. Class 23: Constraint Violation
SQLState Message text
23502 Column '{0}' cannot accept a NULL value.
23503 {2} on table '{1}' caused a violation of foreign key constraint '{0}' for key {3}. The statement has been rolled back.
23505 The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by '{0}' defined on '{1}'.
23513 The check constraint '{1}' was violated while performing an INSERT or UPDATE on table '{0}'.
Table 9. Class 24: Invalid Cursor State
SQLState Message text
24000 Invalid cursor state - no current row.
24501.S The identified cursor is not open.
Table 10. Class 25: Invalid Transaction State
SQLState Message text
25001 Cannot close a connection while a transaction is still active.
25001.S.1 Invalid transaction state: active SQL transaction.
25501 Unable to set the connection read-only property in an active transaction.
25502 An SQL data change is not permitted for a read-only connection, user or database.
25503 DDL is not permitted for a read-only connection, user or database.
25505 A read-only user or a user in a read-only database is not permitted to disable read-only mode on a connection.
Table 11. Class 28: Invalid Authorization Specification
SQLState Message text
28502 The user name '{0}' is not valid.
28503 The user name '{0}' defined as system property cannot be overridden by procedure.
28504 User '{0}' already defined.
Table 12. Class 2D: Invalid Transaction Termination
SQLState Message text
2D521.S.1 setAutoCommit(true) invalid during global transaction.
2D521.S.2 COMMIT or ROLLBACK invalid for application execution environment.
Table 13. Class 38: External Function Exception
SQLState Message text
38000 The exception '{0}' was thrown while evaluating an expression.
38001 The external routine is not allowed to execute SQL statements.
38002 The routine attempted to modify data, but the routine was not defined as MODIFIES SQL DATA.
38004 The routine attempted to read data, but the routine was not defined as READS SQL DATA.
Table 14. Class 39: External Routine Invocation Exception
SQLState Message text
39004 A NULL value cannot be passed to a method which takes a parameter of primitive type '{0}'.
Table 15. Class 3B: Invalid SAVEPOINT
SQLState Message text
3B001.S SAVEPOINT, {0} does not exist or is not active in the current transaction.
3B002.S The maximum number of savepoints has been reached.
3B501.S A SAVEPOINT with the passed name already exists in the current transaction.
3B502.S A RELEASE or ROLLBACK TO SAVEPOINT was specified, but the savepoint does not exist.
Table 16. Class 40: Transaction Rollback
SQLState Message text
40001 A lock could not be obtained due to a deadlock, cycle of locks and waiters is: {0}. The selected victim is XID : {1}.
40XC0 Dead statement. This may be caused by catching a transaction severity error inside this statement.
40XD0 Container has been closed on '{0}'.
40XD1 Container was opened in read-only mode.
40XD2 Container {0} cannot be opened; it either has been dropped or does not exist.
40XL1 A lock could not be obtained within the time requested
40XL2 A lock could not be obtained within the time requested. The lockTable dump is: {0}
40XT0 An internal error was identified by RawStore module.
40XT1 An exception was thrown during transaction commit.
40XT2 An exception was thrown during rollback of a SAVEPOINT.
40XT4 An attempt was made to close a transaction that was still active. The transaction has been aborted.
40XT5 Exception thrown during an internal transaction.
40XT6 Database is in quiescent state, cannot activate transaction. Please wait for a moment till it exits the quiescent state.
40XT7 Operation is not supported in an internal transaction.
Table 17. Class 42: Syntax Error or Access Rule Violation
SQLState Message text
42000 Syntax error or access rule violation; see additional errors for details.
42500 User '{0}' does not have {1} permission on table '{2}'.'{3}'.
42501 User '{0}' does not have {1} permission on table '{2}'.'{3}' for grant.
42502 User '{0}' does not have {1} permission on column '{2}' of table '{3}'.'{4}'.
42503 User '{0}' does not have {1} permission on column '{2}' of table '{3}'.'{4}' for grant.
42504 User '{0}' does not have {1} permission on {2} '{3}'.'{4}'.
42505 User '{0}' does not have {1} permission on {2} '{3}'.'{4}' for grant.
42506 User '{0}' is not the owner of {1} '{2}'.'{3}'.
42507 User '{0}' can not perform the operation in schema '{1}'.
42508 User '{0}' can not create schema '{1}'. Only database owner could issue this statement.
42509 Specified grant or revoke operation is not allowed on object '{0}'.
4250A User '{0}' does not have {1} permission on object '{2}'.'{3}'.
4250B Invalid database authorization property '{0}={1}'.
4250C User(s) '{0}' must not be in both read-only and full-access authorization lists.
4250D Repeated user(s) '{1}' in access list '{0}';
4250E Internal Error: invalid {0} id in statement permission list.
4251A Statement {0} can only be issued by database owner.
42601 In an ALTER TABLE statement, the column '{0}' has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL.
42601.S.372 ALTER TABLE statement cannot add an IDENTITY column to a table.
42605 The number of arguments for function '{0}' is incorrect.
42606 An invalid hexadecimal constant starting with '{0}' has been detected.
42610 All the arguments to the COALESCE/VALUE function cannot be parameters. The function needs at least one argument that is not a parameter.
42611 The length, precision, or scale attribute for column, or type mapping '{0}' is not valid.
42613 Multiple or conflicting keywords involving the '{0}' clause are present.
42621 A check constraint or generated column that is defined with '{0}' is invalid.
42622 The name '{0}' is too long. The maximum length is '{1}'.
42734 Name '{0}' specified in context '{1}' is not unique.
42802 The number of values assigned is not the same as the number of specified or implied columns.
42803 An expression containing the column '{0}' appears in the SELECT list and is not part of a GROUP BY clause.
42815.S.713 The replacement value for '{0}' is invalid.
42815.S.171 The data type, length or value of arguments '{0}' and '{1}' is incompatible.
42818 Comparisons between '{0}' and '{1}' are not supported. Types must be comparable. String types must also have matching collation. If collation does not match, a possible solution is to cast operands to force them to the default collation (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) = 'T1')
42820 The floating point literal '{0}' contains more than 30 characters.
42821 Columns of type '{0}' cannot hold values of type '{1}' for {2}.
42824 An operand of LIKE is not a string, or the first operand is not a column.
42831 '{0}' cannot be a column of a primary key or unique key because it can contain null values.
42834 SET NULL cannot be specified because FOREIGN KEY '{0}' cannot contain null values.
42837 ALTER TABLE '{0}' specified attributes for column '{1}' that are not compatible with the existing column.
42846 Cannot convert types '{0}' to '{1}'.
42877 A qualified column name '{0}' is not allowed in the ORDER BY clause.
42878 The ORDER BY clause of a SELECT UNION statement only supports unqualified column references and column position numbers. Other expressions are not currently supported.
42879 The ORDER BY clause may not contain column '{0}', since the query specifies DISTINCT and that column does not appear in the query result.
4287A The ORDER BY clause may not specify an expression, since the query specifies DISTINCT.
42884 No authorized routine named '{0}' of type '{1}' having compatible arguments was found.
42886 '{0}' parameter '{1}' requires a parameter marker '?'.
42894 DEFAULT value or IDENTITY attribute value is not valid for column '{0}'.
428C1 Only one identity column is allowed in a table.
428EK The qualifier for a declared global temporary table name must be SESSION.
42903 Invalid use of an aggregate function.
42904 Invalid use of a subquery in '{0}'.
42908 The CREATE VIEW statement does not include a column list.
42909 The CREATE TABLE statement does not include a column list.
42915 Foreign Key '{0}' is invalid because '{1}'.
42916 Synonym '{0}' cannot be created for '{1}' as it would result in a circular synonym chain.
42939 An object cannot be created with the schema name '{0}'.
4293A A role cannot be created with the name '{0}', the SYS prefix is reserved.
42962 Long column type column or parameter '{0}' not permitted in declared global temporary tables or procedure definitions.
42972 An ON clause associated with a JOIN operator is not valid.
42995 The requested function does not apply to global temporary tables.
42X01 Syntax error: {0}.
42X02 {0}.
42X03 Column name '{0}' is in more than one table in the FROM list.
42X04 Column '{0}' is either not in any table in the FROM list or appears within a join specification and is outside the scope of the join specification or appears in a HAVING clause and is not in the GROUP BY list. If this is a CREATE or ALTER TABLE statement then '{0}' is not a column in the target table.
42X05 Table/View '{0}' does not exist.
42X06 Too many result columns specified for table '{0}'.
42X07 Null is only allowed in a VALUES clause within an INSERT statement.
42X08 The constructor for class '{0}' cannot be used as an external virtual table because the class does not implement '{1}'.
42X09 The table or alias name '{0}' is used more than once in the FROM list.
42X10 '{0}' is not an exposed table name in the scope in which it appears.
42X12 Column name '{0}' appears more than once in the CREATE TABLE statement.
42X13 Column name '{0}' appears more than once times in the column list of an INSERT statement.
42X14 '{0}' is not a column in table or VTI '{1}'.
42X15 Column name '{0}' appears in a statement without a FROM list.
42X16 Column name '{0}' appears multiple times in the SET clause of an UPDATE statement.
42X17 In the Properties list of a FROM clause, the value '{0}' is not valid as a joinOrder specification. Only the values FIXED and UNFIXED are valid.
42X19 The WHERE or HAVING clause or CHECK CONSTRAINT definition is a '{0}' expression. It must be a BOOLEAN expression.
42X20 Syntax error; integer literal expected.
42X23 Cursor {0} is not updatable.
42X24 Column {0} is referenced in the HAVING clause but is not in the GROUP BY list.
42X25 The '{0}' function is not allowed on the '{1}' type.
42X26 The class '{0}' for column '{1}' does not exist or is inaccessible. This can happen if the class is not public.
42X28 Delete table '{0}' is not target of cursor '{1}'.
42X29 Update table '{0}' is not the target of cursor '{1}'.
42X30 Cursor '{0}' not found. Verify that autocommit is OFF.
42X31 Column '{0}' is not in the FOR UPDATE list of cursor '{1}'.
42X32 The number of columns in the derived column list must match the number of columns in table '{0}'.
42X33 The derived column list contains a duplicate column name '{0}'.
42X34 There is a ? parameter in the select list. This is not allowed.
42X35 It is not allowed for both operands of '{0}' to be ? parameters.
42X36 The '{0}' operator is not allowed to take a ? parameter as an operand.
42X37 The unary '{0}' operator is not allowed on the '{1}' type.
42X38 'SELECT *' only allowed in EXISTS and NOT EXISTS subqueries.
42X39 Subquery is only allowed to return a single column.
42X40 A NOT statement has an operand that is not boolean . The operand of NOT must evaluate to TRUE, FALSE, or UNKNOWN.
42X41 In the Properties clause of a FROM list, the property '{0}' is not valid (the property was being set to '{1}').
42X42 Correlation name not allowed for column '{0}' because it is part of the FOR UPDATE list.
42X43 The ResultSetMetaData returned for the class/object '{0}' was null. In order to use this class as an external virtual table, the ResultSetMetaData cannot be null.
42X44 Invalid length '{0}' in column specification.
42X45 {0} is an invalid type for argument number {1} of {2}.
42X46 There are multiple functions named '{0}'. Use the full signature or the specific name.
42X47 There are multiple procedures named '{0}'. Use the full signature or the specific name.
42X48 Value '{1}' is not a valid precision for {0}.
42X49 Value '{0}' is not a valid integer literal.
42X50 No method was found that matched the method call {0}.{1}({2}).{3} Tried all combinations of object and primitive types and any possible type conversion for any parameters the method call may have. The method might exist but it is not public and/or static, or the parameter types are not method invocation convertible.
42X51 The class '{0}' does not exist or is inaccessible. This can happen if the class is not public.
42X52 Calling method ('{0}') using a receiver of the Java primitive type '{1}' is not allowed.
42X53 The LIKE predicate can only have 'CHAR' or 'VARCHAR' operands. Type '{0}' is not permitted.
42X54 The Java method '{0}' has a ? as a receiver. This is not allowed.
42X55 Table name '{1}' should be the same as '{0}'.
42X56 The number of columns in the view column list does not match the number of columns in the underlying query expression in the view definition for '{0}'.
42X57 The getColumnCount() for external virtual table '{0}' returned an invalid value '{1}'. Valid values are greater than or equal to 1.
42X58 The number of columns on the left and right sides of the {0} must be the same.
42X59 The number of columns in each VALUES constructor must be the same.
42X60 Invalid value '{0}' for insertMode property specified for table '{1}'.
42X61 Types '{0}' and '{1}' are not {2} compatible.
42X62 '{0}' is not allowed in the '{1}' schema.
42X63 The USING clause did not return any results. No parameters can be set.
42X64 In the Properties list, the invalid value '{0}' was specified for the useStatistics property. The only valid values are TRUE or FALSE.
42X65 Index '{0}' does not exist.
42X66 Column name '{0}' appears more than once in the CREATE INDEX statement.
42X67 In the Properties list of a FROM clause, the value '{0}' is not valid as a sizerHints specification. Only values in Constants.QueryHints.SizerHints are valid.
42X68 No field '{0}' was found belonging to class '{1}'. It may be that the field exists, but it is not public, or that the class does not exist or is not public.
42X69 It is not allowed to reference a field ('{0}') using a referencing expression of the Java primitive type '{1}'.
42X70 The number of columns in the table column list does not match the number of columns in the underlying query expression in the table definition for '{0}'.
42X71 Invalid data type '{0}' for column '{1}'.
42X72 No static field '{0}' was found belonging to class '{1}'. The field might exist, but it is not public and/or static, or the class does not exist or the class is not public.
42X73 Method resolution for signature {0}.{1}({2}) was ambiguous. (No single maximally specific method.)
42X74 Invalid CALL statement syntax.
42X75 No constructor was found with the signature {0}({1}). It may be that the parameter types are not method invocation convertible.
42X76 At least one column, '{0}', in the primary key being added is nullable. All columns in a primary key must be non-nullable.
42X77 Column position '{0}' is out of range for the query expression.
42X78 Column '{0}' is not in the result of the query expression.
42X79 Column name '{0}' appears more than once in the result of the query expression.
42X80 VALUES clause must contain at least one element. Empty elements are not allowed.
42X82 The USING clause returned more than one row. Only single-row ResultSets are permissible.
42X83 The constraints on column '{0}' require that it be both nullable and not nullable.
42X84 Index '{0}' was created to enforce constraint '{1}'. It can only be dropped by dropping the constraint.
42X85 Constraint '{0}'is required to be in the same schema as table '{1}'.
42X86 ALTER TABLE failed. There is no constraint '{0}' on table '{1}'.
42X87 At least one result expression (THEN or ELSE) of the '{0}' expression must not be a '?'.
42X88 A conditional has a non-Boolean operand. The operand of a conditional must evaluate to TRUE, FALSE, or UNKNOWN.
42X89 Types '{0}' and '{1}' are not type compatible. Neither type is assignable to the other type.
42X90 More than one primary key constraint specified for table '{0}'.
42X91 Constraint name '{0}' appears more than once in the CREATE TABLE statement.
42X92 Column name '{0}' appears more than once in a constraint's column list.
42X93 Table '{0}' contains a constraint definition with column '{1}' which is not in the table.
42X94 {0} '{1}' does not exist.
42X96 The database class path contains an unknown jar file '{0}'.
42X98 Parameters are not allowed in a VIEW definition.
42X99 Parameters are not allowed in a TABLE definition.
42Y00 Class '{0}' does not implement com.pivotal.gemfirexd.internal.iapi.db.AggregateDefinition and thus cannot be used as an aggregate expression.
42Y01 Constraint '{0}' is invalid.
42Y03 '{0}' is not recognized as a function or procedure.{1}
42Y04 Cannot create a procedure or function with EXTERNAL NAME '{0}' because it is not a list separated by periods. The expected format is <full java path>.<method name>.
42Y05 There is no Foreign Key named '{0}'.
42Y07 Schema '{0}' does not exist
42Y08 Foreign key constraints are not allowed on system tables.
42Y09 Void methods are only allowed within a CALL statement.
42Y10 A table constructor that is not in an INSERT statement has all ? parameters in one of its columns. For each column, at least one of the rows must have a non-parameter.
42Y11 A join specification is required with the '{0}' clause.
42Y12 The ON clause of a JOIN is a '{0}' expression. It must be a BOOLEAN expression.
42Y13 Column name '{0}' appears more than once in the CREATE VIEW statement.
42Y16 No public static method '{0}' was found in class '{1}'. The method might exist, but it is not public, or it is not static.
42Y22 Aggregate {0} cannot operate on type {1}.
42Y23 Incorrect JDBC type info returned for column {0}.
42Y24 View '{0}' is not updatable. (Views are currently not updatable.)
42Y25 '{0}' is a system table. Users are not allowed to modify the contents of this table.
42Y26 Aggregates are not allowed in the GROUP BY list.
42Y27 Parameters are not allowed in the trigger action.
42Y29 The SELECT list of a non-grouped query contains at least one invalid expression. When the SELECT list contains at least one aggregate then all entries must be valid aggregate expressions.
42Y30 The SELECT list of a grouped query contains at least one invalid expression. If a SELECT list has a GROUP BY, the list may only contain valid grouping expressions and valid aggregate expressions.
42Y32 Aggregator class '{0}' for aggregate '{1}' on type {2} does not implement com.ibm.db2j.aggregates.Aggregator.
42Y33 Aggregate {0} contains one or more aggregates.
42Y34 Column name '{0}' matches more than one result column in table '{1}'.
42Y35 Column reference '{0}' is invalid. When the SELECT list contains at least one aggregate then all entries must be valid aggregate expressions.
42Y36 Column reference '{0}' is invalid. For a SELECT list with a GROUP BY, the list may only contain valid grouping expressions and valid aggregate expressions.
42Y37 '{0}' is a Java primitive and cannot be used with this operator.
42Y38 insertMode = replace is not permitted on an insert where the target table, '{0}', is referenced in the SELECT.
42Y39 '{0}' may not appear in a CHECK CONSTRAINT definition because it may return non-deterministic results.
42Y40 '{0}' appears multiple times in the UPDATE OF column list for trigger '{1}'.
42Y41 '{0}' cannot be directly invoked via EXECUTE STATEMENT because it is part of a trigger.
42Y42 Scale '{1}' is not a valid scale for a {0}.
42Y43 Scale '{0}' is not a valid scale with precision of '{1}'.
42Y44 Invalid key '{0}' specified in the Properties list of a FROM list. The case-sensitive keys that are currently supported are '{1}'.
42Y45 VTI '{0}' cannot be bound because it is a special trigger VTI and this statement is not part of a trigger action or WHEN clause.
42Y46 Invalid Properties list in FROM list. There is no index '{0}' on table '{1}'.
42Y48 Invalid Properties list in FROM list. Either there is no named constraint '{0}' on table '{1}' or the constraint does not have a backing index.
42Y49 Multiple values specified for property key '{0}'.
42Y50 Properties list for table '{0}' may contain values for index or for constraint but not both.
42Y55 '{0}' cannot be performed on '{1}' because it does not exist.
42Y56 Invalid join strategy '{0}' specified in Properties list on table '{1}'. The currently supported values for a join strategy are: 'hash' and 'nestedloop'.
42Y58 NumberFormatException occurred when converting value '{0}' for optimizer override '{1}'.
42Y59 Invalid value, '{0}', specified for hashInitialCapacity override. Value must be greater than 0.
42Y60 Invalid value, '{0}', specified for hashLoadFactor override. Value must be greater than 0.0 and less than or equal to 1.0.
42Y61 Invalid value, '{0}', specified for hashMaxCapacity override. Value must be greater than 0.
42Y62 '{0}' is not allowed on '{1}' because it is a view.
42Y63 Hash join requires an optimizable equijoin predicate on a column in the selected index or heap. An optimizable equijoin predicate does not exist on any column in table or index '{0}'. Use the 'index' optimizer override to specify such an index or the heap on table '{1}'.
42Y64 bulkFetch value of '{0}' is invalid. The minimum value for bulkFetch is 1.
42Y65 bulkFetch is not permitted on '{0}' joins.
42Y66 bulkFetch is not permitted on updatable cursors.
42Y67 Schema '{0}' cannot be dropped.
42Y69 No valid execution plan was found for this statement. This may have one of two causes: either you specified a hash join strategy when hash join is not allowed (no optimizable equijoin) or you are attempting to join two external virtual tables, each of which references the other, and so the statement cannot be evaluated.
42Y70 The user specified an illegal join order. This could be caused by a join column from an inner table being passed as a parameter to an external virtual table.
42Y71 System function or procedure '{0}' cannot be dropped.
42Y82 System generated stored prepared statement '{0}' that cannot be dropped using DROP STATEMENT. It is part of a trigger.
42Y83 An untyped null is not permitted as an argument to aggregate {0}. Please cast the null to a suitable type.
42Y84 '{0}' may not appear in a DEFAULT definition.
42Y85 The DEFAULT keyword is only allowed in a VALUES clause when the VALUES clause appears within an INSERT statement.
42Y90 FOR UPDATE is not permitted in this type of statement.
42Y91 The USING clause is not permitted in an EXECUTE STATEMENT for a trigger action.
42Y92 {0} triggers may only reference {1} transition variables/tables.
42Y93 Illegal REFERENCING clause: only one name is permitted for each type of transition variable/table.
42Y94 An AND or OR has a non-boolean operand. The operands of AND and OR must evaluate to TRUE, FALSE, or UNKNOWN.
42Y95 The '{0}' operator with a left operand type of '{1}' and a right operand type of '{2}' is not supported.
42Y97 Invalid escape character at line '{0}', column '{1}'.
42Z02 Multiple DISTINCT aggregates are not supported at this time.
42Z07 Aggregates are not permitted in the ON clause.
42Z08 Bulk insert replace is not permitted on '{0}' because it has an enabled trigger ({1}).
42Z15 Invalid type specified for column '{0}'. The type of a column may not be changed.
42Z16 Only columns of type VARCHAR may have their length altered.
42Z17 Invalid length specified for column '{0}'. Length must be greater than the current column length.
42Z18 Column '{0}' is part of a foreign key constraint '{1}'. To alter the length of this column, you should drop the constraint first, perform the ALTER TABLE, and then recreate the constraint.
42Z19 Column '{0}' is being referenced by at least one foreign key constraint '{1}'. To alter the length of this column, you should drop referencing constraints, perform the ALTER TABLE and then recreate the constraints.
42Z20 Column '{0}' cannot be made nullable. It is part of a primary key or unique constraint, which cannot have any nullable columns.
42Z21 Invalid increment specified for identity for column '{0}'. Increment cannot be zero.
42Z22 Invalid type specified for identity column '{0}'. The only valid types for identity columns are BIGINT and INT.
42Z23 Attempt to modify an identity column '{0}'.
42Z24 Overflow occurred in identity value for column '{1}' in table '{0}'.
42Z25 INTERNAL ERROR identity counter. Update was called without arguments with current value \= NULL.
42Z26 A column, '{0}', with an identity default cannot be made nullable.
42Z27 A nullable column, '{0}', cannot be modified to have identity default.
42Z28 When GatewaySender is attached, only valid types for identity column {0} is BIGINT
42Z29 ALTER TABLE statement cannot add gatewaysender to a table {0} with int type identity column {1}. To add a gatewaysender to a table, identity column's datatype should be bigint
42Z50 INTERNAL ERROR: Unable to generate code for {0}.
42Z53 INTERNAL ERROR: Type of activation to generate for node choice {0} is unknown.
42Z60 {0} not allowed unless database property {1} has value '{2}'.
42Z70 Binding directly to an XML value is not allowed; try using XMLPARSE.
42Z71 XML values are not allowed in top-level result sets; try using XMLSERIALIZE.
42Z72 Missing SQL/XML keyword(s) '{0}' at line {1}, column {2}.
42Z73 Invalid target type for XMLSERIALIZE: '{0}'.
42Z74 XML feature not supported: '{0}'.
42Z75 XML query expression must be a string literal.
42Z76 Multiple XML context items are not allowed.
42Z77 Context item must have type 'XML'; '{0}' is not allowed.
42Z79 Unable to determine the parameter type for XMLPARSE; try using a CAST.
42Z90 Class '{0}' does not return an updatable ResultSet.
42Z91 subquery
42Z92 repeatable read
42Z93 Constraints '{0}' and '{1}' have the same set of columns, which is not allowed.
42Z97 Renaming column '{0}' will cause check constraint '{1}' to break.
42Z99 String or Hex literal cannot exceed 64K.
42Z9A read uncommitted
42Z9B The external virtual table interface does not support BLOB or CLOB columns. '{0}' column '{1}'.
42Z9D.S.1 Procedures that modify SQL data are not allowed in BEFORE triggers.
42Z9D '{0}' statements are not allowed in '{1}' triggers.
42Z9E Constraint '{0}' is not a {1} constraint.
42Z9F Too many indexes ({0}) on the table {1}. The limit is {2}.
42ZA0 Statement too complex. Try rewriting the query to remove complexity. Eliminating many duplicate expressions or breaking up the query and storing interim results in a temporary table can often help resolve this error.
42ZA1 Invalid SQL in Batch: '{0}'.
42ZA2 Operand of LIKE predicate with type {0} and collation {1} is not compatable with LIKE pattern operand with type {2} and collation {3}.
42ZA3 The table will have collation type {0} which is different than the collation of the schema {1} hence this operation is not supported .
42ZB1 Parameter style DERBY_JDBC_RESULT_SET is only allowed for table functions.
42ZB2 Table functions can only have parameter style DERBY_JDBC_RESULT_SET.
42ZB3 XML is not allowed as the datatype of a column returned by a table function.
42ZB4 '{0}'.{1}' does not identify a table function.
42ZB5 Class '{0}' implements VTICosting but does not provide a public, no-arg constructor.
Table 18. Class 57: DRDA Network Protocol: Execution Failure
SQLState Message text
57017.C There is no available conversion for the source code page, {0}, to the target code page, {1}. The connection has been terminated.
Table 19. Class 58: DRDA Network Protocol: Protocol Error
SQLState Message text
58009.C.10 Network protocol exception: only one of the VCM, VCS length can be greater than 0. The connection has been terminated.
58009.C.11 The connection was terminated because the encoding is not supported.
58009.C.12 Network protocol exception: actual code point, {0}, does not match expected code point, {1}. The connection has been terminated.
58009.C.13 Network protocol exception: DDM collection contains less than 4 bytes of data. The connection has been terminated.
58009.C.14 Network protocol exception: collection stack not empty at end of same id chain parse. The connection has been terminated.
58009.C.15 Network protocol exception: DSS length not 0 at end of same id chain parse. The connection has been terminated.
58009.C.16 Network protocol exception: DSS chained with same id at end of same id chain parse. The connection has been terminated.
58009.C.17 Network protocol exception: end of stream prematurely reached while reading InputStream, parameter #{0}. The connection has been terminated.
58009.C.18 Network protocol exception: invalid FDOCA LID. The connection has been terminated.
58009.C.19 Network protocol exception: SECTKN was not returned. The connection has been terminated.
58009.C.20 Network protocol exception: only one of NVCM, NVCS can be non-null. The connection has been terminated.
58009.C.21 Network protocol exception: SCLDTA length, {0}, is invalid for RDBNAM. The connection has been terminated.
58009.C.7 Network protocol exception: SCLDTA length, {0}, is invalid for RDBCOLID. The connection has been terminated.
58009.C.8 Network protocol exception: SCLDTA length, {0}, is invalid for PKGID. The connection has been terminated.
58009.C.9 Network protocol exception: PKGNAMCSN length, {0}, is invalid at SQLAM {1}. The connection has been terminated.
58010.C A network protocol error was encountered. A connection could not be established because the manager {0} at level {1} is not supported by the server.
58014.C The DDM command 0x{0} is not supported. The connection has been terminated.
58015.C The DDM object 0x{0} is not supported. The connection has been terminated.
58016.C The DDM parameter 0x{0} is not supported. The connection has been terminated.
58017.C The DDM parameter value 0x{0} is not supported. An input host variable may not be within the range the server supports. The connection has been terminated.
Table 20. Class X0: Execution exceptions
SQLState Message text
X0A00.S The select list mentions column '{0}' 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 '{0}' cannot be locked in '{1}' mode.
X0X03.S Invalid transaction state - held cursor requires same isolation level
X0X05.S Table/View '{0}' does not exist.
X0X07.S Cannot remove jar file '{0}' because it is on your gemfirexd.distributedsystem.classpath '{0}'.
X0X0D.S Invalid column array length '{0}'. To return generated keys, column array must be of length 1 and contain only the identity column.
X0X0E.S Table '{1}' does not have an auto-generated column at column position '{0}'.
X0X0F.S Table '{1}' does not have an auto-generated column named '{0}'.
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 '{0}' does not exist in schema '{1}'.
X0X57.S An attempt was made to put a Java value of type '{0}' 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 '{0}' already exists.
X0X61.S The values for column '{4}' in index '{0}' and table '{1}.{2}' do not match for row location {3}. The value in the index is '{5}', while the value in the base table is '{6}'. The full index key, including the row location, is '{7}'. The suggested corrective action is to recreate the index.
X0X62.S Inconsistency found between table '{0}' and index '{1}'. Error when trying to retrieve row location '{2}' from the table. The full index key, including the row location, is '{3}'. The suggested corrective action is to recreate the index.
X0X63.S Got IOException '{0}'.
X0X67.S Columns of type '{0}' 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 {0} '{1}' does not exist.
X0X85.S Index '{0}' was not created because '{1}' 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 '{0}' cannot be performed on object '{1}' because there is an open ResultSet dependent on that object.
X0X99.S Index '{0}' does not exist.
X0Y16.S '{0}' is not a view. If it is a table, then use DROP TABLE instead.
X0Y23.S Operation '{0}' cannot be performed on object '{1}' because VIEW '{2}' is dependent on that object.
X0Y24.S Operation '{0}' cannot be performed on object '{1}' because STATEMENT '{2}' is dependent on that object.
X0Y25.S Operation '{0}' cannot be performed on object '{1}' because {2} '{3}' is dependent on that object.
X0Y26.S Index '{0}' is required to be in the same schema as table '{1}'.
X0Y28.S Index '{0}' cannot be created on system table '{1}'. Users cannot create indexes on system tables.
X0Y29.S Operation '{0}' cannot be performed on object '{1}' because TABLE '{2}' is dependent on that object.
X0Y30.S Operation '{0}' cannot be performed on object '{1}' because ROUTINE '{2}' is dependent on that object.
X0Y32.S {0} '{1}' already exists in {2} '{3}'.
X0Y38.S Cannot create index '{0}' because table '{1}' does not exist.
X0Y41.S Constraint '{0}' is invalid because the referenced table {1} has no primary key. Either add a primary key to {1} or explicitly specify the columns of a unique constraint that this foreign key references.
X0Y42.S Constraint '{0}' is invalid: the types of the foreign key columns do not match the types of the referenced columns.
X0Y43.S Constraint '{0}' is invalid: the number of columns in {0} ({1}) does not match the number of columns in the referenced key ({2}).
X0Y44.S Constraint '{0}' is invalid: there is no unique or primary key constraint on table '{1}' that matches the number and types of the columns in the foreign key.
X0Y45.S Foreign key constraint '{0}' cannot be added to or enabled on table {1} because one or more foreign keys do not have matching referenced keys (failed keys: {2}).
X0Y46.S Constraint '{0}' is invalid: referenced table {1} does not exist.
X0Y54.S Schema '{0}' 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 '{0}' on table '{1}.{2}' has {3} rows, but the base table has {4} rows. The suggested corrective action is to recreate the index.
X0Y56.S '{0}' is not allowed on the System table '{1}'.
X0Y57.S A non-nullable column cannot be added to table '{0}' 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 '{0}' 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 '{1}' failed because the table contains {2} row(s) that violate the following check constraint(s): {0}.
X0Y63.S The command on table '{0}' 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.
X0Y66.S Cannot issue commit in a nested connection when there is a pending operation for '{0}' 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 {0} '{1}' already exists.
X0Y69.S {1} is not supported in trigger {0}.
X0Y70.S INSERT, UPDATE and DELETE are not permitted on table {1} because trigger {0} is active.
X0Y71.S Transaction manipulation such as SET ISOLATION is not permitted because trigger {0} is active.
X0Y72.S Bulk insert replace is not permitted on '{0}' because it has an enabled trigger ({1}).
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 {0}.executeQuery() cannot be called because multiple result sets were returned. Use {1}.execute() to obtain multiple results.
X0Y78.S.2 {0}.executeQuery() was called but no result set was returned. Use {1}.executeUpdate() for non-queries.
X0Y79.S Statement.executeUpdate() cannot be called with a statement that returns a ResultSet.
X0Y80.S ALTER table '{0}' failed. Null data found in column '{1}'.
X0Y83.S WARNING: While deleting a row from a table the index row for base table row {0} was not found in index with conglomerate id {1}. This problem has automatically been corrected as part of the delete operation.
X0Y90.S Table can be either partitioned or replicate
X0Y91.S Table '{0}' cannot be colocated with table '{1}' due to different number of colocation columns {2} and {3} respectively.
X0Y92.S Table '{0}' cannot be colocated with table '{1}' due to different column types; column of this table '{2}'[{3}], column of other table '{4}'[{5}].
X0Y93.S Table '{0}' cannot be colocated with table '{1}' due to different server groups '{2}' and '{3}' respectively.
X0Y94.S Table '{0}' cannot be colocated with table '{1}' due to different redundancies or buckets '{2}' and '{3}' respectively.
X0Y95.S Table '{0}' cannot be colocated with table '{1}' due to different partitioning policies '{2}' and '{3}' respectively.
X0Y96.S Table '{0}' cannot be colocated with table '{1}'.
X0Y97.S 'PARTITION BY PRIMARY KEY' for table '{0}' that has no primary key defined.
X0Y98.S Failed to drop table '{0}' due to colocated child tables. Reason '{1}'.
X0Y99.S Failed to create table '{0}' due to referenced table '{1}' having eviction or expiration policy.
X0Z01.S Node '{0}' went down or data no longer available while iterating the results (method '{1}'). Please retry the operation.
X0Z02.T Conflict detected in transaction operation and it will abort: {0}
X0Z03.T Transaction is in read-only mode due to a previous exception and cannot have update operations or be committed. Reason '{0}'.
X0Z04.S No data store node available in {0} to execute {1}
X0Z05.S Transactional data not colocated. Please retry with colocated data.
X0Z06.T In doubt transaction. Failure happened while committing transactional state. Please look at the cause of this exception for details and retry.
X0Z07.S Cannot find Disk Store with name '{0}'.
X0Z08.S No Datastore found in the Distributed System for '{0}'.
X0Z09.S Atleast one persistent datastore is no longer online.
X0Z10.S RowLoader returned invalid row with length {0}', expected '{1}'.
X0Z11.S Auto-generated column start '{0}' not supported for table '{1}'.
X0Z12.S Auto-generated column increment '{0}' not supported for table '{1}'.
X0Z13.S Overflow of generated key for table '{0}' with no primary key.
X0Z14.D DataDictionary has to be persistent when configuring table '{0}' with persistence.
X0Z15.S Table '{0}' is not partitioned for {1}.
X0Z16.T Transaction state is illegal. Reason: '{0}'.
X0Z17.S Provided class {0} does not implement the interface {1}.
X0Z18.S Bucket '{0}' of table '{1}' required for execution is not hosted locally anymore. Please retry the operation.
X0Z19.S Directory pointed to by location '{0}' appears more than once in the CREATE DISKSTORE statement
X0Z20.S Bucket '{0}' of table '{1}' has no primary host in the system. Please retry the operation.
X0Z21.S Specify one or more server groups on which AsyncEventListener/GatewaySender '{0}' can be configured.
X0Z22.S Exception occured during procedure execution for AsyncEventListener/GatewaySender '{0}': {1}.
X0Z23.S No AsyncEventListener/GatewaySender found '{0}'.
X0Z24.S Exception occured during procedure execution for Writer on table '{0}': {1}.
X0Z25.S Exception occured during procedure execution for Listener '{0}': {1}.
X0Z26.S Exception occured during procedure execution for Loader on table '{0}': {1}.
X0Z27.S An unexpected exception occured during procedure execution: {0}.
X0Z28.S Exception occured during procedure execution for Gateway Conflict Resolver: {0}.
X0Z29.S Custom eviction not enabled for table '{0}'.
X0Z30.S An error was received from HDFS while performing '{0}'.
X0Z32.S Member lost connection with the distributed system.
Table 21. Class XBCA: CacheService
SQLState Message text
XBCA0.S Cannot create new object with key {1} in {0} cache. The object already exists in the cache.
Table 22. Class XBCM: ClassManager
SQLState Message text
XBCM1.S Java linkage error thrown during load of generated class {0}.
XBCM2.S Cannot create an instance of generated class {0}.
XBCM3.S Method {1}() does not exist in generated class {0}.
XBCM4.S Java class file format limit(s) exceeded: {1} in generated class {0}.
Table 23. Class XBCX: Cryptography
SQLState Message text
XBCX0.S Exception from Cryptography provider. See next exception for details.
XBCX1.S Initializing cipher with illegal mode, must be either ENCRYPT or DECRYPT.
XBCX2.S Initializing cipher with a boot password that is too short. The password must be at least {0} characters long.
XBCX5.S Cannot change boot password to null.
XBCX6.S Cannot change boot password to a non-string serializable type.
XBCX7.S Wrong format for changing boot password. Format must be : old_boot_password, new_boot_password.
XBCX8.S Cannot change boot password for a non-encrypted database.
XBCX9.S Cannot change boot password for a read-only database.
XBCXA.S Wrong boot password.
XBCXB.S Bad encryption padding '{0}' or padding not specified. 'NoPadding' must be used.
XBCXC.S Encryption algorithm '{0}' does not exist. Please check that the chosen provider '{1}' supports this algorithm.
XBCXD.S The encryption algorithm cannot be changed after the database is created.
XBCXE.S The encryption provider cannot be changed after the database is created.
XBCXF.S The class '{0}' representing the encryption provider cannot be found.
XBCXG.S The encryption provider '{0}' does not exist.
XBCXH.S The encryptionAlgorithm '{0}' is not in the correct format. The correct format is algorithm/feedbackMode/NoPadding.
XBCXI.S The feedback mode '{0}' is not supported. Supported feedback modes are CBC, CFB, OFB and ECB.
XBCXJ.S The application is using a version of the Java Cryptography Extension (JCE) earlier than 1.2.1. Please upgrade to JCE 1.2.1 and try the operation again.
XBCXK.S The given encryption key does not match the encryption key used when creating the database. Please ensure that you are using the correct encryption key and try again.
XBCXL.S The verification process for the encryption key was not successful. This could have been caused by an error when accessing the appropriate file to do the verification process. See next exception for details.
XBCXM.S The length of the external encryption key must be an even number.
XBCXN.S The external encryption key contains one or more illegal characters. Allowed characters for a hexadecimal number are 0-9, a-f and A-F.
XBCXO.S Cannot encrypt the database when there is a global transaction in the prepared state.
XBCXP.S Cannot re-encrypt the database with a new boot password or an external encryption key when there is a global transaction in the prepared state.
XBCXQ.S Cannot configure a read-only database for encryption.
XBCXR.S Cannot re-encrypt a read-only database with a new boot password or an external encryption key .
XBCXS.S Cannot configure a database for encryption, when database is in the log archive mode.
XBCXT.S Cannot re-encrypt a database with a new boot password or an external encryption key, when database is in the log archive mode.
XBCXU.S Encryption of an un-encrypted database failed: {0}
XBCXV.S Encryption of an encrypted database with a new key or a new password failed: {0}
Table 24. Class XBM: Monitor
SQLState Message text
XBM01.D Startup failed due to an exception. See next exception for details.
XBM02.D Startup failed due to missing functionality for {0}. Please ensure your classpath includes the correct GemFireXD software.
XBM05.D Startup failed due to missing product version information for {0}.
XBM06.D Startup failed. An encrypted database cannot be accessed without the correct boot password.
XBM07.D Startup failed. Boot password must be at least 8 bytes long.
XBM08.D Could not instantiate {0} StorageFactory class {1}.
XBM09.D Start failed due to a suspect event during startup. Please re-start.
XBM0G.D Failed to start encryption engine. Please make sure you are running Java 2 and have downloaded an encryption provider such as jce and put it in your class path.
XBM0H.D Directory {0} cannot be created.
XBM0I.D Directory {0} cannot be removed.
XBM0J.D Directory {0} already exists.
XBM0K.D Unknown sub-protocol for database name {0}.
XBM0L.D Specified authentication scheme class {0} does implement the authentication interface {1}.
XBM0M.D Error creating instance of authentication scheme class {0}.
XBM0N.D JDBC Driver registration with java.sql.DriverManager failed. See next exception for details.
XBM0O.D JDBC Driver already registered with java.sql.DriverManager before Authentication settings provided in FabricService.
XBM0P.D Service provider is read-only. Operation not permitted.
XBM0Q.D File {0} not found. Please make sure that backup copy is the correct one and it is not corrupted.
XBM0R.D Unable to remove File {0}.
XBM0S.D Unable to rename file '{0}' to '{1}'
XBM0T.D Ambiguous sub-protocol for database name {0}.
XBM0U.S No class was registered for identifier {0}.
XBM0V.S An exception was thrown while loading class {1} registered for identifier {0}.
XBM0W.S An exception was thrown while creating an instance of class {1} registered for identifier {0}.
XBM0X.D Supplied territory description '{0}' is invalid, expecting ln[_CO[_variant]] ln=lower-case two-letter ISO-639 language code, CO=upper-case two-letter ISO-3166 country codes, see java.util.Locale.
XBM03.D Supplied value '{0}' for collation attribute is invalid, expecting UCS_BASIC or TERRITORY_BASED.
XBM04.D Collator support not available from the JVM for the database's locale '{0}'.
XBM0Y.D Backup database directory {0} not found. Please make sure that the specified backup path is right.
XBM0Z.D Unable to copy file '{0}' to '{1}'. Please make sure that there is enough space and permissions are correct.
Table 25. Class XCL: Execution exceptions
SQLState Message text
XCL01.S Result set does not return rows. Operation {0} not permitted.
XCL05.S Activation closed, operation {0} not permitted.
XCL07.S Cursor '{0}' is closed. Verify that autocommit is OFF.
XCL08.S Cursor '{0}' is not on a row.
XCL09.S An Activation was passed to the '{0}' method that does not match the PreparedStatement.
XCL10.S A PreparedStatement has been recompiled and the parameters have changed. If you are using JDBC you must prepare the statement again.
XCL12.S An attempt was made to put a data value of type '{0}' into a data value of type '{1}' for column '{2}'.
XCL13.S The parameter position '{0}' is out of range. The number of parameters for this prepared statement is '{1}'.
XCL14.S The column position '{0}' is out of range. The number of columns for this ResultSet is '{1}'.
XCL15.S A ClassCastException occurred when calling the compareTo() method on an object '{0}'. The parameter to compareTo() is of class '{1}'.
XCL16.S.0 ResultSet not open. Operation '{0}' not permitted. Verify that autocommit is OFF.
XCL16.S.1 ResultSet not open. Verify that autocommit is OFF.
XCL17.S Statement not allowed in this database.
XCL18.S Stream of column value in result cannot be retrieved twice
XCL19.S Missing row in table '{0}' for key '{1}'.
XCL20.S Catalogs at version level '{0}' cannot be upgraded to version level '{1}'.
XCL21.S You are trying to execute a Data Definition statement (CREATE, DROP, or ALTER) while preparing a different statement. This is not allowed. It can happen if you execute a Data Definition statement from within a static initializer of a Java class that is being used from within a SQL statement.
XCL22.S Parameter {0} cannot be registered as an OUT parameter because it is an IN parameter.
XCL23.S SQL type number '{0}' is not a supported type by registerOutParameter().
XCL24.S Parameter {0} appears to be an output parameter, but it has not been so designated by registerOutParameter(). If it is not an output parameter, then it has to be set to type {1}.
XCL25.S Parameter {0} cannot be registered to be of type {1} because it maps to type {2} and they are incompatible.
XCL26.S Parameter {0} is not an output parameter.
XCL27.S Return output parameters cannot be set.
XCL30.S An IOException was thrown when reading a '{0}' from an InputStream.
XCL31.S Statement closed.
XCL33.S The table cannot be defined as a dependent of table {0} because of delete rule restrictions. (The relationship is self-referencing and a self-referencing relationship already exists with the SET NULL delete rule.)
XCL34.S The table cannot be defined as a dependent of table {0} because of delete rule restrictions. (The relationship forms a cycle of two or more tables that cause the table to be delete-connected to itself (all other delete rules in the cycle would be CASCADE)).
XCL35.S The table cannot be defined as a dependent of table {0} because of delete rule restrictions. (The relationship causes the table to be delete-connected to the indicated table through multiple relationships and the delete rule of the existing relationship is SET NULL.).
XCL36.S The delete rule of foreign key must be {0}. (The referential constraint is self-referencing and an existing self-referencing constraint has the indicated delete rule (NO ACTION, RESTRICT or CASCADE).)
XCL37.S The delete rule of foreign key must be {0}. (The referential constraint is self-referencing and the table is dependent in a relationship with a delete rule of CASCADE.)
XCL38.S the delete rule of foreign key must be {0}. (The relationship would cause the table to be delete-connected to the same table through multiple relationships and such relationships must have the same delete rule (NO ACTION, RESTRICT or CASCADE).)
XCL39.S The delete rule of foreign key cannot be CASCADE. (A self-referencing constraint exists with a delete rule of SET NULL, NO ACTION or RESTRICT.)
XCL40.S The delete rule of foreign key cannot be CASCADE. (The relationship would form a cycle that would cause a table to be delete-connected to itself. One of the existing delete rules in the cycle is not CASCADE, so this relationship may be definable if the delete rule is not CASCADE.)
XCL41.S the delete rule of foreign key can not be CASCADE. (The relationship would cause another table to be delete-connected to the same table through multiple paths with different delete rules or with delete rule equal to SET NULL.)
XCL42.S CASCADE
XCL43.S SET NULL
XCL44.S RESTRICT
XCL45.S NO ACTION
XCL46.S SET DEFAULT
XCL47.S Use of '{0}' requires database to be upgraded from version {1} to version {2} or later.
XCL48.S TRUNCATE TABLE is not permitted on '{0}' because unique/primary key constraints on this table are referenced by enabled foreign key constraints from {1} which is not empty.
XCL49.S TRUNCATE TABLE is not permitted on '{0}' because it has an enabled DELETE trigger ({1}).
XCL50.S Upgrading the database from a previous version is not supported. The database being accessed is at version level '{0}', this software is at version level '{1}'.
XCL51.S The requested function can not reference tables in SESSION schema.
XCL52.S The statement has been cancelled or timed out.
XCL53 Stream is closed
XCL54 Query/DML/DDL '{0}' canceled due to low memory on member '{1}'. Try reducing the search space by adding more filter conditions to the where clause.
Table 26. Class XCW: Upgrade unsupported
SQLState Message text
XCW00.D Unsupported upgrade from '{0}' to '{1}'.
Table 27. Class XCX: Internal Utility Errors
SQLState Message text
XCXA0.S Invalid identifier.
XCXB0.S Invalid database classpath: '{0}'.
XCXC0.S Invalid id list.
XCXE0.S You are trying to do an operation that uses the territory of the database, but the database does not have a territory.
Table 28. Class XCY: GemFire XD Property Exceptions
SQLState Message text
XCY00.S Invalid value for property '{0}'='{1}'.
XCY02.S The requested property change is not supported '{0}'='{1}'.
XCY03.S Required property '{0}' has not been set.
XCY04.S Invalid syntax for optimizer overrides. The syntax should be -- GEMFIREXD-PROPERTIES propertyName = value [, propertyName = value]*
Table 29. Class XCZ: com.pivotal.gemfirexd.internal.database.UserUtility
SQLState Message text
XCZ00.S Unknown permission '{0}'.
XCZ01.S Unknown user '{0}'.
XCZ02.S Invalid parameter '{0}'='{1}'.
Table 30. Class XD00: Dependency Manager
SQLState Message text
XD003.S Unable to restore dependency from disk. DependableFinder = '{0}'. Further information: '{1}'.
XD004.S Unable to store dependencies.
Table 31. Class XIE: Import/Export Exceptions
SQLState Message text
XIE01.S Connection was null.
XIE03.S Data found on line {0} for column {1} after the stop delimiter.
XIE04.S Data file not found: {0}
XIE05.S Data file cannot be null.
XIE06.S Entity name was null.
XIE07.S Field and record separators cannot be substrings of each other.
XIE08.S There is no column named: {0}.
XIE09.S The total number of columns in the row is: {0}.
XIE0B.S Column '{0}' in the table is of type {1}, it is not supported by the import/export feature.
XIE0D.S Cannot find the record separator on line {0}.
XIE0E.S Read endOfFile at unexpected place on line {0}.
XIE0I.S An IOException occurred while writing data to the file.
XIE0J.S A delimiter is not valid or is used more than once.
XIE0K.S The period was specified as a character string delimiter.
XIE0M.S Table '{0}' does not exist.
XIE0N.S An invalid hexadecimal string '{0}' detected in the import file at line {1} column {2}.
XIE0P.S Lob data file {0} referenced in the import file not found.
XIE0Q.S Lob data file name cannot be null.
XIE0R.S Import error on line {0} of file {1}: {2}
XIE0S.S The export operation was not performed, because the specified output file ({0}) already exists. Export processing will not overwrite an existing file, even if the process has permissions to write to that file, due to security concerns, and to avoid accidental file damage. Please either change the output file name in the export procedure arguments to specify a file which does not exist, or delete the existing file, then retry the export operation.
XIE0T.S The export operation was not performed, because the specified large object auxiliary file ({0}) already exists. Export processing will not overwrite an existing file, even if the process has permissions to write to that file, due to security concerns, and to avoid accidental file damage. Please either change the large object auxiliary file name in the export procedure arguments to specify a file which does not exist, or delete the existing file, then retry the export operation.
Table 32. Class XJ: Connectivity Errors
SQLState Message text
XJ004.C Database '{0}' not found.
XJ008.S Cannot rollback or release a savepoint when in auto-commit mode.
XJ009.S Use of CallableStatement required for stored procedure call or use of output parameters: {0}
XJ010.S Cannot issue savepoint when autoCommit is on.
XJ011.S Cannot pass null for savepoint name.
XJ012.S '{0}' already closed.
XJ013.S No ID for named savepoints.
XJ014.S No name for un-named savepoints.
XJ015.M GemFireXD system shutdown.
XJ016.S Method '{0}' not allowed on prepared statement.
XJ017.S No savepoint command allowed inside the trigger code.
XJ018.S Column name cannot be null.
XJ020.S Object type not convertible to TYPE '{0}', invalid java.sql.Types value, or object was null.
XJ021.S Type is not supported.
XJ022.S Unable to set stream: '{0}'.
XJ023.S Input stream did not have exact amount of data as the requested length.
XJ025.S Input stream cannot have negative length.
XJ028.C The URL '{0}' is not properly formed.
XJ030.S Cannot set AUTOCOMMIT ON when in a nested connection.
XJ040.C Failed to start database '{0}', see the cause for details.
XJ041.C Failed to create database '{0}', see the cause for details.
XJ042.S '{0}' is not a valid value for property '{1}'.
XJ044.S '{0}' is an invalid scale.
XJ045.S Invalid or (currently) unsupported isolation level, '{0}', passed to Connection.setTransactionIsolation(). The currently supported values are java.sql.Connection.TRANSACTION_NONE, java.sql.Connection.TRANSACTION_READ_UNCOMMITTED, java.sql.Connection.TRANSACTION_READ_COMMITTED and java.sql.Connection.TRANSACTION_REPEATABLE_READ.
XJ049.C Conflicting create attributes specified.
XJ04B.S Batch cannot contain a command that attempts to return a result set.
XJ04C.S CallableStatement batch cannot contain output parameters.
XJ056.S Cannot set AUTOCOMMIT ON when in an XA connection.
XJ057.S Cannot commit a global transaction using the Connection, commit processing must go thru XAResource interface.
XJ058.S Cannot rollback a global transaction using the Connection, commit processing must go thru XAResource interface.
XJ059.S Cannot close a connection while a global transaction is still active.
XJ05B.C JDBC attribute '{0}' has an invalid value '{1}', valid values are '{2}'.
XJ05C.S Cannot set holdability ResultSet.HOLD_CURSORS_OVER_COMMIT for a global transaction.
XJ061.S The '{0}' method is only allowed on scroll cursors.
XJ062.S Invalid parameter value '{0}' for ResultSet.setFetchSize(int rows).
XJ063.S Invalid parameter value '{0}' for Statement.setMaxRows(int maxRows). Parameter value must be >= 0.
XJ064.S Invalid parameter value '{0}' for setFetchDirection(int direction).
XJ065.S Invalid parameter value '{0}' for Statement.setFetchSize(int rows).
XJ066.S Invalid parameter value '{0}' for Statement.setMaxFieldSize(int max).
XJ067.S SQL text pointer is null.
XJ068.S Only executeBatch and clearBatch allowed in the middle of a batch.
XJ069.S No SetXXX methods allowed in case of USING execute statement.
XJ070.S Negative or zero position argument '{0}' passed in a Blob or Clob method.
XJ071.S Negative length argument '{0}' passed in a BLOB or CLOB method.
XJ072.S Null pattern or searchStr passed in to a BLOB or CLOB position method.
XJ073.S The data in this BLOB or CLOB is no longer available. The BLOB/CLOB's transaction may be committed, or its connection is closed.
XJ074.S Invalid parameter value '{0}' for Statement.setQueryTimeout(int seconds).
XJ076.S The position argument '{0}' exceeds the size of the BLOB/CLOB.
XJ077.S Got an exception when trying to read the first byte/character of the BLOB/CLOB pattern using getBytes/getSubString.
XJ078.S Offset '{0}' is either less than zero or is too large for the current BLOB/CLOB.
XJ079.S The length specified '{0}' exceeds the size of the BLOB/BLOB.
XJ080.S USING execute statement passed {0} parameters rather than {1}.
XJ081.C Conflicting create/restore/recovery attributes specified.
XJ081.S Invalid value '{0}' passed as parameter '{1}' to method '{2}'
XJ085.S Stream has already been read and end-of-file reached and cannot be re-used.
XJ086.S This method cannot be invoked while the cursor is not on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
XJ087.S Sum of position('{0}') and length('{1}') is greater than the size of the LOB.
XJ088.S Invalid operation: wasNull() called with no data retrieved.
XJ090.S Invalid parameter: calendar is null.
XJ091.S Invalid argument: parameter index {0} is not an OUT or INOUT parameter.
XJ093.S Length of BLOB/CLOB, {0}, is too large. The length cannot exceed {1}.
XJ094.S This object is already closed.
XJ095.S An attempt to execute a privileged action failed.
XJ096.S A resource bundle could not be found in the {0} package for {1}
XJ097.S Cannot rollback or release a savepoint that was not created by this connection.
XJ098.S The auto-generated keys value {0} is invalid
XJ099.S The Reader/Stream object does not contain length characters
XJ100.S The scale supplied by the registerOutParameter method does not match with the setter method. Possible loss of precision!
XJ102.S Can not perform an insert at the current position.
XJ103.S Table name can not be null
XJ104.S Shared key length is invalid: {0}.
XJ105.S DES key has the wrong length, expected length {0}, got length {1}.
XJ106.S No such padding
XJ107.S Bad Padding
XJ108.S Illegal Block Size
XJ110.S Primary table name can not be null
XJ111.S Foreign table name can not be null
XJ112.S Security exception encountered, see next exception for details.
XJ113.S Unable to open file {0} : {1}
XJ114.S Invalid cursor name '{0}'
XJ115.S Unable to open resultSet with requested holdability {0}.
XJ116.S No more than {0} commands may be added to a single batch.
XJ117.S Batching of queries not allowed by J2EE compliance.
XJ118.S Query batch requested on a non-query statement.
XJ121.S Invalid operation at current cursor position.
XJ122.S No updateXXX methods were called on this row.
XJ123.S This method must be called to update values in the current row or the insert row.
XJ124.S Column not updatable.
XJ125.S This method should only be called on ResultSet objects that are scrollable (type TYPE_SCROLL_INSENSITIVE).
XJ126.S This method should not be called on sensitive dynamic cursors.
XJ128.S Unable to unwrap for '{0}'
XJ200.S Exceeded maximum number of sections {0}
XJ202.S Invalid cursor name '{0}'.
XJ203.S Cursor name '{0}' is already in use
XJ204.S Unable to open result set with requested holdability {0}.
XJ206.S SQL text '{0}' has no tokens.
XJ207.S executeQuery method can not be used for update.
XJ208.S Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.
XJ209.S The required stored procedure is not installed on the server.
XJ210.S The load module name for the stored procedure on the server is not found.
XJ211.S Non-recoverable chain-breaking exception occurred during batch processing. The batch is terminated non-atomically.
XJ212.S Invalid attribute syntax: {0}
XJ213.C The traceLevel connection property does not have a valid format for a number.
XJ214.S An IO Error occurred when calling free() on a CLOB or BLOB.
XJ215.S You cannot invoke other java.sql.Clob/java.sql.Blob methods after calling the free() method or after the Blob/Clob's transaction has been committed or rolled back.
XJ216.S The length of this BLOB/CLOB is not available yet. When a BLOB or CLOB is accessed as a stream, the length is not available until the entire stream has been processed.
XJ217.S The locator that was supplied for this CLOB/BLOB is invalid
Table 33. Class XK: Security Exceptions
SQLState Message text
XK000.S The security policy could not be reloaded: {0}
Table 34. Class XN: Network Client Exceptions
SQLState Message text
XN001.S Connection reset is not allowed when inside a unit of work.
XN008.S Query processing has been terminated due to an error on the server.
XN009.S Error obtaining length of BLOB/CLOB object, exception follows.
XN010.S Procedure name can not be null.
XN011.S Procedure name length {0} is not within the valid range of 1 to {1}.
XN012.S On {0} platforms, XA supports version {1} and above, this is version {2}
XN013.S Invalid scroll orientation.
XN014.S Network protocol error: encountered an IOException, parameter #{0}. Remaining data has been padded with 0x0. Message: {1}.
XN015.S Network protocol error: the specified size of the InputStream, parameter #{0}, is less than the actual InputStream length.
XN016.S Network protocol error: encountered error in stream length verification, parameter #{0}. Message: {1}.
XN017.S Network protocol error: end of stream prematurely reached, parameter #{0}. Remaining data has been padded with 0x0.
XN018.S Network protocol error: the specified size of the Reader, parameter #{0}, is less than the actual InputStream length.
XN019.S Error executing a {0}, server returned {1}.
XN020.S Error marshalling or unmarshalling a user defined type: {0}
XN021.S An object of type {0} cannot be cast to an object of type {1}.
Table 35. Class XRE: Replication Exceptions
SQLState Message text
XRE00 This LogFactory module does not support replicatiosn.
XRE01 The log received from the master is corrupted.
XRE02 Master and Slave at different versions. Unable to proceed with Replication.
XRE03 Unexpected replication error. See gemfirexd.log for details.
XRE04.U.1 Could not establish a connection to the peer of the replicated database '{0}' on address '{1}:{2}'.
XRE04.U.2 Connection lost for replicated database '{0}'.
XRE05 The log files on the master and slave are not in synch for replicated database '{0}'. The master log instant is {1}:{2}, whereas the slave log instant is {3}:{4}. This is FATAL for replication - replication will be stopped.
XRE06 The connection attempts to the replication slave for the database {0} exceeded the specified timeout period.
XRE07 Could not perform operation because the database is not in replication master mode.
XRE08 Replication slave mode started successfully for database '{0}'. Connection refused because the database is in replication slave mode.
XRE09 Cannot start replication slave mode for database '{0}'. The database has already been booted.
XRE10 Conflicting attributes specified. See reference manual for attributes allowed in combination with replication attribute '{0}'.
XRE11 Could not perform operation '{0}' because the database '{1}' has not been booted.
XRE12 Replication network protocol error for database '{0}'. Expected message type '{1}', but received type '{2}'.
XRE20.D Failover performed successfully for database '{0}', the database has been shutdown.
XRE21 Error occurred while performing failover for database '{0}', Failover attempt was aborted.
XRE22 Replication master has already been booted for database '{0}'
XRE23 Replication master cannot be started since unlogged operations are in progress, unfreeze to allow unlogged operations to complete and restart replication
XRE40 Could not perform operation because the database is not in replication slave mode.
XRE41 Replication operation 'failover' or 'stopSlave' refused on the slave database because the connection with the master is working. Issue the 'failover' or 'stopMaster' operation on the master database instead.
XRE42 Replicated database '{0}' shutdown.
XRE43 Unexpected error when trying to stop replication slave mode. To stop repliation slave mode, use operation 'stopSlave' or 'failover'.
Table 36. Class XSAI: Store - access.protocol.interface
SQLState Message text
XSAI2.S The conglomerate ({0}) requested does not exist.
XSAI3.S Feature not implemented.
Table 37. Class XSAM: Store - AccessManager
SQLState Message text
XSAM0.S Exception encountered while trying to boot module for '{0}'.
XSAM2.S There is no index or conglomerate with conglom id '{0}' to drop.
XSAM3.S There is no index or conglomerate with conglom id '{0}'.
XSAM4.S There is no sort called '{0}'.
XSAM5.S Scan must be opened and positioned by calling next() before making other calls.
XSAM6.S Record {2} on page {1} in container {0} not found.
Table 38. Class XSAS: Store - Sort
SQLState Message text
XSAS0.S A scan controller interface method was called which is not appropriate for a scan on a sort.
XSAS1.S An attempt was made to fetch a row before the beginning of a sort or after the end of a sort.
XSAS3.S The type of a row inserted into a sort does not match the sort's template.
XSAS6.S Could not acquire resources for sort.
Table 39. Class XSAX: Store - access.protocol.XA statement
SQLState Message text
XSAX0.S XA protocol violation.
XSAX1.S An attempt was made to start a global transaction with an Xid of an existing global transaction.
Table 40. Class XSCB: Store - BTree
SQLState Message text
XSCB0.S Could not create container.
XSCB1.S Container {0} not found.
XSCB2.S The required property {0} not found in the property list given to createConglomerate() for a btree secondary index.
XSCB3.S Unimplemented feature.
XSCB4.S A method on a btree open scan has been called prior to positioning the scan on the first row (i.e. no next() call has been made yet). The current state of the scan is ({0}).
XSCB5.S During logical undo of a btree insert or delete the row could not be found in the tree.
XSCB6.S Limitation: Record of a btree secondary index cannot be updated or inserted due to lack of space on the page. Use the parameters gemfirexd.storage.pageSize and/or gemfirexd.storage.pageReservedSpace to work around this limitation.
XSCB7.S An internal error was encountered during a btree scan - current_rh is null = {0}, position key is null = {1}.
XSCB8.S The btree conglomerate {0} is closed.
XSCB9.S Reserved for testing.
Table 41. Class XSCG0: Conglomerate
SQLState Message text
XSCG0.S Could not create a template.
Table 42. Class XSCH: Heap
SQLState Message text
XSCH0.S Could not create container.
XSCH1.S Container {0} not found.
XSCH4.S Conglomerate could not be created.
XSCH5.S In a base table there was a mismatch between the requested column number {0} and the maximum number of columns {1}.
XSCH6.S The heap container with container id {0} is closed.
XSCH7.S The scan is not positioned.
XSCH8.S The feature is not implemented.
Table 43. Class XSDA: RawStore - Data.Generic statement
SQLState Message text
XSDA1.S An attempt was made to access an out of range slot on a page
XSDA2.S An attempt was made to update a deleted record
XSDA3.S Limitation: Record cannot be updated or inserted due to lack of space on the page. Use the parameters gemfirexd.storage.pageSize and/or gemfirexd.storage.pageReservedSpace to work around this limitation.
XSDA4.S An unexpected exception was thrown
XSDA5.S An attempt was made to undelete a record that is not deleted
XSDA6.S Column {0} of row is null, it needs to be set to point to an object.
XSDA7.S Restore of a serializable or SQLData object of class {0}, attempted to read more data than was originally stored
XSDA8.S Exception during restore of a serializable or SQLData object of class {0}
XSDA9.S Class not found during restore of a serializable or SQLData object of class {0}
XSDAA.S Illegal time stamp {0}, either time stamp is from a different page or of incompatible implementation
XSDAB.S cannot set a null time stamp
XSDAC.S Attempt to move either rows or pages from one container to another.
XSDAD.S Attempt to move zero rows from one page to another.
XSDAE.S Can only make a record handle for special record handle id.
XSDAF.S Using special record handle as if it were a normal record handle.
XSDAG.S The allocation nested top transaction cannot open the container.
XSDAI.S Page {0} being removed is already locked for deallocation.
XSDAJ.S Exception during write of a serializable or SQLData object
XSDAK.S Wrong page is gotten for record handle {0}.
XSDAL.S Record handle {0} unexpectedly points to overflow page.
XSDAM.S Exception during restore of a SQLData object of class {0}. The specified class cannot be instantiated.
XSDAN.S Exception during restore of a SQLData object of class {0}. The specified class encountered an illegal access exception.
Table 44. Class XSDB: RawStore - Data.Generic transaction
SQLState Message text
XSDB0.D Unexpected exception on in-memory page {0}
XSDB1.D Unknown page format at page {0}
XSDB2.D Unknown container format at container {0} : {1}
XSDB3.D Container information cannot change once written: was {0}, now {1}
XSDB4.D Page {0} is at version {1}, the log file contains change version {2}, either there are log records of this page missing, or this page did not get written out to disk properly.
XSDB5.D Log has change record on page {0}, which is beyond the end of the container.
XSDB6.D Another instance of GemFireXD may have already booted the database {0}.
XSDB7.D WARNING: GemFireXD (instance {0}) is attempting to boot the database {1} even though GemFireXD (instance {2}) may still be active. Only one instance of GemFireXD should boot a database at a time. Severe and non-recoverable corruption can result and may have already occurred.
XSDB8.D WARNING: GemFireXD (instance {0}) is attempting to boot the database {1} even though GemFireXD (instance {2}) may still be active. Only one instance of GemFireXD should boot a database at a time. Severe and non-recoverable corruption can result if 2 instances of GemFireXD boot on the same database at the same time. The db2j.database.forceDatabaseLock=true property has been set, so the database will not boot until the db.lck is no longer present. Normally this file is removed when the first instance of GemFireXD to boot on the database exits, but it may be left behind in some shutdowns. It will be necessary to remove the file by hand in that case. It is important to verify that no other VM is accessing the database before deleting the db.lck file by hand.
XSDB9.D Stream container {0} is corrupt.
XSDBA.D Attempt to allocate object {0} failed.
XSDBB.D Unknown page format at page {0}, page dump follows: {1}
Table 45. Class XSDF: RawStore - Data.Filesystem statement
SQLState Message text
XSDF0.S Could not create file {0} as it already exists.
XSDF1.S Exception during creation of file {0} for container
XSDF2.S Exception during creation of file {0} for container, file could not be removed. The exception was: {1}.
XSDF3.S Cannot create segment {0}.
XSDF4.S Exception during remove of file {0} for dropped container, file could not be removed {1}.
XSDF6.S Cannot find the allocation page {0}.
XSDF7.S Newly created page failed to be latched {0}
XSDF8.S Cannot find page {0} to reuse.
XSDFB.S Operation not supported by a read only database
XSDFD.S Different page image read on 2 I/Os on Page {0}, first image has incorrect checksum, second image has correct checksum. Page images follows: {1} {2}
XSDFF.S The requested operation failed due to an unexpected exception.
XSDFH.S Cannot backup the database, got an I/O Exception while writing to the backup container file {0}.
XSDFI.S Error encountered while trying to write data to disk during database recovery. Check that the database disk is not full. If it is then delete unnecessary files, and retry connecting to the database. It is also possible that the file system is read only, or the disk has failed, or some other problem with the media. System encountered error while processing page {0}.
Table 46. Class XSDG: RawStore - Data.Filesystem database
SQLState Message text
XSDG0.D Page {0} could not be read from disk.
XSDG1.D Page {0} could not be written to disk, please check if the disk is full, or if a file system limit, such as a quota or a maximum file size, has been reached.
XSDG2.D Invalid checksum on Page {0}, expected={1}, on-disk version={2}, page dump follows: {3}
XSDG3.D Meta-data for Container {0} could not be accessed
XSDG5.D Database is not in create mode when createFinished is called.
XSDG6.D Data segment directory not found in {0} backup during restore. Please make sure that backup copy is the right one and it is not corrupted.
XSDG7.D Directory {0} could not be removed during restore. Please make sure that permissions are correct.
XSDG8.D Unable to copy directory '{0}' to '{1}' during restore. Please make sure that there is enough space and permissions are correct.
Table 47. Class XSLA: RawStore - Log.Generic database exceptions
SQLState Message text
XSLA0.D Cannot flush the log file to disk {0}.
XSLA1.D Log Record has been sent to the stream, but it cannot be applied to the store (Object {0}). This may cause recovery problems also.
XSLA2.D System will shutdown, got I/O Exception while accessing log file.
XSLA3.D Log Corrupted, has invalid data in the log stream.
XSLA4.D Cannot write to the log, most likely the log is full. Please delete unnecessary files. It is also possible that the file system is read only, or the disk has failed, or some other problems with the media.
XSLA5.D Cannot read log stream for some reason to rollback transaction {0}.
XSLA6.D Cannot recover the database.
XSLA7.D Cannot redo operation {0} in the log.
XSLA8.D Cannot rollback transaction {0}, trying to compensate {1} operation with {2}
XSLAA.D The store has been marked for shutdown by an earlier exception.
XSLAB.D Cannot find log file {0}, please make sure your logDevice property is properly set with the correct path separator for your platform.
XSLAC.D Database at {0} have incompatible format with the current version of software, it may have been created by or upgraded by a later version.
XSLAD.D log Record at instant {2} in log file {3} corrupted. Expected log record length {0}, real length {1}.
XSLAE.D Control file at {0} cannot be written or updated.
XSLAF.D A Read Only database was created with dirty data buffers.
XSLAH.D A Read Only database is being updated.
XSLAI.D Cannot log the checkpoint log record
XSLAJ.D The logging system has been marked to shut down due to an earlier problem and will not allow any more operations until the system shuts down and restarts.
XSLAK.D Database has exceeded largest log file number {0}.
XSLAL.D log record size {2} exceeded the maximum allowable log file size {3}. Error encountered in log file {0}, position {1}.
XSLAM.D Cannot verify database format at {1} due to IOException.
XSLAN.D Database at {0} has an incompatible format with the current version of the software. The database was created by or upgraded by version {1}.
XSLAO.D Recovery failed unexpected problem {0}.
XSLAP.D Database at {0} is at version {1}. Beta databases cannot be upgraded,
XSLAQ.D cannot create log file at directory {0}.
XSLAR.D Unable to copy log file '{0}' to '{1}' during restore. Please make sure that there is enough space and permissions are correct.
XSLAS.D Log directory {0} not found in backup during restore. Please make sure that backup copy is the correct one and it is not corrupted.
XSLAT.D The log directory '{0}' exists. The directory might belong to another database. Check that the location specified for the logDevice attribute is correct.
Table 48. Class XSLB: RawStore - Log.Generic statement exceptions
SQLState Message text
XSLB1.S Log operation {0} encounters error writing itself out to the log stream, this could be caused by an errant log operation or internal log buffer full due to excessively large log operation.
XSLB2.S Log operation {0} logging excessive data, it filled up the internal log buffer.
XSLB4.S Cannot find truncationLWM {0}.
XSLB5.S Illegal truncationLWM instant {1} for truncation point {0}. Legal range is from {2} to {3}.
XSLB6.S Trying to log a 0 or -ve length log Record.
XSLB8.S Trying to reset a scan to {0}, beyond its limit of {1}.
XSLB9.S Cannot issue any more change, log factory has been stopped.
Table 49. Class XSRS: RawStore - protocol.Interface statement
SQLState Message text
XSRS0.S Cannot freeze the database after it is already frozen.
XSRS1.S Cannot backup the database to {0}, which is not a directory.
XSRS4.S Error renaming file (during backup) from {0} to {1}.
XSRS5.S Error copying file (during backup) from {0} to {1}.
XSRS6.S Cannot create backup directory {0}.
XSRS7.S Backup caught unexpected exception.
XSRS8.S Log Device can only be set during database creation time, it cannot be changed on the fly.
XSRS9.S Record {0} no longer exists
XSRSA.S Cannot backup the database when unlogged operations are uncommitted. Please commit the transactions with backup blocking operations.
XSRSB.S Backup cannot be performed in a transaction with uncommitted unlogged operations.
XSRSC.S Cannot backup the database to {0}, it is a database directory.
Table 50. Class XSTA2: XACT_TRANSACTION_ACTIVE
SQLState Message text
XSTA2.S A transaction was already active, when attempt was made to make another transaction active.
Table 51. Class XSTB: RawStore - Transactions.Basic system
SQLState Message text
XSTB0.M An exception was thrown during transaction abort.
XSTB2.M Cannot log transaction changes, maybe trying to write to a read only database.
XSTB3.M Cannot abort transaction because the log manager is null, probably due to an earlier error.
XSTB5.M Creating database with logging disabled encountered unexpected problem.
XSTB6.M Cannot substitute a transaction table with another while one is already in use.
Table 52. Class XXXXX: No SQLSTATE
SQLState Message text
XXXXX.C.6 Normal database session close.