Teradata SQL Error and Failure Codes from Error 9325 To 9336

9325 Table structure is altered to add %VSTR column and no qualifier is defined for this time dimension.
Explanation: A ValidTime or TransactionTime column is added in one of the referenced tables in the statement and there
is no qualifier for that time dimension. The error is reported when the statement is executed from a view or macro or a
stored procedure.
Generated By: RES modules.
For Whom: End user.
Remedy: The view or macro must be recreated or the stored procedure must be recompiled using an appropriate temporal
qualifier for the request to be successful..

9326 Cannot add TransactionTime column to the table: %VSTR.
Explanation: A table with a join index and/or a trigger defined on it or if it is a temporal table with uinque or primary
key constraints that requires system-defined JI then table cannot be altered to add a TransactionTime column.
Generated By: RES Modules
For Whom: End User.
Remedy: Drop any join indexes and/or triggers or unique or primary constraints that requires sytem-defined JI(if the
table being altered is a temporal table) and resubmit the request. Recreate the droped join indexes and/or triggers or
unique or primary key constraints once the table is altered.

9327 An existing column can not be altered to be a temporal column.
Explanation: One of the existing columns is defined as a temporal column in the ALTER TABLE statement. An ALTER
TABLE statement does not permit an existing column to be made into a temporal column.
Generated By: OPD Modules
For Whom: End User.
Remedy: Add a new column as a temporal column and drop the existing column once the data is processed into the new
temporal column.

9328 History rows in a table with TransactionTime cannot be modified.
Explanation: The specified ALTER TABLE statement is modifying the values of one of the columns of the Transaction-
Time table without the use of NONTEMPORAL statement prefix. The closed rows in a table with TransactionTime support
cannot be modified unless the user has a NONTEMPORAL privilege.
Generated By: RES modules.
For Whom: End User.
Remedy: Prefix the ALTER TABLE with NONTEMPORAL and retry.

9329 A temporal column cannot be dropped. The table has %VSTR.
Explanation: A temporal table has constraints (CHECK, UNIQUE, PRIMARY KEY or RI) or join index or trigger
defined. The existing constraints or join index or triggers are associated with the temporal time dimension and hence the
temporal column cannot be dropped.
Generated By: OPD modules.
For Whom: End User.
Remedy: Drop the constraints and join indexes and triggers before dropping a temporal column.

9330 ValidTime qualifier requires at least one table with ValidTime.
Explanation: A temporal ValidTime qualifier is specified in the statement and none of the referenced tables are supporting
ValidTime. If the error is reported from a statement executed using a view, macro, trigger or a stored procedure , it is
likely that a table was modified to remove the ValidTime column.
Generated By: RES modules.
For Whom: End User.
Remedy: Fix the temporal qualifier in the statement and resubmit the request. If this is occurring for a statement referenced
in a view or a macro or a stored procedure then these objects may have to be recreated to correctly record the temporal
qualifier.

9331 TransactionTime qualifier requires at least one table with TransactionTime.
Explanation: A temporal TransactionTime qualifier is specified in the statement and none of the referenced tables are
supporting TransactionTime. If the error is reported from a statement executed using a view, macro, trigger or a stored procedure,
it is likely that a table was modified to remove the TransactionTime column.
Generated By: RES modules.
For Whom: End User.
Remedy: Fix the temporal qualifier in the statement and resubmit the request. If this is occurring for a statement referenced
in a view or a macro or a stored procedure then these objects may have to be recreated to correctly record the temporal
qualifier.

9334 Invalid constraint definition.
Explanation: This error can occur for any of the following reasons: 1) A hard RI is being defined on a temporal table.
Hard RI is not allowed on temporal tables. 2) The constraint definition is specifying a ValidTime qualifier option and the
table does not support ValidTime 3) The constraint definition is specifying a TransactionTime qualifier option and the table
does not support TransactionTime.
Generated By: OPD modules.
For Whom: End user.
Remedy: Correct the temporal qualifier used in the constraint and Soft RI can be defined instead of hard RI. Fix and
resubmit the request.

9335 Rows cannot be deleted from a table with TransactionTime.
Explanation: The ALTER TABLE statement to modify the partitioning expression is submitted on a TransactionTime
table using a WITH DELETE or WITH INSERT option. These options cause rows that violate the new partitioning expression
to be deleted from the table. Deletion of rows is not allowed on a TransactionTime table.
Generated By: OPD Modules
For Whom: End User.
Remedy: Use the NONTEMPORAL prefix in the ALTER TABLE statement.

9336 Temporal column cannot be used in constraint definition.
Explanation: A column referenced by a unique or primary key constraint definition or RI constraint defination is a temporal
column. Temporal columns cannot be used in unique or primary key or RI constraint definition.
Generated By: RES modules.
For Whom: End user.
Remedy: Eliminate temporal columns from the unique or primary key or RI constraint definition and resubmit the
request.

Above are list of Teradata Errors or Failure Codes from Error 9325 To 9336 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *