Teradata SQL Error and Failure Codes from Error 10801to 10806

SQLServerF1

10801 Channel does not exist.
Explanation: An attempt was made to use a channel that has not been allocated, or that has already been freed. This typically
indicates a problem with DBS or other software that issued the service call, possibly a timing problem where a task
that got the channel frees it before an associated task is done using it.
Generated By: PDE network channel services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10802 Channel is not a dynamic channel.
Explanation: An attempt was made to free a channel using chnput() that is not a dynamic channel. This indicates a problem
with the program that issued the call.
Generated By: PDE network channel services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10804 Channel local state is not valid for this operation.
Explanation: The internal state of a channel is not what is should be at the time a service request was issued.
Generated By: PDE network channel services.
For Whom: System Support Representative.
Notes: This event may issue an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10805 ERRCHNFIRSTVPROC: This event should not be logged.
Explanation: This event should not appear in the error log. It is returned by chnfirst() to notify the caller that it is the first
task to issue the call. The caller should be prepared to receive this event and handle in appropriately. If it appears in the log,
it probably indicates a problem with the task that logged the event.
Generated By: PDE network channel services.
For Whom: System Support Representative.
Notes: This event does not cause a DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: This event should never be logged. If it is, report the problem to the Global Support Center.

10806 ERRCHNLASTVPROC: This event should not be logged.
Explanation: This event should not appear in the error log. It is returned by chnsignal() to notify the caller that it is the
last task to issue the call. The caller should be prepared to receive this event and handle in appropriately. If it appears in the
log, it probably indicates a problem with the task that logged the event.
Generated By: PDE network channel services.
For Whom: System Support Representative.
Notes: This event does not cause a DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: This event should never be logged. If it is, report the problem to the Global Support Center.

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