Teradata SQL Error and Failure Codes from Error 8215 To 8224

SQLServerF1_Header_Small

8215 ROLLBACK recovery stopped.
Explanation: The Rollback recovery was stopped because the table version number did not match the value recorded in
the journal row images.
Generated By: Host Utilities.
For Whom: End User.
Remedy: If the table version number is different then this indicates a DDL change was applied to the table that is not
reflected in the journal. When applying a DDL change to a table which has journaling, prior journal images may not be
applied to that table unless the earlier version is restored. When the earlier version is restored, the rollback will process all
rows in the journal up to the DDL change. The rollback will cease at that point.

8216 Recovery action stopped.
Explanation: The rollforward/rollback recovery was stopped because the table indicates it is either being fastloaded,
multiloaded, restored, or rebuilt.
Generated By: Host Utilities.
For Whom: End User.
Remedy: If the table is being fastloaded, multiload, or restored, then complete the fastload, multiload or restore the table
and then roll the table.
If the table had recovery aborted or is in the table rebuild state, restore the table and then roll it.

8217 Maximum number of tables exceeded.
Explanation: Number of tables being rolledforward/back exceeds the maximum number of tables allowed (Maximum
number of tables is 3000).
Generated By: Host Utilities.
For Whom: End User.
Remedy: Resubmit the job with less than the maximum number tables.

8218 Data table %DBID.%TVMID does not use the specified journal table.
Explanation: The data table specified does not use the journal table getting copied.
Generated By: Host Utilities.
For Whom: End User.
Remedy: Resubmit the job after correcting list of tables in the APPLY TO list.

8219 Data table %DBID.%TVMID was not copied
Explanation: The specified data table was not copied and therefore may not be the subject of an APPLY TO list.
Generated By: Host Utilities.
For Whom: End User.
Remedy: Resubmit the job with correct list of data tables in the APPLY TO list.

8220 An APPLY TO data table was not found.
Explanation: A table from the DBCAssociation table did not match the tables input by the user.
Generated By: Procedure STPAlt.
For Whom: Support Representative/System Administrator.
Remedy: This error should be documented and reported to your Support Representative.

8221 Roll stopped. Copied table version mis-match
Explanation: The Rollforward/Rollback operation was stopped on the specified table because the version of the table
when copied does not match its current version.
Generated By: Host Utilities.
For Whom: End User.
Remedy: If the table version number is different than what it was when copied, then a DDL operation was applied to the
table after it was copied. Because of this, the copied journal images applied to that table may not be used for rollforward or
rollback. In order to port DDL changes upon the table, it must be recopied. Applying the DDL change to the original and
copied version of the tables is not sufficient.

8222 Roll stopped. Data table not copied
Explanation: The Rollforward/Rollback operation was stopped because the data table being rolled is either doesn’t exist
or not a copied data table, but the journal table containing the images was copied.
Generated By: Host Utilities.
For Whom: End User.
Remedy: In order to Rollforward/Rollback the copied journal images, the data table also must be copied.

8223 Table header is not for a Permanent Journal.
Explanation: The Archive Software will verify internal identifiers before restoring dictionary rows during a COPY or
RESTORE operation. In this case, an identifier for a permanent journal table in one of the dictionary rows was found to
have a table header on disk but the table header indicated it was NOT really a permanent journal table. Mostly likely cause
of this error is either an internal inconsistency or a possible security violation attempt where the row was corrupted on the
ARCHIVE tape.
Generated By: Host Utilities.
For Whom: End User.
Remedy: Verify first that you are following the proper Archive and Recovery procedures, that you are using the proper
ARCHIVE data set for the operation that has not been tampered with, and that you are running compatible versions of
Host and DBS software. If the problem persists, it should be documented and reported to your Support Representative.

8224 Build action stopped.
Explanation: The Build action was stopped because the table indicates it is either being fastloaded, multiloaded or
rebuilt.
Generated By: Host Utilities.
For Whom: End User.
Remedy: Complete the fastload, multiload or rebuild of the table. Build only applies to tables that were restored

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