Teradata SQL Error and Failure Codes from Error 13717 to 13726

SQLServerF1

13717 Cannot set a channel.
Explanation: A chnget() service call returned an error that prevents PDE initialization from continuing. This indicates abug 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.

13718 Cannot initialize the getpma structure area.
Explanation: An error occurred while attempting to initialize 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.

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

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

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

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

13726 Cannot write the VprocConfig GDO.
Explanation: An error occurred while attempting to write the VprocConfig 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 13717 to 13726 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 *