Teradata SQL Error and Failure Codes from Error 11108 to 11122

SQLServerF1

11108 Illegal relative virtual processor.
Explanation: This event is reserved for future use.
Generated By: PDE interconnect 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.

11109 Unable to flow control due to STREAMS thread.
Explanation: This event is not an error, it is a normal occurrence. The message subsystem informed the stream to
requeue and try later.
Generated By: PDE message 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.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center if the frequency of the message is abnormally high.

11110 Configuration requested is unavailable.
Explanation: The requested configuration is not available on this node. This implies the startup sequence on the TPA
layer of PDE is out of sync. We should rarely see this happens.
Generated By: PDE interconnect services.
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: Contact the Global Support Center if the frequency of the message is abnormally high.

11121 Flow control count beyond limit.
Explanation: The flow control count for the given index has incremented beyond the maximum allowed. This is a bug in
the flow control logic.
Generated By: PDE interconnect services.
For Whom: System Support Representative.
Notes: This event forces the node to reboot.
Remedy: Contact the Global Support Center.

11122 Invalid Global Sequence Number.
Explanation: An invalid Global Sequence Number was passed to tdnrnwait().
Generated By: PDE interconnect 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 11108 to 11122 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 *