Teradata SQL Error and Failure Codes from Error 3206 To 3216

3206 Dispatcher has no more semaphores available.
Explanation: This error occurs if there is no semaphore available when GsmGet is called. An attempt will be made to isolate
the fault.
Generated By: Dispatcher.
For Whom: System Support Representative.
Notes: The Dispatcher used up all the semaphores.
Remedy: Contact your support representative.

3207 A Dispatcher fault was addressed by a local exception handler.
Explanation: A Dispatcher fault that occurred while processing a request was addressed by a local exception handler.
Diagnostics captured vary and may include a snapshot dump plus available data about the session and request.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Save the request that caused the problem, and contact your support representative.

3208 A Dispatcher fault was logged.
Explanation: A Dispatcher fault that occurred while processing a request was logged. Action is taken when insufficient
data is available to FaultAbort a request. Diagnostics captured vary and may include a snapshot dump plus available data
about the session and request.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Save the request that caused the problem, and contact your support representative.

3210 Using text logged after AMP step failure.
Explanation: This event occurs if a failed request context is present by the dispatcher and a snapshot dump is taken.
Additionally the request is a parameterized request and some of the using variables (or parameters) have been replaced in
the parser and a plan specific to this data is generated for the request.
Generated By: Dispatcher.
For Whom: System Engineer or Data Base Administrator.
Notes: This event code is only logged in the error log and NOT returned to the end user. If a request context exist in the
DSP storage this event code will be logged. It will also accompany by event code 3112.
Remedy: The request was aborted.

3211 Expanded using text logged after a Dispatcher fault.
Explanation: This message will appear in the log event file along with the expanded using in the request that caused a
Dispatcher fault.
Generated By: Dispatcher.
For Whom: System Engineer or Data Base Administrator.
Remedy: None required.

3212 The stored procedure returned one or more result sets.
Explanation: The Stored Procedure returned one or more dynamic result sets.
Generated By: Dispatcher.
For Whom: End user
Remedy: This is an informational warning only.

3213 The stored procedure tried to return too many dynamic result sets.
Explanation: The Stored Procedure tried to return more dynamic result sets than the max specified a stored procedure
create time.
Generated By: Dispatcher.
For Whom: Stored Procedure programmer
Remedy: Reduce the number of result sets returned or increase the number specified at create time.

3214 Dispatcher fault isolation PE VPROC fault limit was reset to one.
Explanation: The count of all allowable fault isolation occurrences at the PE VPROC level has been exceeded and was
reset to one. This threshhold value now only has a 24 hour long validity. It will be reset only if at the time the threshhold
was exceeded, related validation has determined that less than 30 prior faults occurred within a 24 our period. Otherwise, a
DBS reset will be initiated. Note that the most recent fault instance that caused the threshhold to be exceeded may or may
not have been fault isolated.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: This is merely an informational message.

3215 SQL request text logged after the Dispatcher hit a non-fatal exception.
Explanation: This message, along with the SQL request text, will appear in the log event file to note that the Dispatcher
hit a non-fatal exception, provided the SQL request text is available.
A related tandem entry may appear in the log event file that describes the nature of the non-fatal exception that was
encountered.
Generated By: Dispatcher.
For Whom: System Engineer or Data Base Administrator.
Remedy: Contact your support representative.

3216 The stored procedure attempted to return an external result set.
Explanation: The Stored Procedure returned one or more dynamic result sets but the source of the result sets were from
an external connection or a query performed by another stored procedure.
Generated By: Dispatcher.
For Whom: End user
Remedy: The user can only returned result sets generated directly by this stored procedure.

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