Teradata SQL Error and Failure Codes from Error 9379 To 9391

SQLServerF1_Header_Small

9379 Temporal constraint cannot include time dimension columns.
Explanation: Disallow VT and TT to be part of any user specified constraint that creates a SJI.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement by removing the Temporal columns and resubmit the request.

9380 System-defined join index can not be created on a table with unresolved RI.
Explanation: Currently join indexes cannot be created on a table that has an unresolved RI. Thus a system-defined join
index cannot be created on such temporal tables.
Generated By: RES modules.
For Whom: End User.
Remedy: Create parent tables for corresponding unresolved RIs and resubmit this request.

9381 System-defined join index can not be created on the target table during CREATE TABLE AS WITH DATA operation.
Explanation: System-defined join indexes cannot be created on the target table that has a unique/Primary Key constrait
that requires a system-defined join index during CREATE TABLE AS WITH DATA operation.
Generated By: RES modules.
For Whom: End User.
Remedy: Do CREATE TABLE AS WITH NO DATA and then populate the table using insert select.

9383 A SET temporal table is not yet supported.
Explanation: A temporal table must only be a MULTISET table. Temporal table can not be a SET table explicitly or
implicitly.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement by changing the property to MULTISET and resubmit the request.

9385 TEMPORAL_DATE/TEMPORAL_TIMESTAMP are not allowed in load operation.
Explanation: TEMPORAL_DATE/TEMPORAL_TIMESTAMP are not allowed in load operation.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement by removing TEMPORAL_DATE/TEMPORAL_TIMESTAMP and resubmit the request.

9386 Table structure is altered to remove temporal column.
Explanation: A ValidTime or TransactionTime column is removed in one of the referenced tables in the statement. 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.

9387 Invalid use of system added temporal column.
Explanation: System added temporal column can not be referenced in the same query level except in order by or expand
on clause.
Generated By: RES modules.
For Whom: End user.
Remedy: Remove use of system added temporal columnn.

9388 Value assigned to VT column should not contain CURRENT_DATE or CURRENT_TIMESTAMP.
Explanation: Error will be reported if the value assigned to VT column contains CURRENT_DATE or
CURRENT_TIMESTAMP either assigned directly or through PA.
Generated By: RES and OPD modules.
For Whom: End user.
Remedy: Correct the statement by removing CURRENT_DATE and CURRENT_TIMESTAMP and resubmit the request.

9389 A TRC column can not be modified/dropped. The table has a constraint defined.
Explanation: TRC column can not be dropped until all Temporal Relationship Constraints are dropped.
Generated By: OPD modules.
For Whom: End user.
Remedy: Drop all Temporal Relationship Constraints before dropping TRC column.

9390 Only one column can be defined as TRC column.
Explanation: More than one TRC columns are not allowed. However same column can be used to create multiple temporal
relationship constraints.
Generated By: Resolver.
For Whom: End user.
Remedy: Use the already existing TRC column in the Temporal Relationship Constraint and resubmit.

9391 MultiLoad utility does not support load operations on temporal tables.
Explanation: MultiLoad utility does not support load operations on temporal tables.
Generated By: RES modules.
For Whom: End User.
Remedy: Use a multi-phased mini-batch approach. Load the data into a staging table and then use UPDATE FROM, or
MERGE INTO to modify the target.

Above are list of Teradata Errors or Failure Codes from Error 9379 To 9391 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 *