Teradata SQL Error and Failure Codes from Error 2838 To 2846

SQLServerF1_Header_Small

2838 Table is unhashed; no data dumped.
Explanation: The table being dumped is unhashed. 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. Crash dumps that did not originate from a DUL load
are the only tables that fall in this class.
Remedy: If it is necessary to save the data in the crash dump table, use the DUL utility.

2839 Invalid attempt to operate on a fallback table.
Explanation: An attempt was made to restore a fallback table during an operation other than an all-AMPs restore of an
all-AMPs dump.
Generated By: Restore.
For Whom: End User. Site support representative.
Notes: This error may indicate that (a) a user was attempting to add fallback during the restore attempt (which is not
valid), or (b) there is an internal error in the Archive Utility software.
Remedy: If a concurrent attempt to add fallback is not the problem, identify the tables in the database that are nonfallback,
and restore them via individual restore statements. If this fails, Contact your Support Representative.

2840 Data rows discarded due to inconsistent hash codes
Explanation: During a restore operation, some rows were discarded because of inconsistencies in the row hash codes.
Generated By: Restore.
For Whom: End User. Site support representative.
Notes: Two situations cause this error to occur:
1) During an attempt to restore a row, a row with the same rowid but different data was found on the disk.
2) During a specific-AMP restore, the AMP received a data block containing a row that it does not own, even though reconfiguration
has not taken place since the dump.
The situation may be caused either by a software bug (the rows were mis-distributed when the dump was taken) or a user
error (updating the table before the table was completely restored).
In either case, the restore continues unaffected, except that the offending rows are discarded. Associated with this error is a
count of the rows discarded.
Remedy: If the error is caused by an operational error, start the restore process over or accept an incomplete table.
If there were no operational errors, contact your Support Representative.

2841 A Utility lock was reapplied by recovery.
Explanation: During recovery, a Utility lock was reapplied. The text that accompanies this message describes the lock
that was placed: either a single-AMP Host Utility lock or a lock placed by table rebuild. After Restore/Rebuild, you must
EXPLICITLY use HUT/ARC to Release Locks.
Generated By: Recovery.
For Whom: Operator.
Remedy: If necessary, dump or restore the affected database or rebuild the affected table. Release the lock when no longer
needed.

2842 A utility lock was not reapplied by recovery due to conflict.
Explanation: During recovery, a Utility lock was not reapplied because of a conflict with some other utility lock. The text
associated with this message describes the lock that was not reapplied.
Generated By: Recovery.
For Whom: Operator.
Notes: Normally, this error is caused by a global deadlock brought on when two operations attempt to place utility locks
at the same time.
Remedy: If the error is due to a deadlock, release the locks and restart the conflicting operations.

2843 No more room in database.
Explanation: This error occurs only when an attempt is made to increase the amount of space used by a database, and
there is no space left to accommodate the increase.
Generated By: Archive Utility.
For Whom: End User.
Remedy: Either drop some of the tables currently contained in the database, or have the permanent space limit for the
database increased.

2844 Journal image is longer than maximum.
Explanation: This error occurs when a journal record is generated for an update, delete, or insert operation that is larger
than the maximum allowable journal record.
Generated By: AMP Steps.
For Whom: End User.
Remedy: Reduce the number of fields being updated (if the error occurs on an update operation); reduce the size of the
data rows being deleted by update operations against compressed or variable-length fields; or reduce the level of archive
journaling on the table.

2845 Shut down DBS and rebuild the entire disk.
Explanation: A disk read error was encountered. The bad data block cannot be rebuilt with the processor on-line. This
error is logged prior to a crash due to error ErrAMPDBErrSDown.
Generated By: RbkCtrl.
For Whom: Operator. DBA.
Remedy: Use Diskcopy and Table Rebuild to recover the disk and then restart the Teradata DBS.

2846 Unrecoverable read error detected. Retry.
Explanation: A disk read error is encountered. The bad data block cannot be rebuilt with the Teradata DBS on-line. This
error is logged prior to a crash due to error ErrAMPURcvReadErr.
Generated By: RbkCtrl.
For Whom: Operator. DBA.
Remedy: Manual intervention (table rebuild) or a restart may fix the problem.

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