Skip to main content
Version: 3.16
Features and pricing

ScalarDB Cluster Error Codes

This page provides a list of error codes in ScalarDB Cluster.

Error code classes and descriptions​

ClassDescription
DB-CLUSTER-1xxxxErrors for the user error category
DB-CLUSTER-2xxxxErrors for the concurrency error category
DB-CLUSTER-3xxxxErrors for the internal error category

DB-CLUSTER-1xxxx status codes​

The following are status codes and messages for the user error category.

DB-CLUSTER-10000​

Message

The namespace does not exist. Namespace: %s

DB-CLUSTER-10001​

Message

The table does not exist. Table: %s

DB-CLUSTER-10002​

Message

The user does not exist. User: %s

DB-CLUSTER-10004​

Message

The get type is unspecified

DB-CLUSTER-10005​

Message

The get type is unrecognized

DB-CLUSTER-10006​

Message

The value of the column is not set. Column: %s

DB-CLUSTER-10007​

Message

The scan type is unspecified

DB-CLUSTER-10008​

Message

The scan type is unrecognized

DB-CLUSTER-10009​

Message

The order is unspecified

DB-CLUSTER-10010​

Message

The order is unrecognized

DB-CLUSTER-10011​

Message

The clustering order is unspecified

DB-CLUSTER-10012​

Message

The clustering order is unrecognized

DB-CLUSTER-10013​

Message

The put condition type is unspecified

DB-CLUSTER-10014​

Message

The put condition type is unrecognized

DB-CLUSTER-10015​

Message

The delete condition type is unspecified

DB-CLUSTER-10016​

Message

The delete condition type is unrecognized

DB-CLUSTER-10017​

Message

The operator is unspecified

DB-CLUSTER-10018​

Message

The operator is unrecognized

DB-CLUSTER-10019​

Message

The mutation is not set

DB-CLUSTER-10020​

Message

The data type is unspecified

DB-CLUSTER-10021​

Message

The data type is unrecognized

DB-CLUSTER-10022​

Message

The user option is unspecified

DB-CLUSTER-10023​

Message

The user option is unrecognized

DB-CLUSTER-10024​

Message

The privilege is unspecified

DB-CLUSTER-10025​

Message

The privilege is unrecognized

DB-CLUSTER-10026​

Message

The username is not set

DB-CLUSTER-10027​

Message

This feature is not supported in ScalarDB Cluster

DB-CLUSTER-10028​

Message

The property 'scalar.db.contact_points' must not be empty

DB-CLUSTER-10029​

Message

The property 'scalar.db.contact_points' must be prefixed with 'indirect:' or 'direct-kubernetes:'

DB-CLUSTER-10030​

Message

The format of the property 'scalar.db.contact_points' for direct-kubernetes client mode is 'direct-kubernetes:<NAMESPACE_NAME>/<ENDPOINT_NAME>' or 'direct-kubernetes:<ENDPOINT_NAME>'

DB-CLUSTER-10031​

Message

The property 'scalar.db.sql.cluster_mode.contact_points' must not be empty

DB-CLUSTER-10032​

Message

The property 'scalar.db.sql.cluster_mode.contact_points' must be prefixed with 'indirect:' or 'direct-kubernetes:'

DB-CLUSTER-10033​

Message

The format of the property 'scalar.db.sql.cluster_mode.contact_points' for direct-kubernetes client mode is 'direct-kubernetes:<NAMESPACE_NAME>/<ENDPOINT_NAME>' or 'direct-kubernetes:<ENDPOINT_NAME>'

DB-CLUSTER-10035​

Message

The update condition type is unspecified

DB-CLUSTER-10036​

Message

The update condition type is unrecognized

DB-CLUSTER-10037​

Message

The two-phase commit interface is not supported

DB-CLUSTER-10039​

Message

The policy state is unspecified

DB-CLUSTER-10040​

Message

The policy state is unrecognized

DB-CLUSTER-10041​

Message

The access mode is unspecified

DB-CLUSTER-10042​

Message

The access mode is unrecognized

DB-CLUSTER-10043​

Message

The service does not exist. Service Class: %s

DB-CLUSTER-10044​

Message

The policy does not exist. Policy: %s

DB-CLUSTER-10045​

Message

The property 'scalar.db.embedding.client.contact_points' must not be empty

DB-CLUSTER-10046​

Message

The property 'scalar.db.embedding.client.contact_points' must be prefixed with 'indirect:' or 'direct-kubernetes:'

DB-CLUSTER-10047​

Message

The format of the property 'scalar.db.embedding.client.contact_points' for direct-kubernetes client mode is 'direct-kubernetes:<NAMESPACE_NAME>/<ENDPOINT_NAME>' or 'direct-kubernetes:<ENDPOINT_NAME>'

DB-CLUSTER-10048​

Message

The embeddings must be provided

DB-CLUSTER-10049​

Message

Only one embedding can be added with an embedding ID

DB-CLUSTER-10050​

Message

Text segments cannot be provided when adding an embedding with an embedding ID

DB-CLUSTER-10051​

Message

Both embedding IDs and a filter cannot be provided

DB-CLUSTER-10052​

Message

Unsupported embedding store type. Type: %s

DB-CLUSTER-10053​

Message

Unsupported embedding model type. Type: %s

DB-CLUSTER-10054​

Message

The filter is not set

DB-CLUSTER-10055​

Message

Unsupported metadata value type. Type: %s

DB-CLUSTER-10056​

Message

The metadata value is not set

DB-CLUSTER-2xxxx status codes​

The following are status codes and messages for the concurrency error category.

DB-CLUSTER-20000​

Message

The hop limit is exceeded

DB-CLUSTER-20001​

Message

A transaction associated with the specified transaction ID is not found. The transaction might have expired, or the cluster node that handled the transaction might have been restarted. Transaction ID: %s

DB-CLUSTER-20002​

Message

A scanner associated with the specified scanner ID is not found. The scanner might have expired, or the cluster node that handled the scanner might have been restarted. Transaction ID: %s; Scanner ID: %s

DB-CLUSTER-3xxxx status codes​

The following are status codes and messages for the internal error category.

DB-CLUSTER-30000​

Message

Getting local IP addresses failed

DB-CLUSTER-30001​

Message

Getting a cluster node object from the cache failed. Cluster Node IP Address: %s

DB-CLUSTER-30002​

Message

The ring is empty

DB-CLUSTER-30003​

Message

Getting the Kubernetes API client failed

DB-CLUSTER-30004​

Message

Reading the Kubernetes endpoint failed. Namespace: %s; Name: %s; Code: %d; Response Headers: %s; Response Body: %s

DB-CLUSTER-30005​

Message

Configuring TLS failed

DB-CLUSTER-30006​

Message

No nearest cluster nodes are found