Teradata SQL Error and Failure Codes from Error 8283 To 8291

8283 Restore of selected partitions of a PPI table stopped because PPI information in the table
header is inconsistent between the backup and disk.
Explanation: The restore request for selected partitions of a PPI table was stopped because there is a mismatch in one or
more components in field 5 of the table header on the backup and the table header on disk. The components checked for
consistency are: – Version – Platformtype – offsetofevlcode – lengthofevlcode
Generated By: Restore data block (hutrdb)
For Whom: End User
Remedy: Corrective actions include: – Verify that the correct restore was specified. – Verify that a table backup was performed
successfully following significant DDL changes. – Run checktable utility at level 3 to identify possible table corruption.

8284 Restore restart stopped because there is mismatch in selected partitions.
Explanation: The table is in the process of being restored because a field 4 exists in the table header. However, the
selected partitions to be restored in field 4 does not match the selected partitions in the HUT control segment.
Generated By: Restore data block (hutrdb)
For Whom: End User, Customer Engineer
Remedy: Corrective actions include: – Verify that the correct restore was specified. – If a restore was submitted previously,
verify that it completed successfully. – Contact your Support Representative.

8285 Restore restart stopped because there is an error table mismatch.
Explanation: The table is in the process of being restored because a field 4 exists in the table header. However, the error
table listed in the field 4 of the table header does not match the error table in the HUT control segment.
Generated By: Restore data block (hutrdb)
For Whom: End User
Remedy: Corrective actions include: – Verify that the correct restore was specified. – If a restore was submitted previously,
verify that it completed successfully.

8286 Restore restart stopped because the error table was not found.
Explanation: The restore is being restarted because the table header contains a field 4. However the error table was not
found.
Generated By: Restore data block (hutrdb)
For Whom: End User
Remedy: Corrective actions include: – Determine if the error table was dropped unintentionally. – Verify that the correct
restore was specified. – If a restore was submitted previously, verify that it completed successfully.

8287 For a restore restart, the error table’s table header field 4 is inconsistent with expected restart
values.
Explanation: The restore is being restarted because the target table header contains a field 4. However validation of the
associated error table’s table header field 4 indicates it is inconsistent with a selected partitions restore for one or more of
the following: – no field 4. – the field 4 does not indicate that this for a selected partitions restore. – the field 4 does not reference
the targeted restore table.
Generated By: Restore data block (hutrdb)
For Whom: End User, Customer Engineer
Remedy: Corrective actions include: – Verify that the correct restore was specified. – If a restore was submitted previously,
verify that it completed successfully. – Filer may be used to display the table header for the error table. – Contact your
Support Representative.

8288 The row uniqueness of a restored rowid was recalculated to a new value.
Explanation: The rowid s row uniqueness value of a restored row was recalculated because it collides with an existing
row in the table. WARNING: PERMANENT JOURNAL CHANGE IMAGES CREATED BEFORE THE RESTORE MUST
NOT BE USED FOR ROLLFORWARD OR ROLLBACK OPERATIONS FOLLOWING A RESTORE IN WHICH A ROWID S
ROW UNIQUENESS VALUE IS RECALCULATED. USE OF THESE IMAGES WILL RESULT IN DATA INTEGRITY PROBLEMS.
Generated By: Restore data block (hutrdb)
For Whom: End User
Remedy: Informative.

8289 ROLLFORWARD recovery stopped.
Explanation: The rollforward recovery was stopped because the PRIMARY DATA option and/or USE RESTORED
JOURNAL option was not specified for a ROLLFORWARD associated with a restore of selected partitions.
Generated By: HUT Rollforward (hutrecvy)
For Whom: End User
Remedy: Re-submit the request with PRIMARY DATA and USE RESTORED JOURNAL options.

8290 ROLLBACK recovery stopped.
Explanation: The rollback recovery was stopped because the PRIMARY DATA option and/or USE RESTORED JOURNAL
option was not specified for a ROLLBACK associated with a restore of selected partitions.
Generated By: HUT Rollback (hutrecvy)
For Whom: End User
Remedy: Re-submit the request with PRIMARY DATA and USE RESTORED JOURNAL options.

8291 The PRIMARY DATA flag is not set.
Explanation: The PRIMARY DATA flag must be set when change journal rows are applied and the target table indicates
PPI selected partitions. This is a DBS internal error.
Generated By: Recovery using Permanent Journals (jnlrecvy)
For Whom: Customer Engineer.
Remedy: Contact your Support Representative.

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