Messages Guide

This manual was written for Trafodion database administrators and programmers who use the Trafodion database software conversational or programmatic interface.

Messages for UPDATE STATISTICS have been corrected. Also messages for the new incremental UPDATE STATISTICS features have been added.

This list summarizes the notation conventions for syntax presentation in this manual.

We encourage your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to user@trafodion.incubator.apache.org.

Include the document title and any comment, error found, or suggestion for improvement you have concerning this document.

Trafodion reports exception condition messages at a Trafodion Database Connectivity Service conversational interface (DCS) window and in the Trafodion Command Interface (TrafCI).

Most Trafodion exception condition messages describe error conditions for which recovery action is required. Some messages are warnings that provide information for which no action is required.

Error messages that appear in response to SQL commands are logged to the DCS application’s log file if you have used the LOG command to request them.

The format of a Trafodion error is "* ERROR" followed by the error number in brackets, and the descriptive text. Use the error number shown to find information about a particular error in this manual. For example, information for Trafodion error 1125 can be found under "SQL 1125."

Messages are listed in this manual in numeric order, broken down by the component that produced them.

The message key is a sequential SQL message number that is returned automatically by Trafodion when an exception condition occurs. For example, the following message might be displayed within your application development tool while you prepare an embedded SQL program:

This message number is the SQLCODE value (without the sign). In this manual, you will find the following message information for ERROR[1000]:

SQLSTATE and SQLCODE status codes are returned to indicate either that an SQL statement completed successfully or that an exception condition was raised during execution of an SQL statement.

The ANSI SQL SQLSTATE variable is a five-character string with a two-character class code followed by a three-character subclass code. An SQLSTATE value of 00000 indicates successful completion.

Trafodion extends the ANSI SQL SQLSTATE values to include other situations not described by the ANSI values. If an ANSI SQL SQLSTATE value exists for an error condition, the Trafodion database software returns that value. Otherwise, Trafodion returns an SQLSTATE value that is defined by the Trafodion database software.

Trafodion also returns a numeric SQLCODE value after SQL statement execution. SQLCODE values with negative numbers signify errors.

SQLCODE values with positive numbers other than 0 (successful completion) or 100 (no data was found) signify warning messages. Trafodion identifies all messages by their unsigned SQLCODE value and their calculated SQLSTATE value. The SQLCODE is used to calculate the SQLSTATE value for all Trafodion messages other than those for which an ANSI SQL SQLSTATE value exists.

The SQLCODE parameter is a deprecated feature that is supported to maintain compatibility with earlier versions of the American standard.

SQLSTATE Values identifies the equivalent SQLSTATE and SQLCODE values for Trafodion warning and error messages.

Some messages have no recovery and you will be instructed to contact user@trafodion.incubator.apache.org.

Where <module-name> is the name of a Trafodion source code module.

Where <line-number> is the number of a line within the source code module.

Where <details> gives additional information as to the error.

Cause: An internal error occurred in the Trafodion software.

Effect: The operation fails.

Recovery: None. Contact the Trafodion Developer Distribution List.

Where <catalog> is the ANSI name of the target catalog.

Cause: The catalog does not exist.

Effect: The operation fails.

Recovery: Enter a valid catalog name and resubmit.

Where <schema> is the ANSI name of the affected schema.

Cause: The statement specified a schema that does not exist.

Effect: The operation fails.

Recovery: Check that a schema named <schema> does exist and resubmit.

Where <object-name> is the name of a Trafodion database object.

Cause: You attempted an operation on an object that does not exist.

Effect: The operation fails.

Recovery: Check that an object named <object-name> does exist. If you did not fully qualify the name, check that the defaults generate the correct fully qualified name and resubmit.

Where <constraint-name> is the name of a column constraint or table constraint.

Cause: The ALTER TABLE statement you attempted requires the existence of a constraint named <constraint-name>.

Effect: The operation fails.

Recovery: Check that a constraint named <constraint-name> exists for the table specified. You can use the SHOWDDL command to find the names of the constraints that exist on a table.

Cause: You attempted to GRANT privileges on a metadata table using the WITH GRANT OPTION. This is not allowed.

Effect: The operation fails.

Recovery: Remove the WITH GRANT OPTION clause and resubmit.

Where <auth-id> is a Trafodion platform user name or role name.

Cause: The name specified in a GRANT or REVOKE statement, or the authorization ID in a CREATE SCHEMA statement, does not represent a valid Trafodion platform user or role.

Effect: The operation fails.

Recovery: Correct the name and resubmit.

Where <column-name> is an SQL identifier.

Cause: The table that is referenced does not have a column with this name.

Effect: The operation fails.

Recovery: Replace either the name of the table or the name of the column (whichever is incorrect) and resubmit.

Cause: The statement that you specified is not available for use.

Effect: The operation fails.

Recovery: Do not attempt to use this Trafodion database statement.

Cause: The GRANT or REVOKE statement specified more than one user name or role name. This is currently not supported.

Effect: The operation fails.

Recovery: Resubmit the GRANT or REVOKE for each user name or role name individually.

Cause: You attempted to grant privileges for which you do not have grant options.

Effect: No privileges are granted.

Recovery: You must have grant options for privileges to grant them.

Where <privilege> is a Trafodion privilege on some Trafodion object..

Cause: You attempted to grant privileges, but you do not have grant options for at least the one named.

Effect: The Trafodion database granted some privileges, but not all that you attempted to grant.

Recovery: You must have grant options for privileges to grant them.

Where <privilege> is a Trafodion privilege on some Trafodion object..

Cause: You attempted to revoke a privilege that does not exist or that was granted by another user.

Effect: The Trafodion database did not revoke the privileges.

Recovery: The user who granted the privileges must revoke them.

Where <column-name> is an SQL identifier.

Cause: You created a constraint with multiple references to <column-name>.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You attempted a replication operation without proper authorization.

Effect: The operation fails.

Recovery: In a replication context: Only the catalog owner and the local super ID can perform a replication operation for a catalog and for multiple schemas in a single catalog. Additionally, the schema owner can perform a replication operation for a single schema.

Where <privilege> is a Trafodion privilege and <user-or-role-1> and <user-or-role-2> are user IDs or roles.

Cause: You attempted to revoke a privilege from <user-or-role-2> via <user-or-role-1>, but <user-or-role-1> did not grant that privilege to <user-or-role-2>. Note that <user-or-role-2> can be PUBLIC but <user-or-role-1> cannot.

Effect: The operation fails.

Recovery: If <privilege> or <user-or-role-2> are incorrect, correct them and resubmit. If <user-or-role-1> is incorrect, reconnect to the Trafodion database via the correct user ID or role.

Cause: You attempted to change privilege settings on a metadata table. They cannot be changed.

Effect: Trafodion does not change the settings.

Recovery: None.

Where <node-name> is the name of the system on which the INITIALIZE SQL statement was executed.

Cause: The Trafodion database has already been initialized on this node.

Effect: No operation is performed.

Recovery: None needed if SQL is operating normally.

Where <schema-name> is the name of a Trafodion database schema.

Cause: You attempted to create a schema in a catalog that already contains a schema with that name.

Effect: The operation fails.

Recovery: If you did not use a fully qualified name, check that the default generates the correct catalog name. Retry the request, specifying a schema that does not already exist.

Cause: This error can occur when you drop a constraint, index, or table. These objects cannot be dropped if they have dependent objects and the drop-behavior is RESTRICT.

Effect: Trafodion does not perform the operation.

Recovery: For DROP statements that support the CASCADE drop-behavior, you can reissue the statement specifying CASCADE. For other DROP statements, you must first drop each of the dependent objects, then drop the object.

Where <view-name> is the name of the view specified.

Cause: You attempted to grant column privileges on a view that was created on an earlier release of the Trafodion software, before column privileges were supported.

Effect: No column privileges were granted.

Recovery: Drop and recreate the view, then resubmit the grant request.

Where <object-name> is the name of a Trafodion database object existing in the schema.

Cause: You attempted to drop a schema that contains one or more objects.

Effect: The schema is not dropped.

Recovery: Either drop all the objects in <schema-name> and resubmit the statement, or resubmit the drop statement using the CASCADE option.

Where <object-name> is the name supplied in a CREATE statement.

Cause: This error can result from various CREATE statements. See the accompanying error messages to determine the cause.

Effect: The object is not created.

Recovery: Apply the recovery of the accompanying error messages.

Where <actual-length> is the length of the generated HBase name.

Where <max-length> is the maximum allowed HBase name length.

Cause: You attempted to create a Trafodion object which Trafodion stores in an HBase file. The generated HBase name (consisting of catalog name, schema name and object name, separated by periods) is too long for HBase.

Effect: The operation fails.

Recovery: Use a shorter name and resubmit.

Where <object-name> is the SQL object.

Cause: See the accompanying error message for the cause.

Effect: Trafodion does not drop the object.

Recovery: Apply the recovery of the accompanying error message.

Cause: You used the DISPLAY command to get insight into the plan generated for a particular query. When DISPLAY is used, the query is not executed.

Effect: The query is not executed.

Recovery: If you wish to execute the query, resubmit without the DISPLAY command.

Cause: You attempted a DDL or GRANT/REVOKE operation but Trafodion could not retrieve privilege information needed to process the request. Additional error messages may give insight to the cause.

Effect: The operation is not executed.

Recovery: None. Contact the Trafodion Developer Distribution List.

Where <catalog-name> is the name of a Trafodion database catalog.

Cause: You attempted to create a catalog using the name of an already existing catalog.

Effect: The operation fails.

Recovery: None if this is the desired catalog. Otherwise, correct the catalog name and resubmit.

Where <auth-id-1> is the authorization ID performing the GRANT.

Where <auth-id-2> is the authorization ID that is the target of the GRANT.

Cause: There is a chain of grants leading from <auth-id-2> back to <auth-id-1>. Granting this request might create a circular dependency.

Effect: The operation fails.

Recovery: None.

Where <auth-id-1> and <auth-id-2> are authorization IDs.

Cause: You attempted to revoke a privilege from <auth-id-1>, but that user or role has granted that privilege to a third authorization ID.

