Teradata SQL Error and Failure Codes from Error 1140 to 1149

SQLServerF1

1140 Got CMS Exception of %VSTR.
Explanation: CMS Exception encountered.
Generated By: BAR.
For Whom: Field Engineer.
Notes: None.
Remedy: Contact the field engineer.

1141 Got XML exception of %VSTR.
Explanation: XML Exception encountered.
Generated By: BAR.
For Whom: Field Engineer.
Notes: None.
Remedy: Contact the field engineer.

1142 Got DOM exception of %VSTR.
Explanation: DOM Exception encountered.
Generated By: BAR.
For Whom: Field Engineer.
Notes: None.
Remedy: Contact the field engineer.

1143 Got boost exception of %VSTR.
Explanation: Boost Exception encountered.
Generated By: BAR.
For Whom: Field Engineer.
Notes: This can be caused by internal software problems.
Remedy: Contact the field engineer.

1144 Got unknown exception.
Explanation: Unknown Exception encountered.
Generated By: BAR.
For Whom: Field Engineer.
Notes: None.
Remedy: Contact the field engineer.

1145 Socket mode is not “WRITE”.
Explanation: The write socket mode is not “write”.
Generated By: BAR.
For Whom: Field Engineer.
Notes: None.
Remedy: Contact the field engineer.

1146 The abort record has invalid record length of %VSTR.
Explanation: During Socket Handle BARNC Abort, the abort record has invalid record length.
Generated By: BAR.
For Whom: Field Engineer.
Notes: None.
Remedy: Contact the field engineer.

1147 The abort record has invalid error text length of %VSTR.
Explanation: During Socket Handle BARNC Abort, the abort record has invalid error text length.
Generated By: BAR.
For Whom: Field Engineer.
Notes: None.
Remedy: Contact the field engineer.

1148 The socket abort returned error code and error text of %VSTR.
Explanation: BARNC socket abort returned error code and error text.
Generated By: BAR.
For Whom: Field Engineer.
Notes: None.
Remedy: Contact the field engineer.

1149 Unknown parcel flavor was detected. The DBC exception is %VSTR.
Explanation: Unknown parcel flavor passed to throw DBC Exception.
Generated By: BAR.
For Whom: Field Engineer.
Notes: None.
Remedy: Contact the field engineer.

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