Teradata SQL Error and Failure Codes from Error 1063 to 1072

SQLServerF1

1063 A duplicate job id is found. The job id is %VSTR.
Explanation: A duplicate job id is detected. It is a potential DSC issue.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Wait for the first job to finish and then resubmit the job.

1064 No partitions available for job execution id = %VSTR.
Explanation: No partitions available for running job.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Should wait until some jobs are done so the partition is available.

1065 Time out: job execution id and bucket are %VSTR.
Explanation: Timeout period of 10 minutes is over.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Contact the field engineer.

1066 Cannot exclude Index during a restore. The Index name is %VSTR.
Explanation: Cannot exclude index during a restore.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Remove the index name(s) and resubmit the job.

1067 Internal DSM Storage pool calculation error.
Explanation: The byte count to be substraced from the internal DSM storage pool may be too big.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Contact the field engineer.

1068 Internal DSM Storage spool list is empty.
Explanation: Potential internal programming error.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Contact the field engineer.

1069 Invalid element count in the internal DSM storage list.
Explanation: The element count in the internal DSM storage list is zero.
Generated By: BAR.
For Whom: End user.
Notes: Potential internal programming error.
Remedy: Contact the field engineer.

1070 Invalid message class received; received and expected classes are %VSTR.
Explanation: Received invalid message class.
Generated By: BAR.
For Whom: End user.
Notes: This can be caused by internal programming error.
Remedy: Contact the field engineer.

1071 Error attempting to read Vconfig GDO.
Explanation: Error reading vconfig gdo.
Generated By: BAR.
For Whom: End user.
Notes: Verify if vconfig GDO exists.
Remedy: Contact the field engineer.

1072 Could not locate ONLINE PE to open internal session.
Explanation: Could not locate ONLINE PE to open internal session.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Ensure at least one PE is up.

Above are list of Teradata Errors or Failure Codes from Error 1063 to 1072  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 *