Teradata SQL Error and Failure Codes from Error 2915 To 2924

SQLServerF1_Header_Small

2915 The journal for the updated table does not exist
Explanation: An update operation was specified against a data table which references a permanent journal table that
does not exist.
Generated By: AtcLgIni.
For Whom: User.
Remedy: The Database containing the journal table was probably restored, but the journal itself was not.

2916 Restore of a permanent journal was not complete.
Explanation: The journal table specified to be used in a rollback or rollforward had not been completely restored.
Generated By: HutRecvy.
For Whom: User.
Notes: The database containing the journal table was probably restored, but the journal itself was not, or a table header is
missing for the journal on some AMP.
Remedy: If the problem is due to restore then complete the restore of the journal table. If it is due to a missing table
header then the journal table must be rebuilt using table rebuild.

2917 Permanent Journal %DBID.%TVMID has a bad header.
Explanation: The specified table is supposed to be a journal table yet there is no field 4 in the tables header.
Generated By: HutRecvy.
For Whom: Site support representative.
Remedy: This is an internal error caused by software.

2918 Permanent Journal is invalid
Explanation: A request which caused a permanent journal image to be created or read did so upon a permanent journal
table which has been corrupted.
Generated By: AtclgIni, AtcBlTbl, StpVJT.
For Whom: User.
Remedy: The probable cause was a system failure during a table rebuild of the specified journal table. The rebuild operation
must be completed before the journal is usable.

2919 Requested table is not a journal table.
Explanation: An operation that requires a permanent journal table was given a non journal table id.
Generated By: JnlDlRst.
For Whom: Site support representative.
Remedy: This is an internal error. This should NOT happen. The only known use of this currently is a Delete Restored
Journal operation.

2920 Delete journal and AMP down without dual.
Explanation: A Delete Permanent Journal operation on a saved subtable was issued upon a journal while an AMP was
down and the journal has one or more no fallback data tables utilizing it without the dual option.
Generated By: StpDJT.
For Whom: End User.
Remedy: The operation may only be performed while all AMPs are available under these circumstances.

2921 No saved subtable for journal %DBID.%TVMID.
Explanation: A Delete Permanent Journal operation on the saved subtable was issued upon a journal which currently
does not have a saved subtable.
Generated By: StpDJT.
For Whom: End User.
Remedy: To perform this operation requires a preceding Checkpoint with the Save option.

2922 AMP does not have a restored journal table.
Explanation: An AMP has returned to service between the time a journal table was restored and a rollback or rollforward
was started. The AMP does not have the restored journal.
Generated By: HutRecvy.
For Whom: End User.
Remedy: Do a specific AMP restore of the journal table and then resubmit the rollback or rollforward request.

2923 Missing checkpoint begin row.
Explanation: A checkpoint end row was found in a permanent journal which was not preceded by an associated checkpoint
begin.
Generated By: JnlLogRd.
For Whom: Site support representative.
Remedy: This indicates a corrupted permanent journal during down AMP recovery or journal rebuild. This error should
not occur following the integration/test phase of permanent journaling. Delete and/or restore the offending permanent
journal.

2924 Checkpoint end row missing.
Explanation: A checkpoint begin row was found in the current permanent journal and physical end of file was reached
without finding an associated checkpoint end row.
Generated By: JnlLogRd.
For Whom: Site support representative.
Remedy: Delete and/or restore the permanent journal.

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