Teradata SQL Error and Failure Codes from Error 13866 to 13875

SQLServerF1

13866 Teradata was last up at %s, and cannot restart for %d seconds.
Explanation: The clock has been set back on this node to before Teradata last stopped. Temporal support requires the
system time when Teradata starts to be greater than it was when Teradata was last running. Startup is delayed until small time warps expire, but startup aborts if the time difference is large.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If Teradata comes down on the node after this error, change the system time to exceed what it was when Teradata
was last stopped before trying to restart it. This check can be overridden by removing tpalasttime.dat from tdConfig,
but that risks database errors if temporal features are used.

13867 NTP is not running on this node (ntp_status = %d, errno = %$OsError)
Explanation: Temporal support requires the teradata-ntp package to be installed and operational, but it is not. Teradata will either shut down on this node, or will run with temporal support disabled.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Bring NTP up on this node, then issue a TPA restart to bring it back into the Teradata configuration. Teradata
normally stops on nodes where NTP is not working. Creating a file named “temporaldisable” in the tdConfig directory will allow Teradata to run without NTP, but then Teradata temporal support will be disabled for the entire system when NTP is down on any node.

13868 Teradata stopped on this node due to temporal support restrictions.
Explanation: Temporal support requires the teradata-ntp package to be installed and operational, and the system time
when Teradata restarts to exceed what it was when Teradata was last up. Teradata shut down on this node because one of
those conditions is not true, as indicated by a prior message.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Fix the problem (either install or start teradata-ntp, or change the system clock), then TPA restart will bring this node back into the configuration.

13869 Invalid startup kmsg request type: %d
Explanation: The TPA startup coordinator issues several msgkmsg requests to collect information from all nodes for
purposes such as GDO updates. A node received one of these requests that did not have one of the expected request types
codes.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Do not attempt to change vdisks for a vproc that is not in NEWPROC state.

13870 Vdisk %d not changed to %d because vproc %d state is not NEWPROC
Explanation: The list of vdisks associated with a vproc can only change when the vproc is in NEWPROC state.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Do not attempt to change vdisks for a vproc that is not in NEWPROC state.

13871 HwPerfInfo.txt error: %s
Explanation: An error was detected in the HwPerfInfo.txt file in the tdconfig or pde/etc directory.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If the HwPerfInfo.txt file has been modified by hand, correct the error. If the file has not been intentionally
modified, contact the Global Support Center for assistance.

13872 Vconfig GDO uses undefined %s type %d
Explanation: An error was detected in the HwPerfInfo.txt file in the tdconfig. No definitions from this file will be used. Startup attempts to proceed using only hardcoded default hardware definitions.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If the HwPerfInfo.txt file has been modified by hand, correct the error. If the file has not been modified, contact the Global Support Center.

13873 TPA startup aborted due to HwPerfInfo.txt file errors
Explanation: TPA startup aborted due to errors in the HwPerfInfo.txt file. The specific error is described by the previous message.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If the HwPerfInfo.txt file has been modified by hand, correct the error. If the file has not been modified, contact the Global Support Center.

13874 Node heartbeat polling thread failed to start.
Explanation: Thread to poll the node status on bynet failed to start.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

13875 Node %s is missing from the bynet network.
Explanation: Node is missing from the bynet network list. Either this node is no longer talking to the BYNET or it’s currentlyin a panic, or non-recoverable state. Please take corrective action.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

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