Teradata SQL Error and Failure Codes from Error 11101 to 11107

SQLServerF1

11101 Illegal flow control index.
Explanation: The given index exceeds the depth of the selected flow control table. This is a PDE kernel bug.
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.

11102 Invalid flow control ID values.
Explanation: An attempt was made to reset the flow control table with a max value less than the minimum value. This is
a PDE kernel bug.
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.

11104 Illegal virtual processor number.
Explanation: The requested vproc is currently not part of the TPA or does not exist.
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.

11105 No such processor.
Explanation: The requested PMA is currently not part of the TPA or does not exist.
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.

11107 Invalid network subop code.
Explanation: An unsupported RCB subop was detected for the given op command. This is a PDE kernel bug.
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 11101 to 11107 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 *