Teradata SQL Error and Failure Codes from Error 2818 To 2827

2818 Invalid lock to dump table without after image journaling
Explanation: If the table to be dumped does not have after- image journaling, the USE GROUP READ LOCK option in
the DUMP statement cannot be used.
Generated By: Dump.
For Whom: End User.
Remedy: (1) Switch to USE READ LOCK option when dumping a table without after-image journaling, or
(2) ALTER TABLE for after-image journaling before dumping with USE GROUP READ LOCK option.

2819 Internal error: unimplemented message received.
Explanation: A message was received that requested an unimplemented or unknown function.
Generated By: AMP worker tasks.
For Whom: Site support representative.
Notes: This is probably caused by a bad “Kind” or “Class” field in the message header.
Remedy: Contact your Support Representative.

2820 Fallback reference index row is on the wrong AMP.
Explanation: Incorrectly distributed reference index rows are detected as the reference index subtables are traversed.
The row is discarded from the remainder of the checking process.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2821 Internal error: invalid message kind in message header.
Explanation: A message with an unexpected “Kind” value in the message header was received.
Generated By: AMP worker tasks.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2822 Internal error: invalid message class in message header.
Explanation: A message with an unexpected “Class” value in the message header was received.
Generated By: AMP worker tasks.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2823 Table id is inconsistent during restore operation.
Explanation: During a restore operation, a table id found on the archive data set was found to be inconsistent with other
data on the archive or on the Teradata DBS being restored.
Generated By: Host Utilities.
For Whom: End User. Site support representative.
Notes: This indicates a problem with the dump tape, or an attempt to restore a database from one system to another system.
Remedy: Follow rules for restore operations or, if the rules have been followed, contact your Support Representative.

2824 Database id is inconsistent during restore
Explanation: During a restore operation, a database id found on the archive data set was found to be inconsistent with
other data on the archive or on the Teradata DBS being restored.
Generated By: Host Utilities.
For Whom: End User. Site support representative.
Notes: This indicates a problem with the dump tape, or an attempt to restore a database from one system to another system.
Remedy: Follow rules for restore operations or, if the rules have been followed, contact your Support Representative.

2825 NO RECORD OF THE LAST REQUEST WAS FOUND AFTER DBC RESTART
Explanation: No record of the last request sent was found on the Teradata DBS after restart. The request may or may not
have been rolled back. The user must determine if the request completed or not.
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 last request if it did not complete.

2826 Request completed but all output was lost due to DBC restart.
Explanation: The user’s last request completed, but all the output from the request was lost because the Teradata DBS
restarted.
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: No action needed.

2827 Request was aborted by user or due to statement error.
Explanation: The last request and the transaction it was in was rolled back by a user abort or because of an error during
processing of the statement. The cause of the rollback, however, has been lost because of 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: If the rollback was not due to a user abort, correct the statement and resubmit the transaction.

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