Teradata SQL Error and Failure Codes from Error 2969 To 2980

SQLServerF1_Header_Small

2969 Lock call parameter error.
Explanation: The lock manager has detected an internal error caused either by an invalid procedure parameter or by
inconsistent lock table data structures.
Generated By: LokMangr.
For Whom: Site support representative.
Notes: The lock manager also uses this code internally as a return value for certain procedure calls to indicate an unexpected,
but not necessarily fatal result.
Remedy: Contact your Support Representative.

2970 Fatal error in lock procedures.
Explanation: The lock manager has detected a fatal internal error, typically representing a failed sanity check on lock
table data structures.
Generated By: LokMangr.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2971 The AMP Lock table has overflowed.
Explanation: The lock table segment has overflowed.
Generated By: LokMangr.
For Whom: End User.
Remedy: Wait until some transactions are finished, then resubmit the request.

2972 No table header exists for table.
Explanation: A table header does not exist for the table to be accessed.
Generated By: ExpBai, ExpInr. {DR42040-lg7-01}
For Whom: Site support representative.
Notes: This is either an internal error in the software or an error in the disk structure.
Remedy: If saving crashdumps, check if table exists in the crashdumps database. {DR42040-lg7-01 } For other cases, if the
table header subtable does not exist on the disk, then use the table rebuild utility to rebuild it.

2973 Invalid processor identifier.
Explanation: An invalid processor id was received in a backup message.
Generated By: ExpBai.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2974 Invalid backup message received.
Explanation: An invalid backup message was received by the AMP task.
Generated By: ExpBai.
For Whom: Site support representative.
Remedy: Contact your Support Representative

2975 Message with invalid class has been received.
Explanation: An invalid message class was received by the AMP task.
Generated By: AwtMain.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2976 Message with invalid kind has been received.
Explanation: An invalid message kind was received by the AMP task.
Generated By: AwtExpHd, AwtStpHd, AwtS2sHd, AwtRcv.Hd, AwtRcoHd, AwtHutHd, AwtU2uHd, AwtAcmHd.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2978 Table to be created already exists.
Explanation: The table to be created already exists.
Generated By: ExpCTH.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2979 Prime AMP is down and table is nonfallback.
Explanation: The prime AMP for the table hash code is down, and there is no fallback copy of the table.
Generated By: ExpAcf, ExpDld, ExpInr, ExpRar, ExpR2r, ExpRsi ExpUpr.
For Whom: Site support representative.
Notes: This is an internal error. All tables accessed through the express procedures should have fallback.
Remedy: Contact your Support Representative.

2980 Duplicate prime key.
Explanation: When an insert was attempted using a unique prime key, a row with the key value specified was found
already to exist.
Generated By: ExpInr.
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 2969 To 2980 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 *