Teradata SQL Error and Failure Codes from Error 10414to 10417

SQLServerF1

10414 Priority is not valid.
Explanation: A PDE tsk priority service has been given an invalid Priority Identifier value or Priority Name string.
Generated By: PDE scheduler 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.

10415 Segment creation in child task failed with event %d.
Explanation: The attempt to materialize the segment passed to tskget in the child task failed with the event code shown.
Generated By: PDE task management services.
For Whom: System Support Representative.
Notes: Since this error is detected on the child thread, there is no way to pass it back to the parent. Instead, this event
unconditionally normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

10416 Task aborted abnormally. %$registers
Explanation: Task aborted abnormally due to an unhandled exception. This indicates a bug due to some condition that
the program was not prepared to handle.
Generated By: PDE task management 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. The hardware registers
at the time of the exception are shown in the message. These are also needed to establish the cause of failure
Remedy: Contact the Global Support Center.

10417 Stack overflow exception detected. %$registers
Explanation: Task aborted abnormally due to due to a stack overflow exception. This indicates that the program tried to
use stack space beyond its specified limits
Generated By: PDE task management services.
For Whom: System Support Representative.
Notes: This event may cause an automatic DBS restart.
The associated stack trace from the preceding 10416 event will help the Global Support Center determine the exact cause of
the failure. The hardware registers at the time of the exception are shown in the message. These are also needed to establish
the cause of the failure.
Remedy: Contact the Global Support Center.

10418 ERRTSKSTOP: This event should not be logged.
Explanation: This event is reported when a task that was in a PDE kernel sleep is woken up via tskstop or a reset.
Generated By: PDE task management services.
For Whom: System Support Representative.
Notes: This message should not appear in the error log. Its event code is used within PDE to terminate tasks that are
aborted and killed at reset time, but the task should exit without actually logging the event.
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 to the Global Support Center.

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