Effect: The operation fails.

Recovery: Reconnect to the Trafodion database using an authorization ID that can revoke the dependent privileges, then reconnect again under the original authorization ID and resubmit.

Cause: You attempted to revoke privileges from an authorization ID, but you do not have the ability (grant option) to perform this operation.

Effect: The operation fails.

Recovery: Reconnect to the Trafodion database using an authorization ID that has grant option for these privileges and resubmit.

Cause: An ALTER TABLE statement was issued naming a table that is part of the Trafodion database metadata. Such tables cannot be altered.

Effect: The operation fails.

Recovery: None.

Cause: You attempted to add a primary key to a table that already has a primary key.

Effect: The operation fails.

Recovery: None.

Cause: You did not specify NOT NULL on one or more columns that are included in a UNIQUE or PRIMARY KEY constraint.

Effect: The operation fails.

Recovery: Reissue the statement with NOT NULL specified for all columns that are in the PRIMARY KEY and UNIQUE constraints.

Where <constraint-name> is the name of a column constraint or table constraint.

Cause: You assigned the same constraint name to two constraints on the same table. Constraint names must be unique among all the constraints for a table.

Effect: The operation fails.

Recovery: Make all the constraint names for the table unique. Use SHOWDDL to see the names of existing constraints.

Where <constraint-name> is the name of a column constraint or table constraint.

Cause: The columns that <constraint-name> references in the referenced table are not part of a unique constraint.

Effect: The operation fails.

Recovery: Check that <constraint-name> references a unique or primary constraint in the referenced table.

Cause: The referential constraint is referencing the unique constraint that is declared as deferrable. This is an internal error.

Effect: The operation fails.

Recovery: Check that the referential constraint references a unique constraint that is not declared deferrable. Contact the Trafodion User Distribution List

Where <constraint-name> is the name of a column constraint or table constraint.

Cause: The list of referencing columns in <constraint-name> does not match the list of unique key columns that it is referencing.

Effect: The operation fails.

Recovery: Check that the <constraint-name> list of referencing columns matches the list of referenced columns.

Where <view-name> is the name of the view on the object being dropped.

Cause: An object that has a dependent view cannot be dropped unless you use the CASCADE option on the DROP statement.

Effect: The operation fails.

Recovery: To drop the object and all its dependent objects, you can either drop each of the dependent objects using individual DROP statements before dropping the object itself, or use the CASCADE clause on the DROP statement for the object.

Cause: Drop behavior CASCADE was specified on a DROP statement that supports only RESTRICT drop behavior.

Effect: The operation fails.

Recovery: Reissue the DROP statement, specifying RESTRICT or omitting the drop behavior (which will default to RESTRICT).

Cause: You attempted to drop a constraint that is NOT DROPPABLE.

Effect: The operation fails.

Recovery: None.

Cause: You attempted to drop a unique or primary constraint, with dependent referential constraints, using the RESTRICT option, which does not remove such constraints.

Effect: The drop command fails.

Recovery: If you want to drop the dependent referential constraints, use the CASCADE option for the DROP CONSTRAINT command.

Where <object-name> is the name of the object for which you have insufficient privileges.

Cause: You have insufficient privileges to create a view or a trigger.

Effect: The operation fails.

Recovery: See the Trafodion SQL Reference Manual for the required security needed to create a view or trigger.

Cause: You specified ALTER TABLE DROP CONSTRAINT to drop a constraint from a given table. The constraint you specified, however, does not belong to the table you specified.

Effect: The operation fails.

Recovery: To learn if the constraint name is incorrect, use SHOWDDL on the table you specified. Correct the name and resubmit.

Where <index-name> is the name specified for the index to create.

Cause: The rows already existing in the table violate the uniqueness constraint specified in the CREATE INDEX statement.

Effect: The index is not created.

Recovery: Either change the list of columns for the unique index, or change the rows in the table to remove duplicates. Then reissue the statement.

Where <component-name> is a component name you specified on a REGISTER COMPONENT statement.

Cause: You attempted to register a new component in the Trafodion database but this component already exists.

Effect: The operation takes no action.

Recovery: If the component name is incorrect, correct and resubmit.

Where <table-name> is the name of the histogram table that could not be created.

Cause: You attempted to execute a CREATE SCHEMA statement, but one of the histogram tables needed for the schema could not be created. Additional error messages may give insight to the cause.

Effect: The operation fails.

Recovery: None. Contact the Trafodion Developer Distribution List. Supply the name of the table that could not be created and any accompanying error messages.

Where <constraint-name> is the name of a column constraint or table constraint.

Cause: You attempted to drop a table that has a referential constraint or a check constraint that refers to another table.

Effect: Trafodion does not drop the table.

Recovery: Either drop all constraints that refer to other tables and then drop the table, or reissue the DROP TABLE statement, specifying the CASCADE option.

Where <schema-name> is the name of a Trafodion database metadata or reserved schema.

Cause: You attempted to drop a schema that is part of the Trafodion database metadata or is reserved.

Effect: The operation fails.

Recovery: None.

Cause: You attempted to initialize authorization in the Trafodion database. This succeeded, however some warnings were reported. This message is accompanied by additional warning messages which report the specifics.

Effect: The operation succeeds, however there may be issues you wish to address.

Recovery: Consult the descriptions of the accompanying warning messages.

Where <schema-name> is the name of a Trafodion database schema.

Where <details> is additional message text giving details concerning why the schema could not be dropped.

Cause: The cause is given in the <details>.

Effect: The operation fails.

Recovery: The <details> may offer insights. Possibly there is an inconsistency between HBase and the Trafodion metadata. The CLEANUP SCHEMA command may be used to recover in these cases.

Where <object-name> is the name of the Trafodion database object.

Where <error-number> is the file system error number.

Cause: An attempt to create object <object-name> resulted in file system error <error-number>.

Effect: The operation fails.

Recovery: For information about file system errors, see File-System Errors.

Cause: You attempted to drop the specified schema, however Trafodion was only able to partially drop it.

Effect: The operation fails.

Recovery: Use the CLEANUP SCHEMA <schema-name> command to drop anything remaining.

Where <column-name> is the name of a column of a table.

Cause: You attempted to create a table or view that has two columns with the same name. If you name a column "SYSKEY," duplication can result from the implicit creation by the Trafodion database software of a column named SYSKEY to ensure uniqueness for the clustering key.

Effect: The operation fails.

Recovery: Remove duplicate column names and resubmit.

Where <index-name> is the name of the index being populated.

Cause: Population of the index failed, either because another concurrent operation was being performed on the base table or because data could not be loaded into the index by the Call-level interface (CLI).

Effect: The operation fails.

Recovery: Determine the cause of the CLI failure and resubmit.

Where <constraint-name> is the name of a column or table constraint.

Cause: The constraint validation failed, either because a concurrent operation was being performed on the table or on the referenced table (for a referential integrity constraint), or data in the table violates the constraint.

Effect: The constraint operation fails.

Recovery: If a concurrent operation is in progress, wait until it has finished and try the operation again. If data in the table violates the constraint, remove that data and resubmit.

Where <constraint-name> is the name of a column or table constraint.

Cause: Data in the table violates the check constraint.

Effect: The constraint operation fails.

Recovery: Remove data that violates the constraint from the table and resubmit.

Where <column-name> is the specified column.

Cause: An invalid default value was specified in the column definition for <column-name>.

Effect: Creation of the table or addition of the column fails.

Recovery: Specify a valid default value for the column and resubmit.

Cause: The system-generated SYSKEY column was not the last column in a CREATE INDEX statement.

Effect: The operation fails.

Recovery: Change the column list to place SYSKEY at the end of the list and resubmit the statement.

Cause: You attempted to create a self-referencing constraint. A referential constraint is self-referencing if the foreign key is referencing the primary key of the same table.

Effect: The operation fails.

Recovery: Remove the self-reference and resubmit.

Where <key> is a partition key.

Where <table-name> is the name of the table being created or changed.

Cause: You attempted to create or change a table so that more than one partition has the same first key.

Effect: The operation fails.

Recovery: Change the statement so that it does not define two partitions to have the same first key, and resubmit.

Where <column-number> is the specified column.

Cause: You attempted to create a view by using a query expression in which <column-number> was unnamed.

Effect: The operation fails.

Recovery: Correct the statement to supply an AS clause for each unnamed column and resubmit.

Where <column-name> is the specified column.

Cause: You attempted to perform an ALTER TABLE ALTER COLUMN statement on a LOB column. This is not permitted.

Effect: The operation fails.

Recovery: If the column name is in error, correct and resubmit.

Where <view-col-num> is the number of columns in the view column list.

Where <query-col-num> is the number of columns resulting from the query expression used to define the view.

Cause: The number of columns in the query do not equal the number of columns specified for the view.

Effect: The operation fails.

Recovery: Specify a query statement that has a degree that matches the number of columns in the view column list, and resubmit.

Where <view-name> is the name of the view being created.

Cause: You used WITH CHECK OPTION in the definition of a view that is not updatable.

Effect: The operation fails.

Recovery: Either make the view updatable or omit the WITH CHECK OPTION and resubmit.

Cause: The column list specified in a CREATE INDEX statement consisted only of the system-generated column SYSKEY.

Effect: The operation fails.

Recovery: Change the column list to include additional columns and reissue the statement.

Where <catalog-name> is the name of a Trafodion database catalog.

Where <location-info> is the location where the tables could not be created.

Cause: This error can result from various CREATE statements issued to create the metadata. See the accompanying error messages to determine the cause.

Effect: One or more objects are not created.

Recovery: See the accompanying error messages for recovery action.

Where <file-name> is the name of the file for the label creation that failed.

Where <ANSI-name> is the name of the table.

Where <error> is the error number returned.

Cause: A file system error occurred on the attempt to create the label.

Effect: The table is not created.

Recovery: Correct the file system error and reissue the CREATE statement. For information about file system errors, see File-System Errors.

Where <table-name> is the name of the table.

Cause: The partitioning scheme requires a user-specified clustering key.

Effect: The operation fails.

