ScalarDB Core Error Codes
This page provides a list of error codes in ScalarDB Core.
Error code classes and descriptions​
| Class | Description |
|---|---|
DB-CORE-1xxxx | Errors for the user error category |
DB-CORE-2xxxx | Errors for the concurrency error category |
DB-CORE-3xxxx | Errors for the internal error category |
DB-CORE-4xxxx | Errors for the unknown transaction status error category |
DB-CORE-1xxxx status codes​
The following are status codes and messages for the user error category.
DB-CORE-10000​
Message
Only a single-column index is supported. Operation: %s
DB-CORE-10001​
Message
The column of the specified index key is not indexed. Operation: %s
DB-CORE-10002​
Message
The index key is not properly specified. Operation: %s
DB-CORE-10003​
Message
Clustering keys cannot be specified when using an index. Operation: %s
DB-CORE-10004​
Message
Orderings cannot be specified when using an index. Operation: %s
DB-CORE-10005​
Message
The limit cannot be negative. Operation: %s
DB-CORE-10006​
Message
Cross-partition scan is not enabled. Operation: %s
DB-CORE-10007​
Message
Cross-partition scan ordering is not enabled. Operation: %s
DB-CORE-10008​
Message
Cross-partition scan filtering is not enabled. Operation: %s
DB-CORE-10009​
Message
The specified projection is not found. Projection: %s, Operation: %s
DB-CORE-10010​
Message
The clustering key boundary is not properly specified. Operation: %s
DB-CORE-10011​
Message
The start clustering key is not properly specified. Operation: %s
DB-CORE-10012​
Message
The end clustering key is not properly specified. Operation: %s
DB-CORE-10013​
Message
Orderings are not properly specified. Operation: %s
DB-CORE-10014​
Message
The specified ordering column is not found. Ordering: %s, Operation: %s
DB-CORE-10015​
Message
The condition is not properly specified. Operation: %s
DB-CORE-10016​
Message
The table does not exist. Table: %s
DB-CORE-10017​
Message
The column value is not properly specified. Column: %s, Operation: %s
DB-CORE-10018​
Message
The mutations are empty
DB-CORE-10019​
Message
The storage does not support mutations across multiple partitions. Storage: %s; Mutations: %s
DB-CORE-10020​
Message
The partition key is not properly specified. Operation: %s
DB-CORE-10021​
Message
The clustering key is not properly specified. Operation: %s
DB-CORE-10022​
Message
The authentication and authorization feature is not enabled. To use this feature, you must enable it. Note that this feature is supported only in the ScalarDB Enterprise edition
DB-CORE-10023​
Message
This condition is not allowed for the PutIf operation. Condition: %s
DB-CORE-10024​
Message
This condition is not allowed for the DeleteIf operation. Condition: %s
DB-CORE-10025​
Message
Operator must be LIKE or NOT_LIKE. Operator: %s
DB-CORE-10026​
Message
An escape character must be a string of a single character or an empty string
DB-CORE-10027​
Message
The LIKE pattern must not be null
DB-CORE-10028​
Message
The LIKE pattern must not include only an escape character
DB-CORE-10029​
Message
The LIKE pattern must not end with an escape character
DB-CORE-10030​
Message
The column %s does not exist
DB-CORE-10031​
Message
This operation is not supported when getting records of a database without using an index
DB-CORE-10032​
Message
This operation is not supported when getting records of a database by using an index
DB-CORE-10033​
Message
This operation is not supported when scanning all the records of a database or scanning records of a database by using an index
DB-CORE-10034​
Message
This operation is supported only when scanning records of a database by using an index
DB-CORE-10035​
Message
This operation is not supported when scanning records of a database by using an index
DB-CORE-10037​
Message
This operation is supported only when no conditions are specified. If you want to modify a condition, please use clearConditions() to remove all existing conditions first
DB-CORE-10038​
Message
One or more columns must be specified
DB-CORE-10039​
Message
One or more partition keys must be specified
DB-CORE-10040​
Message
The column definition must be specified since %s is specified as a partition key
DB-CORE-10041​
Message
The column definition must be specified since %s is specified as a clustering key
DB-CORE-10042​
Message
Invalid ID specified. ID: %d
DB-CORE-10043​
Message
The transaction is not active. Status: %s
DB-CORE-10044​
Message
The transaction has already been committed. Status: %s
DB-CORE-10045​
Message
The transaction has not been prepared. Status: %s
DB-CORE-10046​
Message
The transaction has not been prepared or validated. Status: %s
DB-CORE-10047​
Message
The transaction already exists
DB-CORE-10048​
Message
A transaction associated with the specified transaction ID is not found. The transaction might have expired
DB-CORE-10049​
Message
%s is the system namespace name
DB-CORE-10050​
Message
The namespace already exists. Namespace: %s
DB-CORE-10051​
Message
The namespace does not exist. Namespace: %s
DB-CORE-10052​
Message
The table already exists. Table: %s
DB-CORE-10053​
Message
The namespace is not empty. Namespace: %s; Tables in the namespace: %s
DB-CORE-10054​
Message
The column does not exist. Table: %s; Column: %s
DB-CORE-10055​
Message
The index already exists. Table: %s; Column: %s
DB-CORE-10056​
Message
The index does not exist. Table: %s; Column: %s
DB-CORE-10057​
Message
The column already exists. Table: %s; Column: %s
DB-CORE-10058​
Message
The operation does not have the target namespace or table name. Operation: %s
DB-CORE-10059​
Message
The specified value of the property '%s' is not a number. Value: %s
DB-CORE-10060​
Message
The specified value of the property '%s' is not a boolean. Value: %s
DB-CORE-10061​
Message
Reading the file failed. File: %s
DB-CORE-10062​
Message
The property 'scalar.db.cross_partition_scan.enabled' must be set to true to use cross-partition scan with filtering or ordering
DB-CORE-10063​
Message
This column value is out of range for BigInt. Value: %s
DB-CORE-10064​
Message
This type is not supported. Name: %s, Type: %s
DB-CORE-10065​
Message
Storage '%s' is not found
DB-CORE-10066​
Message
Transaction manager '%s' is not found
DB-CORE-10068​
Message
Please use scan() for non-exact match selection. Operation: %s
DB-CORE-10069​
Message
Import-related functionality is not supported in Cassandra
DB-CORE-10070​
Message
The %s network strategy does not exist
DB-CORE-10071​
Message
The property 'scalar.db.contact_port' must be greater than or equal to zero
DB-CORE-10073​
Message
The BLOB type is not supported for clustering keys in Cosmos DB. Column: %s
DB-CORE-10074​
Message
Import-related functionality is not supported in Cosmos DB
DB-CORE-10075​
Message
The property 'scalar.db.contact_points' must not be empty
DB-CORE-10076​
Message
Cosmos DB supports only EQ, NE, IS_NULL, and IS_NOT_NULL operations for the BLOB type in conditions. Mutation: %s
DB-CORE-10077​
Message
The specified consistency level is not supported. Consistency level: %s
DB-CORE-10078​
Message
0x00 bytes are not accepted in BLOB values in DESC order
DB-CORE-10079​
Message
Cannot encode a Text value that contains '\u0000'
DB-CORE-10081​
Message
An index column cannot be set to null or an empty value for Text or Blob in DynamoDB. Operation: %s
DB-CORE-10082​
Message
DynamoDB supports only EQ, NE, IS_NULL, and IS_NOT_NULL operations for the BOOLEAN type in conditions. Mutation: %s
DB-CORE-10083​
Message
Nested multi-storage definitions are not supported. Storage: %s
DB-CORE-10084​
Message
Storage not found. Storage: %s
DB-CORE-10085​
Message
The namespace name is not acceptable in SQLite. Namespace: %s
DB-CORE-10086​
Message
The table name is not acceptable in SQLite. Table: %s
DB-CORE-10087​
Message
Importing tables is not allowed in SQLite
DB-CORE-10088​
Message
The %s table must have a primary key
DB-CORE-10089​
Message
The RDB engine is not supported. JDBC connection URL: %s
DB-CORE-10090​
Message
Data type %s(%d) is not supported: %s
DB-CORE-10091​
Message
Data type %s is not supported: %s
DB-CORE-10092​
Message
Getting a transaction state is not supported in JDBC transactions
DB-CORE-10093​
Message
Rolling back a transaction is not supported in JDBC transactions
DB-CORE-10094​
Message
Coordinator tables already exist
DB-CORE-10095​
Message
Coordinator tables do not exist
DB-CORE-10096​
Message
The namespace %s is reserved. Any operations on this namespace are not allowed
DB-CORE-10097​
Message
Mutating transaction metadata columns is not allowed. Table: %s; Column: %s
DB-CORE-10098​
Message
A %s condition is not allowed on Put operations
DB-CORE-10099​
Message
A %s condition is not allowed on Delete operations
DB-CORE-10100​
Message
The condition is not allowed to target transaction metadata columns. Table: %s; Column: %s
DB-CORE-10101​
Message
The column '%s' is reserved as transaction metadata
DB-CORE-10102​
Message
Non-primary key columns with the 'before_' prefix, '%s', are reserved as transaction metadata
DB-CORE-10103​
Message
Put cannot have a condition when the target record is unread and implicit pre-read is disabled. Please read the target record beforehand or enable implicit pre-read: %s
DB-CORE-10104​
Message
Writing data already-deleted by the same transaction is not allowed
DB-CORE-10106​
Message
Scanning data already-written or already-deleted by the same transaction is not allowed
DB-CORE-10107​
Message
The transaction is not validated. When using the SERIALIZABLE isolation level, you need to call validate() before calling commit()
DB-CORE-10108​
Message
DynamoDB cannot batch more than 100 mutations at once
DB-CORE-10126​
Message
The mutation type is not supported. Only the Put or Delete type is supported. Mutation: %s
DB-CORE-10127​
Message
This condition is not allowed for the UpdateIf operation. Condition: %s
DB-CORE-10128​
Message
Cross-partition scan with ordering is not supported in Cassandra
DB-CORE-10129​
Message
Cross-partition scan with ordering is not supported in Cosmos DB
DB-CORE-10130​
Message
Cross-partition scan with ordering is not supported in DynamoDB
DB-CORE-10136​
Message
Getting a transaction state is not supported in single CRUD operation transactions
DB-CORE-10137​
Message
Rolling back a transaction is not supported in single CRUD operation transactions
DB-CORE-10138​
Message
Multiple mutations are not supported in single CRUD operation transactions
DB-CORE-10139​
Message
Beginning a transaction is not allowed in single CRUD operation transactions
DB-CORE-10140​
Message
Resuming a transaction is not allowed in single CRUD operation transactions
DB-CORE-10141​
Message
Using the group commit feature on the Coordinator table with a two-phase commit interface is not allowed
DB-CORE-10142​
Message
This operation is supported only when no conditions are specified. If you want to modify a condition, please use clearConditions() to remove all existing conditions first
DB-CORE-10143​
Message
The encryption feature is not enabled. To encrypt data at rest, you must enable this feature. Note that this feature is supported only in the ScalarDB Enterprise edition
DB-CORE-10144​
Message
The variable key column size must be greater than or equal to 64
DB-CORE-10145​
Message
The value of the column %s in the primary key contains an illegal character. Primary-key columns must not contain any of the following characters in Cosmos DB: ':', '/', '\', '#', '?'. Value: %s
DB-CORE-10146​
Message
Inserting data already-written by the same transaction is not allowed
DB-CORE-10147​
Message
Deleting data already-inserted by the same transaction is not allowed
DB-CORE-10152​
Message
The attribute-based access control feature is not enabled. To use this feature, you must enable it. Note that this feature is supported only in the ScalarDB Enterprise edition
DB-CORE-10158​
Message
This DATE column value is out of the valid range. It must be between 1000-01-01 and 9999-12-12. Value: %s
DB-CORE-10159​
Message
This TIME column value precision cannot be shorter than one microsecond. Value: %s
DB-CORE-10160​
Message
This TIMESTAMP column value is out of the valid range. It must be between 1000-01-01T00:00:00.000 and 9999-12-31T23:59:59.999. Value: %s
DB-CORE-10161​
Message
This TIMESTAMP column value precision cannot be shorter than one millisecond. Value: %s
DB-CORE-10162​
Message
This TIMESTAMPTZ column value is out of the valid range. It must be between 1000-01-01T00:00:00.000Z to 9999-12-31T23:59:59.999Z. Value: %s
DB-CORE-10163​
Message
This TIMESTAMPTZ column value precision cannot be shorter than one millisecond. Value: %s
DB-CORE-10164​
Message
The underlying-storage data type %s is not supported as the ScalarDB %s data type: %s
DB-CORE-10188​
Message
The replication feature is not enabled. To use this feature, you must enable it. Note that this feature is supported only in the ScalarDB Enterprise edition
DB-CORE-10205​
Message
Some scanners were not closed. All scanners must be closed before committing the transaction
DB-CORE-10206​
Message
Some scanners were not closed. All scanners must be closed before preparing the transaction
DB-CORE-10211​
Message
Mutations are not allowed in read-only transactions. Transaction ID: %s
DB-CORE-10212​
Message
The storage does not support mutations across multiple records. Storage: %s; Mutations: %s
DB-CORE-10213​
Message
The storage does not support mutations across multiple tables. Storage: %s; Mutations: %s
DB-CORE-10214​
Message
The storage does not support mutations across multiple namespaces. Storage: %s; Mutations: %s
DB-CORE-10215​
Message
Mutations across multiple storages are not allowed. Mutations: %s
DB-CORE-10216​
Message
Primary key columns cannot be dropped. Table: %s; Column: %s
DB-CORE-10217​
Message
Cosmos DB does not support the feature for dropping columns
DB-CORE-10218​
Message
DynamoDB does not support the feature for dropping columns
DB-CORE-10219​
Message
Cosmos DB does not support the feature for renaming columns
DB-CORE-10220​
Message
DynamoDB does not support the feature for renaming columns
DB-CORE-10221​
Message
Cassandra does not support renaming non-primary key columns
DB-CORE-10222​
Message
Db2 does not support renaming primary key or index key columns
DB-CORE-10223​
Message
Import-related functionality is not supported in DynamoDB
DB-CORE-10224​
Message
The BLOB type is supported only for the last column in the partition key in DynamoDB. Column: %s
DB-CORE-10225​
Message
The BLOB type is not supported for clustering keys in DynamoDB. Column: %s
DB-CORE-10226​
Message
The BOOLEAN type is not supported for index columns in DynamoDB. Column: %s
DB-CORE-10227​
Message
The TIMESTAMP type is not supported in Cassandra. Column: %s
DB-CORE-10228​
Message
With Db2, using a BLOB column as partition key, clustering key or secondary index is not supported.
DB-CORE-10229​
Message
With Db2, setting an ordering on a BLOB column when using a cross partition scan operation is not supported. Ordering: %s
DB-CORE-10230​
Message
Renaming tables is not supported in Cassandra
DB-CORE-10231​
Message
Renaming tables is not supported in Cosmos DB
DB-CORE-10232​
Message
Renaming tables is not supported in DynamoDB
DB-CORE-10233​
Message
Altering primary key or index key column types is not supported. Table: %s; Column: %s
DB-CORE-10234​
Message
Invalid column type conversion from %s to %s. Column: %s
DB-CORE-10235​
Message
Cassandra does not support the feature for altering column types
DB-CORE-10236​
Message
Cosmos DB does not support the feature for altering column types
DB-CORE-10237​
Message
DynamoDB does not support the feature for altering column types
DB-CORE-10238​
Message
SQLite does not support the feature for altering column types
DB-CORE-10239​
Message
Oracle does not support column type conversion from %s to %s
DB-CORE-10240​
Message
Db2 does not support column type conversion from %s to %s
DB-CORE-10241​
Message
The operations are empty
DB-CORE-10242​
Message
Multiple operations are not supported in single CRUD operation transactions
DB-CORE-10243​
Message
This batch result doesn't have a get result
DB-CORE-10244​
Message
This batch result doesn't have a scan result
DB-CORE-10245​
Message
TiDB does not support column type conversion from %s to %s
DB-CORE-10246​
Message
With Oracle, using a BLOB column as partition key, clustering key or secondary index is not supported.
DB-CORE-10247​
Message
With Oracle, setting an ordering on a BLOB column when using a cross partition scan operation is not supported. Ordering: %s
DB-CORE-10248​
Message
With Oracle, setting a condition on a BLOB column when using a selection operation is not supported. Condition: %s
DB-CORE-10249​
Message
The namespace has non-ScalarDB tables and cannot be dropped. Namespace: %s; Tables in the namespace: %s
DB-CORE-10250​
Message
Import-related functionality is not supported in Object Storage
DB-CORE-10251​
Message
Index-related functionality is not supported in Object Storage
DB-CORE-10252​
Message
Object Storage does not support the feature for dropping columns
DB-CORE-10253​
Message
Object Storage does not support the feature for renaming columns
DB-CORE-10254​
Message
Renaming tables is not supported in Object Storage
DB-CORE-10255​
Message
Object Storage does not support the feature for altering column types
DB-CORE-10256​
Message
Cross-partition scan with ordering is not supported in Object Storage
DB-CORE-10257​
Message
The value of the column %s in the primary key contains an illegal character. Value: %s
DB-CORE-10258​
Message
Specifying transaction metadata columns in the projection is not allowed. Table: %s; Column: %s
DB-CORE-10259​
Message
Specifying transaction metadata columns in the ordering is not allowed. Table: %s; Column: %s
DB-CORE-10260​
Message
Get operations by using an index is not allowed in the SERIALIZABLE isolation level
DB-CORE-10261​
Message
Scan operations by using an index is not allowed in the SERIALIZABLE isolation level
DB-CORE-10262​
Message
Conditions on indexed columns in cross-partition scan operations are not allowed in the SERIALIZABLE isolation level
DB-CORE-10263​
Message
The service account key for Cloud Storage was not found.
DB-CORE-10264​
Message
Failed to load the service account key for Cloud Storage.
DB-CORE-10265​
Message
To support virtual tables, the atomicity unit of the storage must be at least at the namespace level. Storage: %s; Atomicity unit: %s
DB-CORE-10266​
Message
The source tables must reside within the atomicity unit of the storage. Storage: %s; Atomicity unit: %s; Left source table: %s; Right source table: %s
DB-CORE-10267​
Message
The virtual table functionality is not supported in DynamoDB
DB-CORE-10268​
Message
The source tables must have the same primary key. Left source table: %s; Right source table: %s
DB-CORE-10269​
Message
The source tables must have the same data types for primary key column. Column: %s; Left source table: %s; Right source table: %s
DB-CORE-10270​
Message
The source tables must have the same clustering orders for clustering key column. Column: %s; Left source table: %s; Right source table: %s
DB-CORE-10271​
Message
The source tables have conflicting non-key column names. Left source table: %s; Right source table: %s; Conflicting columns: %s
DB-CORE-10272​
Message
Virtual tables cannot be used as source tables. Source table: %s
DB-CORE-10273​
Message
The source tables must be in the same storage. Left source table: %s; Right source table: %s
DB-CORE-10274​
Message
The virtual table must be in the same storage as its source tables. Virtual table: %s; Left source table: %s; Right source table: %s
DB-CORE-10275​
Message
Source tables cannot be dropped while virtual tables depending on them exist. Source table: %s; Virtual tables: %s
DB-CORE-10276​
Message
The DeleteIf IS_NULL condition for right source table columns is not allowed in LEFT_OUTER virtual tables. Virtual table: %s
DB-CORE-10277​
Message
The transaction metadata decoupling feature is not supported in the storage. Storage %s
DB-CORE-10278​
Message
The storage does not guarantee consistent reads for virtual tables. Depending on the storage configuration, you may be able to adjust the settings to enable consistent reads. Please refer to the storage configuration for details. Storage: %s
DB-CORE-2xxxx status codes​
The following are status codes and messages for the concurrency error category.
DB-CORE-20000​
Message
No mutation was applied
DB-CORE-20001​
Message
Logging failed in the batch
DB-CORE-20002​
Message
The operation failed in the batch with type %s
DB-CORE-20003​
Message
An error occurred in the batch. Details: %s
DB-CORE-20004​
Message
A Paxos phase in the CAS operation failed
DB-CORE-20005​
Message
The learn phase in the CAS operation failed
DB-CORE-20006​
Message
A simple write operation failed
DB-CORE-20007​
Message
An error occurred in the mutation. Details: %s
DB-CORE-20008​
Message
A RetryWith error occurred in the mutation. Details: %s
DB-CORE-20009​
Message
A transaction conflict occurred in the mutation. Details: %s
DB-CORE-20010​
Message
A transaction conflict occurred in the mutation. Details: %s
DB-CORE-20011​
Message
A conflict occurred. Please try restarting the transaction. Details: %s
DB-CORE-20012​
Message
The %s condition of the %s operation is not satisfied. Targeting column(s): %s
DB-CORE-20013​
Message
The record being prepared already exists. Details: %s
DB-CORE-20014​
Message
A conflict occurred when preparing records. Details: %s
DB-CORE-20015​
Message
The committing state in the coordinator failed. The transaction has been aborted. Details: %s
DB-CORE-20016​
Message
A conflict occurred during implicit pre-read. Details: %s
DB-CORE-20017​
Message
This record needs to be recovered. Table: %s; Partition Key: %s; Clustering Key: %s; Transaction ID that wrote the record: %s
DB-CORE-20018​
Message
The record does not exist, so the %s condition is not satisfied
DB-CORE-20019​
Message
The record exists, so the %s condition is not satisfied
DB-CORE-20020​
Message
The condition on the column '%s' is not satisfied
DB-CORE-20022​
Message
An anti-dependency was found. The transaction has been aborted
DB-CORE-20023​
Message
A transaction conflict occurred in the Insert operation
DB-CORE-20024​
Message
The %s condition of the %s operation is not satisfied. Targeting column(s): %s
DB-CORE-20025​
Message
A transaction conflict occurred in the Insert operation
DB-CORE-20026​
Message
A conflict occurred when committing records. Details: %s
DB-CORE-20027​
Message
A transaction conflict occurred in the mutation. Details: %s
DB-CORE-3xxxx status codes​
The following are status codes and messages for the internal error category.
DB-CORE-30000​
Message
Creating the namespace failed. Namespace: %s
DB-CORE-30001​
Message
Dropping the namespace failed. Namespace: %s
DB-CORE-30002​
Message
Creating the table failed. Table: %s
DB-CORE-30003​
Message
Dropping the table failed. Table: %s
DB-CORE-30004​
Message
Truncating the table failed. Table: %s
DB-CORE-30005​
Message
Creating the index failed. Table: %s, Column: %s
DB-CORE-30006​
Message
Dropping the index failed. Table: %s, Column: %s
DB-CORE-30007​
Message
Getting the table metadata failed. Table: %s
DB-CORE-30008​
Message
Getting the table names in the namespace failed. Namespace: %s
DB-CORE-30009​
Message
Checking the namespace existence failed. Namespace: %s
DB-CORE-30010​
Message
Checking the table existence failed. Table: %s
DB-CORE-30011​
Message
Checking the index existence failed. Table: %s; Column: %s
DB-CORE-30012​
Message
Repairing the namespace failed. Namespace: %s
DB-CORE-30013​
Message
Repairing the table failed. Table: %s
DB-CORE-30014​
Message
Adding a new column to the table failed. Table: %s; Column: %s; ColumnType: %s
DB-CORE-30015​
Message
Getting the namespace names failed
DB-CORE-30016​
Message
Getting the table metadata of the table being imported failed. Table: %s
DB-CORE-30017​
Message
Importing the table failed. Table: %s
DB-CORE-30018​
Message
Adding the raw column to the table failed. Table: %s; Column: %s; ColumnType: %s
DB-CORE-30019​
Message
Upgrading the ScalarDB environment failed
DB-CORE-30020​
Message
Something wrong because WriteType is neither CAS nor SIMPLE
DB-CORE-30021​
Message
An error occurred in the selection. Details: %s
DB-CORE-30022​
Message
An error occurred in the mutation. Details: %s
DB-CORE-30023​
Message
An error occurred in the selection. Details: %s
DB-CORE-30024​
Message
An error occurred in the mutation. Details: %s
DB-CORE-30025​
Message
An error occurred in the selection. Details: %s
DB-CORE-30026​
Message
An error occurred in the mutation. Details: %s
DB-CORE-30027​
Message
An error occurred in the selection. Details: %s
DB-CORE-30028​
Message
Fetching the next result failed. Details: %s
DB-CORE-30029​
Message
Rolling back the transaction failed. Details: %s
DB-CORE-30030​
Message
Committing the transaction failed. Details: %s
DB-CORE-30031​
Message
The Get operation failed. Details: %s
DB-CORE-30032​
Message
The Scan operation failed. Details: %s
DB-CORE-30033​
Message
The Put operation failed. Details: %s
DB-CORE-30034​
Message
The Delete operation failed. Details: %s
DB-CORE-30035​
Message
Beginning a transaction failed. Details: %s
DB-CORE-30036​
Message
Preparing records failed. Details: %s
DB-CORE-30037​
Message
Validation failed. Details: %s
DB-CORE-30038​
Message
Executing implicit pre-read failed. Details: %s
DB-CORE-30039​
Message
Reading a record from the underlying storage failed. Details: %s
DB-CORE-30040​
Message
Scanning records from the underlying storage failed. Details: %s
DB-CORE-30041​
Message
Rollback failed because the transaction has already been committed
DB-CORE-30042​
Message
Rollback failed
DB-CORE-30043​
Message
The Insert operation failed. Details: %s
DB-CORE-30044​
Message
The Upsert operation failed. Details: %s
DB-CORE-30045​
Message
The Update operation failed. Details: %s
DB-CORE-30046​
Message
Handling the before-preparation hook failed. Details: %s
DB-CORE-30054​
Message
Getting the scanner failed. Details: %s
DB-CORE-30055​
Message
Closing the scanner failed. Details: %s
DB-CORE-30056​
Message
Getting the storage information failed. Namespace: %s
DB-CORE-30057​
Message
Recovering records failed. Details: %s
DB-CORE-30058​
Message
Committing records failed. Details: %s
DB-CORE-30059​
Message
Dropping a column from the table failed. Table: %s; Column: %s
DB-CORE-30060​
Message
Renaming a column failed. Table: %s; Old column name: %s; New column name: %s
DB-CORE-30061​
Message
Renaming a table failed. Old table name: %s; New table name: %s
DB-CORE-30062​
Message
Altering a column type failed. Table: %s; Column: %s; New column type: %s
DB-CORE-30063​
Message
Getting the MySQL JDBC connection metadata failed. Details: %s
DB-CORE-30064​
Message
An error occurred in the selection. Details: %s
DB-CORE-30065​
Message
An error occurred in the mutation. Details: %s
DB-CORE-30066​
Message
Creating the virtual table failed. Virtual table: %s; Left source table: %s; Right source table: %s
DB-CORE-30067​
Message
Getting the virtual table information failed. Table: %s
DB-CORE-4xxxx status codes​
The following are status codes and messages for the unknown transaction status error category.
DB-CORE-40000​
Message
Rolling back the transaction failed. Details: %s
DB-CORE-40001​
Message
Committing state failed with NoMutationException, but the coordinator status does not exist. Details: %s
DB-CORE-40002​
Message
The coordinator status cannot be retrieved. Details: %s
DB-CORE-40003​
Message
The coordinator status is unknown. Details: %s
DB-CORE-40004​
Message
Aborting state failed with NoMutationException, but the coordinator status does not exist. Details: %s
DB-CORE-40005​
Message
One-phase committing records failed. Details: %s