SAND CDBMS uses SQL92-compliant SQLSTATE status codes
to categorize the diagnostic messages. Each SQLSTATE code consists of a 2-character
class, followed by a 3-character subclass. The class specifies
general information about the error type; the subclass specifies more specific
information. For example, SQLSTATE code 54503 indicates the class 54
(Privilege Errors) and the subclass 503 (“Cannot grant privileges
- non-existent object”). Each of the five characters in an SQLSTATE value
is a digit (0...9) or an uppercase letter (A...Z). Class codes that begin
with a digit in the range 0...4, or a letter in the range A...H, are reserved
for SQL92 predefined conditions. All other class codes are reserved for implementation-defined
conditions.
Most of the diagnostic messages in this document are accompanied by a description of the error/warning, and some recommended course of action.
Go To:
00000 Successful completion
The SQL statement has executed successfully and without warnings. This diagnostic message is returned, but not displayed to the user.01000 Warning
Different conditions may cause this generic warning message to appear. Further information is provided by a supplemental diagnostic message.08004 Server refused connection - Maximum number of sessions reached
This message appears if the maximum number of concurrent database sessions has been reached and another connection is attempted. The maximum number of sessions is set via the MaxUsers parameter in the nucleus.ini file. If required, the MaxUsers value can be increased up to a maximum of 127.08006 Connection Failure
This message appears when a connection with another database could not be established while executing the CREATE TABLE...WITH CONNECTION command. A secondary message provides further details about the error. Common causes of this error include an invalid user name or password for the connection, the connection object points to a nonexistent database, and the connection object references a nucleus.ini Connection section that does not exist.0A000 Feature not supported
This message appears when SAND CDBMS encounters an unsupported SQL command, clause, or function.If the secondary message is "Application not supported while loading", then the user attempted to execute an SQL command that can change the database while data was being imported into the database via ndlm. For the duration of any ndlm load operation, such commands are disallowed. Once all load operations have completed, users can issue a COMMIT [WORK] or ROLLBACK [WORK] command to start a new transaction that will then allow the full range of SQL commands.
0B001 Exclusive use not possible while other transactions are active
This message appears when a user issues the SET TRANSACTION...ISOLATION LEVEL EXCLUSIVE command while there are other concurrent user connections to the same database instance. In order to "lock" the database using the SET TRANSACTION...ISOLATION LEVEL EXCLUSIVE command, the user executing the command must have the only connection to the database.The message also appears when two or more users are connected to a database instance, and one of the users attempts to execute an ALTER TABLE...ADD CONSTRAINT command. For concurrency control reasons, SAND CDBMS does not allow constraints to be added to a table while other user sessions are active.
In addition, this message appears when a SAND CDBMS Data Loader (ndlm) operation is attempted on a database while one or more users are connected to the database instance. Ndlm requires that all client sessions be closed in order to start a load transaction.
0B002 Transaction statement failure - duplicate clauses
This message appears when a SET TRANSACTION statement includes more than one ISOLATION LEVEL clause or access mode (READ ONLY, READ WRITE). The access mode and ISOLATION LEVEL clause can appear at most once in a SET TRANSACTION statement.0B003 Transaction statement failure - invalid diagnostic size
This message appears when the DIAGNOSTIC SIZE clause in a SET TRANSACTION or START TRANSACTION statement specifies a value that is zero or less, or greater than 32. The value specified by the DIAGNOSTIC SIZE clause must be between 1 and 32 inclusive.0H000 Invalid SQLSTATE
This message appears for several different error conditions. In most cases, a supplemental message will specify the cause of the error:can't compare or combine host variables
Host variables or parameter markers can neither be combined in arithmetic expressions nor appear on both sides of a comparison operator. Note that embedded SQL is deprecated as of release 3.can't use host variables in NULL or LIKE predicates
Host variables or parameter markers cannot be used in NULL or LIKE predicates in a Boolean value expression (search condition). Note that embedded SQL is deprecated as of release 3.Cannot load into a table that has ENABLED constraints other than not null
The SAND CDBMS Data Loader (ndlm) cannot load data into a table that has PRIMARY KEY, FOREIGN KEY, UNIQUE, and/or CHECK constraints defined and enabled on the table or its columns. Disable or drop the constraints using the ALTER TABLE command before attempting the data load again. When the load is complete, the constraints can be re-enabled or redefined.CASCADE not yet supported
The DROP...CASCADE option is not supported for some objects. For these objects, the DROP command requires that all dependent objects be explicitly dropped prior to attempting to drop the object.escape symbol should be one character only
This message is returned when the LIKE predicate is used in a Boolean value expression (search condition), and the ESCAPE clause specifies more than one escape character. The ESCAPE clause, if included, must specify a single character.Execution failed - Not enough input parameters
This message is returned when a value expression or search condition contains a ‘?’ (without the quotation marks). If this character is intended as a parameter marker, it should be noted that SAND CDBMS does not support embedded SQL.This message is also generated when an INSERT statement contains a ‘?’ (without the quotation marks) in the value list. A ‘?’ can be inserted only into a character column, and it must be enclosed by quotation marks, otherwise this error will be returned.
expression evaluation error
A problem occurred while evaluating an expression in the SQL statement. This can occur when attempting to store a numeric value greater than the maximum size or less than the minimum size of the data type/domain intended to store the value. Refer to the SAND CDBMS SQL Reference Guide for the valid ranges of the numeric SQL data types.host variables not allowed in this command
This message is generated when a host variable or parameter marker appears in an SQL statement that does not permit its use. Note that embedded SQL is deprecated as of release 3.inappropriate specification of variable
This message is generated when a host variable or parameter marker appears in an SQL statement that does not permit its use. Note that embedded SQL is deprecated as of release 3.Load API calling sequence error
This error can be returned when a successive data load is attempted after the previous load did not terminate "cleanly". Restart the server and loader, and attempt to load the data again. If the problem persists, make note of the diagnostic message and circumstances, and contact a SAND support representative.Load API heap allocation failure
A sufficient amount of memory could not be allocated for a SAND CDBMS Data Loader (ndlm) operation. Free up some memory by terminating other running processes, and then attempt the data load again. Also note that the cache size (Cache) parameter in the [Database instance-name] section of the server-side nucleus.ini file should be set to 1/40 of the database size as a rule of thumb. If the error occurred on a UNIX platform, consult the Server Administration Guide for information about increasing user limits for the execution environment.rel_create_rel (Selector TMPSELECT)
An internal error occurred. Make note of the diagnostic message and circumstances, and contact a SAND support representative.tried to add/subtract/multiply/divide inappropriate types
This message is returned when arithmetic operations are attempted on data types or column domains that do not support these operations. For example, the following SQL statement will generate this error:
SELECT date1/date2 FROM table1;In the context of SAND CDBMS SQL, dividing one DATE value by another is not a meaningful operation.
21000 Cardinality violation - scalar subquery returned more than one row
This message appears when a scalar subquery returns more than one record. A scalar subquery must return either a single record or no records. If necessary, rewrite the scalar subquery to ensure that it will return at most one record.22002 Data exception - null value not allowed
This message appears when an INSERT statement attempts to insert a null value into a column that participates in a PRIMARY KEY constraint, or on which a NOT NULL constraint is defined. None of the columns that are part of a primary key can have null values; while a NOT NULL constraint ensures that the column contains no null values.Note that when loading into a table via ndlm, omitting a NOT NULL column from the mapping section of the load specification script will always cause the operation to fail with this error. Since the column is omitted, ndlm will attempt to load the column with default null values, which are disallowed because of the NOT NULL constraint.
22003 Data exception - numeric value out of range
This message appears when an SQL operation results in a numeric overflow or underflow. That is, an evaluated numeric expression is either too large or too small to be contained in a suitable SAND CDBMS data type without loss of precision or scale.22012 Data exception - division by zero
This message appears when a division-by-zero operation is attempted. Dividing by zero is not permitted. The ALTER SESSION ALTER DIVISION command may be used to instruct SAND CDBMS to intercept divide-by-zero errors and return a null value instead.22014 Data exception - field not found
This message appears when a nonexistent column name is referenced in a SELECT, INSERT, UPDATE, DELETE, or view definition statement. If necessary, query the SYSTEM.COLUMNS table or the PUBLIC.COLUMNS views to determine the correct spelling of the column name.22500 Data exception - type mismatch
This message appears whenever an SQL operation involving incompatible data types is attempted. For example, the following operations are not permitted:
- multiplying a number by a character string in a value expression
- inserting a numeric value into a date field
- specifying a UNION between two tables whose corresponding columns have incompatible data types.
22501 Data exception - string truncation
This message appears when an INSERT or UPDATE statement specifies a character string value that is longer than the maximum that can be stored in the target column. The length of the character string must be less than or equal to the maximum length permitted by the column.This message is also returned if the concatenation operator ( || ) or the CONCAT() function produces a string that is 4057 or more characters in length. The maximum length of a concatenated string is 4056 characters.
23500 Unique constraint violation - duplicate value
This message appears when an attempt is made to insert or update a duplicate value into a column -- or a duplicate combination of values into columns -- on which there is a UNIQUE or PRIMARY KEY constraint. The UNIQUE constraint prohibits duplicate column values; the PRIMARY KEY is implicitly UNIQUE.23601 Delete failed - foreign key constraint violation
This message appears when an attempt is made to delete a parent table row that has one or more child rows in a foreign key relation that was defined with the ON DELETE RESTRICT clause. The ON DELETE RESTRICT clause specifically prevents the deletion of parent table rows that have child rows. Delete all of the child rows before attempting to delete the parent table row.23602 Update failed - foreign key constraint violation
This message appears when an UPDATE statement would result in a foreign key value that does not correspond to any value in the parent table. The foreign key constraint requires that each foreign key value have a matching value in the parent table.This message also appears when an attempt is made to update a parent table row that has one or more child rows in a foreign key relation that was defined with the ON UPDATE RESTRICT clause (or without an ON UPDATE clause, since ON UPDATE RESTRICT is the default). The ON UPDATE RESTRICT clause specifically prevents the updating of parent table rows that have child rows. In order to update the parent table rows, either the foreign key constraint has to be removed or the child rows have to be deleted.
23603 Insert failed - foreign key constraint violation
This message appears when an attempt is made to INSERT values into a table that would violate a foreign key constraint defined on the table. The value inserted into the foreign key column(s) must have a corresponding value in the parent table in the foreign key relation.23604 Update failed - not all columns in the foreign key are referenced
This message appears when an attempt is made to update a subset of the primary key of the parent table in a foreign key relation that was defined with the ON UPDATE CASCADE clause. All of the columns in the parent table primary key must be updated by the UPDATE statement when the ON UPDATE CASCADE clause qualifies the foreign key relation.23606 Update failed - attempted to assign values to a row multiple times
This message is returned when multiple values satisfy the conditions of the WHERE clause in an UPDATE...FROM statement, such that the same row in the target table is slated to be updated multiple times. As the same row cannot be updated more than once in a single operation, this condition is illegal. It is up to the user to ensure that a unique set of records is produced by the WHERE clause.25006 Execution failure - the transaction is read only
This message appears when a statement which updates information in the database is executed in a transaction that was specified as read-only (using the SET TRANSACTION statement). To make changes to the database, a new transaction - set to read-write - will have to be started. End the current read-only transaction with a ROLLBACK; and then begin issuing the database-altering SQL statements (since a new transaction is read-write by default). Alternatively, use the SET TRANSACTION READ WRITE command to end the current transaction with an implicit ROLLBACK and start a new transaction in read-write mode.28500 Duplicate authorization name
This message appears when a CREATE AUTHORIZATION statement specifies an authorization name that already exists in the current database. All authorization names must be unique within the database.2B000 Dependent privilege descriptors still exist
This message appears when a REVOKE statement attempts to remove a privilege from an authorization that was granted WITH GRANT OPTION. The authorization has granted the privilege to one or more other authorizations. REVOKE the privilege from these other authorizations before attempting the original REVOKE statement again.2E001 Duplicate connection name
This message appears when a CREATE CONNECTION command specifies a connection name that is being used by an existing connection object. Each connection must have a unique name. Either a different name must be selected for the new connection object, or the existing connection must be deleted via the DROP CONNECTION command before defining the new connection with the same name.3F500 Duplicate schema name
This message appears when a CREATE SCHEMA statement references a schema name that already exists in the current database. All schema names must be unique within the database.40001 Transaction error - a possible conflict forced a rollback
This message appears when a user attempts to commit database changes that conflict with changes committed by one or more other concurrent user connections to the same database. There will be an implicit ROLLBACK of any transactional changes made by the user receiving this error.For example, say that User 1 and User 2 connect to a database at the same time. If User 1 inserts data into Table A, and then User 2 drops Table A and commits the change, User 1 will receive this transaction error when committing the data insert because Table A no longer exists. Any changes made by User 1 in the transaction will be rolled back.
Refer to the SAND CDBMS Concurrency Control section in the SAND CDBMS Administration Guide for more information about transactional conflicts.
42000 Syntax error
This message appears when a syntactically incorrect SQL statement is entered. Consult the SAND CDBMS SQL Reference Guide for full details about SAND CDBMS SQL syntax.The message may also appear if the SQL statement references a non-delimited database object name that contains an ASCII character not found in the following list:
- All uppercase and lowercase letters (A - Z, a - z)
- Digits (0 - 9)
- The symbols #, $, %, &, { (opening brace), } (closing brace), and _ (underscore).
In this case, the database object name must be delimited by double quotation marks ("..."). Consult the "Object Names" section in the SAND CDBMS SQL Database Objects and Language Elements chapter of the SAND CDBMS SQL Reference Guide for more information about database object names.
42100 Too many unions in statement
This message is returned when the number of unions in a single SQL statement exceeds 32. That is, the UNION keyword can appear at most 32 times in the combined query expression.42400 No dba privileges
This message appears when a user without DBA privileges attempts to execute the SHUTDOWN command, or issues the SET TRANSACTION command with the ISOLATION LEVEL EXCLUSIVE clause. Only a user with DBA privileges may issue SHUTDOWN or SET TRANSACTION...ISOLATION LEVEL EXCLUSIVE statements.42500 Create authorization failed - insufficient privileges
This message appears when a user without DBA privileges attempts a CREATE AUTHORIZATION statement. The user must be granted DBA privileges to create an authorization.42502 Insufficient privileges on schema
This message appears when a user attempts an ALTER TABLE, DROP TABLE, or DROP VIEW statement in the user's default schema, and the user does not own the schema, possess the OWNER privilege on it, or possess DBA privileges. This message also appears if a DROP DOMAIN or RENAME DOMAIN statement specifies a domain on which the user issuing the statement has no privileges. In order to ALTER, DROP, or RENAME these database objects, the OWNER privilege on the schema containing the object must be granted by the schema owner or the DBA.42505 Alter authorization failed - insufficient privileges
This message appears when a non-DBA user attempts to execute an ALTER AUTHORIZATION statement that references another authorization. A user without DBA privileges can alter only their own authorization settings. In order to alter another authorization, the user must be granted DBA privileges.42510 Drop authorization failed - insufficient privileges
This message appears when a non-DBA user attempts a DROP AUTHORIZATION statement. The user must be granted DBA privileges to drop an authorization.42511 Drop authorization failed - cannot drop DBA or PUBLIC
This message appears when a user attempts to drop either the DBA or PUBLIC user. These are special authorizations that cannot be dropped from the database.42512 Drop authorization failed - authorization still owns objects
This message appears when a user with DBA privileges attempts to drop an authorization that still owns database objects. Drop all of the database objects owned by the authorization before dropping the authorization.42530 Drop schema failed - insufficient privileges
This message appears when a non-DBA user attempts to drop a schema that they do not own. The user executing the DROP SCHEMA command must own the specified schema, or possess DBA privileges. The message also appears if a user with DBA privileges attempts to drop the PUBLIC, SYSTEM, or DBA schema. These special schemas cannot be dropped.42531 Drop schema failed - dependent object(s)
This message appears when a user attempts to drop a schema that contains one or more database objects. Drop all database objects belonging to the schema before attempting to drop the schema.42535 Create domain failed - insufficient privileges
This message appears when a non-DBA user attempts to create a domain on a schema that the user does not own or possess the OWNER privilege on. In order to create a domain in that schema, the user must be granted the OWNER privilege on the schema from the schema owner or DBA, or be granted DBA privileges.42545 Create table failed - insufficient privileges
This message appears when a non-DBA user attempts one of the following:
- a CREATE TABLE statement on a schema on which the user possesses no privileges
- an ALTER TABLE statement that references a table on which the user possesses no privileges
- a CREATE TABLE statement that references a domain on which the user possesses no privileges
- an ALTER TABLE...ADD COLUMN statement that references a domain on which the user possesses no privileges
In order to create a table in a particular schema, the user must be granted the OWNER privilege on the schema or DBA privileges on the database.
In order to alter a table, the user must be granted the OWNER privilege on the schema to which the table belongs or DBA privileges on the database.
In order to specify a domain in a CREATE or ALTER TABLE statement, the user must be granted USAGE on the domain, the OWNER privilege on the schema that contains the domain, or DBA privileges on the database.
50000 Feature not implemented
This message appears when an unsupported SQL command or clause is attempted.50111 Unable to insert into table
This message appears when an INSERT...SELECT statement is attempted, specifying the same table as both a source and destination for table data. The data entered into a table through an INSERT...SELECT statement must come from other tables.50400 Non-existent authorization
This message appears when an ALTER AUTHORIZATION, DROP AUTHORIZATION, GRANT, REVOKE, or CREATE SCHEMA statement references an authorization name that does not exist in the database. If necessary, query the SYSTEM.AUTHORIZATONS table or the PUBLIC.AUTHORIZATIONS view to determine the correct spelling of the authorization name.50500 Unable to proceed with Group By clause - incorrect argument list
This message appears when a SELECT statement contains inappropriate arguments in the GROUP BY, HAVING, and/or ORDER BY clauses. Every value expression in the projection list that does not contain an aggregate function must also appear in the GROUP BY clause. Aggregate functions cannot appear in the GROUP BY clause. The HAVING clause must include either an aggregate function or a grouped column (that is, a column listed in the GROUP BY clause). The ORDER BY clause must include a grouped column.The optional SELECT clauses, if included, must appear in the following order:
- WHERE
- GROUP BY
- HAVING
- WITH SAMPLE OF
- ORDER BY
- FETCH FIRST...ONLY
Refer to the SAND CDBMS SQL Reference Guide for more information about the SELECT statement syntax.
50501 Incorrect Order By clause
This message appears when one or more SELECT statements are connected by the UNION keyword, and a SELECT statement other than the final one contains an ORDER BY clause. Only the last SELECT statement in a UNION may contain an ORDER BY clause, which is used to order the UNION output table. Also note that the ORDER BY clause must reference an output column by number.This message may also appear when an internal error prevents the successful execution of a SELECT statement with an ORDER BY clause. Retry the SQL command. If this error message appears again, the DBA should shut down the database instance, and then restart the instance and reestablish a connection. If this error message still appears in response to the original SQL command, contact a SAND support representative.
50502 Mismatched union fields
This message appears when a UNION is attempted between two tables with a different number of columns. The two tables must have the same number of columns, and the corresponding columns must have compatible data types or SAND CDBMS domains.50503 Invalid expression - Having without Group By
This message appears when a SELECT statement includes a column in the projection list and a HAVING clause, but does not include a GROUP BY clause. The SELECT statement cannot include a HAVING clause without a GROUP BY clause, unless the projection list and the HAVING clause contain only aggregate functions.50600 Sample incorrect argument list
This message appears when the SELECT...WITH SAMPLE OF clause specifies a number less than or equal to zero (0), or the number argument is greater than the factor argument. Ensure that the WITH SAMPLE OF number is a positive integer, and that number divided by factor does not produce a value greater than 1.0 (that is, 100%).50601 Incorrect With Sample Of clause
This message appears when one or more SELECT statements are connected by the UNION keyword, and a SELECT statement other than the final one contains a WITH SAMPLE OF clause. Only the last SELECT statement in a UNION may contain a WITH SAMPLE OF clause, which is used to return a subset of the UNION output table.50700 Fetch First incorrect argument list
This message appears when the FETCH FIRST...ONLY clause specifies zero or a negative number of rows, or specifies a ratio greater than 1.0. At least one row must be specified when fetching an absolute number of rows. When fetching a percentage of the result set, at most 100% of the results (a ratio of 1.0) can be returned.50701 Incorrect Fetch First Only clause
This message is returned when the FETCH FIRST...ONLY clause is not the last clause in the SELECT statement. Syntactically, the FETCH FIRST...ONLY clause must appear after all other SELECT clauses. In the case of a series of UNIONed SELECT statements, the FETCH FIRST...ONLY clause can be included only at the end of the final query.54500 Insufficient privileges
This message appears when an SQL statement references a database object on which the user issuing the SQL statement has no privileges. The user must be granted the required privilege on the database object by the owner of the object or a user with DBA privileges.54501 Cannot modify privileges for DBA authorization
This message appears when a GRANT or REVOKE statement attempts to modify the DBA's privileges. DBA privileges cannot be modified.54502 Cannot modify own privileges
This message appears when an authorization attempts to modify their own privileges through a GRANT or REVOKE statement. Users cannot modify their own privileges.54503 Cannot grant privileges - non-existent object
This message appears when a user attempts to grant privileges on a database object that does not exist in the current schema or database. If the object belongs to a different schema, qualify the object name with the schema name in the GRANT statement (that is, schema-name.object-name). If necessary, query the appropriate system table or PUBLIC view to determine the correct spelling of the database object name.54504 Cannot revoke privileges - non-existent object
This message appears when a user attempts to revoke privileges on a database object that does not exist in the current schema or database. If the object belongs to a schema other than the current one, qualify the object name with the schema name in the REVOKE statement (that is, schema-name.object-name). If necessary, query the appropriate PUBLIC view to determine the correct spelling of the database object name.54505 Invalid privilege
This message appears when a user attempts to grant or revoke an invalid privilege type. Refer to the GRANT or REVOKE command in the SAND CDBMS SQL Reference Guide for the full syntax of the command.54508 Non-existent routine
This message appears when an SQL statement contains a string that ends with the substring '()'or '(x)', where x is a numeric value, a string enclosed by single quotation marks, or the name of a column from a table referenced in the statement. The SAND CDBMS interprets this string as a routine call. Routines are not supported in the current release.54509 Non-existent privilege
This message appears when a REVOKE statement references a privilege that is not possessed by the specified authorization.62400 Non-existent connection
This message appears when a CREATE TABLE...WITH CONNECTION statement specifies a connection object that does not exist. If necessary, query the SYSTEM.CONNECTIONS table to determine the correct spelling of the connection name.62401 Drop connection failed - dependent object(s) exist(s)
This message appears when the DROP CONNECTION command specifies a connection on which one or more existing tables have been defined. Those tables must be dropped from the database before the connection can be removed.62402 Create connection failed - not a remote connection
This message appears when a CREATE CONNECTION command specifies the nucleus.ini Connection section that was used to start the local database. The CREATE CONNECTION command must reference a Connection section that is or will be used by a remote database.63400 Non-existent materialized join
This message appears when a REFRESH MATERIALIZED JOIN or DROP MATERIALIZED JOIN command specifies an unrecognized materialized join name. Before attempting the command again, check the spelling of the materialized join name and verify that it exists in the SYSTEM.JOININDEXES table.63401 Create materialized join failed - duplicate name
This message appears when a CREATE MATERIALIZED JOIN command specifies a materialized join name that already exists for the current schema. Either specify a different materialized join name, create the materialized join in a different schema, or drop the existing materialized join before attempting the CREATE MATERIALIZED JOIN command again.70400 Non-existent schema
This message appears when a SET SCHEMA or DROP SCHEMA statement references a schema name that does not exist in the current database, or when a database object name is qualified with a schema name that does not exist in the current database. If necessary, query the SYSTEM.SCHEMAS table or the PUBLIC.SCHEMAS view to determine the correct spelling of the schema name.80110 Create domain failed - invalid data type
This message appears when a CREATE DOMAIN statement specifies a nonexistent data type. Refer to the SAND CDBMS SQL Reference Guide for a list and description of the valid SQL data types.80111 Create domain failed - invalid precision
This message appears when a CREATE DOMAIN statement specifies a DEC, DECIMAL, or NUMERIC data type with a precision of 32 or greater, or zero (0). The maximum precision allowed for these data types is 31.80112 Create domain failed - invalid scale
This message appears when a CREATE DOMAIN statement specifies a DEC, DECIMAL, or NUMERIC data type with a scale greater than the precision, or less than zero (0). The scale must be less than or equal to the precision, and cannot be a negative number.80113 Create domain failed - invalid length
This message appears when a CREATE DOMAIN statement specifies a CHAR, CHARACTER, VARCHAR, CHARACTER VARYING, or CHAR VARYING data type with a length less than 1 or greater than 4056. If a length argument is included with the character data types, it must be a value between 1 and 4056.80140 Create domain failed - duplicate domain name
This message appears when a CREATE DOMAIN statement specifies a domain name that already exists in the database for the specified schema. Domain names must be unique within a schema.80141 Create domain failed - reserved domain name
This message appears when a CREATE DOMAIN statement specifies a domain name that begins with an underscore character ("_"). Only system-generated domains are permitted to begin with the underscore character.80310 Drop domain failed - dependent object(s) exist(s)
This message appears when one or more columns reference the domain specified in a DROP DOMAIN statement. Drop the columns that store values in the domain, or the tables containing those columns, before attempting to drop the domain.80311 Drop domain failed - system domain
This message appears when a DROP DOMAIN statement references a system domain (that is, any of the default domains belonging to the SYSTEM schema). System domains cannot be dropped.80400 Non-existent domain
This message appears when a DROP DOMAIN or RENAME DOMAIN statement references a domain name that does not exist in the database. If necessary, query the SYSTEM.DOMAINS table or the PUBLIC.DOMAINS view to determine the correct spelling of the domain name.80500 Rename domain failed - system domain
This message appears when a RENAME DOMAIN statement references a system domain (that is, any of the default domains belonging to the SYSTEM schema). System domains cannot be renamed.80501 Rename domain failed - new domain name already in use
This message appears when a RENAME DOMAIN statement attempts to change a domain name to one that already exists in the same schema. Domain names must be unique within a schema.80600 Alter domain failed - not a blob domain
This message appears when an ALTER DOMAIN statement specifies a domain not defined on the BLOB type. The ALTER DOMAIN command can be executed only against BLOB domains.80601 Alter domain failed - system domain
This message appears when attempting to execute the ALTER DOMAIN command against a SAND system domain. System domains cannot be changed.80602 Alter domain failed - already has text search
This message appears when attempting, via an ALTER DOMAIN statement, to associate a dictionary with a BLOB domain that already has a dictionary associated with it. To associate a new dictionary with a BLOB domain, first drop the old one using the ALTER DOMAIN...DROP DICTIONARY command.80603 Alter domain failed - does not have text search
This message appears when attempting, via an ALTER DOMAIN statement, to remove a dictionary from a BLOB domain that does not have text analytics enabled. That is, no dictionary is associated with the BLOB domain.80604 Alter domain failed - data type for dictionary is not VARCHAR
This message appears when attempting to associate a dictionary that is not of type VARCHAR with a BLOB domain, via an ALTER DOMAIN statement. All text analytics dictionaries must be defined on the VARCHAR(4056) data type, using the BINARY_UPCASE collation table.80605 Alter domain failed - length for dictionary is not 4056
This message appears when attempting to associate a dictionary that is less than 4056 characters in length with a BLOB domain, via an ALTER DOMAIN statement. All text analytics dictionaries must be defined on the VARCHAR(4056) data type, using the BINARY_UPCASE collation table.80606 Alter domain failed - dictionary collation must be UPCASE
This message appears when attempting, via an ALTER DOMAIN statement, to associate a dictionary with a BLOB domain, when that dictionary was not defined with the BINARY_UPCASE collation. All text analytics dictionaries must be defined on the VARCHAR(4056) data type, using the BINARY_UPCASE collation table.80607 Alter domain failed - an exclusive transaction is required
This message appears when attempting to execute an ALTER DOMAIN statement without first setting the isolation level to EXCLUSIVE for the current transaction. Since an exclusive connection to the database server is required to issue the ALTER DOMAIN command, the following command must be executed to start the transaction:SET TRANSACTION ISOLATION LEVEL EXCLUSIVE [ IMMEDIATE ];
80700 Text search failed
This message appears if a text search (a query of BLOB data, using the MATCHES predicate) fails for any reason. Refer to the secondary error message for further information about the cause of the error.90100 Create table failed - duplicate table name
This message appears when a CREATE TABLE or CREATE VIEW statement attempts to create a new table or view using a table/view name that already exists for the current schema. All table/view names must be unique within a schema.90200 Create table failed - column name cannot be an expression
This message appears when a CREATE TABLE or CREATE VIEW statement includes an unnamed value expression (that is not a direct column reference) in the projection list of the defining SELECT statement. The value expression must be given an alias, which will be the name of the output column when the view is queried.90201 Create view failed - a column is a projected expression that is not named
This message appears when a CREATE TABLE or CREATE VIEW statement includes an unnamed value expression (that is not a direct column reference) in the projection list of the defining SELECT statement. The value expression must be given an alias, which will be the name of the output column when the view is queried.90205 Create table failed - too many columns in table definition
This message appears when a CREATE TABLE statement specifies 4097 or more columns. A maximum of 4096 columns are permitted per table.This error is also returned when the number of arguments in the view column list of a CREATE VIEW statement is more or less than the number of output columns returned by the defining query expression. The number of view column names must match precisely the number of columns in the query expression result table.
90206 Create table failed - too many keys in constraint definition
This message appears when a CREATE TABLE or ALTER TABLE statement includes 65 or more columns in a UNIQUE, PRIMARY KEY, or FOREIGN KEY table constraint definition. These constraints can have at most 64 participating columns.90207 Create table failed - no column name provided in key definition
This message appears when a CREATE TABLE or ALTER TABLE statement includes a PRIMARY KEY, FOREIGN KEY, or UNIQUE table constraint definition with an empty column list. The column list of a PRIMARY KEY, FOREIGN KEY, or UNIQUE table constraint must reference at least one column in the designated table.90220 Create table failed - duplicate unique constraint
This message appears when a CREATE TABLE or ALTER TABLE...ADD COLUMN statement repeats the UNIQUE keyword for a column constraint. For example,
CREATE TABLE t (c1 INT UNIQUE UNIQUE);A UNIQUE constraint can be defined only once for a particular column.
90221 Create table failed - duplicate default clause
This message appears when a CREATE TABLE or ALTER TABLE statement includes more than one DEFAULT clause for the same column definition. A column can have only one default value specified.90222 Create table failed - duplicate foreign key reference
This message appears when a CREATE TABLE or ALTER TABLE statement attempts to set a foreign key column constraint more than once on the same column. A column can have only one foreign key column constraint defined on it.90250 Create view failed - partition clause error
This message appears when a CREATE PARTITION TABLE or CREATE VIEW...PARTITION BY statement contains a mistake. For example, this error would be returned in the following situations:
- the same partition is specified more than once
- the same key column is specified more than once
- a key column is not in the specified partition(s)
- a range is specified for a non-RANGE partitioning strategy
- a RANGE partition is defined without a range
- the last RANGE partition has a range specification
Before attempting to create the partitioned table again, verify the correctness of the SQL statement.
90310 Drop table failed - dependent object(s) exist(s)
This message appears when a DROP TABLE statement specifies a table that is referenced by one or more other objects (such as views, snapshot tables, foreign key constraints, materialized joins). Drop the dependent object(s) explicitly before attempting to drop the table, or use the DROP...CASCADE option to drop the dependent object(s) automatically along with the table.90311 Drop table failed - cannot drop system level table
This message appears when a DROP TABLE statement specifies a system table (that is, any of the default tables in the SYSTEM schema). These system tables are essential to the functioning of the database and cannot be dropped.90312 Drop table failed - table is a view
This message appears when a DROP TABLE statement references a view. Use a DROP VIEW statement to remove a view from the database.90313 Drop view failed - base table
This message appears when a DROP VIEW statement specifies a table. Use a DROP TABLE statement to remove a table from the database.90314 Drop view failed - dependent object(s) exist(s)
This message appears when a DROP VIEW statement specifies a view on which one or more other views or snapshot tables are based. The view cannot be dropped until the dependent object(s) are dropped. The DROP...CASCADE option can be used to drop the dependent object(s) automatically along with the view, or else the dependent object(s) can be explicitly dropped one by one before the view is dropped.90315 Drop snapshot failed - not a snapshot
This message appears when the DROP SNAPSHOT TABLE references a non-snapshot table. Use the DROP TABLE command instead to drop a standard table or view.90316 Drop snapshot failed - dependent object(s) exist(s)
This message appears when a DROP SNAPSHOT TABLE statement specifies a snapshot table on which one or more views or other snapshot tables are based. The snapshot table cannot be dropped until the dependent object(s) are dropped. The DROP...CASCADE option can be used to drop the dependent object(s) automatically along with the snapshot table, or else the dependent object(s) can be explicitly dropped one by one before the snapshot table is dropped.90317 Refresh snapshot failed - not a snapshot
This message appears when the REFRESH SNAPSHOT TABLE command is executed against a non-snapshot table. The REFRESH SNAPSHOT TABLE command is not meaningful for standard tables and views.90320 Alter table failed - non-existent constraint
This message appears when an ALTER TABLE...DROP CONSTRAINT statement references a nonexistent constraint. Constraints can only be dropped by specifying the constraint name. If a constraint was created without a user-defined name, one was automatically generated by SAND CDBMS. The easiest way to determine the constraint name is to violate the constraint intentionally. This will produce an error message that lists the name of the violated constraint.90321 Alter table failed - system table
This message appears when an ALTER TABLE statement attempts to modify the structure of a system table (that is, any of the default tables in the SYSTEM schema). These system tables are essential to the functioning of the database and cannot be altered directly.90322 Alter table failed - cannot alter a view
This message appears when an ALTER TABLE statement attempts to modify a view. If you wish to change a view definition, drop the view, then recreate the view with the desired attributes.90323 Alter table failed - too many columns in table definition
This message appears when an ALTER TABLE statement attempts to add a column to a table that already has 4096 columns. The maximum number of columns per table is 4096.90324 Alter table failed - no disabled constraints
This message appears when an ALTER TABLE...ENABLE CONSTRAINTS command is executed against a table that has no disabled constraints.90325 Alter table failed - constraint not disabled
This message appears when an ALTER TABLE...ENABLE CONSTRAINT constraint-name command specifies a constraint that is not disabled.90326 Alter table failed - no enabled constraints
This message appears when an ALTER TABLE...DISABLE CONSTRAINTS command is executed against a table that has no enabled constraints.90327 Alter table failed - constraint not enabled
This message appears when an ALTER TABLE...DISABLE CONSTRAINT constraint-name command specifies a constraint that is not enabled.90330 Rename table failed - system table
This message appears when a RENAME TABLE statement references a system table (that is, any table in the SYSTEM schema). System tables cannot be renamed.90331 Rename table failed - dependent object(s) exist(s)
This message appears when RENAME TABLE statement attempts to rename a table that is referenced by one or more other objects. The dependent object(s) must be dropped before the table can be renamed.90332 Rename table failed - table already exists
This message appears when a RENAME TABLE statement attempts to change the name of a table to one that already exists in the same schema. All table names must be unique within a schema.90400 Non-existent table
This message is returned when an ALTER TABLE, CREATE VIEW, DELETE, DROP TABLE, DROP VIEW, INSERT, SELECT, or UPDATE statement references a table or view name that does not exist in the current schema. If the table or view belongs to a schema other than the current one, the table/view name must be qualified with the schema name (that is, schema-name.table-name or schema-name.view-name). If necessary, query the SYSTEM.TABLES table or the PUBLIC.TABLES view to determine the correct spelling of the table/view name.J0100 Invalid foreign key - duplicate definition
This message appears when a CREATE TABLE statement includes multiple occurrences of the same FOREIGN KEY constraint definition. Remove the redundant constraint definitions before attempting the CREATE TABLE statement again.J0101 Invalid foreign key - non-existent referenced table
This message appears when a CREATE TABLE or ALTER TABLE statement attempts to define a FOREIGN KEY constraint that references a parent table that does not exist in the database. Ensure that the correct table name is being used in the FOREIGN KEY constraint definition before attempting the CREATE TABLE or ALTER TABLE statement again.J0103 Invalid foreign key - non-existent referencing column
This message appears when a CREATE TABLE or ALTER TABLE statement attempts to define a FOREIGN KEY constraint on a column that does not exist in the table being created or altered. Ensure that the FOREIGN KEY constraint is being defined on the correct column name before attempting the CREATE TABLE or ALTER TABLE statement again.J0104 Invalid foreign key - cannot reference a view
This message appears when a CREATE TABLE or ALTER TABLE statement attempts to define a FOREIGN KEY constraint that references a view rather than a parent table. A FOREIGN KEY constraint cannot be defined in reference to a view.J0105 Invalid foreign key - column repeated in definition
This message appears when a CREATE TABLE or ALTER TABLE statement attempts to define a composite FOREIGN KEY constraint that specifies the same column more than once. A composite FOREIGN KEY constraint cannot include repeated columns.J0107 Invalid foreign key - type mismatch between referenced and referencing column
This message appears when a CREATE TABLE or ALTER TABLE statement includes a FOREIGN KEY constraint definition where there is at least one foreign key column that does not share the same data type as the corresponding parent table column. There must be an exact data type match between foreign key columns and parent table columns (respective domains can differ if they are defined on exactly the same data type.)J0108 Invalid foreign key - non-existent parent constraint
This message appears when a CREATE TABLE or ALTER TABLE statement includes a FOREIGN KEY constraint definition that references one or more parent table columns on which there are no PRIMARY KEY or UNIQUE constraints defined, or that references a non-existent parent table column. Foreign keys can be defined only in reference to columns in the parent table that are defined as PRIMARY KEY or UNIQUE.J0109 Invalid foreign key - mismatch in number of parent key columns
This message appears when a CREATE TABLE or ALTER TABLE statement contains a FOREIGN KEY constraint definition where the number of foreign key columns does not correspond to the number of referenced columns. Ensure that the FOREIGN KEY constraint definition specifies the correct columns before attempting the CREATE TABLE or ALTER TABLE statement again.J0111 Invalid foreign key - SET NULL is not compatible with a NOT NULL constraint
This message appears when a FOREIGN KEY constraint is defined on a NOT NULL column and includes the SET NULL option for ON UPDATE and/or ON DELETE. Since the NOT NULL constraint and the SET NULL referential action on a column are contradictory, they cannot both be applied to the same column.J0113 Invalid foreign key - existing rows would violate the proposed constraint
This message appears when an ALTER TABLE statement attempts to add a FOREIGN KEY constraint that would be violated by the existing records in the table (that is, at least one column in the proposed foreign key contains a value not found in the corresponding column of the parent table). In order to add the FOREIGN KEY constraint, the offending value(s) in the child table would have to be removed first, or identical value(s) would first have to be added to the parent table.J0114 Invalid foreign key - referenced constraint is not enabled
This message appears when a CREATE TABLE or ALTER TABLE statement includes a FOREIGN KEY constraint definition that references one or more parent table columns whose PRIMARY KEY or UNIQUE constraint is disabled. Before attempting the CREATE TABLE or ALTER TABLE statement again, ensure that the required parent table constraints have been enabled via the ALTER TABLE...ENABLE CONSTRAINT[S] command.J0200 Invalid unique constraint - non-existent column(s) in definition
This message appears when a CREATE TABLE or ALTER TABLE statement attempts to set a UNIQUE constraint on a column that does not exist in the table. For an ALTER TABLE statement, if necessary, query the SYSTEM.COLUMNS table or the PUBLIC.COLUMNS view to determine the correct spelling.J0201 Invalid unique constraint - column repeated in definition
This message appears when a CREATE TABLE or ALTER TABLE statement attempts to include the same column in more than one UNIQUE constraint, or in one PRIMARY KEY constraint and one or more UNIQUE constraints, within the same statement. A column may participate in at most one UNIQUE constraint; if a column participates in a UNIQUE constraint, it cannot subsequently participate in a primary key.This message is also generated when the same column name is repeated in a UNIQUE constraint definition in a CREATE TABLE or ALTER TABLE statement. A particular column name can be included only once per table constraint definition.
J0203 Invalid unique constraint - existing rows would violate the proposed constraint
This message appears when an ALTER TABLE statement attempts to add a UNIQUE or PRIMARY KEY constraint to a table that has duplicate values in the proposed key column(s). The UNIQUE and PRIMARY KEY constraints ensure that each value or set of values in the participating column(s) is unique, and therefore cannot be added to a table whose existing values would immediately violate the constraint.J0204 Invalid unique or primary key constraint - a key is a subset of another key
This message appears when an ALTER TABLE statement attempts to add a UNIQUE or PRIMARY KEY constraint that includes a column already participating in a UNIQUE constraint. A column can participate in at most one UNIQUE constraint, and a column that is part of a UNIQUE constraint cannot also be part of a primary key.J0205 Invalid unique or primary key - a referencing constraint is not disabled
This message appears when an ALTER TABLE statement attempts to disable a UNIQUE or PRIMARY KEY constraint that is referenced in a FOREIGN KEY constraint. Either the FOREIGN KEY must be disabled or dropped first, or the CASCADE option must be included in the ALTER TABLE...DISABLE CONSTRAINT[S] statement to automatically disable the FOREIGN KEY before disabling the UNIQUE or PRIMARY KEY.J0300 Invalid primary key constraint - only one primary key allowed
This message appears when a CREATE TABLE statement attempts to set more than one primary key column constraint, or an ALTER TABLE statement attempts to add a primary key constraint to a table that already has one. A table can have at most one primary key constraint. If you wish to change the primary key constraint on a table, drop the existing primary key constraint through the ALTER TABLE...DROP CONSTRAINT command, then use the ALTER TABLE...ADD CONSTRAINT command to set the desired primary key constraint.J0301 Invalid primary key constraint - non-existent column(s) in definition
This message appears when a CREATE TABLE or ALTER TABLE statement attempts to set a primary key constraint on a column that does not exist in the table.J0302 Invalid primary key constraint - column repeated in definition
This message appears when a CREATE TABLE or ALTER TABLE statement attempts to set a primary key constraint on the same column more than once in the same statement.J0303 Invalid primary key constraint - duplicate constraint
This message appears when a CREATE TABLE statement attempts to include the same set of columns in a PRIMARY KEY constraint more than once. A PRIMARY KEY constraint can be defined only once per table.J0304 Invalid primary key constraint - null value in constraint definition
This message appears when an ALTER TABLE statement attempts to include a column that contains a null value as part of a primary key constraint. No individual column participating in a primary key constraint may contain a null value.J0400 Invalid constraint definition - duplicate constraint name
This message appears when a CREATE TABLE statement includes two constraint definitions with the same constraint name, or when an ALTER TABLE statement attempts to add a constraint whose name matches one already defined for the table. Each constraint defined on the same table must have a unique constraint name.K0100 Invalid column definition - invalid data type
This message appears when a CREATE TABLE or ALTER TABLE statement defines a column with an unrecognized data type or SAND CDBMS domain. Refer to the SAND CDBMS SQL Reference Guide for a list and description of the valid SQL data types. If necessary, query the SYSTEM.DOMAINS table or the PUBLIC.DOMAINS view to determine the correct spelling of the SAND CDBMS domain name. Note that if a referenced domain belongs to another schema, the domain name must be qualified by the schema name; that is, schema-name.domain-name.K0101 Invalid column definition - invalid precision
This message appears when a CREATE TABLE or ALTER TABLE statement specifies a DEC, DECIMAL, or NUMERIC data type with a precision less than 1 or greater than 31. The minimum precision permitted for these data types is 1; the maximum is 31.K0102 Invalid column definition - invalid scale
This message appears when a CREATE TABLE or ALTER TABLE statement specifies a DEC, DECIMAL, or NUMERIC data type with a scale greater than the precision. The scale must be less than or equal to the precision.K0103 Invalid column definition - invalid length
This message appears when a CREATE TABLE or ALTER TABLE statement specifies a column of type CHAR or VARCHAR with a length greater than the maximum size (4056) or less than the minimum (1). Consult the SAND CDBMS SQL Reference Guide for more information about the SAND CDBMS SQL string data types.K0104 Invalid column definition - invalid default value
This message appears when the default value specified for a column in a CREATE TABLE or ALTER TABLE statement is incompatible with the data type of the column. The default value must be the same data type (NUMERIC, CHARACTER, or DATE/TIME), and must conform to the length or precision/scale arguments defined on the column.K0106 Invalid column definition - duplicate not null constraint
This message appears when a CREATE TABLE or ALTER TABLE statement defines two or more NOT NULL constraints on the same column. A column can have at most one NOT NULL constraint.K0200 Invalid column definition - duplicate column name
This message appears when a CREATE TABLE or CREATE VIEW statement defines two or more columns with the same name. This message is also generated when the new column name specified in an ALTER TABLE...ADD COLUMN or ALTER TABLE...RENAME COLUMN statement duplicates a column name that already exists in the table. Each column in the same table or view must have a unique name.K0300 Drop column failed - column is part of a constraint key
This message appears when an ALTER TABLE...DROP COLUMN statement attempts to drop a column that is part of a multi-column table constraint. Drop the table constraint before attempting to drop the column, and then redefine the table constraint without the dropped column.K0301 Drop column failed - foreign key(s) reference(s) this column
This message appears when an ALTER TABLE...DROP COLUMN statement attempts to drop a column that is referenced by one or more foreign key constraints. Drop the foreign key constraint(s) before attempting to drop the column, and then redefine the foreign key constraints without the dropped column.K0302 Drop column failed - dependent view(s)
This message appears when an ALTER TABLE...DROP COLUMN statement attempts to drop a column that is referenced by one or more other objects, such as views or snapshot tables. Use the ALTER TABLE...DROP COLUMN...CASCADE option to drop the dependent object(s) automatically along with the column, or else drop the dependent object(s) explicitly before attempting to drop the column.K0310 Drop column failed - too few columns in table definition
The message appears if an ALTER TABLE...DROP COLUMN statement attempts to drop the only column in the specified table. A table must have at least one column.K0400 Non-existent column
This message appears when a CREATE TABLE, ALTER TABLE, INSERT, UPDATE, GRANT, or REVOKE statement references a column name that does not exist in the specified table. The message is also returned if a SELECT statement using the JOIN syntax neglects to reference any columns from one of the joined tables. At least one column from each table in the join must be referenced in the join condition.K0500 Ambiguous column reference
This message appears when a SELECT or CREATE statement, or the query expression clause of an INSERT statement, does not qualify duplicate column names selected from multiple tables or views. To avoid this error, prefix the column names with the respective table, view, or correlation names, followed by a period (that is, table-name.column-name, view-name.column-name, or correlation-name.column-name).The error may also appear if a joined table expression contains an unsupported predicate, for example, if the same column is being compared to itself (such as "t1.c1 = t1.c1").
K0600 Mismatch between column list and columns in table
This message appears when an INSERT statement contains a column list with duplicate column names, or when an UPDATE statement attempts to update the same column more than once. The same column name may not be specified more than once in an INSERT column list or in the SET clause of an UPDATE statement.K0700 Table name appears more than once
This message appears when a SELECT or CREATE VIEW statement, or the query expression clause of an INSERT statement, specifies the same table or view name more than once in the FROM clause, without correlation or schema qualification. The table, view, or correlation names appearing in the FROM clause must be unique. The following statement, for instance, produces this error message:
SELECT column1, column3
FROM table_name, table_name ;If the duplicate table/view names use correlation names, the statement becomes legal, as there are now two separate instances of table table_name in the FROM list:
SELECT t1.column1, t2.column3
FROM table_name t1, table_name t2 ;Tables or views sharing the same name but belonging to different schemas may also appear in the FROM clause, provided they are prefixed with their respective schema name, for example:
SELECT *
FROM schema1.table_name, schema2.table_name ;M0100 Insert failed - incorrect number of values
This message appears when an INSERT statement attempts to insert more or less values than there are columns in the target table. The number of values inserted into a table must correspond exactly to the number of data fields in the table.N0001 Expression evaluation error
This message appears when an SQL statement contains an arithmetic expression that produces a value greater than or less than the numeric data type or domain intended to store the value. Refer to the SAND CDBMS SQL Reference Guide for the valid ranges of the numeric SQL data types.O0100 Invalid database reference
This message appears when a database object is qualified with a database name, for instance, database-name.schema-name.table-name. Database objects may not be qualified with the database name in the current release of SAND CDBMS.O0200 Table reference limit exceeded
This message appears when the number of tables referenced in a single query expression exceeds 128. The maximum number of table references permitted in a query, including the tables referenced in subqueries and in the definitions of all views in the query, is 128. If possible, reformulate the query with fewer table references.O0201 Column reference limit exceeded
This message appears when the number of columns referenced in a single query expression exceeds 8192. The maximum number of column references permitted in a query, including the tables referenced in subqueries and in the definitions of all views in the query, is 8192. If possible, reformulate the query with fewer column references.P0200 Vector subsystem failure - EID out of range
An internal error has occurred. Report this error and the circumstances to a SAND support representative.P0300 Execution failure - Join intermediate exceeds limit
This message appears when a query expression join produces an intermediate result table with more rows than the set limit. By default, the maximum size is five hundred billion (500,000,000,000) rows, but this limit can be lowered by setting the nucleus.ini JoinLimit parameter or by executing the ALTER SESSION SET JOINLIMIT command. If the intermediate join limit has been changed from the default, try increasing the limit and running the query again. If necessary, try rewriting the query expression to reduce the complexity of the join, or utilize views that deal with a subset of the data in the original join tables.P0400 Execution failure - Statement execution has been terminated
This message appears when a user’s running query has been cancelled, either by the user or another user with DBA privileges.Q0100 Open database failure
This message appears when SAND CDBMS fails to read a database. This can be caused by hardware or operating system issues. Consult your system administrator for help with resolving this problem.Q0101 Open database failure - another database instance is already running
This message appears if an attempt is made to start a database instance while another database instance is already running. A database server (nserv) process can run only one database instance at a time.Q0102 Open database failure - non-existent database
This message appears when a client application attempts to connect to a database that does not have a section header in the server-side nucleus.ini file and is not located in the SAND CDBMS support directory. Make sure that a corresponding entry for the database exists in the server-side nucleus.ini file before attempting to connect to the database.Q0103 Open database failure - no read permission
This message appears when a user attempts to connect to a database instance on which the database server (nserv) process does not have read permission. Ask the system administrator to change the permissions on the appropriate database files, so as to allow server read access to the database.Q0200 Remote database error
This message appears when an SQL command could not be successfully executed against a remote database. This error can be generated in a number of different ways, so view the secondary message for further details. Some common ways to produce this error includes attempting to alter a remote table (the table and its contents are read only), querying a remote table on which the user's privileges have been revoked, querying a remote table that has had one or more columns removed, and attempting to query a remote table that has been dropped from the remote database.Note that the secondary message "Couldn't connect to the server" will be returned if the remote database has been shut down and restarted during the current user session. To start a new transaction and access the remote database in the current session, execute either a COMMIT [WORK] or ROLLBACK command.
S0101 Execution failure - function not implemented
If the secondary message is "Load initialization failure due to active applications", this error was likely caused by an attempt to load into a database that has one or more non-loader clients connected. Before reattempting the load operation, the non-loader users should be instructed to disconnect, or the -u flag should be included in the ndlm invocation to disconnect other users automatically.If the secondary message is anything else, then an internal error has occurred. Report this error and the circumstances to a SAND support representative.
T0803 Execution failure - time limit exceeded
This message appears when the execution time of an individual SQL command within a transaction exceeds the time limit specified in the SET TRANSACTION..TIMEOUT statement that began the transaction. The message is also returned when the execution time exceeds the time limit established with the nisqlm .SESS DURATION command. Note that SET TRANSACTION...TIMEOUT sets its limit in seconds, while the .SESS DURATION limit is in minutes.