Teradata SQL Error and Failure Codes from Error 2876 To 2883

2876 AMP was not brought online.
Explanation: An AMP could not be brought into deferred catchup so it was put into offline recovery instead. There are
several reasons why the system choose to do this, the text which follows the message should describe the factors that governed
this decision.
Generated By: RcvSLUCM.
For Whom: SE/FE.
Notes: This message is logged during a restart for each processor in offline recovery. This is to help the user understand
why the AMP was not brought into the configuration.
An AMP in offline recovery is not part of the DBS configuration, ie. it is logically down.
An AMP in deferred recovery is part of the DBS configuration.
An AMP is placed into deferred catchup for any of the following reasons:
1) The AMP has not completed local transaction rollback. This means that the AMP has not rolled back/completed all work
that was in progress when it went down. It must also complete any deferred recovery sessions contained on it at the time it
went down.
2) The number of change row journal entries summed across all AMPs in the cluster exceed some threshold. This means
that the number of rows requiring updating is too great.
3) At least one long running ordered systems change journal entry needs to be processed. Long running records include
saving a dump, rebuilding a table or PJ, etc..
4) A HUT lock may exist in the cluster. This means either that a HUT lock is currently held in the cluster and/or a ordered
systems change journal set HUT lock record remains to be processed.
Remedy: Allow offline recovery to catch the AMP up to a point where the deferred catchup rules are met and then restart
the system to place the AMP into deferred catchup. In the case of rule #4, you may need to release the HUT lock manually.
The RCVMANAGER console startable utility can tell when the rules have been meet. The RESTART,COLDWAIT option
can be used to guarantee that the AMP is brought online.

2877 Table Rebuild procedures required to recover AMP.
Explanation: A disk read error was encountered while executing a recovery function. The bad data block cannot be
rebuilt with the processor on-line. The AMP which detects the error will remain offline. This error is logged prior to a crash
due to error ErrAMPRCErrSdown.
Generated By: RbkCtrl.
For Whom: Operator. DBA.
Remedy: Run Table Rebuild to recover the failing table and then restart the Teradata DBS.

2878 Improper character set name %VSTR.
Explanation: This error occurs at the time when character sets are first installed as the DBS starts. The name coding convention
has been improperly used.
Generated By: AMP.
For Whom: Operator. DBA.
Remedy: Correct the character set name in error to the proper convention. Reinstall the character set tables with the correct
name. Restart the DBS software.

2879 Cannot install Charset. DBS is not Kanji-enabled.
Explanation: The Hash Function value in the DBSControl Record does not allow installation of this character set. This
applies to Kanji character sets when the Hash Function does not indicate Japanese Localization.
Generated By: AMP.
For Whom: Operator. DBA.
Remedy: Go through Sysinit procedure to change Hash Function value.

2880 Reference index row indexes non existent data row.
Explanation: The Foreign Key value contained in the reference index row was found in the corresponding primary data
subtable. However, the reference index row indicates that there should be N data rows with that Foreign Key value but we
only found M data rows where M < N.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2881 Foreign Key value is not found in any reference index row.
Explanation: The Foreign Key value in the primary data subtable was not found in the corresponding reference index
subtable.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2882 Data row is not indexed by reference index row.
Explanation: The Foreign Key value contained in the primary data subtable was found in the corresponding reference
index subtable. However, the reference index row indicates that there should be N data rows with that Foreign Key value
but we found M data rows where N < M.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2883 Fallback reference index row is missing.
Explanation: The reference index subtable is fallback. However, there is a primary reference index row which has no corresponding
fallback reference index row.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

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