Teradata SQL Error and Failure Codes from Error 6162 To 6179

SQLServerF1_Header_Small

6162 Encountered disk error on Alternate copy of data during recovery
Explanation: This error occurs in RCORBDat when a disk error is encountered on a Table which is attempting to recover
data for another AMP.
Generated By: RCORBDat.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Need to restore table.

6163 Encountered disk error on Crucial System Table – AMP taken down
Explanation: This error occurs in RCORBDat when a disk error is encountered on a Table like MGCSysRcvStatTID. This
Table is necessary for checkpointing and status of Reconfig. AMP in error is taken down….
Generated By: RCORBDat.
For Whom: Support Representative.
Remedy: Contact your Support Representative. Need to rebuild AMP.

6164 NewReady AMPs which are not in New Configuration need to be DOWN
Explanation: This error occurs in RCOCkFig when a NewReady AMP is present but it is not a member of the configuration
to be. It is not being added or moved. The Amp needs to powered down if not in the destination configuration. This
error occurs in RCOCInput when a move AMP is followed by a cluster change. This is an impossible situation due to
assumptions made in the recovery logic.
Generated By: RCOCkFig. RCOCInpu.
For Whom: Support Representative. Support Representative.
Remedy: Power the AMP(s) in question down before resuming with the reconfig. Do not combine the move and the
change cluster in a single Reconfig. First do one quick Reconfig for the move; then do a second Reconfig for other configuration
changes.

6166 Other configurational changes pending, change cabinet not allowed.
Explanation: This error occurs in RCOCInput when a change cabinet is attempted while there are other configurational
changes defined in the new map (add, delete, cluster).
Generated By: RCOCInpu.
For Whom: Support Representative.
Remedy: Remove configuration changes from new config map. Then resubmit the change cluster.

6174 Invalid Tasks Value Input.
Explanation: This error occurs if the task input command has value is bigger than RCOMAXTASKS or the max amp
worker tasks divide by 3 (because each reconfig control task need 3 amp worker tasks). Therefore, the max number of parallel
tasks for reconfig must be a number between 1 and RCOMAXTASKS or maxampworkertasks/3.
Generated By: RCOParse.
For Whom: End User.
Remedy: Correct the command and resubmit the request.

6175 The BackDownTo16BitBkts flag in DBSControl must be set to true in order to revert to 16-bit hash buckets.
Explanation: This error occurs if the current hash bucket size is 20 bits, and the new hash bucket size is 16 bits. In order
to back down to a 16-bit hash bucket size, the internal flag BackdownTo16BitBkts in DBSControl must be set to true.
Generated By: RCOINPUT.
For Whom: End User.
Remedy: Correct the command and resubmit the request.

6176 The current and new hash bucket size fields must not be changed during reconfig.
Explanation: This error occurs if the current hash bucket size or the new hash bucket size in the DBSControl record
changed during reconfig. User should use the DBSControl utility to change the field(s) back to the correct values.
Generated By: FIGUSTA.C.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

6177 Reconfig Estimator aborted at %VSTR due to error %d.
Explanation: This error occurs when Reconfig estimator aborts due to some unexpected reasons.
Generated By: RCOESTCTRLT.C ,RCOESTNCTRL.C ,or FIGESTEVTHDL.C.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

6178 Hash bucket size changes are not allowed during online reconfig.
Explanation: This error occurs if the system under certain hashbucket changes.
Generated By: RCOSvc.
For Whom: End User.
Remedy: Check the Teradata Database state to ensure that there are no changing hash bucket.

6179 Reconfig online finished.
Explanation: This message is displayed when the reconfiguration process online completes.
Generated By: RCORESUME.
For Whom: End User.
Remedy: None.

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