Teradata SQL Error and Failure Codes from Error 10187to 10192

SQLServerF1

10187 Force a TPA shutdown by DApowerfail script. Restart reason is: %s
Explanation: This event is logged when the TPA is intentionally shutdown, by the DApowerfail script.
Generated By: DApowerfail Script.
For Whom: Operator.
Remedy: None. This message is for information only.

10188 Priority Scheduler was unable to allocate %u bytes for stats.
Explanation: Priority Scheduler was unable to allocate memory for PG/PPID or CPU stats. Priority Scheduler behavior
is not compromised, but will not be able to collect stats for the schstat tool.
Generated By: PDE system services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

10189 %s
Explanation: A backtrace is being generated because of the reason specified.
Generated By: PDE system services.
For Whom: PDE developers.
Remedy: For information only, no response is needed.

10190 A call to a sysukevent function has passed in an illegal token.
Explanation: This error is returned if the token passed to a sysukevent function does not identify a valid event. This may
occur because the caller has the incorrect token value, or because the event that it identifies has been freed.
Generated By: PDE sysukevent services
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

10191 A call to a SYSLOCK function has passed in an illegal token.
Explanation: This error is returned if the token passed to a syslock function does not identify a valid lock. This may
occur because the caller has the incorrect token value, or because the lock that it identifies has been freed.
Generated By: PDE syslock services
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

10192 ERRSYSRESET: Operation aborted because of reset.
Explanation: A task was killed while it was sleeping in a system call due to a TPA reset.
Generated By: PDE scheduler class.
For Whom: System Support Representative.
Notes: This message should not appear in the error log. Its event code is used within the kernel to control reset-time processing,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 10187 to 10192 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 *