メインコンテンツまでスキップ
バージョン: 3.16

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

DB-CORE-10002

メッセージ

The index key is not properly specified. Operation: %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

DB-CORE-10010

メッセージ

The clustering key boundary is not properly specified. Operation: %s

DB-CORE-10011

メッセージ

The start clustering key is not properly specified. Operation: %s

DB-CORE-10012

メッセージ

The end clustering key is not properly specified. Operation: %s

DB-CORE-10013

メッセージ

Orderings are not properly specified. Operation: %s

DB-CORE-10014

メッセージ

The specified ordering column is not found. Ordering: %s, Operation: %s

DB-CORE-10015

メッセージ

The condition is not properly specified. Operation: %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

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

DB-CORE-10021

メッセージ

The clustering key is not properly specified. Operation: %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. 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 null or 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. Namespace: %s

DB-CORE-10086

メッセージ

The table name is not acceptable. Table: %s

DB-CORE-10087

メッセージ

Importing tables is not allowed in the RDB engine. RDB engine: %s

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. 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-10104

メッセージ

Writing data already-deleted by the same transaction is not allowed

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-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

DB-CORE-20014

メッセージ

A conflict occurred when preparing records

DB-CORE-20015

メッセージ

The committing state in the coordinator failed. The transaction has been aborted

DB-CORE-20016

メッセージ

A conflict occurred during implicit pre-read

DB-CORE-20017

メッセージ

This record needs to be recovered

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

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

DB-CORE-30037

メッセージ

Validation failed

DB-CORE-30038

メッセージ

Executing implicit pre-read failed

DB-CORE-30039

メッセージ

Reading a record from the underlying storage failed

DB-CORE-30040

メッセージ

Scanning records from the underlying storage failed

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 snapshot 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

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

DB-CORE-40002

メッセージ

The state cannot be retrieved

DB-CORE-40003

メッセージ

The coordinator status is unknown

DB-CORE-40004

メッセージ

Aborting state failed with NoMutationException, but the coordinator status does not exist