Teradata SQL Error and Failure Codes from Error 10864 to 10901

SQLServerF1

10864 ChnGet: Ran out of channel, exceeded MaxRetry %d
Explanation: An attempt to allocate a new channel object has repeatedly failed during ChnGet() for the maximum
allowed attempts. This event can be caused by a failure in acquiring the resources needed for the object.
Generated By: BNS Channel subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: This event implies no kernel memory resources are available. Contact the Global Support Center if a DBS
restart does not correct the problem.

10865 channel %d exceeded CHNMAXID %d
Explanation: Either the ChnGet() or ChnPut() service detected the given chnid was greater than the maximum allowed.
This event is caused by the calling task passing an invalid id. The operation is aborted.
Generated By: BNS Channel subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: This is an informational event only, no action required.

10866 GetPmaId Error MyPma.Num %d channel = %d
Explanation: A sender of the ChnRead() service detected the given NodeId provided by the receiver is not in the TPA
configuration table.
Generated By: BNS Channel subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: This event should never occur. If it does, it is most likely caused by a hardware glitch that corrupted the
NodeId. Contact the Global Support Center if a DBS restart does not correct the problem.

10900 No more dynamic groups available.
Explanation: All available dynamic groups have been allocated. This typically indicates that DBS software is getting
dynamic groups and never releasing them.
Generated By: PDE network group 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.

10901 Group does not exist.
Explanation: An attempt was made to use a group that has not been allocated, or that has already been freed. This typically
indicates a problem in DBS software, possibly a timing problem where a task that got the group frees it before an associated
task is done using it.
Generated By: PDE network group 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.

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