Teradata SQL Error and Failure Codes from Error 2847 To 2856

2847 Internal error: Invalid record found on transient journal.
Explanation: An invalid record was found on the transient journal. This error is logged just prior to a crash due to error
ErrAMPIllTJRec.
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.

2848 Invalid record type on transient journal.
Explanation: An invalid journal kind was specified or found on a journal. This error is logged just prior to a crash due to
error ErrAMPInvJnlKind.
Generated By: AwtRcv.
For Whom: Site support representative.
Notes: This is an internal error. Transaction recovery detected an inconsistency on the transient journal, and recovery will
continue to abort. To restart the system, shut down the offending processor and rebuild its disk off-line.
Remedy: Contact your Support Representative.

2849 Invalid before image on transient journal.
Explanation: The row that a before journal has written does not exist in the database. This error is logged just prior to a
crash due to error ErrAMPInvBefRow.
Generated By: AwtRcv.
For Whom: Site support representative.
Notes: This is an internal error. Transaction recovery detected an inconsistency on the transient journal Rebuild the
offending processor’s disk.
Remedy: Contact your Support Representative.

2850 User %USERID Session #### logical host id #### caused a DBS crash
Explanation: This message identifies the Teradata DBS user, the associated session and logical host id which caused a
Teradata DBS crash. This message is displayed during Teradata DBS Startup.
Generated By: SSSMain.
For Whom: Operator.
Remedy: This message is for information only.

2851 Internal error: inconsistent record found on Transient journal
Explanation: An attempt was made to read a PJ record using the rowid and tableid found from the TJ but the PJ row
does not contain the ’correct’ information (i.e., transno and/or PJ RowKind is neither CkPtBeg or CkPtEnd).
Generated By: StpAAB.
For Whom: Site support representative.
Notes: This is an internal error.
Remedy: Contact your Support Representative.

2852 Inconsistent check point records found on Restored journal.
Explanation: While restoring/validating a journal table, the event number for the same check point among different
AMPs were found to disagree with each other.
Generated By: Restore, StpVJT.
For Whom: Site support representative.
Notes: This is an internal error.
Remedy: Contact your Support Representative.

2853 Restored Journal table %TVMID does not exist.
Explanation: A restored journal table might not exist on an AMP if it came back online following a Teradata DBS crash
during a rollback/rollforward operation.
Generated By: StpVJT.
For Whom: End User.
Remedy: Do a specific AMP restore of the journal table and then resubmit the rollback or rollforward request.

2854 Specified checkpoint row does not exist in Journal table %TVMID.
Explanation: The checkpoint at which the recovery will terminate does not exist in the specified journal table during a
rollback/rollforward operation.
Generated By: StpVJT.
For Whom: End User.
Remedy: Correct the checkpoint name in the rollback or rollforward statement and then resubmit the request.

2855 Specified checkpoint row already exists.
Explanation: This could occur because of a Teradata DBS restart during a checkpoint operation.
Generated By: StpVJT.
For Whom: Host Utilities.
Notes: This error code is designed to be intercepted by a host utility and should never be seen by the end user.
Remedy: None required. The utility will handle the condition without user intervention.

2856 The journal table %TVMID is being restored.
Explanation: This error occurs when a user issues a request for a journal table that is being restored.
Generated By: StpVJT.
For Whom: End User.
Remedy: Wait until the restore operation is completed, then resubmit the request. If a restore is not in process, the operation
may have been aborted, and needs to be restarted or started over, or the table must be dropped.

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