ScalarDB Core エラーコード
注記
このページは英語版のページが機械翻訳されたものです。英語版との間に矛盾または不一致がある場合は、英語版を正としてください。
このページでは、ScalarDB Core のエラーコードの一覧を示します。
エラーコードのクラスと説明
| クラス | 説明 |
|---|---|
DB-CORE-1xxxx | ユーザーエラーカテゴリのエラー |
DB-CORE-2xxxx | 同時実行エラーカテゴリのエラー |
DB-CORE-3xxxx | 内部エラーカテゴリのエラー |
DB-CORE-4xxxx | 不明なトランザクションステータスエラーカテゴ リのエラー |
DB-CORE-1xxxx ステータスコード
以下は、ユーザーエラーカテゴリのステータスコードとメッセージです。
DB-CORE-10000
メッセージ
Only a single-column index is supported. Operation: %s
DB-CORE-10001
メッセージ
The column of the specified index key is not indexed. Operation: %s; Table metadata: %s
DB-CORE-10002
メッセージ
The index key is not properly specified. Operation: %s; Table metadata: %s
DB-CORE-10003
メッセージ
Clustering keys cannot be specified when using an index. Operation: %s
DB-CORE-10004
メッセージ
Orderings cannot be specified when using an index. Operation: %s
DB-CORE-10005
メッセージ
The limit cannot be negative. Operation: %s
DB-CORE-10006
メッセージ
Cross-partition scan is not enabled. Operation: %s
DB-CORE-10007
メッセージ
Cross-partition scan ordering is not enabled. Operation: %s
DB-CORE-10008
メッセージ
Cross-partition scan filtering is not enabled. Operation: %s
DB-CORE-10009
メッセージ
The specified projection is not found. Projection: %s, Operation: %s; Table metadata: %s
DB-CORE-10010
メッセージ
The clustering key boundary is not properly specified. Operation: %s; Table metadata: %s
DB-CORE-10011
メッセージ
The start clustering key is not properly specified. Operation: %s; Table metadata: %s
DB-CORE-10012
メッセージ
The end clustering key is not properly specified. Operation: %s; Table metadata: %s
DB-CORE-10013
メッセージ
Orderings are not properly specified. Operation: %s; Table metadata: %s
DB-CORE-10014
メッセージ
The specified ordering column is not found. Ordering: %s, Operation: %s; Table metadata: %s
DB-CORE-10015
メッセージ
The condition is not properly specified. Operation: %s; Table metadata: %s
DB-CORE-10016
メッセージ
The table does not exist. Table: %s
DB-CORE-10017
メッセージ
The column value is not properly specified. Column: %s, Operation: %s; Table metadata: %s
DB-CORE-10018
メッセージ
The mutations are empty
DB-CORE-10019
メ ッセージ
The storage does not support mutations across multiple partitions. Storage: %s; Mutations: %s
DB-CORE-10020
メッセージ
The partition key is not properly specified. Operation: %s; Table metadata: %s
DB-CORE-10021
メッセージ
The clustering key is not properly specified. Operation: %s; Table metadata: %s
DB-CORE-10022
メッセージ
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
メッセージ
This condition is not allowed for the PutIf operation. Condition: %s
DB-CORE-10024
メッセージ
This condition is not allowed for the DeleteIf operation. Condition: %s
DB-CORE-10025
メッセージ
Operator must be LIKE or NOT_LIKE. Operator: %s
DB-CORE-10026
メッセージ
An escape character must be a string of a single character or an empty string
DB-CORE-10027
メッセージ
The LIKE pattern must not be null
DB-CORE-10028
メッセージ
The LIKE pattern must not include only an escape character
DB-CORE-10029
メッセージ
The LIKE pattern must not end with an escape character
DB-CORE-10030
メッセージ
The column %s does not exist
DB-CORE-10031
メッセージ
This operation is not supported when getting records of a database without using an index
DB-CORE-10032
メッセージ
This operation is not supported when getting records of a database by using an index
DB-CORE-10033
メッセージ
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
メッセージ
This operation is supported only when scanning records of a database by using an index
DB-CORE-10035
メッセージ
This operation is not supported when scanning records of a database by using an index
DB-CORE-10037
メッセージ
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
メッセージ
One or more columns must be specified
DB-CORE-10039
メッセージ
One or more partition keys must be specified
DB-CORE-10040
メッセージ
The column definition must be specified since %s is specified as a partition key
DB-CORE-10041
メッセージ
The column definition must be specified since %s is specified as a clustering key
DB-CORE-10042
メッセージ
Invalid ID specified. ID: %d
DB-CORE-10043
メッセージ
The transaction is not active. Status: %s
DB-CORE-10044
メッセージ
The transaction has already been committed. Status: %s
DB-CORE-10045
メッセージ
The transaction has not been prepared. Status: %s
DB-CORE-10046
メッセージ
The transaction has not been prepared or validated. Status: %s
DB-CORE-10047
メッセージ
The transaction already exists
DB-CORE-10048
メッセージ
A transaction associated with the specified transaction ID is not found. The transaction might have expired
DB-CORE-10049
メッセージ
%s is the system namespace name
DB-CORE-10050
メッセージ
The namespace already exists. Namespace: %s
DB-CORE-10051
メッセージ
The namespace does not exist. Namespace: %s
DB-CORE-10052
メッセージ
The table already exists. Table: %s
DB-CORE-10053
メッセージ
The namespace is not empty. Namespace: %s; Tables in the namespace: %s
DB-CORE-10054
メッセージ
The column does not exist. Table: %s; Column: %s
DB-CORE-10055
メッセージ
The index already exists. Table: %s; Column: %s
DB-CORE-10056
メッセージ
The index does not exist. Table: %s; Column: %s
DB-CORE-10057
メッセージ
The column already exists. Table: %s; Column: %s
DB-CORE-10058
メッセージ
The operation does not have the target namespace or table name. Operation: %s
DB-CORE-10059
メッセージ
The specified value of the property '%s' is not a number. Value: %s
DB-CORE-10060
メッ セージ
The specified value of the property '%s' is not a boolean. Value: %s
DB-CORE-10061
メッセージ
Reading the file failed. File: %s
DB-CORE-10062
メッセージ
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
メッセージ
This column value is out of range for BigInt in Cosmos DB. Value: %s
DB-CORE-10064
メッセージ
This type is not supported. Name: %s, Type: %s
DB-CORE-10065
メッセージ
Storage '%s' is not found
DB-CORE-10066
メッセージ
Transaction manager '%s' is not found
DB-CORE-10068
メッセージ
Please use scan() for non-exact match selection. Operation: %s
DB-CORE-10069
メッセージ
Import-related functionality is not supported in Cassandra
DB-CORE-10070
メッセージ
The %s network strategy does not exist
DB-CORE-10071
メッセージ
The property 'scalar.db.contact_port' must be greater than or equal to zero
DB-CORE-10073
メッセージ
The BLOB type is not supported for clustering keys in Cosmos DB. Column: %s
DB-CORE-10074
メッセージ
Import-related functionality is not supported in Cosmos DB
DB-CORE-10075
メッセージ
The property 'scalar.db.contact_points' must not be empty
DB-CORE-10076
メッセージ
Cosmos DB supports only EQ, NE, IS_NULL, and IS_NOT_NULL operations for the BLOB type in conditions. Mutation: %s
DB-CORE-10077
メッセー ジ
The specified consistency level is not supported. Consistency level: %s
DB-CORE-10078
メッセージ
0x00 bytes are not accepted in BLOB values in DESC order
DB-CORE-10079
メッセージ
Cannot encode a Text value that contains '\\u0000'
DB-CORE-10081
メッセージ
An index column cannot be set to an empty value for Text or Blob in DynamoDB. Operation: %s
DB-CORE-10082
メッセージ
DynamoDB supports only EQ, NE, IS_NULL, and IS_NOT_NULL operations for the BOOLEAN type in conditions. Mutation: %s
DB-CORE-10083
メッセージ
Nested multi-storage definitions are not supported. Storage: %s
DB-CORE-10084
メッセージ
Storage not found. Storage: %s
DB-CORE-10085
メッセージ
The namespace name is not acceptable in SQLite. Namespace: %s
DB-CORE-10086
メッセージ
The table name is not acceptable in SQLite. Table: %s
DB-CORE-10087
メッセージ
Importing tables is not allowed in SQLite
DB-CORE-10088
メッセージ
The %s table must have a primary key
DB-CORE-10089
メッセージ
The RDB engine is not supported. JDBC connection URL: %s
DB-CORE-10090
メッセージ
Data type %s(%d) is not supported: %s
DB-CORE-10091
メッセージ
Data type %s is not supported: %s
DB-CORE-10092
メッセージ
Getting a transaction state is not supported in JDBC transactions
DB-CORE-10093
メッセージ
Rolling back a transaction is not supported in JDBC transactions
DB-CORE-10094
メッセージ
Coordinator tables already exist
DB-CORE-10095
メッセージ
Coordinator tables do not exist
DB-CORE-10096
メッセージ
The namespace %s is reserved. Any operations on this namespace are not allowed
DB-CORE-10097
メッセージ
Mutating transaction metadata columns is not allowed. Table: %s; Column: %s
DB-CORE-10098
メッセージ
A %s condition is not allowed on Put operations
DB-CORE-10099
メッセージ
A %s condition is not allowed on Delete operations
DB-CORE-10100
メッセージ
The condition is not allowed to target transaction metadata columns. Table: %s; Column: %s
DB-CORE-10101
メッセージ
The column '%s' is reserved as transaction metadata
DB-CORE-10102
メッセージ
Non-primary key columns with the 'before_' prefix, '%s', are reserved as transaction metadata
DB-CORE-10103
メッセージ
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-10106
メッセージ
Scanning data already-written or already-deleted by the same transaction is not allowed
DB-CORE-10107
メッセージ
The transaction is not validated. When using the SERIALIZABLE isolation level, you need to call validate() before calling commit()
DB-CORE-10108
メッセージ
DynamoDB cannot batch more than 100 mutations at once
DB-CORE-10126
メッセージ
The mutation type is not supported. Only the Put or Delete type is supported. Mutation: %s
DB-CORE-10127
メッセージ
This condition is not allowed for the UpdateIf operation. Condition: %s
DB-CORE-10128
メッセージ
Cross-partition scan with ordering is not supported in Cassandra
DB-CORE-10129
メッセージ
Cross-partition scan with ordering is not supported in Cosmos DB
DB-CORE-10130
メッセージ
Cross-partition scan with ordering is not supported in DynamoDB
DB-CORE-10136
メッセージ
Getting a transaction state is not supported in single CRUD operation transactions
DB-CORE-10137
メッセージ
Rolling back a transaction is not supported in single CRUD operation transactions
DB-CORE-10138
メッセージ
Multiple mutations are not supported in single CRUD operation transactions
DB-CORE-10139
メッセージ
Beginning a transaction is not allowed in single CRUD operation transactions
DB-CORE-10140
メッセージ
Resuming a transaction is not allowed in single CRUD operation transactions
DB-CORE-10141
メッセージ
Using the group commit feature on the Coordinator table with a two-phase commit interface is not allowed
DB-CORE-10142
メッセージ
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
メッセージ
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
メッセージ
The variable key column size must be greater than or equal to 64
DB-CORE-10145
メッセージ
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
メッセージ
Inserting data already-written by the same transaction is not allowed
DB-CORE-10147
メッセージ
Deleting data already-inserted by the same transaction is not allowed
DB-CORE-10152
メッセージ
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
メッセージ
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
メッセージ
This TIME column value precision cannot be shorter than one microsecond. Value: %s
DB-CORE-10160
メッセージ
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
メッセージ
This TIMESTAMP column value precision cannot be shorter than one millisecond. Value: %s
DB-CORE-10162
メッセージ
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
メッセージ
This TIMESTAMPTZ column value precision cannot be shorter than one millisecond. Value: %s
DB-CORE-10164
メッセージ
The underlying-storage data type %s is not supported as the ScalarDB %s data type: %s
DB-CORE-10188
メッセージ
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
メッセージ
Some scanners were not closed. All scanners must be closed before committing the transaction
DB-CORE-10206
メッセージ
Some scanners were not closed. All scanners must be closed before preparing the transaction
DB-CORE-10211
メッセージ
Mutations are not allowed in read-only transactions. Transaction ID: %s
DB-CORE-10212
メッセージ
The storage does not support mutations across multiple records. Storage: %s; Mutations: %s
DB-CORE-10213
メッセージ
The storage does not support mutations across multiple tables. Storage: %s; Mutations: %s
DB-CORE-10214
メッセージ
The storage does not support mutations across multiple namespaces. Storage: %s; Mutations: %s
DB-CORE-10215
メッセージ
Mutations across multiple storages are not allowed. Mutations: %s
DB-CORE-10216
メッセージ
Primary key columns cannot be dropped. Table: %s; Column: %s
DB-CORE-10217
メッセージ
Cosmos DB does not support the feature for dropping columns
DB-CORE-10218
メッセージ
DynamoDB does not support the feature for dropping columns
DB-CORE-10219
メッセージ
Cosmos DB does not support the feature for renaming columns
DB-CORE-10220
メッセージ
DynamoDB does not support the feature for renaming columns
DB-CORE-10221
メッセージ
Cassandra does not support renaming non-primary key columns
DB-CORE-10222
メッセージ
Db2 does not support renaming primary key or index key columns
DB-CORE-10223
メッセージ
Import-related functionality is not supported in DynamoDB
DB-CORE-10224
メッセージ
The BLOB type is supported only for the last column in the partition key in DynamoDB. Column: %s
DB-CORE-10225
メッセージ
The BLOB type is not supported for clustering keys in DynamoDB. Column: %s
DB-CORE-10226
メッセージ
The BOOLEAN type is not supported for index columns in DynamoDB. Column: %s
DB-CORE-10227
メッセージ
The TIMESTAMP type is not supported in Cassandra. Column: %s
DB-CORE-10228
メッセージ
With Db2, using a BLOB column as partition key, clustering key or secondary index is not supported.
DB-CORE-10229
メッセージ
With Db2, setting an ordering on a BLOB column when using a cross partition scan operation is not supported. Ordering: %s
DB-CORE-10230
メッセージ
Renaming tables is not supported in Cassandra
DB-CORE-10231
メッセージ
Renaming tables is not supported in Cosmos DB
DB-CORE-10232
メッセージ
Renaming tables is not supported in DynamoDB
DB-CORE-10233
メッセージ
Altering primary key or index key column types is not supported. Table: %s; Column: %s
DB-CORE-10234
メッセージ
Invalid column type conversion from %s to %s. Column: %s
DB-CORE-10235
メッセージ
Cassandra does not support the feature for altering column types
DB-CORE-10236
メッセージ
Cosmos DB does not support the feature for altering column types
DB-CORE-10237
メッセージ
DynamoDB does not support the feature for altering column types
DB-CORE-10238
メッセージ
SQLite does not support the feature for altering column types
DB-CORE-10239
メッセージ
Oracle does not support column type conversion from %s to %s
DB-CORE-10240
メッセージ
Db2 does not support column type conversion from %s to %s
DB-CORE-10241
メッセージ
The operations are empty
DB-CORE-10242
メッセージ
Multiple operations are not supported in single CRUD operation transactions
DB-CORE-10243
メッセージ
This batch result doesn't have a get result
DB-CORE-10244
メッセージ
This batch result doesn't have a scan result
DB-CORE-10245
メッセージ
TiDB does not support column type conversion from %s to %s
DB-CORE-10246
メッセージ
With Oracle, using a BLOB column as partition key, clustering key or secondary index is not supported.
DB-CORE-10247
メッセージ
With Oracle, setting an ordering on a BLOB column when using a cross partition scan operation is not supported. Ordering: %s
DB-CORE-10248
メッセージ
With Oracle, setting a condition on a BLOB column when using a selection operation is not supported. Condition: %s
DB-CORE-10249
メッセージ
The namespace has non-ScalarDB tables and cannot be dropped. Namespace: %s; Tables in the namespace: %s
DB-CORE-10250
メッセージ
Import-related functionality is not supported in Object Storage
DB-CORE-10251
メッセージ
Index-related functionality is not supported in Object Storage
DB-CORE-10252
メッセージ
Object Storage does not support the feature for dropping columns
DB-CORE-10253
メッセージ
Object Storage does not support the feature for renaming columns
DB-CORE-10254
メッセージ
Renaming tables is not supported in Object Storage
DB-CORE-10255
メッセージ
Object Storage does not support the feature for altering column types
DB-CORE-10256
メッセージ
Cross-partition scan with ordering is not supported in Object Storage
DB-CORE-10257
メッセージ
The value of the column %s in the primary key contains an illegal character. Value: %s
DB-CORE-10258
メッセージ
Specifying transaction metadata columns in the projection is not allowed. Table: %s; Column: %s
DB-CORE-10259
メッセージ
Specifying transaction metadata columns in the ordering is not allowed. Table: %s; Column: %s
DB-CORE-10260
メッセージ
Get operations using a secondary index are not allowed in the SERIALIZABLE isolation level without before-image indexes. Run repairTable() to create before-image indexes for the table, which will enable index-based Get operations in the SERIALIZABLE isolation level
DB-CORE-10261
メッセージ
Scan operations using a secondary index are not allowed in the SERIALIZABLE isolation level without before-image indexes. Run repairTable() to create before-image indexes for the table, which will enable index-based Scan operations in the SERIALIZABLE isolation level
DB-CORE-10262
メッセージ
Conditions on indexed columns in cross-partition scan operations are not allowed in the SERIALIZABLE isolation level without before-image indexes. Run repairTable() to create before-image indexes for the table, which will enable conditions on indexed columns in cross-partition scan operations in the SERIALIZABLE isolation level
DB-CORE-10263
メッセージ
The service account key for Cloud Storage was not found.
DB-CORE-10264
メッセージ
Failed to load the service account key for Cloud Storage.
DB-CORE-10265
メッセージ
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
メッセージ
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
メッセージ
The virtual table functionality is not supported in DynamoDB
DB-CORE-10268
メッセージ
The source tables must have the same primary key. Left source table: %s; Right source table: %s
DB-CORE-10269
メッセージ
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
メッセージ
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
メッセージ
The source tables have conflicting non-key column names. Left source table: %s; Right source table: %s; Conflicting columns: %s
DB-CORE-10272
メッセージ
Virtual tables cannot be used as source tables. Source table: %s
DB-CORE-10273
メッセージ
The source tables must be in the same storage. Left source table: %s; Right source table: %s
DB-CORE-10274
メッセージ
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
メッセージ
Source tables cannot be dropped while virtual tables depending on them exist. Source table: %s; Virtual tables: %s
DB-CORE-10276
メッセージ
The DeleteIf IS_NULL condition for right source table columns is not allowed in LEFT_OUTER virtual tables. Virtual table: %s
DB-CORE-10277
メッセージ
The transaction metadata decoupling feature is not supported in the storage. Storage %s
DB-CORE-10278
メッセージ
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-10279
メッセージ
The size of a BLOB column value exceeds the maximum allowed size of %d bytes. Column: %s; Size: %d bytes
DB-CORE-10280
メッセージ
The condition for the Update operation must be UpdateIf or UpdateIfExists. Operation: %s
DB-CORE-10281
メッセージ
The column definition must be specified since %s is specified as a secondary index
DB-CORE-10282
メッセージ
This column value is out of range for BigInt in Object Storage. Value: %s
DB-CORE-10283
メッセージ
Spanner does not support renaming columns
DB-CORE-10284
メッセージ
Spanner does not support column type conversion except from BLOB to TEXT. Conversion: from %s to %s
DB-CORE-10285
メッセージ
Spanner does not support renaming tables
DB-CORE-10286
メッセージ
Spanner uses '\' as the default LIKE escape character and it cannot be configured or disabled. Escape character: '%s'
DB-CORE-10287
メッセージ
Failed to load the service account key for Spanner
DB-CORE-10288
メッセージ
All %d Spanner credential slots are already in use. ScalarDB's Spanner adapter supports up to that many distinct sets of Spanner credentials per JVM
DB-CORE-2xxxx ステータスコード
以下は、同時実行エラーカテゴリのステータスコードとメッセージです。
DB-CORE-20000
メッセージ
No mutation was applied
DB-CORE-20001
メッセージ
Logging failed in the batch
DB-CORE-20002
メッセージ
The operation failed in the batch with type %s
DB-CORE-20003
メッセージ
An error occurred in the batch. Details: %s
DB-CORE-20004
メッセージ
A Paxos phase in the CAS operation failed
DB-CORE-20005
メッセージ
The learn phase in the CAS operation failed
DB-CORE-20006
メッセージ
A simple write operation failed
DB-CORE-20007
メッセージ
An error occurred in the mutation. Details: %s
DB-CORE-20008
メッセージ
A RetryWith error occurred in the mutation. Details: %s
DB-CORE-20009
メッセージ
A transaction conflict occurred in the mutation. Details: %s
DB-CORE-20010
メッセージ
A transaction conflict occurred in the mutation. Details: %s
DB-CORE-20011
メッセージ
A conflict occurred. Please try restarting the transaction. Details: %s
DB-CORE-20012
メッセージ
The %s condition of the %s operation is not satisfied. Targeting column(s): %s
DB-CORE-20013
メッセージ
The record being prepared already exists. Details: %s
DB-CORE-20014
メッセージ
A conflict occurred when preparing records. Details: %s
DB-CORE-20015
メッセージ
The committing state in the coordinator failed. The transaction has been aborted. Details: %s
DB-CORE-20016
メッセージ
A conflict occurred during implicit pre-read. Details: %s
DB-CORE-20017
メッセージ
This record needs to be recovered. Table: %s; Partition Key: %s; Clustering Key: %s; Transaction ID that wrote the record: %s
DB-CORE-20018
メッセージ
The record does not exist, so the %s condition is not satisfied
DB-CORE-20019
メッセージ
The record exists, so the %s condition is not satisfied
DB-CORE-20020
メッセージ
The condition on the column '%s' is not satisfied
DB-CORE-20022
メッセージ
An anti-dependency was found. The transaction has been aborted
DB-CORE-20023
メッセージ
A transaction conflict occurred in the Insert operation
DB-CORE-20024
メッセージ
The %s condition of the %s operation is not satisfied. Targeting column(s): %s
DB-CORE-20025
メッセージ
A transaction conflict occurred in the Insert operation
DB-CORE-20026
メッセージ
A conflict occurred when committing records. Details: %s
DB-CORE-20027
メッセージ
A transaction conflict occurred in the mutation. Details: %s
DB-CORE-20028
メッセージ
Before-image index recovery retry limit exceeded. Transaction ID: %s
DB-CORE-20029
メッセージ
Records that need recovery were found during the before-image index check when closing the scanner. Transaction ID: %s
DB-CORE-3xxxx ステータスコード
以下は、内部エラーカテゴリのステータスコードとメッセージです。
DB-CORE-30000
メッセージ
Creating the namespace failed. Namespace: %s
DB-CORE-30001
メッセージ
Dropping the namespace failed. Namespace: %s
DB-CORE-30002
メッセージ
Creating the table failed. Table: %s
DB-CORE-30003
メッセージ
Dropping the table failed. Table: %s
DB-CORE-30004
メッセージ
Truncating the table failed. Table: %s
DB-CORE-30005
メッセージ
Creating the index failed. Table: %s, Column: %s
DB-CORE-30006
メッセージ
Dropping the index failed. Table: %s, Column: %s
DB-CORE-30007
メッセージ
Getting the table metadata failed. Table: %s
DB-CORE-30008
メッセージ
Getting the table names in the namespace failed. Namespace: %s
DB-CORE-30009
メッセージ
Checking the namespace existence failed. Namespace: %s
DB-CORE-30010
メッセージ
Checking the table existence failed. Table: %s
DB-CORE-30011
メッセージ
Checking the index existence failed. Table: %s; Column: %s
DB-CORE-30012
メッセージ
Repairing the namespace failed. Namespace: %s
DB-CORE-30013
メッセージ
Repairing the table failed. Table: %s
DB-CORE-30014
メッセージ
Adding a new column to the table failed. Table: %s; Column: %s; ColumnType: %s
DB-CORE-30015
メッセージ
Getting the namespace names failed
DB-CORE-30016
メッセージ
Getting the table metadata of the table being imported failed. Table: %s
DB-CORE-30017
メッセージ
Importing the table failed. Table: %s
DB-CORE-30018
メッセージ
Adding the raw column to the table failed. Table: %s; Column: %s; ColumnType: %s
DB-CORE-30019
メッセージ
Upgrading the ScalarDB environment failed
DB-CORE-30020
メッセージ
Something wrong because WriteType is neither CAS nor SIMPLE
DB-CORE-30021
メッセージ
An error occurred in the selection. Details: %s
DB-CORE-30022
メッセージ
An error occurred in the mutation. Details: %s
DB-CORE-30023
メッセージ
An error occurred in the selection. Details: %s
DB-CORE-30024
メッセージ
An error occurred in the mutation. Details: %s
DB-CORE-30025
メッセージ
An error occurred in the selection. Details: %s
DB-CORE-30026
メッセージ
An error occurred in the mutation. Details: %s
DB-CORE-30027
メッセージ
An error occurred in the selection. Details: %s
DB-CORE-30028
メッセージ
Fetching the next result failed. Details: %s
DB-CORE-30029
メッセージ
Rolling back the transaction failed. Details: %s
DB-CORE-30030
メッセージ
Committing the transaction failed. Details: %s
DB-CORE-30031
メッセージ
The Get operation failed. Details: %s
DB-CORE-30032
メッセージ
The Scan operation failed. Details: %s
DB-CORE-30033
メッセージ
The Put operation failed. Details: %s
DB-CORE-30034
メッセージ
The Delete operation failed. Details: %s
DB-CORE-30035
メッセージ
Beginning a transaction failed. Details: %s
DB-CORE-30036
メッセージ
Preparing records failed. Details: %s
DB-CORE-30037
メッセージ
Validation failed. Details: %s
DB-CORE-30038
メッセージ
Executing implicit pre-read failed. Details: %s
DB-CORE-30039
メッセージ
Reading a record from the underlying storage failed. Details: %s
DB-CORE-30040
メッセージ
Scanning records from the underlying storage failed. Details: %s
DB-CORE-30041
メッセージ
Rollback failed because the transaction has already been committed
DB-CORE-30042
メッセージ
Rollback failed
DB-CORE-30043
メッセージ
The Insert operation failed. Details: %s
DB-CORE-30044
メッセージ
The Upsert operation failed. Details: %s
DB-CORE-30045
メッセージ
The Update operation failed. Details: %s
DB-CORE-30046
メッセージ
Handling the before-preparation hook failed. Details: %s
DB-CORE-30054
メッセージ
Getting the scanner failed. Details: %s
DB-CORE-30055
メッセージ
Closing the scanner failed. Details: %s
DB-CORE-30056
メッセージ
Getting the storage information failed. Namespace: %s
DB-CORE-30057
メッセージ
Recovering records failed. Details: %s
DB-CORE-30058
メッセージ
Committing records failed. Details: %s
DB-CORE-30059
メッセージ
Dropping a column from the table failed. Table: %s; Column: %s
DB-CORE-30060
メッセージ
Renaming a column failed. Table: %s; Old column name: %s; New column name: %s
DB-CORE-30061
メッセージ
Renaming a table failed. Old table name: %s; New table name: %s
DB-CORE-30062
メッセージ
Altering a column type failed. Table: %s; Column: %s; New column type: %s
DB-CORE-30063
メッセージ
Getting the MySQL JDBC connection metadata failed. Details: %s
DB-CORE-30064
メッセージ
An error occurred in the selection. Details: %s
DB-CORE-30065
メッセージ
An error occurred in the mutation. Details: %s
DB-CORE-30066
メッセージ
Creating the virtual table failed. Virtual table: %s; Left source table: %s; Right source table: %s
DB-CORE-30067
メッセージ
Getting the virtual table information failed. Table: %s
DB-CORE-4xxxx ステータスコード
以下は、不明なトランザクションステータスエラーカテゴリのステータスコードとメッセージです。
DB-CORE-40000
メッセージ
Rolling back the transaction failed. Details: %s
DB-CORE-40001
メッセージ
Committing state failed with NoMutationException, but the coordinator status does not exist. Details: %s
DB-CORE-40002
メッセージ
The coordinator status cannot be retrieved. Details: %s
DB-CORE-40003
メッセージ
The coordinator status is unknown. Details: %s
DB-CORE-40004
メッセージ
Aborting state failed with NoMutationException, but the coordinator status does not exist. Details: %s
DB-CORE-40005
メッセージ
One-phase committing records failed. Details: %s