Recovery: Specify a clustering key, either through a PRIMARY KEY, STORE BY, or PARTITION BY clause.

Cause: You attempted to drop the only partition of the object.

Effect: The operation fails.

Recovery: None.

Where <table-name> is the name of the object.

Cause: You attempted to create an object in the metadata schema.

Effect: The operation fails.

Recovery: Specify a different schema and resubmit.

Where <table-name> is the name of a Trafodion database metadata table.

Cause: You attempted to use the DROP TABLE statement to drop a table that is part of the Trafodion database metadata.

Effect: The table is not dropped.

Recovery: Metadata tables can be dropped only by using the DROP SQL statement or the MXTOOL GOAWAY utility. Both methods will irrevocably destroy the database.

Cause: You attempted an operation on a partitionable table that has float datatype in the partitioning key.

Effect: The operation fails.

Recovery: Enable the default ALLOW_FLOAT_DATATYPES_IN_PARTITIONING_KEY via a control query default statement and retry the operation.

Where <table-name> is the name of the table.

Cause: You attempted to do an invalid ADD, DROP, or MODIFY of a partition.

Effect: The operation fails.

Recovery: None.

Where <partition-key-value-list> is a list of the partition key values.

Where <object-name> is the name of the object.

Where <key-col-number> is the number of columns in the user-defined key.

Cause: The number of specified partition key values (<partition-key-valuelist>) for object <object-name> exceeds the number of user-defined key columns, <key-col-number>.

Effect: The operation fails.

Recovery: Fix the statement and resubmit.

Where <key> is a list of the partition key values.

Where <object-name> is the name of the object.

Cause: You attempted to access a table using a first key value that contains an element that is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You attempted an operation on a partitionable table that has float datatype in the partitioning key.

Effect: The operation completes without errors, but the results might not be correct. The float data value might not be evaluated consistently to the same value each time.

Recovery: Do not use float data types in the partitioning key of a partitionable table.

Where <table-name> is the name of the table.

Cause: You attempted to perform an operation that can be performed only on a base table, and the specified object is not a base table.

Effect: The operation fails.

Recovery: Specify a valid base table and resubmit.

Cause: You attempted to create a column that requires a default value, without specifying a default value.

Effect: The operation fails.

Recovery: Specify a valid default value for the column and resubmit.

Cause: You attempted to add a column that is both DEFAULT NULL and NOT NULL.

Effect: The operation fails.

Recovery: Determine whether the column should be DEFAULT NULL or NOT NULL and resubmit.

Cause: You attempted to perform an operation that can be performed only by the super ID.

Effect: The operation fails.

Recovery: Log on as the super ID and then resubmit.

Where <object-name> is the name of the object.

Cause: You attempted to execute a utility or alter the DDL of an object while a concurrent utility or DDL operation was being performed on the object, its parent, or its dependencies.

Effect: The operation fails.

Recovery: Wait until the concurrent operation has finished and then resubmit.

Where <column-name> is the name of the column in the clustering key.

Cause: You attempted to make a column that is not NOT NULL NOT DROPPABLE a part of the clustering key of a table.

Effect: The operation fails.

Recovery: Specify that the <column-name> is NOT NULL NOT DROPPABLE and resubmit.

Cause: You used the ALTER TABLE statement to add a column specifying a primary key that is not droppable. A primary key added through ALTER TABLE must be droppable.

Effect: The operation fails.

Recovery: Change the ALTER TABLE statement to specify DROPPABLE for the primary key.

Where <column-name> is the name of a column of <table-name>.

Where <table-name> is the name of the affected table.

Cause: You attempted to create a check constraint that references a system-generated column. The column named SYSKEY is often system-generated.

Effect: The operation fails.

Recovery: Modify the statement so that no check constraints reference any system-generated column and resubmit.

Where <actual-row-length> is the length of a row of the table.

Where <maximum-row-length> is the largest row size allowed.

Where <table-name> is the name of the table.

Cause: On a CREATE or ALTER TABLE statement, the size of the row exceeds the maximum allowed row size.

Effect: The operation fails.

Recovery: See the Trafodion SQL Reference Manual for row size limit calculations. Change the column definitions and reissue the statement.

Where <file-name> is the Trafodion platform file name of a partition of object.

Where <error-number> is a Trafodion platform file system error.

Cause: An ALTER TABLE or ALTER INDEX operation encountered a file system error.

Effect: The operation fails.

Recovery: For information about file system errors, see File-System Errors.

Cause: Internal error.

Effect: The Trafodion database is unable to perform the requested operation.

Recovery: None. Contact the Trafodion User Distribution List

Where <constraint-name> is the name of a column constraint or table constraint.

Where <referencing-table-name> is the table on which the constraint is being added.

Where <referenced-table-name> is the table specified in the FOREIGN KEY clause.

Where <statement-text> is a query.

Cause: You attempted to add a referential integrity constraint that is violated by rows already in the table.

Effect: The operation fails.

Recovery: Run the query <statement-text> to see the rows that violate the referential constraint. Either change those rows or change the referential constraint definition and resubmit.

Where <column-name> is the column in <table-name>.

Where <table-name> is the name of the table.

Where <first-key-string> is the erroneous value used in the FIRST KEY clause for <column-name>.

Cause: In a CREATE TABLE statement, a value specified as first key is not a quoted string, but the type of the column for which this value is specified is one of the character data types.

Effect: The operation fails.

Recovery: Correct the value <first-key-string> to be a type that is compatible with the type of column <column-name> and resubmit.

Where <catalog-name> is the name of a Trafodion database catalog.

Cause: Trafodion reserves certain catalog names for its own use.

Effect: The operation fails.

Recovery: See the Trafodion SQL Reference Manual for reserved names. Change <catalog-name> to a name that is not reserved and resubmit.

Where <object-name> is the name of the object being requested.

Where <object-type> is the type of object required for the DDL statement issued.

Cause: The type of the object specified in the command is inconsistent with the DDL command being used. For example, this occurs if DROP TABLE is used, and the object you specify is an INDEX.

Effect: The operation fails.

Recovery: Check that the correct object name was specified and execute a statement that is consistent with that type of object.

Where <column-name> is the SYSKEY column.

Where <table-name> is the name of the table.

Cause: You tried to create a unique or primary key constraint on the SYSKEY column.

Effect: The operation fails.

Recovery: Do not use the SYSKEY as part of the unique or primary key.

Where <column-name> is the SYSKEY column.

Where <table-name> is the name of the table.

Cause: You tried to create a referential constraint on a table column that is the SYSKEY, which is not supported.

Effect: The operation fails.

Recovery: Do not use the SYSKEY as part of the referenced key.

Where <table-name> is the name of the table.

Cause: When the Partition Overlay Support feature is enabled without setting volume names (through CQD POS_LOCATIONS) for table partitions to reside on, location names are generated automatically. However, the Trafodion database software could not generate the location names automatically and, because the CQD POS_RAISE_ERROR is set, the table is not created.

Effect: The operation fails.

Recovery: To correct the error, choose a recovery method:

Where <table-name> is the name of the table.

Cause: When the Partition Overlay Support feature is enabled without setting volume names (through CQD POS_LOCATIONS) for table partitions to reside on, location names are generated automatically. However, the Trafodion database software could not generate the location names automatically, and because the CQD POS_RAISE_ERROR is not set, the given table is created as a simple table without partitions as it would be if the Partition Overlay Support feature was not enabled.

Effect: The POS feature was not applied. A simple table without partitions was created.

Recovery: None if a non-partitioned table is requested. To request a partitioned table, delete the table, verify that disk volumes are available, and resubmit. You can also specify the volume names where the partitions need to be created for the given CREATE TABLE through CONTROL QUERY DEFAULT POS_LOCATIONS, and then retry the request.

Cause: Trafodion could not create the object because the requested table size is bigger than the total amount of disk space available on the system.

Effect: The SQL operation fails.

Recovery: Check that the table size requested is big enough to fit on the system and retry the statement.

Cause: You specified an alter or drop of synonym on an object <object-name>, which is not a synonym.

Effect: The operation fails.

Recovery: Correct the syntax so that the correct <object-name> is used.

Cause: You specified a create or alter of synonym <name> on an object that is not a table or view.

Effect: The operation fails.

Recovery: Correct the syntax so that the correct <name> is used.

Cause: You specified an alter of synonym on an object <name>, which is the same as its previous mapping.

Effect: The operation succeeds with a warning.

Recovery: None.

Cause: You specified a create of synonym <name> on an object, but a synonym of that name already exists.

Effect: The operation fails.

Recovery: Correct the syntax so that the correct <name> is used.

Cause: You specified an alter or drop of synonym <name>, but a synonym of that name already exists.

Effect: The operation fails.

Recovery: Correct the syntax so that the correct <name> is used.

Cause: You attempted to create a table that contains both a NOT DROPPABLE PRIMARY KEY constraint and a STORE BY clause. The syntax specified is not correct. The STORE BY column list must be the same as, or a prefix of, the NOT DROPPABLE PRIMARY KEY column list.

Effect: The operation fails.

Recovery: If you want the STORE BY column list that specifies the clustering key to be different than the PRIMARY KEY, specify a DROPPABLE PRIMARY KEY. If you want the PRIMARY KEY to be the same as the STORE BY key, do not specify a STORE BY clause. Correct the syntax and resubmit.

Cause: Trafodion could not create the object because system-generated column SYSKEY is not allowed as part of the PARTITION BY clause.

Effect: The DDL operation fails.

Recovery: Remove the system added column SYSKEY from the PARTITION BY clause and retry the DDL statement.

Where <schema-name> is the schema in which the object is being created.

Where <directory-name> is the designated subvolume name for that schema.

Cause: One or more LOCATION clauses in the CREATE or MODIFY statement contained a Trafodion platform location whose subvolume did not match the designated subvolume for the schema in which the object was being created.

Effect: The object was not created.

Recovery: Either correct the invalid LOCATION clauses or remove them and allow the system to generate the Trafodion platform locations.

Where <file-name> is the name of the table, index, view, or routine being dropped.

Where <error> is the returned file system error number.

