Teradata SQL Error and Failure Codes from Error 10419to 10501

SQLServerF1

10419 ERRTSKDEBUGSTOP: 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 remove tasks from system
calls for debugging purposes.
Remedy: This event should never be logged. If it is, report the problem to the Global Support Center.

10420 Unable to start a new task due to OS error %$OsError.
Explanation: The specified error occurred when attempting to start a new task. This is not necessarily a fatal error; the
operation will be retried when this message is issued. If the retries also fail, the appropriate event will then be logged to
handle the fatal error.
Generated By: PDE task management services.
For Whom: System Support Representative.
Notes: The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Problems have been observed on NT that cause this event to be logged on occasion in circumstances where
retrying the operation will succeed. No action is needed in that case, unless this occurs too frequently or has some other
serious impact. Contact the Global Support Center.

10421 Tsk call not implemented.
Explanation: This error is returned if TSK service call is not implemented because no native OS support is available by
target OS platform or release
Generated By: PDE task management services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

10422 Timeout waiting for task %d to stop – attempting forced termination.
Explanation: The specified task did not exit for a pending tskstop request, so PDE attempted to recover by killing the
task.
Generated By: PDE task management services.
For Whom: System Support Representative.
Notes: The associated stack trace and snapshot dump will help the Global Support Center determine the exact cause of
the failure.
Remedy: The forced termination should eliminate the hung task, which usually lets Teradata continue normally with no
further action. However, there is a slight risk that this could lead to a system-level hang, which requires a manually initiated
Teradata restart to recover.

10501 Hashcode is invalid.
Explanation: The message subsystem has been given an invalid virtual processor hash code and the processor id cannot
be determined. This is probably caused by a coding error in the program logging the event.
Generated By: PDE message subsystem.
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 10419to 10501 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 *