Teradata SQL Error and Failure Codes from Error 2809 To 2817


2809 Invalid recovery sequence detected
Explanation: An illegal sequence of recovery actions has been detected. This could be a cluster Restore of a fallback table
that was not preceded by a dictionary restore or a specific-AMP restore operation during a Fast Load or MLoad.
Generated By: AMP Software.
For Whom: End User.
Notes: All cluster restores of fallback tables must be preceded by a dictionary restore. This situation may arise in doing a
specific-AMP restore of a no fallback table after CREATE/ DROP INDEX, a Fast Load, or an MLoad.
Remedy: To restore a fallback table to AMP clusters, you must first perform a dictionary restore of the table from a dictionary
dump. If the problem is CREATE/DROP INDEX, perform an all-AMPs restore followed by a specific-AMPs restore
of the no fallback table. Then do the CREATE/DROP INDEX. If the problem is Fast Load or MLoad, the operation must finish
prior to issuing the recovery operation, or all-AMPs must be restored first.

2810 Internal error: permanent journal error found.
Explanation: An unexpected reference to permanent journals was found.
Generated By: AMP Software.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2811 Data rowid is already indexed.
Explanation: During an insert of a rowid into an index, the row id was found to exist already in the index.
Generated By: AMP Worker Tasks.
For Whom: Site support representative.
Notes: This error is a status result returned by the secondary index service routines. The caller of these routines may
either ignore the error if it is expected or log an event if it was not expected.
Remedy: If this event was logged, contact your Support Representative.

2812 Internal error: invalid record found on transient journal.
Explanation: An invalid record was found on the transient journal. The AMP which detects the error will remain offline.
Generated By: AMP System and Transaction Recovery.
For Whom: Site support representative.
Notes: This error usually results from an incorrect “Kind” field in the transient journal record header.
Remedy: Contact your Support Representative.

2813 Internal error: bad InXaction flag in step header.
Explanation: The value of the InXaction flag in the step header was False (True) in a step that must be (must not be) in a
Generated By: AMP Steps.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2814 Data size exceeds the maximum specified.
Explanation: This status indicator is returned when the host side of host utilities specifies that it will accept n bytes of
data and the AMP finds that there are more than n bytes to send.
Generated By: Host Utilities.
For Whom: Programmers.
Notes: This should never be seen by an end user or in a crash situation.
Remedy: Supply a larger max byte count and resend the parcel.

2815 Apparent invalid restart of a restore.
Explanation: This error is returned when restarting a restore. It indicates that either the table was rebuilt by table
rebuild, or was subject to a BUILD statement prior to the restore restart. This could cause data loss in the failed table.
Generated By: Host Utilities.
For Whom: End User.
Notes: This is a user error. An invalid sequence of restore operations was attempted, probably an invalid restart of a
restore from the host.
Remedy: Use correct sequence of restores.

2816 Auto CHECKTABLE mode found errors.
Explanation: This error indicates that CHECKTABLE encountered at least one error while validating the ALL TABLES.
Generated By: DBS Auto CHECKTABLE mode.
For Whom: SE/FE.
Notes: Auto CHECKTABLE mode is enable/disabled by the RcvACUTL console startable utility.
When enabled, CHECKTABLE is automatically run on all tables immediately after startup has set up for transaction recovery
(ie. voted and placed all required locks).
To find out exactly which tables had errors, the auto CHECKTABLE mode should be disabled, the system should be
restarted and CHECKTABLE should be run manually. Alternatively, if the debugger is running, a GO AFTERTRAP will
allow the system to continue and then a manual CHECKTABLE can be run.
If the debugger is not running then this error does not cause the system to crash. The trace back is printed on the console
but operation continues.
Remedy: See notes

2817 Internal error: transaction not found in TIP table.
Explanation: A supposedly active transaction was not found in the Transaction In Process table on the AMP.
Generated By: AMP Steps.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

Above are list of Teradata Errors or Failure Codes from Error 2809 To 2817 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.

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 *