Cause: The object you attempted to drop resulted in file system error <error>.

Effect: The DDL DROP operation fails.

Recovery: See previous messages in this Trafodion database software operation to determine the necessary corrective actions. Also, use the file system error <error-number> to analyze the cause. For information about file system errors, see File-System Errors. Fix the error and resubmit.

Where <error> is the error returned.

Where <file-name> is the name of the file.

Cause: File system error.

Effect: The operation fails.

Recovery: For information about file system errors, see File-System Errors.

Where <error> is the error returned.

Where <ANSI-name> is the metadata table.

Where <file-name> is the name of the file.

Cause: File system error.

Effect: The operation fails.

Recovery: For information about file system errors, see File-System Errors.

Where <column-name> is the name of a column specified in the references part of a referential integrity constraint.

Cause: You attempted to establish a referential integrity constraint on a column for which the executing user ID has no REFERENCES privileges.

Effect: The operation fails.

Recovery: Establish correct column privileges and resubmit.

Cause: A partition location is either invalid or missing.

Effect: The operation fails.

Recovery: Specify the correct location for all partitions involved in the affected command.

Where <column-name> is the name of the column that has an error.

Where <column-data-type> is the data type of <column-name>

Where <value-data-type> is the value specified as the default value for the column.

Cause: The value specified as the default for the column is incompatible with the type of the column.

Effect: The operation fails.

Recovery: Change either the column data type or the value for the default to be compatible types and resubmit.

Where <schema-name> is the name of a Trafodion database schema.

Cause: Trafodion reserves certain schema names for its own use.

Effect: The operation fails.

Recovery: See the Trafodion SQL Reference Manual for reserved schema names. Choose a name that is not reserved and reissue the CREATE statement.

Where <constraint-name> is the name of a column constraint or table constraint. Where <table-name> is the name of the table specified in the operation.

Where <dependency-information> is a list of unique constraints that cause the circular dependency.

Cause: You tried to define a referential constraint that is creating a circular dependency, where one of the columns of the table is referencing a column that belongs to the same table, either directly or indirectly.

Effect: The operation fails.

Recovery: None. You cannot define a referential constraint that creates a circular dependency.

Where <parameter-name> is the name of the parameter.

Cause: You specified a data type for this routine parameter that is not supported.

Effect: Trafodion is unable to complete the operation.

Recovery: Specify a different data type.

Cause: EXECUTE and another privilege were specified in the same GRANT or REVOKE statement, which is not allowed.

Effect: The operation fails.

Recovery: Use separate GRANT or REVOKE statements for EXECUTE and other privileges.

Cause: The GRANT or REVOKE statement did not specify a valid combination of privileges.

Effect: The operation fails.

Recovery: Specify a valid combination of privileges in the GRANT or REVOKE statement.

Where <procedure-name> is the stored procedure’s ANSI name.

Cause: The stored procedure could not be created.

Effect: The CREATE PROCEDURE statement fails.

Recovery: Fix the error conditions identified in messages preceding this message and reissue the CREATE PROCEDURE statement.

Where <table-name> is the table being dropped whose DDL was to be saved.

Where <path-name> is the pathname of the file to which the DDL was to be saved.

Cause: A file system error occurred when you attempted to save a table DDL. Possible reasons are:

Effect: The table is not dropped.

Recovery: Either correct the file system problem and drop the table or perform a SHOWDDL on the existing table, capture the output, set. SAVE_DROPPED_TABLE_DDL to "OFF," and drop the table. For information about file system errors, see File-System Errors.

Where <catalog-name> is the name of the Trafodion database catalog.

Cause: You attempted to create a schema in the system catalog.

Effect: The operation fails.

Recovery: Choose a different catalog name and reissue the CREATE statement.

for table or index <table-name>.

Cause: A CREATE or ALTER statement specified an invalid combination of EXTENT sizes and MAXEXTENTS.

Effect: The operation fails.

Recovery: Correct the error and retry the operation.

Where <object-name> is the name of the SQL object.

Cause: You specified a schema name for an object that is different from the name of the schema being created.

Effect: The operation fails.

Recovery: Specify a schema name for the object that matches the name of the schema being created.

Cause: You specified a literal with a character set other than ISO88591 in the text of a create trigger statement.

Effect: The operation fails.

Recovery: Specify only ISO88591 literals in the command.

Cause: You specified a literal with a character set other than ISO88591 in the text of a create view statement.

Effect: The operation fails.

Recovery: Specify only ISO88591 literals in the command.

Cause: You specified a literal with a character set other than ISO88591 as a partition key.

Effect: The operation fails.

Recovery: Specify only ISO88591 literals as partition keys.

Cause: You specified a literal with a character set other than ISO88591 in a HEADING clause.

Effect: The operation fails.

Recovery: Specify only ISO88591 literals in HEADING clauses.

Cause: You specified a literal with a character set other than

ISO88591 in the text of a constraint.

Effect: The operation fails.

Recovery: Specify only ISO88591 literals in constraints.

Cause: You specified a hexadecimal literal in the text of the statement, which is not allowed.

Effect: The operation fails.

Recovery: Do not specify hexadecimals in this type of command.

Where <key-value> is the specified first key value.

Where <column-name> is the column of <object-name> that corresponds to the invalid key value.

Where <object-name> is the name of the affected object.

Cause: A utility command specified an invalid key value.

Effect: The operation fails.

Recovery: Specify valid key values and resubmit.

with the data type of column <column-name> of object <object-name>.

Where <key-value> is the specified first key value.

Where <column-name> is the column of <object-name> that corresponds to the invalid key value.

Where <object-name> is the name of the affected object.

Cause: A utility command specified a key value that is inconsistent with the data type of the column that corresponds to the key value.

Effect: The operation fails.

Recovery: Specify valid key values and resubmit.

Where <partition-name> is the name specified for a partition.

Cause: Partition names are required to be unique within the set of partitions of an object.

Effect: The CREATE statement fails.

Recovery: Choose a name that is not the same as any other partition name in this object and reissue the CREATE statement.

Where <object-name> is the ANSI name of the object named in the DROP command.

Where <operation-type> is the type of utility operation.

Where <lock-name> is the ANSI name of the DDL lock object that is associated with the utility operation.

Cause: You attempted to drop an object that a utility command is using.

Effect: The operation fails.

Recovery: Wait until the utility operation has finished, and then retry the DROP operation.

Where <value> is the default value that was specified for <column-name>.

Where <column-name> is the name of the column in the table.

Cause: A CREATE TABLE or ALTER TABLE. . .ADD COLUMN specified a default value with a scale greater than the scale of the column.

Effect: The scale of the default value is set to that of the column; extra digits to the right are discarded.

Recovery: None. This is a warning message only.

Where <index-name> is the name of an existing unpopulated index.

Cause: An existing index that is not populated has been chosen for a unique or primary constraint, which is not allowed.

Effect: The operation fails.

Recovery: Populate the index and resubmit.

Cause: You attempted to specify both the unique and primary key constraints or multiple unique constraints on the same set of columns, which is not allowed.

Effect: The operation fails.

Recovery: Change your query so that both unique and primary constraints or multiple unique constraints are not specified on the same set of columns.

Where <operation> is a schema-level operation.

Where <schema> is the ANSI name of the affected schema.

Cause: You attempted a DDL or utility operation on a database object while <operation> was in progress for that object’s <schema>.

Effect: The DDL or utility operation fails.

Recovery: Wait until the operation has finished, and then retry the DDL or utility operation.

Where <text> is the disallowed name that was specified.

Cause: You specified a Trafodion database reserved object name.

Effect: The object is not created.

Recovery: See the Trafodion SQL Reference Manual for the list of reserved object names. Choose a name that is not reserved and reissue the CREATE statement.

Cause: You specified duplicate privileges in a GRANT or REVOKE statement.

Effect: The operation fails.

Recovery: Reissue the GRANT or REVOKE statement, specifying a single privilege or a list of distinct privileges.

Cause: You specified duplicate grantees in a GRANT or REVOKE statement.

Effect: The operation fails.

Recovery: Reissue the GRANT or REVOKE statement specifying a single grantee or a list of distinct grantees.

Cause: You specified an unsupported privilege on a procedure or routine in a GRANT statement.

Effect: The operation fails.

Recovery: Reissue the GRANT statement specifying the valid privilege for the procedure or routine.

Cause: You specified a privilege that is not supported for the object type in a GRANT statement.

Effect: The operation fails.

Recovery: Reissue the GRANT statement specifying the valid privilege for the object type.

Cause: You specified duplicate column names with the update or references privilege in a GRANT or REVOKE statement.

Effect: The operation fails.

Recovery: Correct the GRANT or REVOKE statement by specifying a single column name or a list of distinct column names.

Where <sql-object-name> is the ANSI name of the affected SQL database object.

Where <file-system-error-number> is a Trafodion platform file system error code.

Cause: A CREATE or ALTER operation encountered a file system error <error-number> during processing of the ALLOCATE or DEALLOCATE attribute.

Effect: The operation fails.

Recovery: For information about file system errors, see <file-system-errors,File-System Errors>.

Where <object-name> is the ANSI name of the affected database object.

Where <number> is the specified number of extents.

Cause: A CREATE or ALTER operation specified an ALLOCATE attribute value that was greater than the MAXEXTENTS value for the affected database object, which is not allowed.

Effect: The operation fails.

Recovery: If possible, alter the MAXEXTENTS attribute value to be greater than the

desired number of extents to be allocated. The current maximum value for MAXEXTENTS is 768.

Cause: The value that you specified to change MAXEXTENTS is less than or equal to the allocated extents.

Effect: The operation fails.

Recovery: Use a MAXEXTENTS value greater than the allocated extents.

Cause: You specified an insufficient MAXEXTENTS value while creating an index.

Effect: The SQL operation completed with a warning.

Recovery: This is a warning only.

Where <constraint-1> is the constraint you are trying to drop.

Where <constraint-2> is the UNIQUE constraint.

Cause: You attempted to drop a constraint that is needed by a UNIQUE constraint, which is not allowed because it would leave a UNIQUE constraint on a column, but without a NOT NULL constraint for that column.

