Teradata SQL Error and Failure Codes from Error 13600 to 13716

SQLServerF1

13600 ERRDMPNOSPACE: This event should not be logged.
Explanation: This event is never entered into the event log. It is used internally by the PDE dump tool to report a kernel data file that is too small.
Generated By: PDE dump facility.
For Whom: System Support Representative.
Remedy: None needed.

13602 %s
Explanation: This event reports a failure to copy kernel data into a PDE dump. It probably indicates either an internal
logic error in the PDE DMP tool or memory corruption in the PDE kernel driver. The message text gives additional information about the data that was being dumped.
Generated By: PDE dump facility.
For Whom: System Support Representative.
Remedy: This error only occurs when taking a PDE crashdump as a consequence of some other error. When reporting
that problem, also note that the dump failed and give the reason as shown in the associated log message.

13699 DMP internal error
Explanation: This event indicates an internal logic error in the DMP tool. It should never be logged in the field.
Generated By: PDE dump facility.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

13700 Cannot allocate memory for PDE initialization.
Explanation: There is not enough physical memory available to start PDE. If this ever occurs, it is most likely after a DBS restart when the node has been up for an extended period, and something has not been releasing memory when it should.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This event aborts PDE startup, causing an automatic retry. After three failures, PDE stops retrying and remains
down. The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: An operating system shutdown and reboot should clear up the problem. However, this is probably caused by a
memory leak in PDE reset or startup logic, which should be reported to the Global Support Center.

13701 Invalid relative vproc number.
Explanation: The relatvie vproc number passed on an internal PDE driver service call is invalid. This either indicates a bug in PDE or memory corruption caused by the DBS.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This event aborts PDE startup, causing an automatic retry. After three failures, PDE stops retrying and remains
down.
Remedy: An operating system shutdown and reboot may clear up the problem. However, this is probably caused by an
error in PDE startup logic, which should be reported to the Global Support Center.

13707 PDE startup synchronization point timed out on this node.
Explanation: At various points during PDE initialization, a synchronization is performed to ensure that all nodes have
reached that point before continuing. If some node has not yet reached a given sync point, the other nodes will wait until it does. To prevent the system from hanging, each sync point has a timeout interval. If the timeout expires before all nodes reach the sync point, the other nodes will log this event to restart PDE initialization.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This event aborts PDE startup, causing an automatic retry. After three failures, PDE stops retrying and remains
down. The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: This indicates a PDE startup problem on some other node. Check their logs to find the real error and respond
accordingly.

13709 User not authorized for PDE control service.
Explanation: A privileged system call that should only be made by the PdeMain program was called by some other
user. Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Report the problem to the Global Support Center.

13711 Cannot enter a group.
Explanation: A grpenter() service call returned an error that prevents PDE initialization from continuing. This indicates a bug in PDE initialization logic.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This event aborts PDE startup, causing an automatic retry. After three failures, PDE stops retrying and remains
down. The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: An operating system shutdown and reboot may clear up the problem. However, this is probably caused by a
bug in PDE startup logic, which should be reported to the Global Support Center.

13713 Cannot get number of members in a group.
Explanation: A grpcount() service call returned an error that prevents PDE initialization from continuing. This indicates a bug in PDE initialization logic.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This event aborts PDE startup, causing an automatic retry. After three failures, PDE stops retrying and remains
down. The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: An operating system shutdown and reboot may clear up the problem. However, this is probably caused by a
bug in PDE startup logic, which should be reported to the Global Support Center.

13715 NTP status polling thread failed to start.
Explanation: Temporal support requires NTP to be operational, but the thread in pdemain to verify that NTP remains
running while the DBS is active failed to start.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: An operating system shutdown and reboot may clear up the problem. However, this is probably caused by a
bug in PDE startup logic, which should be reported to the Global Support Center.

13716 The TPA node list file could not be written.
Explanation: An error occurred attempting to create a new file containing a list of TPA candidate nodes. This list is created in parallel on all nodes. The node that reports the error is not necessarily the one where it occurred.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: This is most likely caused by disk space exhaustion on some node. Verify that the disk containing the tdTemp
directory is not full on any node of the system, then try restarting PDE.

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