Teradata SQL Error and Failure Codes from Error 10106 to 10111

SQLServerF1

10106 Invalid address for argument 6.
Explanation: The kernel could not access data pointed to by sixth argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
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.

10107 Invalid address for argument 7.
Explanation: The kernel could not access data pointed to by seventh argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
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.

10108 Invalid address for argument 8.
Explanation: The kernel could not access data pointed to by eighth argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
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.

10109 Invalid address for argument 9.
Explanation: The kernel could not access data pointed to by ninth argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
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.

10111 Resource limit is exceeded.
Explanation: This event code is reserved for future use.
Generated By: PDE system 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: This event should never be logged. If it is, report the problem the Global Support Center.

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