Effect: The operation fails.

Recovery: To drop the constraint, you must remove the UNIQUE constraint or add an additional NOT NULL constraint to the columns that contain UNIQUE constraints and only one NOT NULL constraint for that column.

<object-name> is the name of the SQL object (table or index).

Cause: The Trafodion database does not recognize the partitioning scheme stored in the metadata for the named object.

Effect: The named object is considered corrupt and is inaccessible.

Recovery: None. Contact the Trafodion User Distribution List Consider running the VERIFY operation on the named object to check for inconsistencies in the metadata with respect to the partitioning scheme.

<operation> is a schema level operation, currently UPGRADE or DOWNGRADE, that uses the ALL SCHEMAS IN CATALOG flavor. <catalog> is a catalog name that is affected by <operation>.

Cause: An attempt was made to execute a DDL or utility operation that affected <catalog>, or a schema in that catalog.

Effect: The operation fails.

Recovery: Wait until <operation> is finished, then retry the failed DDL or utility operation.

Where <referential-triggered-action> can either be ON DELETE or ON UPDATE.

Cause: NO ACTION referential action is specified in the referential integrity definition, and the CONTROL QUERY DEFAULT value for REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT is 'OFF.'

Effect: The NO ACTION referential action cannot be defined.

Recovery: To alter the behavior of NO ACTION referential action, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.

Where <referential-triggered-action> can either be ON DELETE or ON UPDATE.

Cause: NO ACTION referential action is specified in the referential definition and the CONTROL QUERY DEFAULT value for REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT is 'SYSTEM.'

Effect: The NO ACTION referential action has RESTRICT referential action semantics. It is recorded as NO ACTION in the metadata table.

Recovery: To alter the behavior of the NO ACTION referential action, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.

Where <directory> is the Trafodion platform subvolume name specified in the LOCATION clause of the CREATE SCHEMA command.

Where <schema> is the ANSI name of an existing schema that already uses <directory> as a schema subvolume.

Cause: In a CREATE SCHEMA command, you specified <directory> in the LOCATION clause; however, this subvolume is already being used as schema subvolume by <schema>.

Effect: The statement fails unless it includes the optional REUSE clause to allow reuse of the same schema subvolume name. If the REUSE clause is used, this is a warning message and the schema is created successfully. The warning can be issued repeatedly for a single CREATE SCHEMA command if multiple schemas already exist with <directory> as the schema subvolume.

Recovery: Only schemas that are RDF replicated to another node should have the same subvolume names as their corresponding schemas on the other node. To create these, use the optional REUSE clause in the CREATE SCHEMA statement. All other schemas should have unique subvolume names. Schemas that are, or will be, related as RDF primary and backup schemas must have identical schema names and subvolumes on the primary and backup nodes.

Where <directory> is the Trafodion platform subvolume name specified in the LOCATION clause of the CREATE SCHEMA command.

Cause: In a CREATE SCHEMA command, you specified subvolume in the LOCATION clause, however subvolume names with the format ZSD<digit><anything> are reserved for Trafodion database software metadata schemas.

Effect: The operation fails.

Recovery: Specify a subvolume name using the format ZSD<letter><anything> in the LOCATION clause, and resubmit.

Where <object-name> is the name of the object.

Cause: You specified an object for an SQL operation that does not support its object type.

Effect: The operation fails.

Recovery: Specify an object of valid object type and retry the operation.

Cause: You specified creation of triggers in the CREATE SCHEMA statement.

Effect: The operation fails.

Recovery: Remove the creation of triggers from the CREATE SCHEMA statement and resubmit. Create triggers in separate statements.

Cause: You attempted to drop a column that is a part of a primary key.

Effect: The operation fails.

Recovery: Correct the column name or table name as appropriate and resubmit.

Cause: You attempted to drop a column, but that column is used by the secondary index named.

Effect: The operation fails.

Recovery: If the secondary index is no longer needed, drop it and resubmit. If the column name or table name are incorrect, correct them and resubmit.

Cause: You attempted to use a name containing an invalid character for a Trafodion object that is stored in HBase.

Effect: The operation fails.

Recovery: Correct the name and resubmit.

Cause: During an INITIALIZE TRAFODION, UPGRADE operation, a write to metadata table <table-name> failed. There may be additional messages giving details of the failure.

Effect: The upgrade operation fails.

Recovery: None. Contact the Trafodion User Distribution List. Include any additional messages.

Cause: You attempted to drop the only remaining user-defined column in the table.

Effect: The operation fails.

Recovery: If the table is no longer needed, simply drop the table.

Cause: You attempted an operation on table <table-name> but the operation could not be performed. <reason> gives more details.

Effect: The operation fails.

Recovery: Correct any issues indicated by <reason> as appropriate and resubmit.

Cause: When accessing an external HBase table (for example, using ROW format), you specified an invalid HBase column name.

Effect: The operation fails.

Recovery: Correct the column name and resubmit.

Cause: You attempted to perform ALTER TABLE RENAME but the rename could not be performed. <reason> gives more detail.

Effect: The operation fails.

Recovery: Perform the operations suggested by <reason> and resubmit.

Cause: This is a Trafodion internal error. It is highly unlikely that you will encounter this error unless you are making code changes to Trafodion yourself.

Effect: The operation fails.

Recovery: None. Contact the Trafodion Developer Distribution List.

Cause: You attempted an INSERT/SELECT into an external ROW format HBase table, or you attempted an INSERT using the VALUES clause but did not use a COLUMN_CREATE function.

Effect: The operation fails.

Recovery: Correct the statement and resubmit.

Cause: Trafodion received an internal error from the Trafodion compiler.

Effect: The operation fails.

Recovery: None. Report the entire message to user@trafodion.incubator.apache.org.

Cause: An outstanding transaction must be resolved before the Trafodion compiler can be restarted.

Effect: The operation fails.

Recovery: None.

Where error <number> is the error number.

Where <name> is the name of the program file.

Cause: Trafodion was unable to create a server process because of the process control procedure error <number> it received while resolving the program file name.

Effect: The operation fails.

Recovery: Use the process control procedure error to diagnose and correct the problem.

Where <name> is the name of the server process.

Where <number-1> is the error number.

Where <number-2> is the TPCError.

Where <text> is the error message text.

Cause: Trafodion was unable to create server process <name> because of the process control procedure error <number> it received. More information appears in detail <text>.

Effect: The operation fails.

Recovery: Use the process control procedure error to diagnose and correct the problem.

Where <name> is the name of the server process.

Where <number> is the error number.

Cause: Trafodion was unable to create server process <name> because of the process control procedure error <number> it received on the program file.

Effect: The operation fails.

Recovery: Use the process control procedure error to diagnose and correct the problem.

Where <name> is the server process name.

Where <number> is the error number.

Cause: Trafodion was unable to create server process <name> because of the process control procedure error <number> it received on the swap file.

Effect: Trafodion does not create the server process.

Recovery: Use the process control procedure error to diagnose and correct the problem.

Where <name> is the server process name.

Cause: Trafodion was unable to create server process <name> because it is an unlicensed privileged program. The server process was configured incorrectly at installation.

Effect: The operation fails.

Recovery: The server process must be a licensed privileged program. Check your configuration.

Where <number> is the current maximal value.

Cause: The new minimal value is greater than the current maximal value.

Effect: The new minimal value is not set.

Recovery: Specify a new minimal value that is less than the current maximal value or specify a new maximal value that is greater than the new minimal value.

Where <number> is the current minimal value.

Cause: The new maximal value is smaller than the current minimal value.

Effect: The new maximal value is not set.

Recovery: Specify a new maximal value that is greater than the current minimal value.

Where <process-id> identifies the process.

Where <number> is the error number.

Where <name> is the name of the server process.

Cause: The Trafodion database <process-id> received process control procedure error <number> while communicating with the server process <name>.

Effect: Trafodion is not able to communicate with the process.

Recovery: Use the process control procedure error to diagnose and correct the problem.

Where <process-id> identifies the process.

Where <number> is the error number.

Where <name> is the name of the server process.

Cause: The Trafodion database <process-id> received process control procedure error <number> while communicating with server process <name>.

Effect: Trafodion process is not able to communicate with the server process.

Recovery: Use the process control procedure error to diagnose and correct the problem.

Where <process-id> identifies the process.

Where <name> is the name of the server process.

Where <number> is the error number.

Cause: The Trafodion database <process-id> was unable to open server process <name> because of the operating system error <number> it received.

Effect: The operation fails.

Recovery: Use the operating system error to diagnose and correct the problem.

Where <name> is the name of the character set.

Cause: You specified a non-ISO88591 character set name.

Effect: The operation fails.

Recovery: Specify an ISO88591 character set name.

Where <attribute> is the attribute name you specified.

Cause: If the SQLSTATE is 42000, this is an error. You attempted to set a CONTROL QUERY DEFAULT setting, but the <attribute> name you specified is not valid. If the SQLSTATE is 01000, this is a warning. In an earlier Trafodion database session, you inserted a row into a DEFAULTS table whose <attribute> column value is invalid.

Effect: If this is an error, the operation fails. If this is a warning, this is an informational message.

Recovery: Correct the attribute name and resubmit.

Cause: You specified an invalid <control-option name> or a valid option with an invalid <value>.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: This is an informational message that is a result of the two-pass mechanism of the optimizer. The optimizer created a simple plan, and then while refining that plan, an internal error occurred, so the simple plan was not improved. The simple plan is still valid and will work.

Effect: Your query will use the original, simple plan.

Recovery: Informational message only; no corrective action is needed. This message will be accompanied by an assertion failure message and, possibly, CONTROL QUERY SHAPE information. However, report the entire message, and the preceding assertion failure message, to user@trafodion.incubator.apache.org.

This additional information will also be helpful: the DDL for the tables involved, the query that produced this warning, and any CONTROL QUERY SHAPE and CONTROL QUERY DEFAULT settings in effect when the error occurred.

Cause: You attempted to set the CQD HIST_NO_STATS_ROWCOUNT value as less than the current value of CQD HIST_NO_STATS_UEC.

