Teradata SQL Error and Failure Codes from Error 9761 To 9807


9761 Dictionary load isolation information for %VSTR does not match header load isolation
Explanation: This message is displayed if the load isolation information in the table header does not match the corresponding
information in DBC.TVM record for the table.
Generated By: Checktable.
For Whom: Site support representative.
Remedy: Contact your support representative.

9762 The RowLoadID value in the index sub-table and the base-row does not match.
Explanation: This message is displayed if the RowLoadID of the secondary index and the primary data does not match
for a LDI table.
Generated By: Checktable.
For Whom: Site support representative.
Remedy: Contact your support representative.

9771 AutoCheck detected NUSI corruption when transaction is in non-abortable state. %s
Explanation: Corruption was detected in the NUSI or CDT index while doing index maintenance during rollback or
deferred transaction.
Generated By: AutoCheck.
For Whom: Site support representative.
Remedy: Contact your support representative.

9801 The PERCENTILE_CONT/PERCENTILE_DISC ORDER BY column must be a numeric data type.
Explanation: The PERCENTILE_CONT/PERCENTILE_DISC ORDER BY column must have a numeric data type.
Generated By: Res modules
For Whom: End User.
Remedy: Resubmit the request with a valid numeric expression.

9802 The DictionaryCacheSegmentSize is too small for this request.
Explanation: The request for cache is made that exceeds the segment size for cache. A single request should not exceed
the segment size.
Generated By: MGC modules.
For Whom: Internal.
Remedy: Increase the DBS Control Record field DictionaryCacheSegmentSize. See Teradata Utilities Manual for information
on DBS Control fields. Simplify the table by reducing the number of columns or shortening or removing some of
the titles or defaults .

9803 Views/Macros having SEQUENCED qualifier may fail during its use.
Explanation: View or Macros having SEQUENCED qualifier may report an error during its use if SEQUENCED semantics
can not be converted to point-in-time semantics.
Generated By: parser.
For Whom: User.
Remedy: Nothing to be done. Such cases are not yet by the database.

9804 Response Row size or Constant Row size overflow.
Explanation: The user request generated a response or constant row of data that exceeded internal Teradata database
NOTE: Although the size of spool files has been increased to 1 MB, response rows still have lower limits. The response row is limited to two 64k fields generated by the projection list and the order by clause. Constant rows are limited to approximately 1MB.
Generated By: Parser modules.
For Whom: End User.
Remedy: Change the SQL and/or reduce the data field sizes and/or number of fields being returned and resubmit the
request. Limit the projection list and order by clause to approximately 64k bytes of data each.

9805 User %FSTR is not authorized to use the VERYHOT temperature setting.
Explanation: The user tried to execute a statement that would manually set data to VERYHOT temperature but was not
Generated By: SYN and RES modules.
For Whom: The DBA.
Remedy: Grant execute macro access to macro DBC.VHCTRL to the user that caused the error and resubmit the request.

9806 Invalid Restore of database TD_SYSFNLIN.
Explanation: The user requested an invalid restore of database TD_SYSFNLIB. A restore of the TD_SYSFNLIB is not
Generated By: OPT Modules.
For Whom: User.
Remedy: The user must change the command to remove any invalid options. Then re-submit the rquest.

9807 Query caused a snapshot. It will be retried.
Explanation: This is a warning only, not an error. It informs the user that an automatic retry is being executed for the
Generated By: PAR modules.
For Whom: End User.
Notes: The request is still processed despite the warning.
Remedy: This message is for information only.

Above are list of Teradata Errors or Failure Codes from Error 9761 To 9807 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.

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 *