Teradata SQL Error and Failure Codes from Error 1095 to 1105

SQLServerF1

1095 Invalid table id is received from AMP.
Explanation: Unexpected table id is received from AMP.
Generated By: BAR.
For Whom: End user.
Notes: This can be caused by internal software problems.
Remedy: Contact the field engineer.

1096 Invalid record type is received. The record type is %VSTR.
Explanation: Unexpected record type is received.
Generated By: BAR.
For Whom: End user.
Notes: The dump is bad.
Remedy: If possible, please take a new dump. Otherwise, contact field engineer.

1097 The AMP number does not exist in the internal structure.
Explanation: The AMP number in the data segment is not found in the internal structure.
Generated By: BAR.
For Whom: End user.
Notes: Internal programming error.
Remedy: Contact the field engineer.

1098 The message does not contain data segment.
Explanation: The data segment is missing in the message.
Generated By: BAR.
For Whom: End user.
Notes: Potential internal programming error.
Remedy: Contact the field engineer.

1100 The hash code does not exist in the internal structure.
Explanation: The hash code is not found in the internal structure.
Generated By: BAR.
For Whom: End user.
Notes: Internal programming error.
Remedy: Contact the field engineer.

1101 Failed to create XML document for socket information.
Explanation: Failed to create xml document for socket information.
Generated By: BAR.
For Whom: End user.
Notes: Internal programming error.
Remedy: Contact the field engineer.

1102 Only %FSTR failed access rights are reported. The user does not have DUMP/RESTORE access on %VSTR objects.
Explanation: User does not have dump or restore access on objects.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Fix access right then resubmit the job.

1103 Task Details not found, taskset id and dataset id are:%VSTR.
Explanation: Task details not found.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Contact the field engineer.

1104 Bad file kind is detected. The file kind is %VSTR.
Explanation: The valid file kinds is either Meta or Data.
Generated By: BAR.
For Whom: End user.
Notes: This is a programming error.
Remedy: Contact the field engineer.

1105 SYSBAR.POSTSCRIPTWORKTBL has rows for current job execution id %VSTR ; please clean them.
Explanation: Rows exist in post script work table that needs to be cleaned.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Remove the rows from postscriptworktbl for the job that has the execution id given in the error message then
resubmit the job.

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