Teradata SQL Error and Failure Codes from Error 13100 to 13109

SQLServerF1

13100 LZS not installed
Explanation: The DBS requested an LZS operation, but the required hardware or software is not installed.
Generated By: PDE LZS Services.
For Whom: DBS developers.

13101 LZS cannot allocate memory
Explanation: The DBS requested an LZS operation, but the required memory cannot be allocated.
Generated By: PDE LZS Services.
For Whom: DBS developers.

13102 LZS operation failed
Explanation: The DBS requested an LZS operation, and the operation failed.
Generated By: PDE LZS Services.
For Whom: DBS developers.

13103 Invalid LZS flags
Explanation: The DBS passed invalid flags to lzsop().
Generated By: PDE LZS Services.
For Whom: DBS developers.

13104 Invalid LZS address
Explanation: The DBS passed an invalid address to lzsop().
Generated By: PDE LZS Services.
For Whom: DBS developers.

13105 Invalid LZS length
Explanation: The DBS passed an invalid length to lzsop().
Generated By: PDE LZS Services.
For Whom: DBS developers.

13106 LZS cannot hash
Explanation: The DBS requested a hash buffer when requesting an LZS decode operation. Hashing is only supported for
LZS encode operations.
Generated By: PDE LZS Services.
For Whom: DBS developers.

13107 Invalid LZS data
Explanation: The DBS passed invalid data to lzsop().
Generated By: PDE LZS Services.
For Whom: DBS developers.

13108 LZS not configured correctly
Explanation: The DBS requested an LZS operation that cannot be satisfied by the LZS driver as currently configured.
Generated By: PDE LZS Services.
For Whom: DBS developers.

13109 LZS busy
Explanation: The DBS requested an LZS operation that cannot be satisfied by the LZS driver because the hardware is
currently busy.
Generated By: PDE LZS Services.
For Whom: DBS developers.

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