Teradata SQL Error and Failure Codes from Error 13727 to 13733

SQLServerF1

13727 Cannot initialize the Kernel GDO.
Explanation: An error occurred while attempting to initialize 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. should be reported to the Global Support
Center.

13728 Cannot initialize the Control GDO.
Explanation: An error occurred while attempting to initialize the Control 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.

13729 Cannot read the Control GDO.
Explanation: An error occurred while attempting to read the Control 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.

13730 Cannot write the Control GDO.
Explanation: An error occurred while attempting to write the Control 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.

13731 Cannot initialize the V2P GDO.
Explanation: An error occurred while attempting to initialize the Virtual-to-Physical table 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.

13732 Cannot read the V2P GDO.
Explanation: An error occurred while attempting to read the Virtual-to-Physical table Globally Distributed Object. This
indicates a bug in PDE initialization logic.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
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 a
bug in PDE startup logic, which should be reported to the Global Support Center.

13733 Cannot write the V2P GDO.
Explanation: An error occurred while attempting to write the Virtual-to-Physical table 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.

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