Teradata SQL Error and Failure Codes from Error 6100 To 6110

6100 The status of an AMP is set to down by startup. ErrRCOAMpsDown – The status of an AMP is set to down by startup
Explanation: This error occurs if the status field of an AMP’s descriptor indicates that the AMP is down.
Generated By: RCOCkDwn.
For Whom: End User.
Remedy: Fix the down AMP, restart the DBS, and restart RCONFIG.

6102 RCONFIG restarts DBS. ErrRCORestart – RCONFIG restarts DBS.
Explanation: This message is displayed when the reconfiguration program terminates and the Teradata Database is to
be restarted.
Generated By: RCORECON.
For Whom: End User.
Remedy: None.

6103 A reconfiguration participant must be on-line. ErrRCONotOnline – A reconfiguration participant must be on-line.
Explanation: This error occurs if the status of an AMP is not on-line in the current configuration, and the status of the AMP with the same logical processorID is either FigProcDel or FigProcCC in the new configuration.
Generated By: RCOCkDwn.
For Whom: End User.
Remedy: Examine the new configuration and ensure that all participating AMPs are ONLINE.

6104 A Reconfig participant has inconsistent status in Config Map.
Explanation: This error occurs if the status of an AMP is on-line in the current configuration, but the status of the AMP with the same logical processorID is FigNullProcStatus in the new configuration.
Generated By: RCOCkDwn.
For Whom: Support Representative.
Notes: The configuration table may or may not be properly initialized.
Remedy: Contact your Support Representative.

6105 An on-line AMP is specified to be added in new Config Map. ,= ErrRCOAmpNotNew – An Online Amp is specified as new in new Config
Explanation: This error occurs if the status of an AMP is on-line in the current configuration, and the status of the AMP with the same logical processorID is FigProcNew in the new configuration.
Generated By: RCOCkDwn.
For Whom: Support Representative.
Notes: If this situation occurs, the configuration program has a bug.
Remedy: Contact your Support Representative.

6106 Logon is not disabled, or some sessions are logged on.
Explanation: This error occurs if the Teradata Database has not disabled the Logon facility or if there are some sessions
already logged on.
Generated By: RCOInput.
For Whom: End User.
Remedy: Check the Teradata Database state to ensure that logons are disabled and that no sessions are logged on.

6107 Invalid Input command.
Explanation: This error occurs if the input command has either a syntactic or semantic error.
Generated By: RCOParse.
For Whom: End User.
Remedy: Correct the command and resubmit the request.

6108 New Config Maps are not the same across all AMPs.
Explanation: This error occurs if the new configuration map on the disk of an AMP is not the same as the one on the
disk of the control AMP.
Generated By: RCOCkFig.
For Whom: Support Representative.
Notes: The user may or may not have invoked fsuiniter to initialize the added AMPs. If this is an ADD AMP operation,
make sure that fsuiniter was run just prior to reconfiguration. If not, rerun fsuiniter on the new AMP and retry the procedure.
Remedy: Contact your Support Representative.

6109 Current Config Maps are not the same on all AMPs.
Explanation: This error occurs if the current configuration map on the disk of an AMP is not the same as the one on the
disk of the control AMP.
Generated By: RCOCkFig.
For Whom: Support Representative.
Notes: The user may or may not have invoked fsuiniter to initialize the added AMPs. If this is an ADD AMP operation,
make sure that fsuiniter was run just prior to reconfiguration. If not, rerun fsuiniter on the new AMP and retry the procedure.
Remedy: Contact your Support Representative.

6110 Two version numbers are not the same on the configuration map.
Explanation: This error occurs if the version number field on a configuration map is not valid.
Generated By: RCOCkFig.
For Whom: Support Representative.
Notes: The system may have crashed when the Teradata Database was updating a configuration map.
Remedy: Contact your Support Representative.

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