Teradata SQL Error and Failure Codes from Error 2828 To 2837

SQLServerF1_Header_Small

2828 Request was rolled back during system recovery.
Explanation: The last request and its transaction was rolled back because it was in an active transaction during a Teradata
DBS restart.
Generated By: System Recovery.
For Whom: End User.
Notes: This error is sent in response to a host status request from the TDP after a Teradata DBS restart.
Remedy: Resubmit the transaction.

2829 Specified AMP does not exist.
Explanation: A processor number specified by the user in a specific-AMP(s) host utility operation does not correspond
to that of a currently configured AMP.
Generated By: Host Utilities.
For Whom: End User.
Remedy: Resubmit the request with the correct processor number.

2830 Unique secondary index must be dropped before restoring table.
Explanation: During a single-AMP restore of a nonfallback table, the table header on disk indicated the existence of a
unique secondary index.
Generated By: Host Utilities.
For Whom: End User.
Notes: Because a single-AMP restore should always be preceded by an all-AMPs restore with the single AMP down, and
because the unique secondary indexes on a nonfallback table are invalidated during such a restore, this error indicates a
user error. Either the index was added after the AMP came back up (modifications should never be made to the database
until the AMP is restored), the single-AMP restore was not preceded by an all-AMPs restore, or the single-AMP restore was
not preceded by an all-AMPs restore.
Remedy: The restore operation must be started over.

2831 No row was found for the event in the Recovery Control Catalog.
Explanation: The event number specified by the host utility was not found in the Recovery Control Catalog table.
Generated By: Host Utility steps
For Whom: Site support representative.
Notes: This is a logic error in the Host Utility.
Remedy: Contact your Support Representative.

2832 Unique secondary index violation on table %DBID.%TVMID during restore.
Explanation: During a restore operation, a duplicate unique secondary index was encountered.
Generated By: Host Utilities.
For Whom: End User.
Notes: This is the result of reapplying dump data sets in the incorrect sequence during a restore operation.
Remedy: Apply archive data sets in the correct sequence during restore.

2833 Row already exists with different content.
Explanation: During a restore operation, an attempt was made to restore a row that already existed, but whose data was
different from that of the one being restored.
Generated By: Host utilities.
For Whom: End User.
Notes: This is probably caused by applying single-AMP dump tapes of the same data, but made at a different time.
Remedy: Use the correct sequence of archive data sets during the restore.

2834 Another user released the lock requested by the current operation.
Explanation: While the current operation was waiting for a host utility lock, another user released all host utility locks
on the specified object via the “override” option. The current operation was aborted.
Generated By: Host Utilities.
For Whom: End User.
Notes: This error is not returned to the user if the lock has already been granted when another user releases it. No error is
returned in this case.
Remedy: Resubmit the host utility operation.

2835 A unique index has been invalidated; resubmit request.
Explanation: Unique secondary index for retrieval has been invalidated by a restore operation.
Generated By: AMP Steps.
For Whom: End User.
Remedy: Resubmit the request.

2836 The specified index id was not found.
Explanation: The specified index id was not found in the table header.
Generated By: AwtLocID.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2837 Table being Fast/Multi Loaded; no data dumped.
Explanation: The table being dumped is in the process of being Fast/Mutli Loaded. 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: If the data in the table must be backed up, complete the Fast Load and dump the database again.

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