Teradata SQL Error and Failure Codes from Error 6128 To 6139

SQLServerF1_Header_Small

6128 Space accounting error during Reconfig. Error code – . ,= ErrRCOSpaceError – Space
accounting error during Reconfig. Error code – .
Explanation: TReconfig received error return code from space accounting routine.
Generated By: Reconfig.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

6129 The row being inserted already exists in the specified table.
Explanation: This error occurs when a row being inserted already exists in the specified table.
Generated By: FigRPR.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

6130 The parameter passed into a procedure is invalid.
Explanation: This error occurs when the parameter passed into a procedure is invalid.
Generated By: FigWriTH.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

6131 Reconfig-states are not the same on all AMPs.
Explanation: This error occurs if the Reconfig-status of the control AMP is greater than RCOPhsCalcHB, yet the Reconfig-
status of another AMP is RCOPhsIdle. This situation could happen in the following sequence of events:
StartUp Reconfig Crash Restart with down AMP in an irreversible state Reconfig refuses to resume User restores the Teradata
Database without the down AMP Startup after restoring the Teradata Database Add the down AMP without restoring
it
The Teradata Database might be restarted several times until one day AMP X is elected to be the control AMP. Reconfiguration
can now catch this AMP.
Generated By: RCOStaHD.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

6132 An AMP is specified as an PE in the new Config.
Explanation: This error occurs if the ProcTypes of an entry in the current configuration is set to AMP, but the corresponding
entry in the new configuration AMP is set to PE. The user must remove the AMP and processor kind to PE before
starting the reconfiguration session.
Generated By: RCOCkDwn.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

6134 RCONFIG is stopped by Operator.
Explanation: This error occurs when the user decides to stop the Teradata Database and wait for down processors to be
fixed.
Generated By: RCOChFig.
For Whom: End User.
Remedy: None.

6135 Reconfig is aborted at a reversible state.
Explanation: This error occurs when the user decides to abort the reconfig operation, and reconfig is reversible.
Generated By: RCOChFig.
For Whom: End User.
Remedy: Contact your Support Representative.

6136 Restore DBS because reconfig aborted at an irreversible state.
Explanation: This error occurs when the user decides to abort the reconfig operation after an AMP has failed and the
Teradata Database has to be rebuilt.
Generated By: RCOChFig.
For Whom: End User.
Notes: This situation occurs when, during the reconfig operation, the Teradata Database crashed in an irreversible state,
and the system returned with an AMP down.
Remedy: None.

6137 The hash bucket arrays on an AMP are invalid.
Explanation: This error occurs if the user has not run fsuiniter before starting Reconfig.
Generated By: RCOCkFig.
For Whom: End User.
Notes: The fsuiniter utility must be run when the “Add AMP” operation is invoked.
Remedy: Start fsuiniter on the new AMPs.

6138 You cannot invoke this operation before startup completes.
Explanation: This error occurs when the user starts the check table (RCoCKTB) utility before completing startup.
Generated By: RCoCKTB.
For Whom: End User.
Remedy: Resubmit after startup completes.

6139 An invalid table header information was returned.
Explanation: This error occurs when a table is missing its table header.
Generated By: FigTBC.
For Whom: Support Representative.
Remedy: Find the bad table and correct it.

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