Teradata SQL Error and Failure Codes from Error 9352 To 9362

9352 Invalid use of AS OF clause.
Explanation: An AS OF qualifier is in one of the following incorrect contexts: (1) the table on which it is specified does
not have ValidTime or TransactionTime dimension. (2) it is specified on the target table being modified.
Generated By: RES modules.
For Whom: End User.
Remedy: Remove the AS OF qualifier if it is not applicable.

9353 Multiple tables must not be specified with a sequenced TransactionTime qualifier.
Explanation: A Sequenced qualifier in the TransactionTime dimension is specified in the statement and there are multiple
tables referenced in the statement.
Generated By: RES modules.
For Whom: End User.
Remedy: Remove the sequenced qualifier if it is not applicable.

9354 Invalid temporal qualifier in the query statement.
Explanation: A Sequenced qualifier in the TransactionTime dimension is allowed only in a view or derived table or a
subquery in the CREATE TABLE AS statement. It is invalid if it is used in any other context.
Generated By: RES modules.
For Whom: End User.
Remedy: Remove the sequenced qualifier if it is not applicable.

9356 Table %VSTR does not support the ValidTime. ValidTime qualifier is invalid.
Explanation: A ValidTime qualifier is specified in the modification statement but the table being modified does not support
ValidTime dimension.
Generated By: RES modules.
For Whom: End User.
Remedy: Remove the ValidTime qualifier if it is not applicable.

9357 Normalize option is invalid. %VSTR.
Explanation: The modification statement specifies a Normalize clause and one of the following conditions is true. The
clause is not supported in such conditions. (a) The table is not having ValidTime support. (b) The table declared is a multiset
table. (c) The qualifier specified is NONSEQUENCED VALIDTIME or is a NONTEMPORAL insert. (d) The table is
involved in a load job.
Generated By: RES modules.
For Whom: End User.
Remedy: Remove the NORMALIZE clause.

9358 Values cannot be assigned to a TransactionTime column.
Explanation: The modification statement is current in TransactionTime dimension. The TransactionTime column values
cannot be specified. The values are system generated.
Generated By: RES modules
For Whom: End user
Remedy: Remove the assignment for the TransactionTime column or check if a NONTEMPORAL qualifier is required.

9359 Invalid temporal qualifier for INSERT statement.
Explanation: A SEQUENCED VALIDTIME with a period of applicablity in the INSERT statement must be specified
only if the INSERT statement is an INSERT-SELECT. In other contexts a period of applicability cannot be specified.
Generated By: RES modules.
For Whom: End User.
Remedy: Remove the period of applicability and specify the value in the INSERT value list for the ValidTime column.

9360 ValidTime column name is invalid in the column list for a sequenced insert-select statement.
Explanation: A SEQUENCED VALIDTIME INSERT-SELECT statement is specified and the insert names the ValidTime
column in the name list. A name list cannot include ValidTime column as the resulting ValidTime value of the sequenced
SELECT will be inserted into the target table.
Generated By: RES modules.
For Whom: End user.
Remedy: Remove the ValidTime column name from the named list.

9361 Table %VSTR does not support TransactionTime. NONTEMPORAL qualifier is invalid.
Explanation: A NONTEMPORAL qualifier is specified in the statement but the target table being operated does not
support TransactionTime dimension.
Generated By: RES modules.
For Whom: End User.
Remedy: Remove the NONTEMPORAL qualifier.

9362 Invalid value specified for the TransactionTime column.
Explanation: A NONTEMPORAL qualifier is recording a TransactionTime value and one of the following conditions is
met. a) the beginning bound of the TransactionTime column value is greater than the TT_TIMESTAMP value as generated
in the AMP b) the ending bound of the TransactionTime column is greater than the TT_TIMESTAMP value generated in the
AMP but is not an UNTIL_CLOSED value.
Generated By: AMP modules
For Whom: End user
Remedy: Fix the value being assigned to the TransactionTime column.

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