Teradata SQL Error and Failure Codes from Error 08018 to 08035

SQLServerF1

08018 The session id is illegal.
Explanation: The session id specified in any request is not valid. Either the session had never been logged on, the session
did not reconnect within the gateway timeout period after a DBS reset, or the session id is simply malformed.
Generated By: Gateway
For Whom: End User
Remedy: Correct the session number and resubmit the request.

08019 The parcel stream is invalid.
Explanation: The parcel stream following the message header on the assign, reassign, authorization, single sign-on, connect
or reconnect request is not valid either because the sizes of the parcel(s) are wrong or the kinds of the parcel(s) are
wrong.
Generated By: Gateway
For Whom: End User
Remedy: Repeat the assign sequence with a good parcel stream.

08022 That request is not valid for the session state.
Explanation: The session state was not suitable for processing a request message, e.g., a reconnect request was received
for a session while the session state was in transition.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Continue to resubmit the request until the session state is no longer in transition.

08024 All virtual circuits are currently in use.
Explanation: This error is sent in response to an assign request when a either the gateway capacity or the capacity of all
PEs configured with the same logical host id has been reached.
Generated By: Gateway
For Whom: End User
Remedy: Wait some amount of time and retry the assign request. The assign will succeed when another session logs off.

08025 The LAN message SessionNo field is invalid.
Explanation: This error is generated when an assign request contains a non-zero session number. It is also generated
when a reassign request contains a zero session number.
Generated By: Gateway
For Whom: End User
Remedy: Correct the assign/reassign session number and try again.

08026 The LAN message RequestNo field is invalid.
Explanation: This error is generated when a start request contains a request number lower than that of any previous
start request or when a continue request contains a request number higher than any previous start request.
Generated By: Gateway
For Whom: End User
Remedy: Correct the request number and retry the continue or start request.

08028 The LAN message Authentication is invalid.
Explanation: The authentication value passed in the LAN header contains a value that does not match the value the
gateway expected or the TDGSS cryptographic routines reported an error.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

08029 The LAN message ByteVar is invalid.
Explanation: The ByteVar value passed in the LAN header contains a value that does not match the value the gateway
expects. If the message is a reconnect, the value of ByteVar should be either 0 or 1.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Correct the ByteVar and retry the reconnect request.

08031 Gateway could not recover a session from a down COP.
Explanation: The message occurs when the gateway tries to switch a session from a down PE and the switch operation
failes in session control.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

08033 Logons are disabled by the Gateway software.
Explanation: This message occurs when logons are disabled by the gtwcontrol or gtwglobal utilities.
Generated By: Gateway
For Whom: End User
Remedy: Contact the system adminstrator to enable logons with the gtwcontrol or gtwglobal utilities.

08035 The LAN message WordVar is invalid.
Explanation: The WordVar values passed in the LAN header contains a value that does not match the value the gateway
expects. If the message is a directed request, the value of WordVar must be a legitimate HUT request message kind. Otherwise
WordVar must contain zero.
Generated By: Gateway
For Whom: Field Engineer
Notes: This error should never be seen by an end user unless the end user takes it upon himself to generate directed
requests in the LAN environment.
Directed request are only supported for use by Teradata utilities.
Remedy: Contact the Global Support Center.

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