Skip to main content
Version: 3.15

ScalarDB SQL Error Codes

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

Error code classes and descriptions​

ClassDescription
DB-SQL-1xxxxErrors for the user error category

DB-SQL-1xxxx status codes​

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

DB-SQL-10000​

Message

The namespace does not exist. Namespace: %s

DB-SQL-10001​

Message

The table does not exist. Table: %s

DB-SQL-10002​

Message

The column %s does not exist

DB-SQL-10003​

Message

The column does not exist. Table: %s; Column: %s

DB-SQL-10004​

Message

The column index is out of bounds. Index: %d; Size: %d

DB-SQL-10005​

Message

A positional bind marker is not allowed when binding named values

DB-SQL-10006​

Message

A named bind marker is not allowed when binding positional values

DB-SQL-10007​

Message

Cannot convert BLOB values to SQL. Please use a bind marker for a BLOB value and bind it separately

DB-SQL-10008​

Message

No namespace name has been specified. Set a default namespace name, or explicitly specify a namespace name

DB-SQL-10009​

Message

Zero bytes may not occur in string parameters

DB-SQL-10010​

Message

Mixing positional values and named values is not allowed

DB-SQL-10011​

Message

Preparing a transaction is supported only in two-phase commit transaction mode

DB-SQL-10012​

Message

Validating a transaction is supported only in two-phase commit transaction mode

DB-SQL-10013​

Message

The previous transaction is still in progress. Commit, roll back, or suspend the previous transaction first

DB-SQL-10014​

Message

This SQL session has already been closed

DB-SQL-10015​

Message

A transaction has not begun

DB-SQL-10016​

Message

The type %s is not supported

DB-SQL-10017​

Message

No connection mode implementations are found. Please add a connection mode implementation to the classpath

DB-SQL-10018​

Message

The connection mode is not specified, but multiple connection mode implementations are found. Specify one of the following connection modes: %s

DB-SQL-10019​

Message

The connection mode '%s' is not found. Specify one of the following connection modes: %s

DB-SQL-10020​

Message

Access denied: You need the %s privilege on the namespace %s to execute this operation

DB-SQL-10021​

Message

Access denied: You need the %s privilege on the table %s to execute this operation

DB-SQL-10022​

Message

Access denied: You can't grant the %s privilege because you don't have the same privilege on the table %s

DB-SQL-10023​

Message

Access denied: You can't grant the %s privilege because you don't have the same privilege on the namespace %s

DB-SQL-10024​

Message

Access denied: You can't revoke the %s privilege because you don't have the same privilege on the table %s

DB-SQL-10025​

Message

Access denied: You can't revoke the %s privilege because you don't have the same privilege on the namespace %s

DB-SQL-10026​

Message

Syntax error. Line %d:%d %s

DB-SQL-10027​

Message

Syntax error. Multiple PRIMARY KEYs specified (exactly one required)

DB-SQL-10028​

Message

Cannot grant the INSERT privilege if the user doesn't have the UPDATE privilege

DB-SQL-10029​

Message

Cannot grant the UPDATE privilege if the user doesn't have the INSERT privilege

DB-SQL-10030​

Message

Cannot grant the UPDATE privilege if the user doesn't have the SELECT privilege

DB-SQL-10031​

Message

Cannot grant the DELETE privilege if the user doesn't have the SELECT privilege

DB-SQL-10032​

Message

Cannot revoke the SELECT privilege if the user has the UPDATE privilege

DB-SQL-10033​

Message

Cannot revoke the SELECT privilege if the user has the DELETE privilege

DB-SQL-10034​

Message

Cannot revoke the INSERT privilege if the user has the UPDATE privilege

DB-SQL-10035​

Message

Cannot revoke the UPDATE privilege if the user has the INSERT privilege

DB-SQL-10036​

Message

A non-clustering-key column is specified in the CLUSTERING ORDER directive. Column: %s

DB-SQL-10037​

Message

The order of the columns in the CLUSTERING ORDER directive must match the order for the clustering key (%s must appear before %s)

DB-SQL-10038​

Message

The CLUSTERING ORDER is missing for the column %s

DB-SQL-10039​

Message

Empty SQL is specified

DB-SQL-10040​

Message

