|
Error code
|
Class
|
Type
|
Description
|
|---|---|---|---|
|
13001
|
Table
|
Error
|
Illegal character constant constant.
An illegal character constant was found in the SQL statement.
|
|
13002
|
Table
|
Error
|
Type CHAR not allowed for arithmetic.
You have entered a calculation having a character type constant. Character constants are not supported in arithmetic.
|
|
13003
|
Table
|
Error
|
Aggregate function not available for ordinary call.
The aggregate function, such as SUM(), is called as an ordinary function. This is not allowed. For example, the following calls are illegal: SELECT * FROM TAB1 WHERE SUM(INT_COL) > 5; CALL SUM(1);
|
|
13004
|
Table
|
Error
|
Illegal aggregate function parameter parameter.
An illegal parameter has been given to an aggregate function. Aggregate function parameters can only be column names or numbers.
|
|
13005
|
Table
|
Error
|
SUM and AVG not supported for CHAR type.
Aggregate functions SUM and AVG are not supported for character type parameters.
|
|
13006
|
Table
|
Error
|
SUM or AVG not supported for DATE type.
Aggregate functions SUM and AVG are not supported for date type parameters.
|
|
13007
|
Table
|
Error
|
Function function is not defined.
The function you tried to use is not defined.
|
|
13008
|
Table
|
Error
|
Illegal parameter to ADD function.
|
|
13009
|
Table
|
Error
|
Division by zero.
A division by zero has occurred.
|
|
13011
|
Table
|
Error
|
Table table does not exist.
You have referenced a table which does not exist or you do not have REFERENCES privilege on the table.
|
|
13013
|
Table
|
Error
|
Table name table conflicts with an existing entity.
Choose a unique name for a table. The specified name is already used.
|
|
13014
|
Table
|
Error
|
Index index does not exist.
You have referenced an index which does not exist.
|
|
13015
|
Table
|
Error
|
Column column does not exist on table table.
You have referenced a column in a table which does not exist.
|
|
13018
|
Table
|
Error
|
Join table is not supported
Joined tables are not supported in this version of solidDB®.
|
|
13019
|
Table
|
Error
|
Transaction savepoints are not supported.
Transaction savepoints are not supported in this version of solidDB®.
|
|
13020
|
Table
|
Error
|
Default values are not supported.
Default column values are not supported in this version of solidDB®.
|
|
13022
|
Table
|
Error
|
Descending keys are not supported.
Descending keys are not supported in this version of solidDB®.
|
|
13023
|
Table
|
Error
|
Schema is not supported.
Schema is not supported in this version of solidDB®.
|
|
13025
|
Table
|
Error
|
Update through a cursor with no current row.
You have tried to update using a cursor, but you do not have a current row in the cursor.
|
|
13026
|
Table
|
Error
|
Delete through a cursor with no current row
You have tried to delete using a cursor, but you do not have a current row in the cursor.
|
|
13028
|
Table
|
Error
|
View view_name does not exist.
You have referenced a view which does not exist.
|
|
13029
|
Table
|
Error
|
View name view_name conflicts with an existing entity.
Choose a unique name for a view. The specified name is already used.
|
|
13030
|
Table
|
Error
|
No value specified for NOT NULL column column.
You have not specified a value for a column which is defined NOT NULL.
|
|
13031
|
Table
|
Error
|
Data dictionary operation is active for accessed table or key.
You can not access the table or key, because a data dictionary operation is currently active. Try again after the data dictionary operation has completed.
|
|
13032
|
Table
|
Error
|
Illegal type type.
You have tried to create a table with a column having an illegal type.
|
|
13033
|
Table
|
Error
|
Illegal parameter parameter for type type.
The type of the parameter you entered is illegal in this column.
|
|
13034
|
Table
|
Error
|
Illegal constant constant.
You have entered an illegal constant.
|
|
13035
|
Table
|
Error
|
Illegal INTEGER constant constant.
You have entered an illegal integer type constant. Check the syntax of the statement and try again.
|
|
13036
|
Table
|
Error
|
Illegal DECIMAL constant constant.
You have entered an illegal decimal type constant. Check the decimal number and try again.
|
|
13037
|
Table
|
Error
|
Illegal DOUBLE PREC constant constant.
Typically, this is a general parse error. The SQL statement may contain a syntax error before the constant. As a last resort, the parser has attempted to parse a DOUBLE PREC constant, but has failed.
This error also occurs if you entered an illegal double precision type constant.
(More specifically, this error occurs when a space is placed between the asterisk and the closing parenthesis ("* )") in an optimizer hint.)
In any of these cases, be sure to check the syntax of the statement and try again.
|
|
13038
|
Table
|
Error
|
Illegal REAL constant constant.
You have entered an illegal real type constant. Check the real number and try again.
|
|
13039
|
Table
|
Error
|
Illegal assignment.
You have tried to assign an illegal value for a column. For example, you may have tried to assign a value that was too large or was of the wrong data type.
|
|
13040
|
Table
|
Error
|
Aggregate function function is not defined.
The aggregate function you tried to use is not supported.
|
|
13041
|
Table
|
Error
|
Type DATE not allowed for arithmetic.
DATE type columns or constants are not allowed in arithmetic.
|
|
13042
|
Table
|
Error
|
Power® arithmetic not allowed for NUMERIC and DECIMAL data type. Decimal and numeric data types do not support power arithmetic.
|
|
13043
|
Table
|
Error
|
Illegal date constant constant.
A date constant is illegal. The correct form for date constants is: YYYY-MM-DD.
|
|
13046
|
Table
|
Error
|
Illegal user name user.
User name entered is not legal. A legal user name is at least 2 and at most 31 characters in length. A user name may contain characters from A to Z, numbers from 0 to 9 and underscore character _.
|
|
13047
|
Table
|
Error
|
No privileges for operation.
You have no privileges for the attempted operation. To carry out this operation, you must be granted appropriate privileges. Alternatively, the operation can be performed by another user who already has the appropriate privileges. See the GRANT statement for more information.
Note If you are trying to drop a catalog that you previously created, and you get this error message, then your SYS_ADMIN_ROLE (i.e. DBA) privileges have been revoked. Only the creator of the database or users having SYS_ADMIN_ROLE (i.e. DBA) have privileges to create or drop a catalog. Even the creator of a catalog cannot drop that catalog if she loses SYS_ADMIN_ROLE privileges. (Creating a catalog, unlike creating most other objects (such as tables) does not make you the owner; instead, the ownership of all catalogs belongs to the DBA/ SYS_ADMIN_ROLE.)
|
|
13048
|
Table
|
Error
|
No grant option privilege for entity name.
You have no privileges to grant privileges for the entity.
|
|
13049
|
Table
|
Error
|
Column privileges cannot be granted WITH GRANT OPTION
Granting column privileges WITH GRANT OPTION is not supported in this version of solidDB®.
|
|
13050
|
Table
|
Error
|
Too long constraint value.
Maximum constraint length has been exceeded. Maximum constraint length is 255 characters.
|
|
13051
|
Table
|
Error
|
Illegal column name column.
You have tried to create a table with an illegal column name.
|
|
13052
|
Table
|
Error
|
Illegal comparison operator operator for a pseudo column column.
You have tried to use an illegal comparison operator for a pseudo column. Legal comparison operators for pseudo columns are: equality = and non-equality <>.
|
|
13053
|
Table
|
Error
|
Illegal data type for a pseudo column.
You have tried to use an illegal data type for a pseudo column. Data type of pseudo columns is BINARY.
|
|
13054
|
Table
|
Error
|
Illegal pseudo column data, maybe data is not received using pseudo column.
You have tried to compare pseudo column data with non-pseudo column data. Pseudo column data can only be compared with data received from a pseudo column.
|
|
13055
|
Table
|
Error
|
Update not allowed on pseudo column. Updates are not allowed on pseudo columns.
|
|
13056
|
Table
|
Error
|
Insert not allowed on pseudo column. Inserts are not allowed on pseudo columns.
|
|
13057
|
Table
|
Error
|
Index name index already exists.
You have tried to create an index, but an index with the same name already exists. Use another name for the index.
|
|
13058
|
Table
|
Error
|
Constraint checks were not satisfied on column column.
Column has constraint checks which were not satisfied during an insert or update.
|
|
13059
|
Table
|
Error
|
Reserved system name name.
You tried to use a name which is a reserved system name such as PUBLIC and SYS_ADMIN_ROLE.
|
|
13060
|
Table
|
Error
|
User name user not found.
You tried to reference a user name which is not created.
|
|
13061
|
Table
|
Error
|
Role name role not found.
You tried to reference a role name which is not created.
|
|
13062
|
Table
|
Error
|
Admin option is not supported.
Admin option is not supported in this version of solidDB®.
|
|
13063
|
Table
|
Error
|
Name name already exists.
You tried to use a role or user which already exists. User names and role names must all be different, that is, you can not have a user named HOBBES and a role named HOBBES.
|
|
13064
|
Table
|
Error
|
Not a valid user name user.
You tried to create an invalid user name. A valid user name has at least 2 characters and at most 31 characters. A user name may contain characters from A to Z, numbers from 0 to 9 and underscore character _.
|
|
13065
|
Table
|
Error
|
Not a valid role name role.
You tried to create an invalid role name. A valid role name has at least 2 characters and at most 31 characters. A role name may contain characters from A to Z, numbers from 0 to 9 and underscore character _.
|
|
13066
|
Table
|
Error
|
User user not found in role role.
You tried to revoke a role from a user and the user did not have that role.
|
|
13067
|
Table
|
Error
|
Too short password.
You have entered a too short password. Password length must be at least 3 characters.
|
|
13068
|
Table
|
Error
|
Shutdown is in progress.
You are unable to complete this operation, because server shutdown is in progress.
|
|
13070
|
Table
|
Error
|
Numerical overflow.
A numerical overflow has occurred. Check the values and types of numerical variables.
|
|
13071
|
Table
|
Error
|
Numerical underflow.
A numerical underflow has occurred. Check the values and types of numerical variables.
|
|
13072
|
Table
|
Error
|
Numerical value out of range.
A numerical value is out of range. Check the values and types of numerical variables.
|
|
13073
|
Table
|
Error
|
Math error.
A mathematical error has occurred. Check the mathematics in the statement and try again.
|
|
13074
|
Table
|
Error
|
Illegal password.
You have tried to enter an illegal password.
|
|
13075
|
Table
|
Error
|
Illegal role name role.
You have tried to enter an illegal role name. A legal role name is at least 2 and at most 31 characters in length. A user role may contain characters from A to Z, numbers from 0 to 9 and underscore character _.
|
|
13077
|
Table
|
Error
|
Last column can not be dropped.
You have tried to drop the final column in a table. This is not allowed; at least one column must remain in the table.
|
|
13078
|
Table
|
Error
|
Column already exist on table.
You have tried to create a column which already exists in a table.
|
|
13079
|
Table
|
Error
|
Illegal search constraint.
Check the search engine. There may be mismatch between data types.
|
|
13080
|
Table
|
Error
|
Incompatible types, can not modify column column fromtype type to type type.
You have tried to modify column to a data type that isincompatible with the original definition, such as VARCHARand INTEGER
|
|
13081
|
Table
|
Error
|
Descending keys are not supported for binary columns. You can not define a descending key for a binary column.
|
|
13082
|
Table
|
Error
|
Function function: parameter * not supported.
You can not use parameter star (*) with ODBC Scalar Functions.
|
|
13083
|
Table
|
Error
|
Function function: Too few parameters.
The function expects more parameters. Check the function call.
|
|
13084
|
Table
|
Error
|
Function function: Too many parameters.
The function expects fewer parameters. Check the function call.
|
|
13085
|
Table
|
Error
|
Function function: Run-time failure.
An error was detected during the execution of the function. Check the parameters.
|
|
13086
|
Table
|
Error
|
Function function: type mismatch in parameter parameter number.
An erroneous type of parameter was detected in the given position of the function call. Check the function call.
|
|
13087
|
Table
|
Error
|
Function function: illegal value in parameter parameter number.
An illegal value for a parameter detected in the given position of the function call. Check the function call.
|
|
13088
|
Table
|
Error
|
No primary key for table.
|
|
13090
|
Table
|
Error
|
Foreign key column column data type not compatible with referenced column data type.
References specification error. Check that the column data type are compatible between referencing and referenced tables.
|
|
13091
|
Table
|
Error
|
Foreign key does not match to the primary key or unique constraint of the referenced table.
References specification error. Check that the column data types are compatible between referencing and referenced tables and that the foreign key is unique for the referenced table.
|
|
13092
|
Table
|
Error
|
Event name event conflicts with an existing entity.
Choose a unique name for an event. The specified name is already used.
|
|
13093
|
Table
|
Error
|
Event event does not exist.
You referenced a nonexistent event. Check the name of the event.
|
|
13094
|
Table
|
Error
|
Duplicate column column in primary key definition.
Duplicate columns are not allowed in a table-constraint-definition. Remove duplicate columns from the definition.
|
|
13095
|
Table
|
Error
|
Duplicate column column in unique constraint definition.
Duplicate columns are not allowed in a table-constraint-definition. Remove duplicate columns from the definition.
|
|
13096
|
Table
|
Error
|
Duplicate column column in index definition.
Duplicate columns are not allowed in CREATE INDEX statement. Remove duplicate columns.
|
|
13097
|
Table
|
Error
|
Primary key columns must be NOT NULL.
Error in a column_constraint_definition. Define primary key columns NOT NULL. For example: CREATE TABLE DEPT (DEPTNO INTEGER NOT NULL, DNAME VARCHAR, PRIMARY KEY(DEPTNO));
|
|
13098
|
Table
|
Error
|
Unique constraint columns must be NOT NULL.
Error in a column_constraint_definition. Define unique columns NOT NULL. For example: CREATE TABLE DEPT4 (DEPTNO INTEGER NOT NULL, DNAME VARCHAR, UNIQUE(DEPTNO));
|
|
13099
|
Table
|
Error
|
No REFERENCES privileges to referenced columns in table table. You do not have privileges to reference to the table.
|
|
13100
|
Table
|
Error
|
Illegal table mode combination.
You have defined an illegal combination of concurrency control settings. This message occurs, for example, if you have an in-memory table and you try to change it from pessimistic concurrency control (locking) to optimistic concurrency control by using the command ALTER TABLE <table_name> SET PESSIMISTIC.
In-memory tables must always use pessimistic concurrency control.
Setting In-memory tables to be compressed is illegal.
|
|
13101
|
Table
|
Error
|
Only execute privileges can be used with procedures.
|
|
13102
|
Table
|
Error
|
Execute privileges can be used only with procedures.
|
|
13103
|
Table
|
Error
|
Illegal grant or revoke operation.
This error occurs if you try to revoke privileges from yourself.
This error occurs if the DBA tries to grant privileges to herself or himself (to the DBA).
|
|
13104
|
Table
|
Error
|
Sequence name sequence conflicts with an existing entity.
Choose a unique name for a sequence. The specified name is already used.
|
|
13105
|
Table
|
Error
|
Sequence sequence does not exist.
You referenced a nonexistent sequence. Check the name of sequence.
|
|
13106
|
Table
|
Error
|
Foreign key reference exists to table table.
|
|
13107
|
Table
|
Error
|
Illegal set operation.
You tried to execute a non-existent set operation.
|
|
13108
|
Table
|
Error
|
Comparison between incompatible types datatype and datatype.
|
|
13109
|
Table
|
Error
|
There are schema objects for this user, drop failed
|
|
13110
|
Table
|
Error
|
NULL values given for NOT NULL column column.
|
|
13111
|
Table
|
Error
|
Ambiguous entity name name.
This message occurs if the name of the specified database object (for example, a table name) does not exist in the schema that you are currently in, but more than one other schema contains an object with that name.
If the database object that you want is in a different schema than the schema you are currently in, then change to the appropriate schema by using the SET SCHEMA command, or specify the desired object by using a more fully qualified object name, for example:
sales_catalog.jan_wong_schema.table.1
|
|
13112
|
Table
|
Error
|
Foreign keys are not supported with main memory tables.
|
|
13113
|
Table
|
Error
|
Illegal arithmetic between types datatype and datatype.
|
|
13114
|
Table
|
Error
|
String operations are not allowed on values stored as BLOBs or CLOBs.
|
|
13115
|
Table
|
Error
|
Function function_name: Too long value (stored as CLOB) in parameter parameter. The parameter value was stored as CLOB and cannot be used with a function.
|
|
13116
|
Table
|
Error
|
Column column_name specified more than once.
Column was specified more than once in the GRANT or REVOKE statement.
|
|
13117
|
Table
|
Error
|
Wrong number of parameters
Wrong number of parameters when converting subscription parameters to base publication parameter types.
|
|
13118
|
Table
|
Error
|
Column privileges are supported only for base tables.
Column privileges are allowed only for base tables; they cannot be used, for example, for views.
|
|
13119
|
Table
|
Error
|
Types column_type and column_type are not union compatible.
Column types are not union compatible. When a UNION operation is performed, two columns from two different tables are used to generate one column of output. The operation is successful as long as the two columns are of the same type or “compatible” types. Types are compatible if one type can reasonably be converted into the other type. For example, you can UNION a column of FLOAT with a column of INT because any integer value can also be represented as a corresponding float value (for example, 2 can be converted to 2.0). However, if you attempt a UNION operation on two incompatible types, such as FLOAT and DATE, you will receive 13119.
|
|
13120
|
Table
|
Error
|
Too long entity name 'entity_name'.
Entity name is too long, maximum entity name is 254 characters.
|
|
13121
|
Table
|
Error
|
Too many columns, maximum number of columns per table is value.
Note that the maximum number of columns may be less if each column requires a large number of bytes.
|
|
13122
|
Table
|
Error
|
Operation is not supported for a table with sync history.
Operation is not supported because the table has synchronization history defined.
|
|
13123
|
Table
|
Error
|
Table 'table_name' is not empty.
Some operations are allowed only for empty tables.
|
|
13124
|
Table
|
Error
|
User id user_id not found.
Internal user id was not found; the user may have been dropped.
|
|
13125
|
Table
|
Error
|
Illegal LIKE pattern 'pattern'.
Illegal like pattern was given as a search constraint.
|
|
13126
|
Table
|
Error
|
Illegal type datatype for LIKE pattern.
Only CHAR and WCHAR allowed for LIKE search constraints.
|
|
13127
|
Table
|
Error
|
Comparison failed because at least one of the values was too long.
Comparison failed because at least one of the column values was stored as a BLOB or CLOB.
|
|
13128
|
Table
|
Error
|
LIKE predicate failed because value is too long.
LIKE predicate failed because the column value is stored as a CLOB.
|
|
13129
|
Table
|
Error
|
LIKE Predicate failed because pattern is too long.
LIKE predicate failed because pattern value is stored as a CLOB.
|
|
13130
|
Table
|
Error
|
Illegal type datatype for LIKE ESCAPE character.
Like ESCAPE character must be CHAR or WCHAR type.
|
|
13131
|
Table
|
Error
|
Too many nested triggers.
Maximum number of nested triggers is reached. Triggers may be nested, for example, by activating other triggers from a trigger or causing recursive cycle when activating triggers. Default value for maximum allowed nested triggers is 16. It can be changed using a configuration parameter:
[SQL] MaxNestedTriggers=n
|
|
13132
|
Table
|
Error
|
Too many nested procedures.
Maximum number of nested procedures is reached. Procedures may be nested, for example, by activating other procedures from a procedure or causing a recursive cycle when activating procedures. Default value for maximum allowed nested procedures is 16. It can be changed using a configuration parameter:
[SQL] MaxNestedProcedures=n
|
|
13133
|
Table
|
Error
|
Not a valid license for this product.
The license file is for another solidDB® product.
|
|
13134
|
Table
|
Error
|
Operation is allowed only for base tables. Given operation is available only for base tables.
|
|
13135
|
Table
|
Error
|
Internal error, arithmetic error in estimator
For more information, contact solidDB® Support.
|
|
13136
|
Table
|
Error
|
Internal error, transaction is not active
For more information, contact solidDB® Support.
|
|
13137
|
Table
|
Error
|
Illegal grant/revoke mode
Grant or revoke mode is not allowed for given database objects.
|
|
13138
|
Table
|
Error
|
Index index_name given in index hint does not exist.
Index name given in optimizer hint is not found for a table.
|
|
13139
|
Table
|
Error
|
Catalog catalog_name does not exist. Catalog name is not a valid catalog.
|
|
13140
|
Table
|
Error
|
Catalog catalog_name already exists. Catalog name is an existing catalog.
|
|
13141
|
Table
|
Error
|
Schema schema_name does not exist. Schema name is not a valid schema.
|
|
13142
|
Table
|
Error
|
Schema schema_name already exists. Schema name is an existing schema.
|
|
13143
|
Table
|
Error
|
Schema schema_name is an existing user. Schema name specifies an existing user name.
|
|
13144
|
Table
|
Error
|
Commit and rollback are not allowed inside trigger.
Commit or rollback are not supported inside trigger execution. This error is also given if a trigger calls a procedure that tries to execute commit or rollback command.
|
|
13145
|
Table
|
Error
|
Sync parameter not found.
Parameter name given in command SET SYNC PARAMETER name NONE is not found.
|
|
13146
|
Table
|
Error
|
There are schema objects for this catalog, drop failed.
Catalog contains schema object and cannot be dropped. Schema objects like tables and procedures need to be dropped before catalog can be dropped.
|
|
13147
|
Table
|
Error
|
Current catalog can not be dropped.
The catalog that you want to drop must not be the current catalog. If you get this message, you should switch to another catalog, then re-execute the DROP CATALOG command.
|
|
13148
|
Table
|
Error
|
There are objects for this schema, drop failed.
|
|
13149
|
Table
|
Error
|
There are objects for this catalog, drop failed.
|
|
13150
|
Table
|
Error
|
Index can be created only into same catalog and schema as the base table.
|
|
13151
|
Table
|
Error
|
Cannot drop a column that is part of primary or unique key.
Table definition contains a column that is part of a primary or unique key in an index.
|
|
13152
|
Table
|
Error
|
There are objects for this user, drop failed.
|
|
13153
|
Table
|
Error
|
Can not remove last administrator.
|
|
13154
|
Table
|
Error
|
Name cannot be an empty string.
|
|
13155
|
Table
|
Error
|
Column <column name> already exists on view <view name> The view definition contains the same column name twice.
|
|
13156
|
Table
|
Error
|
Column attributes already exists on view.
|
|
13157
|
Table
|
Error
|
Current schema cannot be dropped.
|
|
13158
|
Table
|
Error
|
Current user cannot be dropped.
|
|
13160
|
Table
|
Error
|
Cannot alter table name because it is referenced in trigger(s).
Altering the name of the table would prevent the trigger from working properly.
|
|
13161
|
Table
|
Error
|
An M-table is being updated with UPDATE ... WHERE CURRENT OF CURSOR and CURSOR is not declared FOR UPDATE.
When you update an in-memory table (an “M-table”) using the command UPDATE ... WHERE CURRENT OF CURSOR, you must have declared the cursor using the FOR UDPATE clause. This is required when the table is an in-memory table; it is strongly recommended, but not required, when the table is a disk-based table.
|
|
13162
|
Table
|
Error
|
A record in an M-table is being deleted with DELETE ... WHERE CURRENT OF CURSOR and CURSOR is not declared FOR UPDATE.
When you delete a record from an in-memory table (an “M-table”) using the command DELETE ... WHERE CURRENT OF CURSOR, you must have declared the cursor using the FOR UDPATE clause. This is required when the table is an in-memory table; it is strongly recommended, but not required, when the table is a disk-based table.
|
|
13163
|
Table
|
Error
|
Descending keys are not supported for bigint columns.
If you try to create a DESCending index on a column of type BIGINT, you will get this message. Use an ASCending key instead.
|
|
13164
|
Table
|
Error
|
Transaction is active, operation failed.
|
|
13165
|
Table
|
Error
|
Cannot fetch previous row from an M-table.
This message can occur only when fetching rows from in in-memory table (“M‑table”) by using solidDB®’s low-level SA API.
|
|
13166
|
Table
|
Error
|
License does not allow accessing M-tables
|
|
13167
|
Table
|
Error
|
Only M-tables can be transient.
|
|
13168
|
Table
|
Error
|
Transient tables can not be set temporary.
|
|
13169
|
Table
|
Error
|
Temporary tables can not be set transient.
|
|
13170
|
Table
|
Error
|
Only M-tables can be temporary.
|
|
13171
|
Table
|
Error
|
Foreign key constraints between D- and M-tables are not supported.
|
|
13172
|
Table
|
Error
|
A persistent table can not reference a transient table.
For more details, see the discussion on persistent and transient tables under the CREATE TABLE command in “Solid SQL Syntax” in solidDB® SQL Guide.
|
|
13173
|
Table
|
Error
|
A persistent table can not reference a temporary table.
For more details, see the discussion on persistent and transient tables under the CREATE TABLE command in “Solid SQL Syntax” in solidDB® SQL Guide.
|
|
13174
|
Table
|
Error
|
A transient table can not reference a temporary table.
For more details, see the discussion on persistent and transient tables under the CREATE TABLE command in “Solid SQL Syntax” in solidDB® SQL Guide.
|
|
13175
|
Table
|
Error
|
A reference between temporary and non-temporary table is not allowed.
|
|
13176
|
Table
|
Error
|
Cannot change STORE for a table with sync history.
|
|
13177
|
Table
|
Error
|
Cannot define UNIQUE constraint with duplicated or implied restriction.
|
|
13178
|
Table
|
Error
|
Constraint not found.
|
|
13179
|
Table
|
Error
|
Foreign key actions other than restrict are not supported.
|
|
13180
|
Table
|
Error
|
Constraint name already exists.
|
|
13181
|
Table
|
Error
|
Constraint check fails on existing data.
|
|
13182
|
Table
|
Error
|
Added column with NOT NULL must have a non-NULL default.
|
|
13183
|
Table
|
Error
|
Index is referenced by foreign key, it cannot be dropped.
|
|
13184
|
Table
|
Error
|
Primary key not found for table. Cannot define foreign key.
|
|
Error code
|
Class
|
Type
|
Description
|
|
13185
|
Table
|
Error
|
Cannot set NOT NULL on column that already has NULL value.
|
|
13186
|
Table
|
Error
|
Cannot drop NOT NULL on column that is used as part of unique key.
|
|
13187
|
Table
|
Error
|
The cursor cannot continue accessing M-tables after the transaction has committed or aborted. The statement must be re-executed.
|
|
13188
|
Table
|
Error
|
Foreign key refers to itself.
|
|
13189
|
Table
|
Error
|
Positioning is not supported for M-tables.
|
|
13190
|
Table
|
Fatal Error
|
Definition in file is not valid.
|
|
13191
|
Table
|
Fatal Error
|
Parameter setting in file conflicts with the setting in database.
|
|
13192
|
Table
|
Fatal Error
|
Database is in read-only state
|
|
13193
|
Table
|
Fatal Error
|
Foreign key creates update dependency loop.
A foreign key creates a dependency between one or more tables in such a way that update to one row in one table might cause multiple updates to the same row in the same or another table. Such update might be ambiguous and the server does not allow creation of such dependencies.
This restriction does not apply to cascaded deletes (when deletion of one row causes multiple deletions of another row), but it still applies when the deletion of one row causes multiple updates (SET NULL or SET DEFAULT) to another row.
|
|
13194
|
Table
|
Error
|
Can not drop a table that is part of a foreign key
|
|
13195
|
Table
|
Error
|
Update failed, READ COMMITTED isolation requires FOR UPDATE
|
|
13196
|
Table
|
Error
|
Delete failed, READ COMMITTED isolation requires FOR UPDATE
|
|
13197
|
Table
|
Error
|
M-tables are not supported
|
|
13198
|
Table
|
Error
|
Commit and rollback are not allowed inside function.
|
|
13199
|
Table
|
Error
|
Duplicate index definition
This error is returned when a duplicate or redundant index is detected during index creation.
For example, if you have created an index as follows:
CREATE UNIQUE INDEX IND_1 ON T1(C1,C2,C3);
Next, if you create this index:
CREATE INDEX IND_2 ON T1(C2,C3,C1,C4);
After this step, solidDB® returns error 13199. In the example above, the second index is a superset of the unique first index. This implies that the second index (although it is not explicitly specified as unique) is also unique. In practice, the second index is useless. It only affects space consumption and update performance, not lookup performance.
|
|
13200
|
Table
|
Error
|
Update failed.
Used isolation level requires FOR UPDATE.
|
|
13201
|
Table
|
Error
|
Delete failed.
Used isolation level requires FOR UPDATE.
|
|
13202
|
Table
|
Error
|
Cluster connection does not support isolation levels higher than READ COMMITTED.
|
|
13203
|
Table
|
Error
|
License does not allow creating D-tables
|
|
13204
|
Table
|
Error
|
SET WRITE command makes sense only for TC connection
|
|
13205
|
Table
|
Error
|
Cannot change STORE for a table with foreign keys.
|
|
13206
|
Table
|
Error
|
Sequence <sequence> has incorrect START WITH constant <constant>
|
|
13207
|
Table
|
Error
|
Sequence <sequence> has incorrect INCREMENT BY constant <constant>
|
|
13400
|
Table
|
Error
|
Alter or drop table not allowed for propagated tables.
|
|
13401
|
Table
|
Error
|
Truncate table not allowed for propagated tables.
|
|
13402
|
Table
|
Error
|
Propagation information loading active.
|
|
13403
|
Table
|
Error
|
Propagation information loading not active.
|
|
13404
|
Table
|
Error
|
Triggers not allowed for propagated tables.
|
|
13405
|
Table
|
Error
|
Cascading foreign keys not allowed for propagated tables.
|
|
13406
|
Table
|
Error
|
Primary key is required for propagated tables.
|
|
13407
|
Table
|
Error
|
Propagation schema data inconsistent: Table name not found.
|
|
13408
|
Table
|
Error
|
Logreader feature is disabled.
|
|
13409
|
Table
|
Error
|
Log overflow, catchup is not possible.
|
|
13410
|
Table
|
Error
|
Logreader partition not found .
|
|
13411
|
Table
|
Error
|
No active logreader query.
|
|
13412
|
Table
|
Error
|
Propagated tables allow only one row update when primary or unique key is changed.
|
|
13413
|
Table
|
Error
|
Row size exceeds the allowed value for propagated tables.
|
|
13414
|
Table
|
Error
|
Given attribute value is incorrect for range partitioned table <value>.
|
|
13415
|
Table
|
Error
|
Range column <value> is not found from partitioned table <value>.
|
|
13416
|
Table
|
Error
|
Logreader partition already exists
|
|
13417
|
Table
|
Error
|
Table not found from logreader partition
|
|
13418
|
Table
|
Error
|
Table already exists in logreader partition
|
|
13471
|
Table
|
Error
|
Table table_name does not have conditions for cache segment cache_segment_name
|
|
13501
|
Table
|
Warning
|
String data truncation in assignment from <value> to <value>
|
|
13502
|
Table
|
Warning
|
Numeric value right truncation in assignment from <value> to <value>
|