Teradata SQL Error and Failure Codes from Error 2925 To 2935

SQLServerF1_Header_Small

2925 Permanent journal modified during read.
Explanation: During the rebuild or down AMP recovery of a permanent journal, the journal has been changed. Since the
journal should be locked out from any changes, this error should not occur after the permanent journaling integration/testing
phase.
Generated By: JnlLogRd.
For Whom: Operator/FE.
Remedy: Restart the rebuild/recovery operation, making sure no other task will be modifying the journal. Contact the
NSC.

2926 No more room in journal table for %DBID.%TVMID.
Explanation: This error occurs only when an update to a data table causes the indicated permanent journal table to
exceed its allocated space.
Generated By: AMP Step Processing Software.
For Whom: End User.
Remedy: Dump the permanent journal table and delete the saved subtable, or increase the space allocated to the database.

2927 The permanent journal cache buffer is out of space
Explanation: A request to initialize the journal cache control entry was submitted but space could not be found in the
cache control buffer.
Generated By: Permanent Journal Procedure JnlBufIn.
For Whom: Customer Engineer.
Remedy: This is an internal error. Contact your Support Representative.

2928 The backup processor for a permanent journal is down
Explanation: A request to initialize journaling was issued for a dual journal requiring a backup processor that was not
available.
Generated By: Permanent Journal Procedure JnlBufIn.
For Whom: User.
Remedy: The requested operation may proceed once the backup processor is restored to online activity.

2929 The journal to suspend is active
Explanation: A request to suspend permanent journaling, probably during journal table rebuild, was requested while
the journal was active.
Generated By: Journal Control Cache Management. (AtcSusp)
For Whom: Customer Engineer.
Remedy: This is an internal error. Contact your Support Representative.

2930 Last session request caused the DBS to crash.
Explanation: The last request submitted by the session encountered an error which caused the Teradata DBS to crash.
Resubmitting the request will probably cause another system crash.
Generated By: System Recovery.
For Whom: User.
Remedy: The crash is caused by a Teradata DBS error. Contact your Support Representative.

2931 Table has failed the structure check.
Explanation: The table has failed a check of its header and row structures.
Generated By: UtaCtSvc.
For Whom: Customer Engineer.
Remedy: This is an internal error. Contact your Support Representative.

2932 No database defined with the name input.
Explanation: The database referenced by a utility function does not exist.
Generated By: UtaDBID.
For Whom: Customer Engineer.
Remedy: This is an internal error, and should be converted to a text string by the output. Contact your Support Representative.

2933 No table defined for input table name.
Explanation: The table referenced by a utility function does not exist.
Generated By: UtaTID.
For Whom: Customer Engineer.
Remedy: This is an internal error, and should be converted to a text string by the output. Contact your Support Representative.

2934 Input is in new row format — expected old format.
Explanation: The row input to an express request was in Release 2.0 format. The procedure expected the format to be in
pre-Release 2.0 format.
Generated By: Several.
For Whom: Customer Engineer.
Remedy: This is an internal error. Contact your Support Representative.

2935 Table header format is invalid
Explanation: An attempt to locate information in a table header was not successful.
Generated By: Several.
For Whom: Customer Engineer.
Remedy: Contact your Support Representative.

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