Teradata SQL Error and Failure Codes from Error 9308 To 9324

SQLServerF1_Header_Small

9308 Some rows in the expanded result may have expanded period duration less than the interval
specified.
Explanation: This is a warning message only. This warning is reported if the interval being expanded is of higher granule
than the element type of the period being expanded.
Generated By: PAR modules
For Whom: End User.
Remedy: Informational message only.

9309 Invalid expression for ANCHOR/INTERVAL in the BY clause.
Explanation: The element type of the ANCHOR/INTERVAL expression must be either of the following EVLCHARFIX,
EVLCHARVAR, EVLINTEGER8,EVLANSIINTERVAL
Generated By: QRW modules
For Whom: End User.
Remedy: Submit a new request with the valid ANCHOR/INTERVAL expression.

9310 Invalid argument to a business calendar UDF.
Explanation: Invalid argument is supplied to a business calendar UDF.
Generated By: RES modules
For Whom: End User.
Remedy: Resubmit the request with the correct arguments.

9311 Calendar does not exist.
Explanation: The calendar specified by the user does not exist.
Generated By: RES modules
For Whom: End User.
Remedy: Resubmit the request with a valid calendar name.

9316 Duplicated ’%VSTR’ attribute is specified.
Explanation: There can be at most one column with the same temporal column attribute ie., defining more than one TT
col or VT col is not allowed in the temporal table.
Generated By: RES Modules.
For Whom: End User.
Remedy: Correct the values and re-submit.

9317 A queue table cannot be temporal.
Explanation: A Queue Table cannot be a Temporal Table
Generated By: SYN Modules.
For Whom: End User.
Remedy: Correct the values and re-submit.

9318 A table without a primary index can not be a temporal table.
Explanation: The specified temporal table is defined without a primary index.
Generated By: OPD modules.
For Whom: End User.
Remedy: Remove the temporal columns or attributes in the table definition or create a nonunique primary index and
resubmit request or enable NoPI Temporal feature.

9319 A unique primary index is not permitted on a temporal table.
Explanation: The specified temporal table is defined with a unique primary index.
Generated By: Syntaxer.
For Whom: End User.
Remedy: Remove the temporal columns or attributes in the table definition or create a nonunique primary index and
resubmit request.

9320 The table already has a %VSTR column.
Explanation: The table being altered is adding a ValidTime or TransactionTime column and the table already has that
temporal column
Generated By: RES Modules.
For Whom: End User.
Remedy: Fix the request to remove the duplicated temporal column and resubmit the request.

9321 A temporal column cannot be added to a table which has a referential integrity constraint.
Explanation: The table being altered to add ValidTime and/or TransactionTime column/s has RI defined on it. A temporal
column cannot be added to table with RI.
Generated By: RES Modules
For Whom: End User.
Remedy: Drop the RI on the table being altered and then alter it to add ValidTime or TransactionTime columns.

9322 A temporal attribute is not allowed on a table with a unique primary index.
Explanation: The table being altered as a temporal table has UPI defined. A temporal table cannot have UPI.
Generated By: OPD Modules
For Whom: End User.
Remedy: Check the table definition.

9324 Cannot add ValidTime 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 ValidTime 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.

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