Teradata SQL Error and Failure Codes from Error 8118 To 8125

8118 Index or Row size is too small.
Explanation: The row passed to the server for Tbl_Select, Tbl_Insert or Tbl_Update operations contains too little 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.

8119 An index field size is invalid.
Explanation: The size of a field involved in an index was not valid. For VARBYTE and VARCHAR fields, the size must
be less than or equal to the maximum size of the field. For all other fields, the size must be identical.
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.

8120 A field is null.
Explanation: A field which is defined as “NOT NULL” or a field which is involved in an index was passed as a NULL
value to Tbl_Select or TblMvFld was asked to move data FROM the row returned by Tbl_Select and the field containing the
data was null.
Generated By: TblServe, TblMvFld
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.

8121 Field does not exist
Explanation: The field name specified in a call to TblLocat or TblMvFld does not exist.
Generated By: TblLocat, TblMvFld
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

8122 Not enough room to move that field.
Explanation: The size specified in a call to TblLocat or TblMvFld is not valid. VARCHAR and VARBYTE fields can be no
larger than the maximum length permitted and all other fields must be exactly the maximum length.
Generated By: TblMvFld
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.

8123 Service disallowed when more select data is available.
Explanation: Tbl_Insert, Tbl_Update, Tbl_Delete and Tbl_Close operations are not allowed when a Tbl_Select has been
initiated against a table with nonunique prime keys and the client has not done enough continuation Tbl_Selects to cause
the server to return ErrTblEndOfData. New Tbl_Select operations (those specifying keys or row ids) are also disallowed.
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.

8124 More rows are waiting to be selected.
Explanation: The client has issued a non-unique primary index select and the table driver has found more than one row.
This return code is not intended as an error, but as an informational warning message.
Generated By: TblServe
For Whom: Field engineer.
Notes: This is an internal error which should never be seen in the field. It should not cause a restart to occur, nor should
it be reported to end users.
Remedy: Contact your Support Representative.

8125 Requested operation is not ReadOnly.
Explanation: Some operation other than TblSelect, TblRedist, TblDupHand or TblClose is not legal on tables opened
with the TblOpt_ReadOnly option.
Generated By: TblServe
For Whom: Field engineer.
Notes: This is an internal error which should never be seen in the field. It should not cause a restart to occur, nor should
it be reported to end users.
Remedy: Contact your Support Representative.

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