Teradata SQL Error and Failure Codes from Error 10183to 10197

SQLServerF1

10193 Premature return from system call.
Explanation: A task was interrupted while it was sleeping in a system call. This can happen for a variety of reasons,
such as the task being stopped by a debugger.
When a service call returns this event code, the program should normally reissue the call, since nothing is really wrong, but
the call was not completed. For many PDE system calls, the call is automatically reissued, but in some cases the call returns
this error to the caller.
Programs issuing calls that can receive this event code should test for it and proceed accordingly (normally, by reissuing
the call after taking appropriate corrective action), so if this event is logged, it probably indicates a bug in the program that
logged it.
Generated By: PDE scheduler class.
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: This event should never be logged. If it is, contact the Global Support Center.

10194 System name limit reached.
Explanation: This event is used when the vpruniquename value got wrap-around. The vpruniquename is used for allocating
unique sysname and monitor. Vpruniquename is an integer field that gets reset after tpareset. Experiement shows
that it probably takes 7 years to use all possible values before wrap-around. Thus this is a very unlikely condition.
Generated By: PDE system services.
For Whom: Operator.
Notes: This will cause the system to reset. As a result, vpruniquename associates with each vproc will get reset back to 0.
Remedy: None. This message is for information only.

10195 Premature return from system call.
Explanation: A task was interrupted while it was sleeping in a system call. This can happen for a variety of reasons, such
as the task being stopped by a debugger.
When a service call returns this event code, the program should normally reissue the call, since nothing is really wrong, but
the call was not completed. For many PDE system calls, the call is automatically reissued, but in some cases the call returns
this error to the caller.
Programs issuing calls that can receive this event code should test for it and proceed accordingly (normally, by reissuing the
call after taking appropriate corrective action), so if this event is logged, it probably indicates a bug in the program that
logged it.
Generated By: PDE scheduler class.
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: This event should never be logged. If it is, contact the Global Support Center.

10196 Force a TPA restart with a dump. Restart reason is: %s
Explanation: This event is logged when the TPA is intentionally restarted and a dump is requested. This is normally
done by the operator with a restart command in the DBW supervisor window.
Generated By: PDE restart.
For Whom: Operator.
Remedy: None. This message is for information only.

10197 Force a TPA dump followed by panic dump. Restart reason is: %s
Explanation: This event is logged when the TPA is intentionally resetted and both TPA and panic dump are requested.
This is normally done by the operator with a tpareset -p command.
Generated By: PDE restart.
For Whom: Operator.
Remedy: None. This message is for information only.

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