Teradata SQL Error and Failure Codes from Error 13736 to 13749

SQLServerF1

13736 Cannot initialize the Hashmap GDO.
Explanation: An error occurred while attempting to initialize the Hashmap Globally Distributed Object. 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.

13742 Cannot write the getpma structure area.
Explanation: An error occurred while attempting to write the structure returned by the tosgetpma() service, which is
managed as a GDO. 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.

13743 VConfig GDO does not match actual hardware.
Explanation: The node ID for one of the nodes in the system is not defined in the VConfig GDO.
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: Rerun PUT to correct the problem and restart PDE.

13744 Cannot initialize the System GDO.
Explanation: An error occurred while attempting to initialize the System Globally Distributed Object. 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.

13745 Cannot read the System GDO.
Explanation: An error occurred while attempting to read the System Globally Distributed Object. 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.

13746 Cannot write the System GDO.
Explanation: An error occurred while attempting to write the System Globally Distributed Object. 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.

13748 Cannot write the Kernel GDO.
Explanation: An error occurred while attempting to write the Kernel Globally Distributed Object. 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.

13749 NTP failed on this node.
Explanation: PDE detected an NTP (Network Time Protocol) failure. The prior log message gives additional information
about the cause of the failure. Temporal support requires NTP to be operational, so the TPA is restarted to bring Teradata
back up without this node.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Fix the problem with NTP, then issue a TPA restart to bring this node back into the Teradata configuration once
NTP is operational on it again.

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