Teradata SQL Error and Failure Codes from Error 5060 To 5069

5060 The CI read was not the one requested.
Explanation: The CI read did not have the expected internal extent id.
Generated By: File System
For Whom: Field Engineer
Notes: This indicates that the vconfig.out file was incorrectly edited or that the devices referenced in the vconfig.out file
have been incorrectly modified.
Remedy: Correct the vconfig.out file and/or the devices assigned to the VPROCS.

5061 The DBD and DB rowcounts do not match.
Explanation: The refcount in the DB does not match the row count in the DBD.
Generated By: File System
For Whom: Field Engineer
Notes: This indicates either a File System software error or a Hardware error has occurred.
Remedy: Contact a field engineer.

5062 The DBD and DB row-id ranges do not match.
Explanation: The first row-id or last row hash in the DB does not match the DBD.
Generated By: File System
For Whom: Field Engineer
Notes: This indicates either a File System software error or a Hardware error has occurred.
Remedy: Contact a field engineer.

5063 The SRD and DB tableid.typeandindex do not match.
Explanation: The table-id.tai in the DB does not match the SRD.
Generated By: File System
For Whom: Field Engineer
Notes: This indicates either a File System software error or a Hardware error has occurred.
Remedy: Contact a field engineer.

5064 The SRD and DB tableid.uniq do not match.
Explanation: The table-id.uniq in the DB does not match the SRD.
Generated By: File System
For Whom: Field Engineer
Notes: This indicates either a File System software error or a Hardware error has occurred.
Remedy: Contact a field engineer.

5065 The block cannot be modified in place.
Explanation: The block cannot be modified in place as there are insufficient or inappropriate free sectors on this cylinder.
Generated By: File System
For Whom: Field Engineer
Notes: This is used to transfer information between File System functions.
Remedy: Contact a field engineer.

5066 The CID and CI first row-id do not match.
Explanation: The first row-id in the CID does not match the first row-id in the first DBD of the CI.
Generated By: File System
For Whom: Field Engineer
Notes: This indicates either a File System software error or a Hardware error has occurred.
Remedy: Contact a field engineer.

5067 The CID and CI first tableid do not match.
Explanation: The first table-id in the CID does not match the first table-id in the first SRD of the CI.
Generated By: File System
For Whom: Field Engineer
Notes: This indicates either a File System software error or a Hardware error has occurred.
Remedy: Contact a field engineer.

5068 The CID and CI last hash code do not match.
Explanation: The last row hash in the CID does not match the last row hash in the last DBD of the CI.
Generated By: File System
For Whom: Field Engineer
Notes: This indicates either a File System software error or a Hardware error has occurred.
Remedy: Contact a field engineer.

5069 The CID and CI last table-id do not match.
Explanation: The last table-id in the CID does not match the last table-id in the last SRD of the CI.
Generated By: File System
For Whom: Field Engineer
Notes: This indicates either a File System software error or a Hardware error has occurred.
Remedy: Contact a field engineer.

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