Teradata SQL Error and Failure Codes from Error 08085 to 08095

SQLServerF1

08085 A non-fatal internal error has occurred.
Explanation: An internal error has occurred in the gateway software. This error should be accompanied by the logevent
by the gateway which indicated the gateway error incountered.
Generated By: Gateway
For Whom: Field Engineer
Remedy: If the frequency of the message is abnormally high, contact the Global Support Center. Otherwise, ignore this
message.

08086 All the virtual circuits on the node are in use
Explanation: The number of virtual circuits on the node has reached the capacity specified in the gateway gdo. The session
will be closed so that the client can connect to a different node.
Generated By: Gateway
For Whom: End User
Remedy: If the frequency of the message is abnormally high, contact the Global Support Center. Otherwise, ignore this
message.

08087 Session caused an illegal state transition.
Explanation: A session event which should not occur caused a state transition,
Generated By: Gateway
For Whom: Field Engineer
Remedy: If the frequency of the message is abnormally high, contact the National Support Center. Otherwise, ignore this
message.

08088 Invalid Configuration Alert: %s
Explanation: Either the gateway configuration, the PE configuration, the Lan configuration or the host group is invalid,
or they are inconsistent. The gateway will either continue in a degraded mode, force a database restart, or will suspend its
startup and not accept connections.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Correct the configuration. If host names or internet addresses are invalid, the problem may be in the network
setup or in the host name lookup service, rather than in the configuration of the Teradata components. If the problem persists,
contact the National Support Center.

08089 An non-fatal unexpected error was returned by PDE: %s
Explanation: An error was returned by PDE.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

08091 Detail for 8017: The user is attempting to logon from a non-authorized host. %s
Explanation: Logon restriction by host has been enabled and the user is attempting to logon from a host that they are
not authorized to use. Error 8017 was returned in the logon response message.
Generated By: Gateway
For Whom: System Administrator
Remedy: Investigate why an account is attempting to logon from a host it is not authorized to use, and either remove the
IP address restriction if the logon should have been allowed, or deal with it appropriately if the attempt was accidental or
malicious.

08092 This host group has reached its maximum session limit. %s
Explanation: When the gateway’s assign task receives an assign request, it needs to assign the session to an available PE.
If the capacity of all PEs configured with the same logical host id has been reached or if there is only one gateway vproc up
and running in the host group, and its capacity has been reached, then the session cannot be assinged to a PE and error
8024 was returned to the client application in the assign response message.
Generated By: Gateway
For Whom: System Administrator
Remedy: Ask the client application user to wait for some amount of time and retry the logon attempt so that it may succeed
when another session logs off. If this problem occurs frequently, then the system administrator may need to contact
Global Support Center to increase the number of PEs in the host group, or to increase the number of sessions that the gateway
is allowed to handle.

08093 %s
Explanation: Information often needs to be converted between character sets. The information could not be converted
because it cannot be represented in the new character set.
Generated By: Gateway
For Whom: System Administrator
Remedy: Tell the user to choose a session character set that can represent the information or modify their account information
to use only characters that can be represented in their session character set, the database character set and Unicode.
If the information is generated by the database or the gateway and changing the session character set doesn’t fix the problem,
contact the Global Support Center.

08094 Gateway suspending: %s
Explanation: The Gateway has been suspended. It will not respond to new or existing connections until it resumes.
Generated By: Gateway
For Whom: System Administrator
Remedy: Determine why the gateway has suspended itself and fix the problem, or contact the Global Support Center.

08095 Gateway resuming: %s
Explanation: The Gateway has resumed execution. It should now respond to all new or existing connections.
Generated By: Gateway
For Whom: System Administrator
Remedy: Information only. No action is needed.

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