Teradata SQL Error and Failure Codes from Error 2991 To 2999

SQLServerF1_Header_Small

2991 Express request does not contain database id.
Explanation: A required database id is not present in an express request.
Generated By: ExpCth, 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.

2992 Invalid database id.
Explanation: A database id in a step or express request does not correspond to a valid database, usually as determined
from the contents of the space accounting table DBC.DataBaseSpace.
Generated By: AMP space accounting logic. Table rebuild utility. MLoad error table processing.
For Whom: Site support representative.
Notes: This error may also be generated by other sanity checks in AMP software when a database id fails to match an
expected value. For example, MLoad uses it in this way.
Remedy: Contact your Support Representative.

2993 Primary reference index row is on the wrong AMP.
Explanation: Incorrectly distributed reference index rows are detected as the reference index subtables are traversed.
The row is discarded from the remainder of the checking process.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2994 Prime key field not present in row.
Explanation: A prime key field does not exist in the row that was input to the CalcHash procedure. The hash value is
still calculated without a value for one or more prime key fields.
Generated By: FMPProcs.
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.

2995 Duplicate field in into specification.
Explanation: A duplicate field id to be packed into a row by the FMPPkFld procedure is not packed. However, all other
fields are packed.
Generated By: FMPProcs.
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.

2996 Array specification is too small.
Explanation: The field specification array does not contain enough space for the number of fields in the row. The positions
available are used up.
Generated By: FMPProcs.
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.

2997 Requested field does not exist in row.
Explanation: A field with a nonzero size that was to be unpacked by the FMPUpFld procedure was not unpacked,
although the field does exist, and all other fields were unpacked.
Generated By: FMPProcs.
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.

2998 Requested field not found in row.
Explanation: The field identified in the request could not be found in the specified row.
Generated By: FMPProcs.
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.

2999 EOF when searching row for field.
Explanation: An entire row was searched without finding the requested field.
Generated By: FMPProcs.
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 2991 To 2999 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 *