Teradata SQL Error and Failure Codes from Error 10902 to 11000

SQLServerF1

10902 Group is not valid.
Explanation: An PDE network group service was requested for a groupid that is not a valid group identifier. This indicates
a problem with the program that issued the call. It is also returned by other PDE network services when GRPALL (the
group that includes all virtual processors) is specified for a service that is not allowed for that group.
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.

10903 Virtual processor is already a member of the group.
Explanation: The virtual processor issuing a grpenter() or grpswitch() service is already a member of the group it is
being requested to enter. This generally indicates a problem with the program that issued the call.
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.

10904 Virtual processor is not a member of the group.
Explanation: The virtual processor issuing a grpleave() or grpswitch() service is not a member of the group it is being
requested to leave. This generally indicates a problem with the program that issued the call.
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.

10957 Failed ImplicitGrpEnter – Destination group was put.
Explanation: The group that was supposed to be entered no longer exists. This event may be due to a stale message left
in the message queue, or a timing problem relating to group services.
Generated By: BNS Group 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: Contact the Global Support Center if the frequency of the message is abnormally high.

11000 Attributes do not match segment found in memory.
Explanation: The attribute of a descriptor passed to a file segment service does not match the one found in memory.
Generated By: DBS file segment management.
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 10902 to 11000 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 *