Teradata SQL Error and Failure Codes from Error 9363 To 9378

9363 Temporal column reference in %VSTR is invalid.
Explanation: A temporal column is referenced in the following contexts and it is invalid in the specified qualifier in the
modification statement: SET clause in the update statement. For example, a ValidTime column is not allowed in the SET
clause if the statement is a current or sequenced update.
Generated By: RES modules.
For Whom: End User.
Remedy: Fix the statement to avoid explicit assignment of the ValidTime and/or TransactionTime column.

9367 Specified ValidTime qualifier does not match with the qualifier of the updateable cursor select statement.
Explanation: The qualifier for the CURSOR select statement and the specified qualifier in the positioned update or
delete are not compatible.
Generated By: GNC modules.
For Whom: End User.
Remedy: Resubmit the positioned update or delete with appropriate qualifier.

9368 The temporal request violates CURSOR semantics.
Explanation: The qualifier of the cursor select statement and the specified qualifier in the searched update or delete are
not compatible. The modification statement is disallowed.
Generated By: GNC modules.
For Whom: End User.
Remedy: Resubmit the positioned update or delete with appropriate qualifier.

9369 Period of applicability does not result in a valid period data type.
Explanation: Period of applicability must be a period expression resulting in a PERIOD(DATE) or PERIOD(TIMESTAMP)
type, any other element type will report this error.
Generated By: RES modules.
For Whom: End User.
Remedy: Change the period expression so that period element type is date or timestamp.

9370 A Global Temporary Trace table can not be temporal.
Explanation: A Global Temporary Trace table can not be a temporal table.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

9371 Invalid use Of UNTIL_CHANGED.
Explanation: This error occurs only if UNTIL_CHANGED is used for a TT col.
Generated By: RES modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and the dump, and contact your support representative.

9373 Specified uniqueness/primary key constraint requires a system-defined join index. Constraint is not allowed on the table.
Explanation: Currently join indexes cannot be created on volatile and temporary tables. Thus a system-defined join
index cannot be created on such temporal tables.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement by removing the constraint and resubmit the request.

9374 A system-defined join index cannot be altered.
Explanation: An attempt to alter the system-defined join indexes properties or altering the system-defined join indexes
to currrent will cause this error.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

9375 The temporal qualifier of the updatable cursor is not CURRENT.
Explanation: This release supports only CURRENT temporal qualifier for an updatable cursor.
Generated By: OPT modules
For Whom: End user
Remedy: Change the temporal qualifier of the updatable cursor’s SELECT/UPDATE/DELETE statement to CURRENT.

9376 The temporal request violates cursor semantics.
Explanation: Two cases may cause the error: 1. A table is opened by a current updatable cursor and a non-current
searched update is performed on the table before the cursor does update. Then when the cursor does update later, confliction
happens.
2. The temporal qualifier of a searched update/delete on a table, which is currently being updated by a updatable cursor, is
not current.
Generated By: OPT modules
For Whom: End user
Remedy: Change the temporal qualifier of the updatabale cursor’s SELECT/UPDATE/DELETE statement to CURRENT.

9377 Diagnostic OLDREWRITES not allowed when the query contains Temporal Tables.
Explanation: When there are temporal tables in the query, they must follow the NEW Query Rewrite Logic.
Generated By: RES modules.
For Whom: End User.
Remedy: Switch off the OLDREWRITES diagnostic and then resubmit the query.

9378 Operation is not permitted for replication.
Explanation: case(i): When a table in replication group is being altered to add ValidTime or TransactionTime column.
The default value for the column must not contain current_date, current_timestamp, temporal_date, temporal_timestamp case(ii): When DDL capture is enabled, the CREATE TABLE AS <QUERY EXPRESSION> WITH DATA and CREATE
TABLE AS <TABLE> WITH DATA is not supported for creating temporal tables.
Generated By: RES/OPU Modules
For Whom: End User.
Remedy: case(i): Provide a period value with literal date or timestamp as default value for ValidTime column.If adding a
ValidTime column. None. If adding a TransactionTime column.
case(ii): Table must be created using CREATE TABLE followed by an INSERT-SELECT.

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