Teradata SQL Error and Failure Codes from Error 10112 to 10116

SQLServerF1

10112 System is not ready to issue a PDE service call.
Explanation: A program attempted to use a PDE system service during start-up before the necessary initialization to
perform the service was complete. This typically occurs when the operator tries to run a utility program too soon after a
node is booted, or after a DBS restart.
Generated By: PDE system services.
For Whom: Operator or System Support Representative.
Notes: The necessary state and substate is determined based on the service call attempted. Some programs can run successfully
during PDE initialization and others cannot, depending on which system services they use.
The associated stack trace will help the Global Support Center determine the service in question, if it is necessary to do that.
Remedy: Wait until PDE initialization is complete, then rerun the program that reported the error.

10113 A syszone resource could not be acquired.
Explanation: A task was killed while it was sleeping in a syszone allocation call. This can happen when the TPA is
restarted because the system is hung due to exhaustion of some syszone resource.
Generated By: PDE system services.
For Whom: System Support Representative.
Notes: The associated stack trace will help the Global Support Center determine the exact reason for the error.
Remedy: Although this event is expected in cases of syszone exhaustion, the reason that the system ran out of resources
needs to be investigated. That is typically due to a resource leakage in the DBS.

10114 Could not start %s PDE system daemon.
Explanation: The indicated system daemon could not be started.
Generated By: PDE system services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

10115 A call to a sysqevent function has passed in an illegal qevent token.
Explanation: This error is returned if the token passed to a sysqevent 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 sysqevent services
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

10116 A call to sleep has resulted in a TIMEOUT wakeup.
Explanation: A task was sleeping, and a timeout (requested on the call to sleep) has triggered.
Generated By: PDE syssleep.
For Whom: The code that asked for the sleep has to check for this value.
Remedy: None. This is for information only.

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