Teradata SQL Error and Failure Codes from Error 3902 To 3913

SQLServerF1_Header_Small

3902 Session is not logged on.
Explanation: Session control has sent the parser a logoff request for a session that is not logged on, or a host has sent in a
request for a session that is not logged on.
A case where this can occur is if two hosts have the same HostID and a Host Start is done on one of those hosts. In that
event, users on the other host will begin to see errors of this sort.
Generated By: SQL, CON and SYN modules.
For Whom: System Support Representative and the End User.
Remedy: Save all relevant information and notify your support representative.

3903 Session is in wrong state to be logged off.
Explanation: Session control has sent the Parser a logoff request for a session that is not in a state where it can be logged
off. For example, the session state should never show that the Parser is processing a request.
Generated By: CON modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3904 Session is in wrong state to be parsing.
Explanation: Session must be in logon state to change to the parsing state.
Generated By: CON modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3905 Internal error: Cannot unquiesce an invalid session.
Explanation: Either 2PC or the Performance Monitor tried to unquiesce a session that was quiesced as something else.
Generated By: ConTsk.
For Whom: System Support Representative.
Remedy: Save all information. Contact your support representative.

3906 Session is in wrong state to abort a request.
Explanation: Session is in a wrong state to abort an in-progress request. The parser cannot abort the request.
Generated By: CON modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3907 Session in wrong state for logon state change.
Explanation: Session is in a wrong state to change to the logon state. To make this transition, the session control block
must show the session as parsing.
Generated By: CON modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3908 Internal error: No in-doubt transactions for non-2PC sessions.
Explanation: The PscBegSessInfo message indicated a 2PC in-doubt transaction, but this is not a 2PC session.
Generated By: ConTsk.
For Whom: System Support Representative.
Remedy: Save all information. Contact your support representative.

3909 Internal error: This session was not marked as known.
Explanation: ParTsk found a session that was not marked as known. SPF message sessions in ConTsk’s session context
must be marked by the Dispatcher as known.
Generated By: ParTsk.
For Whom: System Support Representative.
Remedy: Save all information. Contact your support representative.

3910 MemGet from pool failed.
Explanation: Memory was unable to parse the request.
Generated By: SYS, LEX, RES, OPT and GEN modules.
For Whom: User or System Support Representative.
Remedy: Simplify the Teradata SQL statement and resubmit it. If the problem persists, contact your support representative.

3911 Invalid message class received.
Explanation: This error code is used by Parser routines that receive and process messages. If the message that was
received has an invalid class in the message header, this error code is used as the restart cause.
Generated By: CON, PAR and SStTsk modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3912 Invalid message kind received.
Explanation: This error code is used by Parser routines that receive and process messages. If the message that was
received has an invalid kind in the message header, this error code is used as the restart cause.
Generated By: CON and PAR modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3913 The specified check does not exist.
Explanation: The user tried to drop/modify a non-existent check constraint.
Generated By: RES modules.
For Whom: End User.
Remedy: Do not resubmit the request. No such check constraint exists.

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