Teradata SQL Error and Failure Codes from Error 10301to 10405

SQLServerF1

10331 A duplicate persistent segment exists in the vproc.
Explanation: A segment with the same name, vproc, and partition already exists in the caller’s vproc. The second remap
operation is most likely unintentional.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This event usually means the application is trying to remap a shared segment to the wrong vproc.
Remedy: Contact the Global Support Center.

10399 Unrecoverable error in segment system.
Explanation: This event is logged for various conditions that should be logically impossible that are detected by the PDE
segment management subsystem. This indicates a PDE kernel driver problem.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center.

10402 Process ID is not valid.
Explanation: A PDE task management service has been given a process identifier for a task that does not exist, or is not
a member of the database scheduling class (SCHDB). This is usually caused by an error in the logic of the program logging
the event.
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.
Remedy: Contact the Global Support Center.

10404 Critical region nesting limit exceeded.
Explanation: A task is trying entering a critical region too many times, or leaving a critical region more times than it has
entered one. This is usually caused by an error in the logic of the program logging the event.
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.
Remedy: Contact the Global Support Center.

10405 Cannot continue a task that is not suspended.
Explanation: The tskcont() service has been used to continue a task that has not been suspended by the tskpause() service.
This is usually caused by an error in the logic of the program logging the event.
Generated By: PDE task management services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
In order to allow for timing windows in which the tskcont() call precedes the corresponding tskpause(), this error is actually
only returned when tskcont() has been called twice for the same task with no intervening tskpause().
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 10301to 10405 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 *