Teradata SQL Error and Failure Codes from Error 13880 to 13898

SQLServerF1

13880 Vproc %d is not grouped with others of vproc type %d.
Explanation: Vprocs of a given type must all be grouped together. The specified vproc ID is not grouped with previously
defined vprocs of the indicated type. The number range for a vproc types except for AMPs can contain holes for unallocated vprocs, but no vprocs of another type can appear within that range.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Change the vproc numbering to be contiguous within a vproc type, recreate the VConfig GDO, and restart
PDE.

13881 Vproc ID %d is not allowed.
Explanation: The specified vproc ID exceeds the maximum TPA vproc number.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Change the vproc number to be within the permitted range, recreate the VConfig GDO, and restart PDE.

13888 Pdisk type codes in the Vconfig GDO have not been updated by the V2R5 version of PUT.
Explanation: A new set of pdisk types codes are used in the VConfig GDO starting with V2R5 to select the appropriate
set of parser optimization constants. PUT must be rerun to recreate the vconfig GDO after V2R5 is installed before these code will be used. Until this is done, the same set of optimizer constants will be used as in prior releases, which will result poor execution plans being used for some queries.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Rerun PUT to recreate the VConfig GDO, and restart PDE.

13889 COD: %s
Explanation: Because the WM COD setting in the current TDWM ruleset is greater than the WM COD MAX setting as
specified by the pme-config files, the WM COD setting was internally reduced to the WM COD MAX setting. The WM
COD setting in the TDWM ruleset was not modified.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This message is informational.
Remedy: The WM COD setting in the current TDWM ruleset needs to be modified to be less than or equal to the WM
COD MAX setting. This message will be displayed every TPA startup until this is resolved.

13890 Vproc %d not added to VprocConfig GDO because its vproc type is invalid.
Explanation: Vproc types must be between 1 and 15. The type of the specified vproc ID is not within this range.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Change the vproc type to the correct value, recreate the VConfig GDO, and restart PDE.

13891 Global crashloop count will not be cleared; %$OsError.
Explanation: The global crashloop count is normally reset after 30 minutes of error free operation. That will not happen
on this startup cycle because of the specified operating system specific error.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Change the vproc type to the correct value, recreate the VConfig GDO, and restart PDE.

13895 %s
Explanation: This event provides information about a TPA restart.
Generated By: PDE restart.
For Whom: System Support Representative.
Notes: This message is informational. The details about original restart are available in the event log on the initiator
node.
Remedy: Contact the Global Support Center.

13896 COD: %s
Explanation: This event provides information about a Capacity On Demand (COD) settings that affect optimizer performance
data in the Control GDO.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This message is informational.
Remedy: None needed if COD scaling shown is expected. Otherwise, contact the Global Support Center.

13897 Unable to open %16s file errno = %$OsError.
Explanation: This event provides information about a missing tpalastime.dat file.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This message is informational.
Remedy: Contact the Global Support Center.

13898 Application not started because fatal AMPs count has reached the limit specified in the control gdo.
Explanation: The DBS is not started becuase maximum number fatal AMPs count has reached the limit specified in the
control gdo.
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 13880 to 13898 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 *