Teradata SQL Error and Failure Codes from Error 10204to 10302

SQLServerF1

10204 Process is not in the yield state.
Explanation: The monresume() service was passed a task identifier for a task that has not yielded a monitor. This is usually
caused by an error in the logic of the program logging the event.
Generated By: PDE monitor 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.

10205 Monitor is in use by another task
Explanation: The monenter() service was passesd a monitor identifier for a monitor that is already owned by an another
task. This is not an error,this is logged when a task which does not want to wait for a monitor could not get the monitor
immediately
Generated By: PDE monitor services.
For Whom: System Support Representative.
Remedy: No action is needed.

10300 Address is in use.
Explanation: The new location passed to the segrelocate() service is already in use. This is usually caused by an error in
the logic of the program logging the event.
Generated By: PDE segment 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.

10301 Invalid segment identifier.
Explanation: The segment identifier passed to a segment system service is not assigned to any segment. This is usually
caused by an error in the logic of the program logging the event.
Generated By: PDE segment 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.

10302 Invalid pointer: No segment at this address.
Explanation: The address passed to a segment service is does not point to a segment that is accessed by the program, or
the segment passed to segchange() is a shared segment, or the address passed to segaccessloc() or seggetloc() or the new
location passed to segrelocate () is not aligned on a segment boundary. This usually indicates an error in the logic of the program
logging the event.
Generated By: PDE segment 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 10204to 10302 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 *