Effect: The current value of the HIST_NO_STATS_ROWCOUNT is retained.

Recovery: Set the value of CQD HIST_NO_STATS_ROWCOUNT greater than or equal to the value of HIST_NO_STATS_UEC. If you want to use a smaller value, reduce the value of CQD HIST_NO_STATS_UEC first. Note that any change in either of the two values can have an effect on the plan quality.

Cause: You specified an invalid value for the DEFAULTS attribute listed in the message.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a value outside of the allowed range <value>.

Effect: The operation fails.

Recovery: Enter a valid value and resubmit.

Cause: You specified an invalid value for an attribute. It must be a multiple of <value>.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Where <name> is the DEFAULTS attribute name.

Where <data-type> is the attribute name value.

Cause: You specified a DEFAULTS attribute name value of <data-type>, which is not supported. The item is being converted to <data-type>, which is supported.

Effect: Because of the conversion, the actual value used might be truncated or rounded.

Recovery: Specify the value using the expected type, if appropriate.

Where <name> is the name of the table.

Cause: You received an error on the DEFAULTS table <name>. A previous error message has appeared with specific information.

Effect: The operation fails.

Recovery: None.

Where <name> is the procedure name.

Cause: You defined procedure <name> twice in this module.

Effect: Trafodion uses the first definition.

Recovery: This is an informational message only; no corrective action is needed.

Where <name> is the cursor name.

Cause: You defined the static cursor <name> twice in this module.

Effect: Trafodion uses the first static cursor definition.

Recovery: This is an informational message only; no corrective action is needed.

Where <name> is the cursor name.

Cause: You defined the static cursor <name> twice in this module.

Effect: Trafodion uses the first dynamic cursor definition.

Recovery: This is an informational message only; no corrective action is needed.

Where <name> is the cursor name.

Cause: You defined the dynamic cursor <name> twice in this module.

Effect: Trafodion uses the first static cursor definition.

Recovery: This is an informational message only; no corrective action is needed.

Where <name> is the cursor name.

Cause: You defined the dynamic cursor <name> twice in this module.

Effect: Trafodion uses the first dynamic cursor definition.

Recovery: This is an informational message only; no corrective action is needed.

Where <name> is the statement name.

Where <name> is the module name.

Cause: Trafodion could not find statement <name> in module <name>.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Where <name> is the cursor name.

Where <name> is the module name.

Cause: Trafodion could not find cursor <name> in module <name>.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Where <name> is the descriptor name.

Cause: You defined the descriptor <name> twice in this module.

Effect: Trafodion uses the first definition.

Recovery: Informational message only; no corrective action is needed.

Cause: You specified a procedure whose body is invalid. It must be a SELECT, INSERT, UPDATE, DELETE, DECLARE CATALOG, DECLARE SCHEMA, or static DECLARE CURSOR.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a static cursor declaration that is outside the body of a procedure. It should appear only in the body of a procedure.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: In a module definition file, you specified a query statement such as SELECT, INSERT, UPDATE, DELETE, or a DDL statement. These statements must be embedded in procedures.

Effect: Trafodion is unable to compile the module.

Recovery: Correct the syntax and resubmit.

Where <name> is the name of the module.

Where <definition-type> is the previous definition

Cause: You defined <name> twice in this module in which it was defined as a type definition type.

Effect: Trafodion uses the previous definition.

Recovery: Specify a new name for the item and resubmit, if necessary.

Cause: You specified a simple value as a literal, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Where <name> is the name of the module.

Cause: You attempted to compile a system module that can be compiled only by the super ID.

Effect: The operation fails and is unable to compile the entire module correctly.

Recovery: None. Use a different name for your module and recompile.

Where <name> is the name of the module.

Cause: You attempted to use a name that is reserved for future system modules.

Effect: The operation fails and is unable to compile the entire module correctly.

Recovery: None. Use a different name for your module and recompile.

compilation

Cause: You specified mxcmp -a <application-name> system-moduledefinition-file, which is not supported.

Effect: The operation fails.

Recovery: Delete the -a <application-name> and retry the mxcmp systemmodule-definition-file command.

Cause: You attempted to set the CQD HIST_NO_STATS_UEC value as greater than the current value of CQD HIST_NO_STATS_ROWCOUNT.

Effect: The current value of the HIST_NO_STATS_UEC is retained.

Recovery: Set the value of CQD HIST_NO_STATS_UEC less than or equal to the value of HIST_NO_STATS_ROWCOUNT. If you want to use a larger value, increase the value of CQD HIST_NO_STATS_ROWCOUNT first. Note that any change in either of the two values can have an effect on the plan quality.

Cause: Trafodion received error <number> while reading module <name>. <value> shows the number of bytes read from <text>. The module file is unusable. Either it has been corrupted or overwritten.

Effect: The operation fails.

Recovery: Recompile the module definition file, using the Trafodion compiler, to create a valid module file.

Where <number> is the error number.

Where <name> is the name of the file.

Cause: Trafodion received error <number> while opening file <name> for read.

Effect: Trafodion does not open the file.

Recovery: Use the error number to diagnose and correct the problem.

Where <number> is the error number.

Where <name> is the name of the file.

Cause: Trafodion received error <number> while opening file <name> for write.

Effect: Trafodion does not open the file.

Recovery: Use the error number to diagnose and correct the problem.

Where <number> is the error number.

Where <name> is the name of the file.

Cause: Trafodion received error <number> while naming or locating file <name>.

Effect: Trafodion does not name or locate the file.

Recovery: Use the error to diagnose and correct the problem.

Cause: Trafodion database software received error <number> while writing to file <name>. <value> shows the number of bytes being written.

Effect: Trafodion does not open the file.

Recovery: Use the error to diagnose and correct the problem.

Where <number> is the error number.

Where <name> is the name of the file.

Cause: Trafodion received error <number> when closing file <name>.

Effect: Trafodion does not close the file.

Recovery: Use the error number to diagnose and correct the problem.

Where <name> is the name of the file.

Cause: A compilation failed, and for some reason Trafodion database software was not able to purge the module file.

Effect: The module file is not valid and should not be used.

Recovery: Purge the file from the Trafodion platform.

Where <name-1>, <name-2>, and <name-3> are module file names.

Cause: Trafodion ignored the command line argument for module <name-1>. Instead, it used the second module <name-2> in file <name-3>.

Effect: None.

Recovery: None.

Where <name> is the name of the file.

Cause: Trafodion could not find the required module statement in file <name>.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Where <name> is the name of the file.

Cause: You included more than one module statement. <name> will be used.

Effect: Trafodion ignores the second module statement.

Recovery: Informational message only; no corrective action is needed.

Where <name> is the name of the file.

Cause: Trafodion did not find a module timestamp statement in the module definition file <name>.

Effect: Trafodion uses a default timestamp value of all zeros.

Recovery: Supply a timestamp and resubmit.

Cause: You specified a timestamp statement twice in this module.

Effect: Trafodion uses the first timestamp.

Recovery: Informational message only; no corrective action is needed.

Where <name-1>, <name-2>, and <name-3> are module file names.

Cause: Trafodion expected to find the first module <name-1>, but instead found the second module <name-2>, in file <name-3>.

Effect: Only the second module is compiled.

Recovery: None.

Cause: The Trafodion compiler was invoked on a module definition file that contains more than one SOURCE_FILE statement. A module definition can have only one SOURCE_FILE statement that specifies that module’s SQL source file.

Effect: The operation fails.

Recovery: Edit the module definition file so that it contains no more than one SOURCE_FILE statement, and rerun the Trafodion compiler on the module definition.

Cause: The Trafodion compiler was invoked on a module definition file that contains a SOURCE_FILE statement whose source path name has over 1024 characters.

Effect: The operation fails.

Recovery: Edit the module definition file so that its SOURCE_FILE statement’s source path name is no more than 1024 characters long. Rerun the Trafodion compiler on the module definition file.

Cause: <compilation-type> completed with the number of warnings given as <value>.

Effect: None.

Recovery: Informational message only; no corrective action is needed.

Cause: <compilation-type> failed with the number of errors and warnings given as <value>.

Effect: Any statement with an error is not compiled.

Recovery: If this is a warning, this is an informational message. Otherwise, correct the syntax and resubmit.

Cause: Trafodion received a break and aborted the compilation.

Effect: Trafodion does not continue compilation.

Recovery: Informational message only; no corrective action is needed.

Cause: Trafodion was unable to compile this query using the MINIMUM optimization level.

Effect: Trafodion is unable to process this query.

Recovery: Resubmit the query with MEDIUM optimization level. Precede the statement with: CONTROL QUERY DEFAULT OPTIMIZATION-LEVEL 'MEDIUM';

Cause: Trafodion was unable to compile this query, either because it was not able to use the MINIMUM optimization level or because you used an incompatible CONTROL QUERY SHAPE specification.

Effect: Trafodion is unable to process this query.

Recovery: If applicable, resubmit the query with MINIMUM optimization level. Precede the statement with:

CONTROL QUERY DEFAULT OPTIMIZATION-LEVEL 'MEDIUM'; Correct the CONTROL QUERY SHAPE specification and resubmit.

Cause: Trafodion was unable to compile this query, either because it was not able to use the MEDIUM optimization level or because you used an incompatible CONTROL QUERY SHAPE specification.

Effect: Trafodion is unable to process this query.

Recovery: If applicable, use the MAXIMUM optimization level, correct the CONTROL QUERY SHAPE specification, and resubmit.

Cause: Trafodion was unable to compile this query because you used an incompatible CONTROL QUERY SHAPE specification.

Effect: Trafodion is unable to process this query.

Recovery: Correct the CONTROL QUERY SHAPE specification and resubmit.

Cause: Trafodion was unable to compile this query because it is too long.

Effect: Trafodion is unable to process this query.

Recovery: Try breaking the statement into smaller pieces.

Cause: Trafodion was unable to compile the query.

Effect: The operation fails.

Recovery: Use the warning messages returned by the compiler to diagnose and correct the problem.

