Teradata SQL Error and Failure Codes from Error 8109 To 8117

SQLServerF1_Header_Small

8109 Table structure modified during Open.
Explanation: The dictionary for the table was modified by some user while a Tbl_Open request was being processed.
Generated By: TblServe
For Whom: Field engineer.
Notes: This is an internal error which should be handled by other procedures. It should not cause a restart or be reported
to users.
Remedy: Contact your Support Representative.

8110 Selects must specify an index.
Explanation: The Tbl_Select operation must specify an IndexId and a pointer to an index row.
Generated By: TblServe
For Whom: Field engineer.
Notes: This is an internal error which should be handled by other procedures. It should not cause a restart or be reported
to users.
Remedy: Contact your Support Representative.

8111 Specified index does not exist.
Explanation: The IndesId passed in Tbl_Select operations specifies a value larger than the number of indices created on
the table.
Generated By: TblServe
For Whom: Field engineer.
Notes: This is an internal error which should be handled by other procedures. It should not cause a restart or be reported
to users.
Remedy: Contact your Support Representative.

8112 Secondary index is not unique.
Explanation: The specific secondary index specified in IndexId on Tbl_Select requests identifies a secondary index
which is nonunique. Only unique secondary index selects will be supported. Currently, no secondary index selects are supported.
Generated By: Not used.
For Whom: No user.
Remedy: Contact your Support Representative.

8113 No more data rows available.
Explanation: The nonunique primary index select has returned all the data it is going to. This is a warning that no more
data is available to the client. This does not indicate that a row with a matching primary index could not be located. That condition is indicated by the standard ErrAmpInvalidKey. ErrTblEndOfData is not returned when the primary index is
unique.
Generated By: TblServe
For Whom: Field engineer.
Notes: This is an internal error which should be handled by other procedures. It should not cause a restart or be reported
to users.
Remedy: Contact your Support Representative.

8114 Update is illegal.
Explanation: The Tbl_Update operation is not allowed on tables with secondary indices.
Generated By: TblServe
For Whom: Field engineer.
Notes: This is an internal error which should be handled by other procedures. It should not cause a restart or be reported
to users.
Remedy: Contact your Support Representative.

8115 Delete is illegal.
Explanation: The Tbl_Delete operation is not allowed on tables with secondary indices.
Generated By: TblServe
For Whom: Field engineer.
Notes: This is an internal error which should be handled by other procedures. It should not cause a restart or be reported
to users.
Remedy: Contact your Support Representative.

8116 Insert is illegal.
Explanation: The Tbl_Insert operation is not allowed on tables with secondary indices.
Generated By: TblServe
For Whom: Field engineer.
Notes: This is an internal error which should be handled by other procedures. It should not cause a restart or be reported
to users.
Remedy: Contact your Support Representative.

8117 Index or Row size is too big.
Explanation: The row passed to the table server on a Tbl_Select, Tbl_Update or Tbl_Insert operation contains too much
data to be considered a valid row.
Generated By: TblServe
For Whom: Field engineer.
Notes: This is an internal error which should be handled by other procedures. It should not cause a restart or be reported
to users.
Remedy: Contact your Support Representative.

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