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
Mutations that span multiple partitions are not supported. 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 or rolled back. 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. Namespace: %s
DB-CORE-10086
​
Message
The table name is not acceptable. Table: %s
DB-CORE-10087
​
Message
Importing tables is not allowed in the RDB engine. RDB engine: %s
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. 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 already-deleted data is not allowed
DB-CORE-10105
​
Message
Getting data neither in the read set nor the delete set is not allowed
DB-CORE-10106
​
Message
Reading already-written data is not allowed
DB-CORE-10107
​
Message
The transaction is not validated. When using the EXTRA_READ serializable strategy, you need to call validate() before calling commit()
DB-CORE-10108
​
Message
DynamoDB cannot batch more than 100 mutations at once
DB-CORE-10109
​
Message
The partition keys of the table %s.%s were modified, but altering partition keys is not supported
DB-CORE-10110
​
Message
The clustering keys of the table %s.%s were modified, but altering clustering keys is not supported
DB-CORE-10111
​
Message
The clustering ordering of the table %s.%s were modified, but altering clustering ordering is not supported
DB-CORE-10112
​
Message
The column %s of the table %s.%s has been deleted. Column deletion is not supported when altering a table
DB-CORE-10113
​
Message
The data type of the column %s of the table %s.%s was modified, but altering data types is not supported
DB-CORE-10114
​
Message
Specifying the '--schema-file' option is required when using the '--repair-all' option
DB-CORE-10115
​
Message
Specifying the '--schema-file' option is required when using the '--alter' option
DB-CORE-10116
​
Message
Specifying the '--schema-file' option is required when using the '--import' option
DB-CORE-10117
​
Message
Specifying the '--coordinator' option with the '--import' option is not allowed. Create Coordinator tables separately
DB-CORE-10118
​
Message
Reading the configuration file failed. File: %s
DB-CORE-10119
​
Message
Reading the schema file failed. File: %s
DB-CORE-10120
​
Message
Parsing the schema JSON failed. Details: %s
DB-CORE-10121
​
Message
The table name must contain the namespace and the table. Table: %s
DB-CORE-10122
​
Message
The partition key must be specified. Table: %s
DB-CORE-10123
​
Message
Invalid clustering-key format. The clustering key must be in the format of 'column_name' or 'column_name ASC/DESC'. Table: %s; Clustering key: %s
DB-CORE-10124
​
Message
Columns must be specified. Table: %s
DB-CORE-10125
​
Message
Invalid column type. Table: %s; Column: %s; Type: %s
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-10131
​
Message
The directory '%s' does not have write permissions. Please ensure that the current user has write access to the directory.
DB-CORE-10132
​
Message
Failed to create the directory '%s'. Please check if you have sufficient permissions and if there are any file system restrictions. Details: %s
DB-CORE-10133
​
Message
Directory path cannot be null or empty.
DB-CORE-10134
​
Message
No file extension was found on the provided file name %s.
DB-CORE-10135
​
Message
Invalid file extension: %s. Allowed extensions are: %s
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 already-written data is not allowed
DB-CORE-10147
​
Message
Deleting already-inserted data is not allowed
DB-CORE-10148
​
Message
Invalid key: Column %s does not exist in the table %s in namespace %s.
DB-CORE-10149
​
Message
Invalid base64 encoding for blob value for column %s in table %s in namespace %s
DB-CORE-10150
​
Message
Invalid number specified for column %s in table %s in namespace %s
DB-CORE-10151
​
Message
Method null argument 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-10153
​
Message
The provided clustering key %s was not found
DB-CORE-10154
​
Message
The column '%s' was not found
DB-CORE-10155
​
Message
The provided partition key is incomplete. Required key: %s
DB-CORE-10156
​
Message
The provided clustering key order does not match the table schema. Required order: %s
DB-CORE-10157
​
Message
The provided partition key order does not match the table schema. Required order: %s
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-10165
​
Message
Missing namespace or table: %s, %s
DB-CORE-10166
​
Message
Failed to retrieve table metadata. Details: %s
DB-CORE-10167
​
Message
Duplicate data mappings found for table '%s' in the control file
DB-CORE-10168
​
Message
No mapping found for column '%s' in table '%s' in the control file. Control file validation set at 'FULL'. All columns need to be mapped.
DB-CORE-10169
​
Message
The control file is missing data mappings
DB-CORE-10170
​
Message
The target column '%s' for source field '%s' could not be found in table '%s'
DB-CORE-10171
​
Message
The required partition key '%s' is missing in the control file mapping for table '%s'
DB-CORE-10172
​
Message
The required clustering key '%s' is missing in the control file mapping for table '%s'
DB-CORE-10173
​
Message
Duplicated data mappings found for column '%s' in table '%s'
DB-CORE-10174
​
Message
Missing required field or column mapping for clustering key %s
DB-CORE-10175
​
Message
Missing required field or column mapping for partition key %s
DB-CORE-10176
​
Message
Missing field or column mapping for %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
DB-CORE-20014
​
Message
A conflict occurred when preparing records
DB-CORE-20015
​
Message
The committing state in the coordinator failed. The transaction has been aborted
DB-CORE-20016
​
Message
A conflict occurred during implicit pre-read
DB-CORE-20017
​
Message
This record needs to be recovered
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-20021
​
Message
Reading empty records might cause a write skew anomaly, so the transaction has been aborted for safety purposes
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-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