Teradata SQL Error and Failure Codes from Error 2981 To 2990

SQLServerF1_Header_Small

2981 Invalid unique primary index.
Explanation: When a select was attempted using a key, no row was found that contained the key value.
Generated By: ExpRer.
For Whom: Site support representative.
Notes: This is an internal error that should be handled by other procedures. It should not cause a crash or be reported to
a user.
Remedy: Contact your Support Representative.

2982 No current row defined.
Explanation: In an express request to select the next row, no current row was defined.
Generated By: ExpRar.
For Whom: Site support representative.
Notes: This is an internal error that should be handled by other procedures. It should not cause a crash or be reported to
a user.
Remedy: Contact your Support Representative.

2983 Invalid current row.
Explanation: In an express request to select the next row, the row that is defined as current does not exist.
Generated By: ExpRar.
For Whom: Site support representative.
Notes: This is an internal error that should be handled by other procedures. It should not cause a crash or be reported to
a user.
Remedy: Contact your Support Representative.

2984 Invalid row in express update request.
Explanation: In an express request to update a row, the row to be updated does not exist.
Generated By: ExpUpr.
For Whom: Site support representative.
Notes: This is an internal error that should be handled by other procedures. It should not cause a crash or be reported to
a user.
Remedy: Contact your Support Representative.

2985 No unique prime key for express request.
Explanation: In an express request to add a constant to a field of a table, the table is not defined with a unique primary
index.
Generated By: ExpAcf.
For Whom: Site support representative.
Notes: This is an internal error that should be handled by other procedures. It should not cause a crash or be reported to
a user.
Remedy: Contact your Support Representative.

2986 Invalid field type for express request.
Explanation: The field identified in an express request to add a constant to a field of a row has an invalid field format.
Generated By: ExpAcf.
For Whom: Site support representative.
Notes: This is an internal error that should be handled by other procedures. It should not cause a crash or be reported to
a user.
Remedy: Contact your Support Representative.

2987 Invalid lock types in express request.
Explanation: An invalid lock type is present in the request.
Generated By: ExpLok.
For Whom: Site support representative.
Notes: This is an internal error that should be handled by other procedures. It should not cause a crash or be reported to
a user.
Remedy: Contact your Support Representative.

2988 Invalid format for express request.
Explanation: An express request requires a row definition, and neither a rowidentifier nor a prime key is present.
Generated By: ExpAcf, ExpDld, ExpRer.
For Whom: Site support representative.
Notes: This is an internal error that should be handled by other procedures. It should not cause a crash or be reported to
a user.
Remedy: Contact your Support Representative.

2989 Table id is not present in express request.
Explanation: A required table id is not present in an express request.
Generated By: ExpCth, ExpDld, ExpFth, ExpInr, ExpRar, ExpRer, ExpRsi, ExpUpr.
For Whom: Site support representative.
Notes: This is an internal error that should be handled by other procedures. It should not cause a crash or be reported to
a user.
Remedy: Contact your Support Representative.

2990 Table id in express request does not exist.
Explanation: The table id in an express request is invalid.
Generated By: ExpCth, ExpDld, ExpFth, ExpInr, ExpRar, ExpRer, ExpRsi, ExpUpr.
For Whom: Site support representative.
Notes: This is an internal error that should be handled by other procedures. It should not cause a crash or be reported to
a user.
Remedy: Contact your Support Representative.

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