Teradata SQL Error and Failure Codes from Error 13899 to 13908

SQLServerF1

13899 Warning NTP failed on this node.
Explanation: PDE detected an NTP (Network Time Protocol) failure. Temporal support requires the teradata-ntp package
to be installed and operational. Only a warning is issued as Temporal support is disabled.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Fix the problem with NTP

13900 Cannot open PDE device driver: %$OsError
Explanation: An error occurred attempting to open the PDE device driver. This driver is used to by most PDE services,
so it must be accessable by all TPA programs.
Generated By: PDE program management services.
For Whom: System Support Representative.
Remedy: Verify that the pdesys device driver has been started. If not, start it.

13901 Invalid KTCB pointer.
Explanation: The internal PDE device driver pointer to the task context block is invalid.
Generated By: PDE program management services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

13902 PdeVproc failed to enable PDE: %s
Explanation: The PdeVproc program failed internal PDE initialization for the reason specified.
Generated By: PDE program management services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

13903 PDE stopped due to OS request: %s
Explanation: PDE was stopped by the operating system due to operator intervention, such as a system-wide shutdown.
The specific reason is given in the second line of the message
Generated By: PDE program management services.
For Whom: Operator.
Remedy: None. This is simply an informational message to show why PDE was stopped, in case the shutdown was not
expected.

13904 Task aborted abnormally. %$registers
Explanation: PdeMain aborted abnormally due to an unhandled exception. This indicates a bug due to some condition
that the program was not prepared to handle.
Generated By: PDE task management services.
For Whom: System Support Representative.
Notes: This event causes PDE to stop.
The associated stack trace will help the Global Support Center determine the exact cause of the failure. The hardware registers
at the time of the exception are shown in the message. These are also needed to establish the

13905 %s
Explanation: PdeMain detected an error early in startup. This is used for a variety of unlikely errors that could occur
before PDE is fully started. The message text gives the specific cause of the error.
Generated By: PDE initialzation.
For Whom: System Support Representative.
Notes: This event causes PDE to stop.
Remedy: Contact the Global Support Center.

13906 %s
Explanation: An “impossible” condition has been detected in PdeMain or PdeLib.
PDE code contains a number of assertions for conditions that should never occur. The occurrance of one of these conditions is known as an assertion failure. Catching assertion failures at the point where they occur can be useful for debugging on development and test systems. In a production environment, though, stopping the program at the point where an assertion fails is not useful, and may seem to cause Teradata to hang inexplicably. Therefore, by default, when an assertion fails, this message is logged to note the fact that the error occurred, and the programs that detected the error tries to continue running. The result of doing this is generally unpredictable. Depending on the exact condition being asserted, this may range
from an immediate fatal error at one extreme, to having no apparent affect at the other extreme. In other cases, Teradata will continue to run, but with unexpected results.
In a debugging environment, asserts can be made to cause a dialog box to pop up, stopping the program at the point where the error occurred so that it can be debugged. To enable this, put a line containing:
set pdeassert 1 in the startup.txt file in the PDE configuration file directory.
Generated By: PDE initialization.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

13907 PDE Debug Information: %s
Explanation: Diagnostic message logged in the event log by the PDE Kernel Driver
Generated By: PDE Kernel Driver.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

13908 Spurious signal: %s
Explanation: The process receiveved the specified signal, which was unexpected, and ignored.
Generated By: PDE program management services.
For Whom: System Support Representative.
Remedy: None needed.

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