Teradata SQL Error and Failure Codes from Error 10101 to 10105

SQLServerF1

10101 Invalid address for argument 1.
Explanation: The kernel could not access data pointed to by first 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.

10102 Invalid address for argument 2.
Explanation: The kernel could not access data pointed to by second 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.

10103 Invalid address for argument 3.
Explanation: The kernel could not access data pointed to by third 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.

10104 Invalid address for argument 4.
Explanation: The kernel could not access data pointed to by fourth 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.

10105 Invalid address for argument 5.
Explanation: The kernel could not access data pointed to by fifth 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.

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