Teradata SQL Error and Failure Codes from Error 9294 To 9307

SQLServerF1_Header_Small

9294 Warning: Skipping system-defined join index validation.
Explanation: This message is displayed if any AMP fails to lock the system-defined join index in order to validate
against data table. This error can be reported in all levels of checking. Only that particular SJI validation is bypassed.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

9295 System-defined join index data row hash code is incorrect.
Explanation: A primary (or fallback if an AMP is down) SJI data row has incorrect hash code. The row’s hash code will
not be corrected in the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9296 Data subtable count does not match system-defined join index row count.
Explanation: This message is displayed if the row count of the system-defined join index is greater than the row count of
the base temporal table.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9297 Data row indexed by system-defined join index row with incorrect key.
Explanation: A discrepancy is detected when the key of each system-defined join index row is compared to the expected
key extracted from the data row.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9298 System-defined join index row has duplicate key with overlapping time values.
Explanation: Duplicated system defined join index keys with overlapping time values are detected as the system
defined join index subtables are traversed. The row is discarded from the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9301 EXPAND ON clause is non-ANSI.
Explanation: This is a warning code only. Warning is reported for a query with EXPAND ON clause when SQL flagger is
set to BTET for the session.
Generated By: RES modules
For Whom: End User.
Remedy: Informational message only.

9302 Specified expression for an EXPAND ON clause does not have a PERIOD data type.
Explanation: The expand expression does not have a valid data type.
Generated By: RES modules
For Whom: End User.
Remedy: Resubmit the request where the expand expression data type is PERIOD(DATE), PERIOD(TIMESTAMP), or
PERIOD(TIME).

9303 EXPAND ON clause must not be specified in a query expression with no table references.
Explanation: There is no table reference in the SELECT statement.
Generated By: RES modules
For Whom: End User.
Remedy: Resubmit the request with a table name specified in the SELECT statement.

9304 Invalid EXPAND ON column number.
Explanation: The specified column position is invalid; for example, it is more than the projected number of columns of
the SELECT statement.
Generated By: RES modules
For Whom: End User.
Remedy: Submit a new request with the actual column position of the expand period column or expression in the projection
list.

9305 Invalid data type in anchored EXPAND ON clause.
Explanation: The element type of the expand column in anchor expansion must not have TIME data type.
Generated By: RES modules
For Whom: End User.
Remedy: Submit a new request with element type of the period column to be either DATE or TIMESTAMP.

9306 Time option must not be specified when the data type of the expand expression is PERIOD(DATE).
Explanation: A time literal must not be specified if the element type of the period column is DATE.
Generated By: RES modules
For Whom: End User.
Remedy: Submit a new request without the time option.

9307 Invalid use of the expanded column name.
Explanation: This error is reported if the expanded column name is specified in any other clause other than ORDER BY
clause and in any expression in the projection list or ORDER BY clause.
Generated By: PAR modules
For Whom: End User.
Remedy: Submit a new request that correctly uses the expanded column name

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