Teradata SQL Error and Failure Codes from Error 9692 To 9704

SQLServerF1_Header_Small

9692 HASH BY/PARTITION BY expression not found in input SELECT list.
Explanation: A HASH BY or PARTITION BY expression must be part of the input SELECT list for the user defined table
operator.
Generated By: OPT modules.
For Whom: End User.
Remedy: Change HASH BY/PARTITION BY phrase or input SELECT list.

9693 NORMALIZE not allowed for system projected transaction time column.
Explanation: NORMALIZE not allowed for system projected transaction time column.
Generated By: OPT module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9694 MultiLoad utility does not support load operations on NORMALIZE tables.
Explanation: MultiLoad utility does not support load operations on NORMALIZE tables.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9695 SET REDRIVE FOR TRANSACTION is not supported in query band statement.
Explanation: The SET REDRIVE FOR TRANSACTION is not supported in query band statement. It is supported with
FOR SESSION option only.
Generated By: OPD
For Whom: User.
Remedy: Correct the query band statement and resubmit.

9696 Unwind parser stack and return to dispatcher during abort of IPE request.
Explanation: Unwind parser stack and return to previous dispatcher logmark when aborting an IPE request.
Generated By: Dispatcher, Parser modules.
For Whom: Internal only.
Remedy: This operation is internal to the database. When parser optimizes a request using IPE and the SQL request
receives an abort, dispatcher raises this event to signal parser to unwind the stack and return to the previous dispatcher
logmark.

9697 Updating ignore column(s) is not allowed on normalize table with current or sequenced validtime update.
Explanation: Updating ignore column(s) is not allowed on normalize table with current or sequenced validtime update.
Generated By: RES module.
For Whom: End User.
Remedy: Don’t update only the ignore column.
9698 Invalid DELETE in Fastload: %VSTR.
Explanation: FastLoad does not permit DELETE other than Nontemporal DELETE.
Generated By: resolver.
For Whom: Host Utility Fast Load.
Remedy: Correct the statement and resubmit the request.

9699 Only one expression is permitted in the WITHIN GROUP ORDER BY clause .
Explanation: The PERCENTILE_CONT/PERCENTILE_DISC functions support one expression in WITHIN GROUP
ORDER BY specification.
Generated By: Res modules
For Whom: End User.
Remedy: Resubmit the request with a valid ORDER BY expression.

9700 The PERCENTILE_CONT/PERCENTILE_DISC(expression) must be a numeric value between 0 and 1.
Explanation: The PERCENTILE_CONT/PERCENTILE_DISC expression must evaluate to a numeric value between 0
and 1.
Generated By: Res modules
For Whom: End User.
Remedy: Resubmit the request with a valid numeric expression.

9701 The system was restarted with redrive disabled due to a crash during startup.
Explanation: There was a crash during startup. Redrive has been disabled in order to prevent this crash from occurring
repeatedly and taking down the PE.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Contact your support representative.

9703 A table does not have Normalize definition.
Explanation: Normalize definition can not be dropped without defined it on a table.
Generated By: RES module.
For Whom: End User.
Remedy: Normalize definition can not be dropped without defined it on a table.

9704 A Dispatcher is late in responding to a TDWM internal message; no action needed.
Explanation: This is a TDWM informational message only. On each TDWM dashboard interval a message is sent to each
dispatcher requesting data. If a dispatcher does not respond before the next interval, this message is logged. As a result of a late dispatcher message, some rows may be missing through the TDWMExceptions API however all rows are logged to disk.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: This is an informational message only. The software handles the situation and no user response is needed. The
DBA may take note of the logged message in investigating system responses.

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