Teradata SQL Error and Failure Codes from Error 2866 To 2875

2866 Table was Recovery Aborted; no data dumped.
Explanation: The table being dumped was Recovery Aborted. No data rows are being dumped, just the table header.
Generated By: Dump.
For Whom: End User.
Notes: When the table is restored from this dump, it will be empty.
Remedy: The data in the table is inconsistent and cannot be used in any manner. The table should be restored or dropped
and recreated.

2867 AMP nnnn failed to recover permanent journal %DBID.%TVMID.
Explanation: Down Amp recovery has failed to recover the indicated permanent journal table. The journal table on AMP
nnnn has been invalidated.
Generated By: System Recovery
For Whom: End User.
Remedy: The data in the table is inconsistent and cannot be used in any manner. This is an internal error. Contact your
Support Representative.

2868 This permanent journal table is damaged; no data dumped.
Explanation: Data in this permanent journal table has been corrupted.
Generated By: Dump.
For Whom: User.
Remedy: The probable cause was a system failure during a table rebuild of the specified journal table. The rebuild operation
must be completed before the journal is usable.

2869 Requested lock cannot be granted.
Explanation: The required lock cannot be granted.
Generated By: USVLock.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2870 Database lock on DBC.DBCInfoTbl prevented updates.
Explanation: A transaction read lock or higher was encountered on some AMP for DBC.DBCInfoTbl during system
startup.
Generated By: SSSUINFO
For Whom: Operator.
Remedy: The lock, most likely a lock placed by recover, should eventually be released. The DBCInfoTbl table will not be
updated until the next system restart.

2871 Missing table header for DBC.DBCInfoTbl, updates bypassed.
Explanation: The table header for DBC.DBCInfoTbl is missing on some AMP.
Generated By: SSSUINFO
For Whom: Site support representative.
Notes: The receipt of this error indicates that the DBCInfoTbl table is corrupted.
Remedy: Contact your Support Representative.

2872 Unexpected DBC.DBCInfoTbl format, updates bypassed.
Explanation: The DBC.DBCInfoTbl table does not have the expected format.
Generated By: SSSUINFO
For Whom: Site support representative.
Notes: The receipt of this error indicates that the DBCInfoTbl table is corrupted in some way.
Remedy: Contact your Support Representative.

2873 Pending operation on DBC.DBCInfoTbl prevented updates.
Explanation: This table is in the process of being Fast Loaded Restored, or has been Recovery Aborted on some AMP.
Generated By: SSSUINFO
For Whom: Site support representative.
Notes: Since tables in the DBS database can not be the target of a Recovery Abort or a Fast Load operation, and proper
user of Restore will not leave a table in DBS in the ’restoring’ state, this error should never be encountered.
Remedy: Contact your Support Representative.

2874 A read error occurred in a permanent journal table.
Explanation: A disk read error occurred in a permanent journal table. Refer to the accompanying 2538 error message for
the permanent journal table id. The bad data block cannot be rebuilt automatically by the Teradata DBS. Manual intervention
is required. This error is logged prior to a crash due to error ErrAMPPJReadErr.
Generated By: RbkCtrl.
For Whom: Operator. DBA. Site support representative.
Remedy: The permanent journal table must be rebuilt. If any user table which journals to this permanent journal table is
not defined as dual image, then there will be loss of data in the permanent journal table during the table rebuild. Contact
your Support Representative.

2875 Task Lock cannot be granted – resource busy
Explanation: A Task Lock for a particular row hash or row hash range for a particular subtable is locked by another task
and the requesting task does not want to wait for the resource.
Generated By: AwtTLGAl.
For Whom: Site support representative.
Notes: This is an internal condition that is handled internally. 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 2866 To 2875 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 *