Teradata SQL Error and Failure Codes from Error 9679 To 9691

SQLServerF1_Header_Small

9679 SQL request cannot be prepared because query capture is in effect for this session.
Explanation: The BEGIN QUERY CAPTURE session currently does not support parameterized SQL requests with question-
mark parameter markers & non-parameterized SQL requests as part of Auto-Generated Key Retrieval (AGKR).
Generated By: parser.
For Whom: User.
Remedy: Do not submit parameterized SQL requests with question-mark parameter markers & non-parameterized SQL
requests as part of Auto-Generated Key Retrieval (AGKR) in BEGIN QUERY CAPTURE session.

9680 SQL request was not executed because query capture is in effect for this session.
Explanation: This is only a warning to indicate that the SQL request submitted within a BEGIN QUERY CAPTURE session
is not actually executed. The query capture is successfully done for the submitted SQL request.
Generated By: parser.
For Whom: User.
Remedy: Simply ignore, as this is the expected behaviour in BEGIN QUERY CAPTURE session. However, if the SQL
request needs to be executed then end the BEGIN QUERY CAPTURE session using END QUERY CAPTURE statement and
resubmit the SQL request.

9682 Invalid Normalize operation , MEETS only is not allowed.
Explanation: MEETS NORMALIZE operation is not supported on TD1410.
Generated By: SYN module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9683 The DBQL ObjectUsage logging is not enabled. The change percentage to skip statistics collection is determined based on dynamic AMP sampling, which can only detect the row count change.
Explanation: The DBQL ObjectUsage logging is not enabled. The change percentage to skip this statistics collection is
determined based on the dynamic AMP sampling which can only detect the row count change. Therefore, the system cannot
accurately determine the update and the combination of insert and delete counts on the target table.
Generated By: OPD modules.
For Whom: End User.
Notes: This warning is issued when the DBQL ObjectUsage logging is not enabled and statistics collection is skipped.
Remedy: Turn on ObjectUsage logging for the target database if more accuracy is needed.

9685 Statistics on this expression are not valid.
Explanation: The statistics expression refers to objects which no longer exists or matches with the original expression.
Generated By: OPT modules.
For Whom: End User.
Remedy: Revalidate the statistics by recreating the object referred in the expression or drop the invalid stats by dropping
all the statistics on the table and recollect the required statistics.

9686 The specified sampling percentage may not be optimal for some of the statistics.
Explanation: A user-specified sampling percentage value is not optimal and might cause estimation errors.
Generated By: OPD modules.
For Whom: End User.
Notes: This warning is issued when a user specified a sampling percentage which is not optimal.
Remedy: Use system-determined sampling percentage (recommended) or increase the user-specified sampling percentage.

9687 No active BEGIN QUERY CAPTURE to end.
Explanation: There is no active BEGIN QUERY CAPTURE session in progress to end. END QUERY CAPTURE statement
is used to end the scope of previously submitted BEGIN QUERY CAPTURE statement in the session.
Generated By: parser.
For Whom: User.
Remedy: Nothing to be done. This error is for information only that there is no currently active BEGIN QUERY CAPTURE
session in progress..

9688 Table operator’s execution error: %VSTR.
Explanation: Table operation’s execution error with the detailed message.
Generated By: Parser.
For Whom: System Support Representative.
Remedy: Contact your support representative.

9689 A CURSOR is not updatable when NORMALIZE clause is specified in the CURSOR select statement.
Explanation: A CURSOR is not updatable when NORMALIZE clause is specified in the CURSOR select statement.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9690 WITH clauses may not be specified in a SELECT NORMALIZE request.
Explanation: WITH clauses may not be specified in a SELECT NORMALIZE request.
Generated By: OPT module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9691 Invalid HASH BY/PARTITION BY constant.
Explanation: A HASH BY or PARTITION BY constant does not represent the position of a selected expression.
Generated By: OPT modules.
For Whom: End User.
Remedy: Change HASH BY/PARTITION BY phrase.

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