Cause: Trafodion attempted to compile this query with query caching on but failed. It then successfully compiled this query with caching turned off.

Effect: Trafodion compiled the query as if query plan caching was turned off even though caching is currently on. The prepared query can be executed as usual.

Recovery: This is an informational message. To prevent this warning, turn off query caching before query preparation.

Where <attribute> is the DEFAULTS attribute.

Cause: You attempted to change the DEFAULTS <attribute>, which is read-only.

Effect: The operation fails.

Recovery: None.

Cause: You invoked mxCompileUserModule on an application file that has an embedded module definition. An SQL compilation of an embedded module definition resulted in a Trafodion compiler nonzero exit code, indicating a warning or error.

Effect: The operation fails.

Recovery: Review the Trafodion compiler warning or error message. Trace the diagnostic back to the module source file and correct the offending source statement. Retry preprocessing, translating, compiling, and SQL compiling the application file.

Cause: You invoked mxCompileUserModule on an application file that is not a Trafodion platform ELF object file.

Effect: The operation fails.

Recovery: Verify that the name <application-file> is an ELF object file. Verify that the name of <application-file> is spelled correctly, and retry the command.

Cause: You invoked mxCompileUserModule (or mxcmp -a <application-pathname> mdf) on an application that does not exist or is inaccessible to the user.

Effect: The operation fails.

Recovery: Verify that <application-pathname> exists and is readable by the user. Verify that <application-pathname> is spelled correctly, and retry the command.

Where <module-name> is the name of the module.

Cause: You invoked mxCompileUserModule on an application file that has embedded module definition(s). The SQL compilation of the named embedded module definition produced a Trafodion compiler warning or error.

Effect: The operation fails.

Recovery: Review the Trafodion compiler warning or error. Trace the diagnostic back to the source file of the named module. Correct offending source statements. Retry preprocessing, translating, compiling, and SQL compiling the application file.

Cause: You invoked mxCompileUserModule on an application file that has many embedded module definitions. The tool cannot create another temporary file name to hold the contents of an embedded module definition. The tool used tmpnam() to create a string that is not the name of an existing file which tmpnam() could not do.

Effect: The operation fails.

Recovery: Clean up TMPDIR (the directory where temporary files are created) by deleting unused temporary files. Retry the command.

Where <temp-filename> is the name of the temporary file.

Cause: You invoked mxCompileUserModule on an application file that has many embedded module definitions.The tool cannot create another temporary file to hold the contents of an embedded module definition.

Effect: The operation fails.

Recovery: Verify that you have write access to TMPDIR (the directory where temporary files are created) and that TMPDIR has free space. Delete unused temporary files from TMPDIR and retry the command.

Where -<option> is the command-line option.

Cause: You invoked mxCompileUserModule with an unrecognized command-line option.

Effect: The operation fails.

Recovery: Review the allowable command-line options by invoking

mxCompileUserModule. Verify that the desired command-line options are spelled correctly and retry the command.

Cause: You invoked mxCompileUserModule without supplying an application file.

Effect: The operation fails.

Recovery: Invoke mxCompileUserModule on an application file, such as a Trafodion platform ELF object file.

Cause: You invoked mxCompileUserModule using a command-line option allowing a delimited identifier, but the delimited identifier has an invalid character, such as the @ sign.

Effect: The operation fails.

Recovery: Remove invalid characters, such as the @ sign, from the delimited identifier and retry the command.

Cause: You invoked mxCompileUserModule using a command-line option allowing a delimited identifier, but the delimited identifier has no closing quote.

Effect: The operation fails.

Recovery: Make sure that the delimited identifier has a closing quote and retry the command.

Cause: You invoked mxCompileUserModule on an application file, possibly intending to SQL compile only a subset of its embedded module definitions, but you specified an unknown character in the module name list.

Effect: The operation fails.

Recovery: Review the module name list syntax. Verify that the module names are specified correctly and retry the command.

Cause: You invoked mxCompileUserModule on an application file, intending to SQL compile only a subset of its embedded module definitions, but you specified an unexpected string in the module name list.

Effect: The operation fails.

Recovery: Review the module name list syntax, especially where string1 is expected. Verify that the list of module names are specified correctly and retry the command.

Cause: You invoked mxCompileUserModule on an application file, possibly intending to SQL compile only a subset of its embedded module definitions, but you specified an unexpected string in the module name list.

Effect: The operation fails.

Recovery: Review the module name list syntax, especially where an identifier is expected. Verify that the list of module names are specified correctly and retry the command.

Cause: You invoked mxCompileUserModule on an application file to SQL compile its embedded module definitions. An internal error occurred during the operation.

Effect: The operation fails.

Recovery: None. Contact the Trafodion User Distribution List

Cause: You invoked mxCompileUserModule on an application file, possibly intending to SQL compile only a subset of its embedded module definitions, but you specified an invalid regular identifier in the module name list.

Effect: The operation fails.

Recovery: Review the module name list syntax, especially where an identifier is expected. Verify that the list of module names is specified correctly. Verify that regular identifiers used are not SQL reserved words and retry the command.

Where <mxcmp-path> is the Trafodion compiler environment variable.

Cause: You set your Trafodion compiler environment variable to point to your own Trafodion compiler and invoked mxCompileUserModule on an application file to SQL compile its module definitions. Your Trafodion compiler is not executable.

Effect: The operation fails.

Recovery: Verify that your Trafodion compiler exists and is executable and retry the command.

Where <error-code> is the error message code.

Cause: You invoked mxCompileUserModule on an application file to SQL compile its module definitions. This command invoked the Trafodion compiler, which returned error code, indicating an abnormal termination.

Effect: The operation fails.

Recovery: If the system is heavily loaded, retry the command later. If the problem persists under normal system load, report it as an internal error and contact user@trafodion.incubator.apache.org.

Where <module-name> is the requested module name.

Where <application-filename> is the requested application file.

Cause: You invoked mxCompileUserModule on an application file with a list of module names to SQL compile. This list includes the named module, which cannot be found in the application file.

Effect: The operation fails.

Recovery: Verify the spelling of the module name and retry the command.

Where <filename> is the name of the application file.

Cause: You invoked mxCompileUserModule on the named application file, which does not exist or is not readable.

Effect: The operation fails.

Recovery: Verify the spelling of the application file name and retry the command.

Where <nodename> is the name of the node such as node01.host.com on which the failure occurred.

Where <error-num> is the file system error number.

Cause: The <nodename> you specified is not available.

Effect: The compiler tried to produce a plan without using that node. This might result in a suboptimal plan.

Recovery: For information about file system errors, see File-System Errors.

Where <number> is the line number.

Cause: An error occurred in file name at line <number>.

Effect: Compilation failed because of a syntax error.

Recovery: This is a general error that is issued before a more specific error. Use the error that follows this one to diagnose and correct the problem.

Cause: There is a syntax error near the text <SQL-text>.

Effect: The operation fails.

Recovery: See the errors that accompany this message for more information. Correct the syntax and resubmit.

Cause: You specified an invalid column reference, which must have four or fewer parts.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You defined length or precision as zero. You must enter a value greater than zero.

Effect: The operation fails.

Recovery: Enter a value greater than zero and resubmit.

Cause: You defined a delimited identifier as blanks. You must enter at least one non-blank character.

Effect: The operation fails.

Recovery: Enter at least one non-blank character and resubmit.

Cause: You attempted to use a DECLARE CURSOR statement without declaring a cursor name or using the name of a previously prepared statement.

Effect: The operation fails.

Recovery: Declare a cursor name, or use the name of a previously prepared statement, and resubmit.

Cause: You attempted to declare a dynamic cursor in a way that does not match the statement. Both must be literals or both must be string host variable expressions.

Effect: The operation fails.

Recovery: Declare the cursor in a way that matches the statement and resubmit.

Cause: You specified an ALLOCATE CURSOR statement with invalid syntax. Both the cursor and the statement must be named using string host variables.

Effect: The operation fails.

Recovery: Name the cursor and statement with string host variables and resubmit.

Cause: You specified a CREATE TABLE statement with a precision value greater than nine for the PRECISION field, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You attempted to perform a DROP ASSERTION statement, which is not supported.

Effect: The operation fails.

Recovery: None.

Where <name> is the name of the character set.

Cause: You specified character set <name> that is not supported for use in a Trafodion object, such as a table or module. Examples include creating a KANJI or KSC5601 column in a Trafodion table.

Effect: The operation fails.

Recovery: Specify a valid character set and resubmit.

Where <name> is the name specified in the operation.

Cause: You specified an invalid name <name>, which must have three or fewer parts. <catalog.schema.table> is valid. <catalog.schema.table.name> is invalid.

Effect: The operation fails.

Recovery: Correct the name and resubmit.

Cause: You submitted an AVG or other aggregate function that does not allow (*) as an operand. Only COUNT allows you to use (\*).

Effect: The operation fails.

Recovery: Remove the (*) operand and resubmit.

Cause: You specified an expression with invalid syntax. Only subtraction is supported in the parenthesized expression that precedes an interval qualifier.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You defined a numeric item, <value>, with precision greater than 18, which is not supported.

Effect: The operation fails.

Recovery: Redefine the item with a precision value of 18 or less.

Cause: You defined a scale value with greater precision than Trafodion allows.

Effect: The operation fails.

Recovery: Redefine the scale with a precision value less than or equal to the allowable value.

Cause: You gave a decimal item, <value>, with precision greater than 18, which is not supported.

Effect: The operation fails.

Recovery: Redefine the item with a precision value of 18 or less.

Cause: You specified an unexpected value, <value>. Trafodion requires an unsigned integer.

Effect: The operation fails.

Recovery: Replace the value with an unsigned integer and resubmit.

Cause: You specified an unexpected value, <value>. Trafodion requires an unsigned smallint.

Effect: The operation fails.

Recovery: Replace the value with an unsigned smallint and resubmit.

Cause: You specified an unexpected value, <value>. Trafodion requires an unsigned number.

Effect: The operation fails.

Recovery: Replace the value with an unsigned number and resubmit.

Cause: You specified an unexpected value, <value>. Trafodion requires an unsigned number.