Multiple SQLs are not allowed

DB-SQL-10041​

Message

The column %s is ambiguous

DB-SQL-10042​

Message

The column %s cannot be specified in the %s clause. Only the columns in the table %s can be specified in the %s clause

DB-SQL-10043​

Message

An unbound bind marker is still in the escape character of the LIKE predicate for the column %s

DB-SQL-10044​

Message

The escape character must be a TEXT value for the LIKE predicate for the column %s

DB-SQL-10045​

Message

The value of the predicate must not be null unless the operator is 'IS NULL' or 'IS NOT NULL'. Predicate: %s

DB-SQL-10046​

Message

An unbound bind marker is still in the LIMIT clause

DB-SQL-10047​

Message

The LIMIT must be an INT value

DB-SQL-10048​

Message

Unmatched column names or values

DB-SQL-10049​

Message

The column %s is specified twice

DB-SQL-10050​

Message

All primary key columns must be specified in the INSERT or UPSERT statement

DB-SQL-10051​

Message

An unbound bind marker is still in the value of the column %s

DB-SQL-10052​

Message

Unmatched column type. The type of the column %s should be %s, but a boolean value (BOOLEAN) is specified

DB-SQL-10053​

Message

Unmatched column type. The type of the column %s should be %s, but a decimal number (INT or BIGINT) is specified

DB-SQL-10054​

Message

Unmatched column type. The type of the column %s should be %s, but a floating point number (FLOAT or DOUBLE) is specified

DB-SQL-10055​

Message

Unmatched column type. The type of the column %s should be %s, but a string (TEXT, DATE, TIME, TIMESTAMP, or TIMESTAMPTZ) is specified

DB-SQL-10056​

Message

Unmatched column type. The type of the column %s should be %s, but a BOOLEAN value is specified

DB-SQL-10057​

Message

Unmatched column type. The type of the column %s should be %s, but an INT value is specified

DB-SQL-10058​

Message

Unmatched column type. The type of the column %s should be %s, but a BIGINT value is specified

DB-SQL-10059​

Message

Unmatched column type. The type of the column %s should be %s, but a FLOAT value is specified

DB-SQL-10060​

Message

Unmatched column type. The type of the column %s should be %s, but a DOUBLE value is specified

DB-SQL-10061​

Message

Unmatched column type. The type of the column %s should be %s, but a TEXT value is specified

DB-SQL-10062​

Message

Unmatched column type. The type of the column %s should be %s, but a BLOB value is specified

DB-SQL-10063​

Message

RIGHT OUTER JOIN can only be specified as the first join

DB-SQL-10064​

Message

The JOIN predicate is not specified properly. Predicate: %s

DB-SQL-10065​

Message

The data types of the columns in the JOIN predicate do not match. Predicate: %s

DB-SQL-10066​

Message

The column %s is specified twice in the JOIN predicates. Predicates: %s

DB-SQL-10067​

Message

Either all primary key columns or an indexed column for the table %s must be specified in the JOIN predicates. Predicates: %s

DB-SQL-10068​

Message

Cannot issue mutation DML SQLs such as INSERT, UPDATE or DELETE with executeQuery()

DB-SQL-10069​

Message

Cannot issue SELECT SQLs with executeUpdate()

DB-SQL-10070​

Message

The TWO_PHASE_COMMIT_TRANSACTION mode is not supported in the current transaction manager

DB-SQL-10071​

Message

The encrypted column %s is not allowed in the %s clause

DB-SQL-10072​

Message

The user %s does not exist

DB-SQL-10073​

Message

Unmatched column type. The type of the column %s should be %s, but a DATE value is specified

DB-SQL-10074​

Message

Unmatched column type. The type of the column %s should be %s, but a TIME value is specified

DB-SQL-10075​

Message

Unmatched column type. The type of the column %s should be %s, but a TIMESTAMP value is specified

DB-SQL-10076​

Message

Unmatched column type. The type of the column %s should be %s, but a TIMESTAMPTZ value is specified

DB-SQL-10077​

Message

The policy %s does not exist
This website uses cookies to enhance the visitor experience. By continuing to use this website, you acknowledge that you have read and understood our privacy policy and consent to the use of cookies to help improve your browsing experience and provide you with personalized content.