Teradata SQL Error and Failure Codes from Error 5159 To 5167

5159 System test forced tpareset
Explanation: Identifies the system test forced tpareset.
Generated By: File System
For Whom: System Test Engineer
Notes: This indicates a error injected during in-house system test.
Remedy: Contact a System Test engineer.

5160 Module %s at insertion point %d
Explanation: Identifies the system test forced tpareset.
Generated By: File System
For Whom: System Test Engineer
Notes: This is a second level error providing additional information.
Remedy: Contact a System Test engineer.

5161 Heap space could not be allocated from the Sync Scan segment.
Explanation: A request to allocate heap space from the sync scan segment failed. Either the number of current scans
exceeds the maximum segment size or the segment is corrupted.
Generated By: File System
For Whom: Site support personnel.
Notes: This indicates a file system software error or a hardware error.
Remedy: Contact the Global Support Center.

5162 Illegal SyncScanCheckInterval of %d in DBS Control GDO. Default of %d used.
Explanation: A bad value was found in the AMP’s copy of the DBS Control GDO, so the system default for the value is
used instead.
Generated By: File System
For Whom: Site support personnel.
Notes: This indicates a software error in the DBSControl utility or a hardware error.
Remedy: Contact the Global Support Center.5163 Illegal SyncScanCacheThr of %d in DBS Control GDO. Default of %d used.

5163 Illegal SyncScanCacheThr of %d in DBS Control GDO. Default of %d used.
Explanation: A bad value was found in the AMP’s copy of the DBS Control GDO, so the system default for the value is
used instead.
Generated By: File System
For Whom: Site support personnel.
Notes: This indicates a software error in the DBSControl utility or a hardware error.
Remedy: Contact the Global Support Center.

5164 Expected sync scan table entry not found for table ID %u %u %u.
Explanation: When attempting to remove a task’s scan from the global sync scan segment, the associated table entry was
not found.
Generated By: File System
For Whom: Site support personnel.
Notes: This indicates a file system software error or a hardware error.
Remedy: Contact the Global Support Center.

5165 Expected sync scan task entry not found for table ID %u %u %u.
Explanation: When attempting to remove a task’s scan from the global sync scan segment, the task entry was not found
on the task chain associated with the correct table entry.
Generated By: File System
For Whom: Site support personnel.
Notes: This indicates a file system software error or a hardware error.
Remedy: Contact the Global Support Center.

5166 Defragment of cylinder[s] occurred.
Explanation: A request to defragment a cylinder ocurred as a result of a user initiated FERRET Defragment command or
the system could not allocate a set of contiguous sectors from the cylinder and the total free cylynders was less than the
DefragLowCylProd.
Generated By: File System
For Whom: End User
Remedy: Delete or offload unused data, rebalance data by changing the primary key or purchase additional hardware.

5167 An invalid pointer has been detected.
Explanation: An invalid pointer was detected.
Generated By: File System
For Whom: Field Engineer
Notes: This indicates a File System software error.
Remedy: Contact a field engineer.

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