Teradata SQL Error and Failure Codes from Error 3021 To 3031

SQLServerF1_Header_Small

3021 GSN response is malformed.
Explanation: This consistency check was put in to check if GSN response is malformed.
Generated By: SesSInit.
For Whom: Support Representative.
Notes: This error is returned by an internal consistency check.
Remedy: Save the dump and contact your Support Representative.

3023 UserId or Password string is malformed.
Explanation: This error occurs when a poorly formed string was used either in the UserId or Password portion of the
logon string.
Generated By: Session Control.
For Whom: End User.
Notes: This error is caused by not properly terminating a double-quoted string or by not properly embedding a doublequote
inside a double-quoted string.
Remedy: Correct the logon string and resubmit.

3024 There are already 20 utility sessions running.
Explanation: The maximum number of utility requests that can run per PE is currently 20.
Generated By: Session Control.
For Whom: End User.
Remedy: Wait until some other user logs off.

3025 Host quiesced by DBC operator. New activity not allowed.
Explanation: The Teradata Database operator ran the HOSTABORT utility to quiesce all sessions for the host. No further
session activity, like the CLI DBCLGN, DBCRUN, DBCLGF and DBCSWP services, is allowed until the TDP is restarted.
Generated By: Session Control, Dispatcher.
For Whom: End User.
Remedy: The TDP must be restarted.

3026 The user’s right to log on has been revoked.
Explanation: The user attempted to log on after the security administrator executed a ’REVOKE LOGON…’ statement.
Generated By: Session Control.
For Whom: End User.
Remedy: Request the security administrator to ’GRANT LOGON …’ on your behalf.

3027 Invalid system message received.
Explanation: Something in the DBC or TDP generated a message to session control with an invalid message source, message
type, message class or message kind.
Generated By: Session Control.
For Whom: Support Representative.
Notes: This error is returned by an internal consistency check. This error causes a DBC restart to occur.
Remedy: Save the dump and contact your Support Representative.

3028 No thread contexts available.
Explanation: All the preallocated thread contexts have been allocated, thereby prohibiting the processing of of any new
session control requests.
Generated By: Session Control.
For Whom: Support Representative.
Notes: This error is returned by an internal consistency check. This error causes a DBC restart to occur.
Remedy: Save the dump and contact your Support Representative.

3029 Associated LSN was not found.
Explanation: An LSN associate connect request has been received for a host/LSN which cannot be found in the system.
Generated By: Session Control.
For Whom: Support Representative.
Notes: This error is returned by an internal consistency check. This error causes an error message to be returned to the
host.
Remedy: Check the LSN sent to the DBC to see that it already exists.

3030 Associated session has pending threads.
Explanation: A request message has been received for a session which currently has an active thread associated with it.
Generated By: Session Control.
For Whom: Support Representative.
Notes: This error is returned by an internal consistency check. This error causes an error message to be returned to the
host.
Remedy: Retry the request when the session is idle.

3031 Session is in-doubt and not logged on.
Explanation: Session Control has determined that a session is still in-doubt and is no longer logged on to the system.
Generated By: Session Control.
For Whom: Support Representative.
Notes: This error is generated by an internal consistency check. The locks that were placed by the in-doubt session will
remain until this is repaired.
Remedy: Contact your Support Representative.

Above are list of Teradata Errors or Failure Codes from Error 3021 To 3031 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 *