Teradata SQL Error and Failure Codes from Error 10198to 10202

SQLServerF1

10198 Force a TPA restart. Restart reason is: %s
Explanation: This event is logged when the TPA is intentionally restarted, either by the operator or some DBS utility,
such as reconfig.
Generated By: PDE restart.
For Whom: Operator.
Remedy: None. This message is for information only.

10199 Assertion failed.
Explanation: This event code is reserved for internal use. It is generated by debugging code for diagnosing unexpected
internal states. This code is omitted in software released to the field.
Generated By: PDE kernel drivers.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center

10200 Monitor ID is not assigned.
Explanation: A monitor service was passed a monitor identifier that is not allocated. This could be due to passing a bad
monitor id argument, or the monitor could have been deallocated by another task.
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.

10201 Process is not in the monitor.
Explanation: A monleave(), mondetach(), or monyield() service was passed a monitor identifier for a monitor that is not
owned by the task. 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.

10202 Process is already in the monitor.
Explanation: The monenter() service was passed a monitor identifier for a monitor that is already owned by the task.
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.

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