TDP3600 "npname" TERADATA SERVER ENCAPSULATION-VIOLATION: TU(xx), ERROR(n), INFO(xxxxxxxx) - Teradata Director Program

Teradata Director Program (TDP Prefix) Messages

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Director Program
Release Number
15.xx, 16.xx, 17.xx, 20.xx
Published
June 2020
Language
English (United States)
Last Update
2023-11-20
lifecycle
Latest
Product Category
Teradata Tools and Utilities

TDP3600 "npname" TERADATA SERVER ENCAPSULATION-VIOLATION: TU(xx), ERROR(n), INFO(xxxxxxxx)

Explanation:

A network transmission from the Teradata Database violated the encapsulation protocol. The hexadecimal id of the Transmission Unit from the header is displayed. The decimal error code and hexadecimal additional information is that which is valid in a Reject TU. If the error code is less than 1000 it is defined by the Teradata Database; otherwise it is defined by TDP, as follows (here using Database internal terminology): 1000 A TU specified a Kind of zero. 1001 A TU specified a TU_body length greater than the maximum bytes per communication protocol block, the maximum size of a datablock TU. 1002 Data followed a valid TU in a UDP datagram. 1003 An improper TU was received by the client end-point. 1004 A Connect_done TU specified a maximum TU size that was less than the minimum valid value. 1005 A Connect_done TU specified a maximum blocksize that exceeded the specified maximum TU size minus the length of the TU header. 1006 A Connect_done TU specified a KeepAlive-ACK frequency of zero. 1007 A Connect_done TU specified a maximum number of TUs sent without ACK of zero when using the UDP transport. 1008 A Connect_done TU specified Window-rotation wait of zero when the maximum TUs sent without ACK is not zero. 1009 A Connect_done TU specified a maximum successive rotation wait of zero when the maximum TUs sent without ACK is not zero. 1010 A Connect_done TU did not provide a port when using the UDP transport. 1011 A Connect_done TU provided a port when using the TCP transport. 1012 A Connect_done TU provided an NP qualifier that differs from the NP qualifier returned from a previous Connect_Done TU. 1013 At least one reconnect encapsulation protocol parameter differs from the negotiated connect encapsulation protocol parameter.

Generated By:

TDP.

Notes:

Additional information may be captured by using the ENABLE TRAP SERVEREV command before the situation occurs. If START processing has not yet completed, the START will fail, otherwise, the NP enters the PERM ERR state and will not be used further. Any requests that are active on the NP will be failed and the associated sessions will be logged off. Sessions without active requests or with requests active on other NP's are unaffected.

Remedy:

Subsequent use of the NP may be attempted by first issuing the TDP STOP NP (necessary (only if the NP is in the PERM ERRstate), then the TDP START NP command. Contact Customer Support personnel and provid the text of this message and any diagnostic information available for the Teradata Database error.