Teradata SQL Error and Failure Codes from Error 8292 To 8501

SQLServerF1_Header_Small

8292 Change Journal row is outside restored partition ranges.
Explanation: The Change Journal rows are applied to the target table in which selected partitions were restored. All
Change Journal rows for the target table are applied 迪 that is changes that fall both inside and outside the selection partitions
range. The primary index is updated but the secondary index rows are not updated. The secondary indexes will be
inconsistent when change journal rows outside the selected partitions range are applied.
Generated By: Recovery using Permanent Journals (jnlrecvy)
For Whom: End User.
Remedy: Secondary indexes should be re-built when this message is returned.

8293 Restore stopped because the error table is defined with too many columns.
Explanation: The restore request for selected partitions of a PPI table was stopped because the number of columns in the
error table has exceeded the maximum internal DBS limit of 2560. The error table is defined with the following columns: –
all columns of the target table being restored. – DBCErrorCode – DBCOldROWID
Generated By: Host utility service routines (hutsvc)
For Whom: System Support Representative.
Remedy: The DBS provides for additional columns beyond the user column limitation for internal DBS use. This appears
to be an internal error. Save all relevant information and notify your support representative.

8294 Restore stopped because the error table row size exceeded the maximum allowed.
Explanation: The restore request for selected partitions of a PPI table was stopped because the error table row size has
exceeded the maximum internal DBS limit of 64768. Additional row space is allocated for the DBCErrorCode and DBCOld-
ROWID. The error table is defined with the following columns: – all columns of the target table being restored. – DBCError-
Code – DBCOldROWID
Generated By: Host utility service routines (hutsvc)
For Whom: System Support Representative.
Remedy: The DBS internals provides additional row space beyond the user row size limitation. This appears to be an
internal error. Save all relevant information and notify your support representative.

8295 Restore stopped because block optimization is disabled. Unable to rebuild secondary
indexes. Selected partition restore error table %DBID.%TVMID.
Explanation: Selected partition restore uses block optimization to restore NUSI and USI indexes. However this feature
has been disabled by the user.
Generated By: Hut build process for data tables.
For Whom: End User
Remedy: The user must use DROP INDEX followed by CREATE INDEX to rebuild the NUSI and USI indexes.

8296 Restore/Copy stopped because of inconsistent table header information.
Explanation: The field 4 of the error table and the associated restore target table are inconsistent. That is, when the target
table does not yet have field 4, the error table does not exist or it does exist but already has field 4. This is an internal error.
Generated By: Hut Restore Data Block step (hutrdb).
For Whom: Support Representative.
Remedy: Contact your Support Representative.

8297 Selected partition restore error table %DBID.%TVMID.
Explanation: Identifies the error table referenced by the DBS for the BUILD statement.
Generated By: Process BUILD for data tables (hutbldd).
For Whom: ARCMAIN.
Remedy: Informational.

8298 Build statement error: HUTBLDCLR2 received out of sequence.
Explanation: This indicates a protocol error between the ARCMAIN client and the DBS.
Generated By: Process BUILD for data tables (hutbldd).
For Whom: Support Representative.
Remedy: Contact your Support Representative.

8299 Out of segments for partitions.
Explanation: A request to add another dump partition to the partition segment failed because there are no more partition
segments.
Generated By: Hut Split table (hutstbl).
For Whom: Support Representative.
Remedy: This is an internal error. Contact your Support Representative.

8500 Object not found.
Explanation: A large object access routine has indicated that a requested object does not exist.
Generated By: lobOpen
For Whom: Site support representative.
Notes: This is a normal return code from lobOpen. If this code is reported in a system event, it means that it was unexpected
in the context in which it occurred and indicates an AMP software malfunction.
Remedy: Contact your System Representative.

8501 LOB end of data encountered.
Explanation: A large object access routine has indicated that the end of data was encountered.
Generated By: lobRead, lobSeek
For Whom: Site support representative.
Notes: This is a normal return code from the LOB access routines. If this code is reported in a system event, it means that
it was unexpected in the context in which it occurred and indicates an AMP software malfunction.
Remedy: Contact your System Representative.

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