Effect: The operation fails.

Recovery: Replace the value with an unsigned number and resubmit.

Cause: You specified an unexpected value, <value>. Trafodion requires an unsigned number.

Effect: The operation fails.

Recovery: Replace the value with an unsigned number and resubmit.

Cause: You attempted to use an operator that is not supported.

Effect: The operation fails.

Recovery: None.

Cause: You attempted to perform a COLLATE clause in a sort specification, which is not supported.

Effect: Trafodion ignores the COLLATE clause.

Recovery: Remove the COLLATE clause and resubmit.

Cause: You attempted to use a MATCH PARTIAL clause, which is not supported.

Effect: The operation fails.

Recovery: Remove the MATCH PARTIAL clause and resubmit.

Cause: You used an invalid location <name> for a subvolume that must be eight characters long and begin with the letters <ZSD>.

Effect: The operation fails.

Recovery: Correct the name and resubmit.

Cause: You made a syntax error in a list of file attributes, which must be separated by commas.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified an invalid name <name>, which must have only one name part.

Effect: Trafodion could not prepare the statement.

Recovery: Correct the name and resubmit.

Cause: You attempted to specify a privilege column list in an INSERT clause, which is not supported.

Effect: The operation fails.

Recovery: Remove the privilege column list and resubmit.

Cause: You attempted to specify an <option> that is not supported in a referential integrity constraint definition.

Effect: The operation fails.

Recovery: Remove the option and resubmit.

Cause: You used the PARALLEL EXECUTION clause, which is not supported.

Effect: The operation fails.

Recovery: Remove the PARALLEL EXECUTION clause and resubmit.

Cause: You attempted to drop an object with the CASCADE option, which is not supported.

Effect: The operation fails.

Recovery: Drop the item without CASCADE.

Cause: You used the COLUMN clause in the ALTER TABLE statement, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You used the MOVE clause in the ALTER TABLE statement, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You used the PARTITION clause in the ALTER TABLE statement, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You used the RENAME clause in the ALTER TABLE statement, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You used the SET CONSTRAINT clause in the ALTER TABLE statement, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a CREATE TABLE statement with a precision value greater than 18 for <data-type>, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a PIC X type with a sign, which is not supported.

Effect: The operation fails.

Recovery: Remove the sign, or redefine the type, and resubmit.

Cause: You specified a PIC X type with COMP, which is not supported.

Effect: The operation fails.

Recovery: Remove the COMP, or redefine the type, and resubmit.

Cause: You specified an item with precision zero. You must add the number nine to the PICTURE clause.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified UNSIGNED for a numeric or decimal type that has a scale greater than nine, which is not supported.

Effect: The operation fails.

Recovery: Change the specification to SIGNED and resubmit.

Cause: You specified UPSHIFT for a numeric type, which is not supported.

Effect: The operation fails.

Recovery: Change the specification and resubmit.

Cause: You specified a precision value greater than 18 for a COMP numeric type, which is not supported.

Effect: The operation fails.

Recovery: Change the precision to a value of 18 or less and resubmit.

Cause: You specified an invalid interval <value>.

Effect: The operation fails.

Recovery: Correct the interval value to a valid one and resubmit.

Cause: You specified an invalid date <value>.

Effect: The operation fails.

Recovery: Change the date value and resubmit.

Cause: You specified an invalid time <value>.

Effect: The operation fails.

Recovery: Correct the time value and resubmit.

Cause: You specified an invalid timestamp <value>.

Effect: The operation fails.

Recovery: Correct the timestamp value to a valid one and resubmit.

Cause: You attempted to use parameters in a static compilation, which is not supported.

Effect: The operation fails.

Recovery: Remove the parameters and resubmit.

Cause: You attempted to use host variables in dynamic compilation, which is not supported.

Effect: The operation fails.

Recovery: Remove the host variables and resubmit.

Cause: You specified a constraint whose catalog and schema do not match the specified table.

Effect: The operation fails.

Recovery: Correct the syntax so that the constraint and table have the same catalog and schema.

Cause: You defined column <name> with more than one HEADING clause.

Effect: The operation fails.

Recovery: Define the column with only one HEADING clause and resubmit.

Cause: You defined column <name> with more than one NOT NULL clause.

Effect: The operation fails.

Recovery: Define the column with only one NOT NULL clause and resubmit.

Cause: You defined column <name> with more than one PRIMARY KEY clause.

Effect: The operation fails.

Recovery: Define the column with only one PRIMARY KEY clause and resubmit.

Cause: You specified a constraint with an invalid NOT DROPPABLE clause, which can appear only in PRIMARY KEY and NOT NULL constraint definitions.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You defined duplicate DELETE rules.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You defined duplicate UPDATE rules.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You provided an invalid size value in the ALLOCATE clause.

Effect: The operation fails.

Recovery: See the Trafodion SQL Reference Manual for correct size values, and resubmit.

Cause: You defined a BLOCKSIZE with an invalid value. It must be 4096.

Effect: The operation fails.

Recovery: Correct the BLOCKSIZE value and resubmit.

Cause: You provided an invalid size value in the MAXSIZE clause.

Effect: The operation fails.

Recovery: See the Trafodion SQL Reference Manual for correct size values, and resubmit.

Cause: You provided an invalid percentage value in the DSLACK clause.

Effect: The operation fails.

Recovery: See the Trafodion SQL Reference Manual for correct percentage values, and resubmit.

Cause: You provided a location <name> with an invalid format.

Effect: The operation fails.

Recovery: See the Trafodion SQL Reference Manual for correct name format, and resubmit.

Cause: You specified duplicate EXTENT/MAXEXTENTS clauses in the PARTITION clause.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified duplicate DSLACK clauses in the PARTITION clause.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified duplicate ISLACK clauses in the PARTITION clause.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You defined a primary key as droppable in a table that includes STORE BY PRIMARY KEY in its definition, which is not supported.

Effect: Trafodion is unable to process this definition.

Recovery: Change the definition of the primary key constraint so that it is NOT DROPPABLE.

Cause: You specified an ALTER TABLE ADD CONSTRAINT statement with NOT DROPPABLE constraints. Only DROPPABLE constraints are allowed.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified an ALTER INDEX statement with both an ALLOCATE and a DEALLOCATE clause, which is not supported.

Effect: Trafodion ignores the ALTER INDEX statement.

Recovery: Correct the ALTER INDEX statement to include either ALLOCATE or DEALLOCATE.

Cause: You specified the [NO]AUDIT clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified duplicate [NO]AUDITCOMPRESS clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified an ALTER INDEX. . .ATTRIBUTE(S) statement that includes a BLOCKSIZE clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a [NO]BUFFERED clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified the SEPARATE BY clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified an ALTER INDEX. . .ATTRIBUTE(S) statement that includes a [NO]COMPRESS clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified duplicate DEALLOCATE clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified an ALTER INDEX. . .ATTRIBUTE(S) statement that includes the [NO]ICOMPRESS clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified an ALTER INDEX. . .ATTRIBUTE(S) statement that includes the LOCKLENGTH clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified duplicate EXTENT/MAXEXTENT clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified the [NO]SERIALWRITES clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified duplicate ALLOCATE clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified duplicate [NO]AUDIT clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified duplicate [NO]AUDITCOMPRESS clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified an ALTER TABLE. . .ATTRIBUTE(S) statement that includes the BLOCKSIZE clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified duplicate [NO]BUFFERED clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified duplicate [NO]CLEARONPURGE clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

ATTRIBUTE(S) statement.

Cause: You specified an ALTER TABLE. . .ATTRIBUTE(S) statement that includes the [NO]COMPRESS clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified an ALTER TABLE statement with both ALLOCATE and DEALLOCATE clauses, which is not supported.

Effect: The operation fails.

Recovery: Correct the ALTER TABLE statement to include either ALLOCATE or DEALLOCATE.

Cause: You specified an ALTER TABLE. . .ATTRIBUTE(S) statement that includes the [NO]ICOMPRESS clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate LOCKLENGTH clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a CREATE INDEX statement with the [NO]AUDIT clause, which is not supported.

Effect: Trafodion ignores the CREATE INDEX statement.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate BLOCKSIZE clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate DCOMPRESS clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a CREATE INDEX statement that includes the DEALLOCATE clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate [NO]ICOMPRESS clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate [NO]SERIALWRITES clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a CREATE TABLE statement that includes the DEALLOCATE clause, which is not supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate LOCATION clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate FILE ATTRIBUTE(S) clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate DSLACK clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate ISLACK clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate PARALLEL EXECUTION clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate PARTITION clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a CREATE TABLE statement with incorrect syntax. Only the ADD option is supported in a PARTITION clause.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You attempted to specify an invalid partitioning method. Currently only range, hash, hash2, and system partitioning are supported.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate PRIMARY KEY clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with duplicate LIKE clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with both LIKE and STORE BY clauses, which is not supported.

Effect: The operation fails.

Recovery: Correct the statement to include one of these clauses.

Cause: You specified a statement with duplicate STORE BY clauses.

Effect: The operation fails.

Recovery: Correct the syntax and resubmit.

Cause: You specified a statement with both LIKE and ATTRIBUTE(S) clauses, which is not supported.

Effect: The operation fails.

Recovery: Correct the statement to include one of these clauses.

Cause: You specified a statement with both LIKE and LOCATION clauses, which is not supported.

Effect: The operation fails.

Recovery: Correct the statement to include one of these clauses.

Cause: You specified a statement with both LIKE and PARTITION clauses, which is not supported.

Effect: The operation fails.

Recovery: Correct the statement to include one of these clauses.

Where <number> is the error number.

Cause: There is an error <number> in the CONTROL statement you specified.

Effect: The operation fails.

Recovery: Correct the CONTROL statement and resubmit.

Cause: You specified a statement with both READ WRITE and READ UNCOMMITTED clauses, which is not supported.

Effect: The operation fails.

Recovery: Correct the statement to include one of these clauses.