Teradata SQL Error and Failure Codes from Error 6150 To 6161

SQLServerF1_Header_Small

6150 Operator has Cancelled Reconfig due to AMPs down in configuration
Explanation: This error occurs in RCOCkDwn when the operator chooses to cancel rather than continue after Reconfig
reports that one or more AMPs are down in the configuration.
Generated By: RCOCkDwn.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Operator invoked error. Operator may restart Reconfig at his/her convenience.

6151 Remove Rules from DBC.LogonRuleTbl before running Reconfig
Explanation: This error occurs in RCOLogRl when rules are found for hosts which are to deleted from configuration.
Generated By: RCOLogRl.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Remove Rules and then proceed to next step prior to Reconfig.

6152 Unable to rebuild Non-Unique Secondary Index, needs rebuilding
Explanation: This error occurs in RCOErrUT when a disk error is encountered on a Non-Unique Secondary index which
cannot be rebuilt on the fly.
Generated By: RCOErrUt.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Drop subtable and rebuild.

6153 Unable to rebuild Unique Secondary Index, needs to be rebuilt
Explanation: This error occurs in RCOErrUT when a disk error is encountered on a Unique Secondary index which cannot
be rebuilt on the fly.
Generated By: RCOErrUt.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Drop subtable and rebuild.

6154 Encountered disk error on Table header, AMP needs to be rebuilt
Explanation: This error occurs in RCOErrUT when a disk error is encountered on a Table Header. Entire AMP is forced
down. Requires Amp rebuild following reconfig.
Generated By: RCOErrUt.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Rebuild AMP after reconfig.

6155 Encountered disk error on Table without Fallback, need to restore
Explanation: This error occurs in RCOErrUT when a disk error is encountered on a Table which has no fallback copy.
Table needs to be restored.
Generated By: RCOErrUt.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Restore Table after Reconfig.

6156 Encountered disk error, causing too many Amps down in cluster
Explanation: This error occurs in RCOErrUT when a disk error is encountered on a Table forcing an AMP down. Unfortunately
there is already an AMP down in the Cluster. Reconfig is forced to terminate.
Generated By: RCOErrUt.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Need to restore all tables.

6157 Encountered disk error on Table which has Amp Down in cluster
Explanation: This error occurs in RCORBDat when a disk error is encountered on a Table with an incomplete cluster.
Table will be marked – RCOAbort.
Generated By: RCORBDat.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Need to restore tables.

6158 Recovery is still active, Reconfig will not run until recovery done
Explanation: This error occurs in RCOCkSta while trying to start up Reconfig. If recovery is still active, Reconfig can not
be started.
Generated By: RCOCkSta.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Need to Wait for recovery to complete.

6159 Configuration map has been changed since Reconfig was initiated
Explanation: This error occurs in RCOCkSta while trying to start up Reconfig. If Config map is different from when
Reconfig was started, Reconfig will not run. Config must have ended after Reconfig was started.
Generated By: RCOCkSta.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Need to re-start Reconfig.

6160 Recovery still has AMPs in Hold or Catchup. Reconfig aborted
Explanation: This error occurs in RCOCkDwn while trying to start up Reconfig. If Config map reflects an Amp in hold
or catchup it will not continue.
Generated By: RCOCkSta.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Need to re-start Reconfig.

6161 Reconfig restarting system to recover remaining rows from disk error
Explanation: This error occurs in RCORBDat when an error is encount- ered during the Table Resistribution Phase of
Reconfig in a block which has a mix of new and old data rows. The old data rows have been recovered and the checkpoint
has been adjusted so that the potential new rows which were lost will be resent. This can also happen in the Old Table Deletion Phase when data block has collapsed due to no rows being returned in the recovery (all rows in this block have moved to another AMP). This is purely an informational type error.
Generated By: RCORBDat.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Reconfig will restart automatically.

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