Teradata SQL Error and Failure Codes from Error 6022 To 6034

SQLServerF1_Header_Small

6022 The AMP Vproc Number specified is moved to the wrong AMP.
Explanation: This error occurs with the move amp command. Either the source AMP or the destination AMP does not
match the definitions in the vconfig GDO.
Generated By: RCOCErr.
For Whom: End User.
Remedy: Examine the vconfig GDO and either correct the AMPs specified in the move amp command, or correct the
vconfig GDO if it is incorrect.

6023 Configuration type should be either Current or New.
Explanation: This error occurs if neither current or new configuration is specified.
Generated By: RCOCErr.
For Whom: End User.
Remedy: Press the HELP function key to check syntax.

6024 Configuration map is inconsistent.
Explanation: This error occurs if the system crashed when the config map was written back to disk.
Generated By: RCOCErr.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

6025 Some hosts are not connected to any PE.
Explanation: This error occurs if hosts are not connected to a PE.
Generated By: RCOCErr.
For Whom: End User.
Remedy: Use the LIST command to check the configuration.

6026 Some hosts are connected to more than 512 PEs.
Explanation: This error occurs if hosts are connected to more than 512 IFPs in a Teradata Database.
Generated By: RCOCSess.
For Whom: End User.
Remedy: Use the LIST command to check the configuration.

6027 Some PEs are not connected to any host.
Explanation: This error occurs if one or more IFPs, APPs or PEPs are not connected to a host.
Generated By: RCOCSess.
For Whom: End User.
Remedy: Use the LIST command to check the configuration.

6028 Addition, Deletion, and Moving of AMPs are mutually exclusive.
Explanation: This error occurs if mutually exclusive operations are specified.
Generated By: RCOCErr.
For Whom: End User.
Remedy: Use the LIST command to check the configuration.

6029 Cluster Numbers are not consecutive.
Explanation: This error occurs if cluster numbers are not consecutive.
Generated By: RCOCErr.
For Whom: End User.
Notes: Cluster numbers start at 0 and, when specified in configuration, must be consecutive.
Remedy: Use the LIST command to check the configuration.

6030 The move AMP command was not entered for all AMPs that are to be moved.
Explanation: This error occurs with the move amp command. There are moved AMPs defined in the vconfig GDO, but
were not moved with the config move amp command.
Generated By: RCOCErr.
For Whom: End User.
Remedy: Examine the vconfig GDO and either move the remaining AMPs with the move amp command, or correct the
vconfig GDO if it is incorrect.

6032 Warning: The number of Amps in a cluster is less than one-half of the Default Cluster value specified.
Explanation: This warning occurs if a DEFAULT CLUSTER command is entered and the size chosen for the default cluster
size resulted in a Cluster with less than one-half of the Default cluster size.
Generated By: RCOCErr.
For Whom: End User.
Remedy: Choose a different default cluster size or Add/Delete more Amps or Modify the existing Amps to different
clusters.

6033 The Default Cluster size results in a cluster with one Amp.
Explanation: This warning occurs if a DEFAULT CLUSTER command is entered and the size chosen for the default cluster
size resulted in a Cluster with just one Amp. This Amp would have no Fallback Amp(s).
Generated By: RCOCErr.
For Whom: End User.
Remedy: Choose a different default cluster size or Add/Delete more Amps.

6034 Incompatible operation with the Vproc type in current config map.
Explanation: This error occurs if an ADD command is entered and the Vproc type in the current config map is defined
as some incompatible type. Currently there are two situations that can cause this error:
1) ADD AMP mmm where mmm is defined in the current map but NOT as an AMP.
2) ADD PE mmm where mmm is defined in the current map but NOT as an PE.
Generated By: RCOCErr.
For Whom: End User.
Remedy: You probably are trying to delete either a PE from the current config and ADD it back as an AMP, or vice versa.
The two operations must be performed with two separate Reconfiguration runs.

Above are list of Teradata Errors or Failure Codes from Error 6022 To 6034 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 *