Teradata SQL Error and Failure Codes from Error 6140 To 6149

6140 RECONFIG aborted due to improper disk initialization procedure.
Explanation: This error occurs when one or more of the following situations are detected:
1) A new AMP has a different row count in DBC.Proc, 2) A new AMP has a different row count in DBC.Lib, 3) A new AMP
has a different version number, 4) A new AMP has tables other than DBC.Proc, DBC.Lib, Scratch table, and Spool table.
Generated By: RcoCKPNL.
For Whom: Support Representative. Operator.
Remedy: Start fsuiniter on the new AMPs.

6141 RECONFIG aborted due to inconsistent database tables.
Explanation: This error indicates that database tables on all online AMPs are not in the same order, or some of the database
tables are missing from some AMPs. The reconfiguration process is aborted.
Generated By: RcoVT
For Whom: Support Representative. Operator.
Remedy: Contact your Support Representative.

6142 RECONFIG aborted at an irreversible state.
Explanation: This error indicates that in the Table Redistribution phase of RECONFIG, a database table could not be
found on all of the online AMPs, and the user decides to abort the reconfiguration process.
Generated By: RCOPhsRedistTables
For Whom: Support Representative.
Remedy: Contact your Support Representative.

6143 Operation aborted because it conflicts with currently active Reconfig.
Explanation: This error indicates that the Reconfig is active. So we can not begin config, or end config, or run multiple
reconfig now.
Generated By: RCOCInpu
For Whom: Support Representative.
Remedy: Wait for ReConfig to finish.

6144 Reconfig aborted, DBS State was not proper, unable to proceed.
Explanation: This error indicates that the Teradata Database is not quite ready to be reconfigured. The system is not
ready or Reconfig may be presently active.
Generated By: RcoCkSta.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

6145 Reconfig stopped, is in an irreversible state with down AMPs.
Explanation: This error occurs in RCOCHFIG when system restarted in an irreversible state and an AMP in the new
Configuration is offline.
Generated By: RcoChFig.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

6146 Reconfig stopped, logged on sessions found in DBC.Session Table
Explanation: This error occurs in RCOCkSes when Reconfig is started with a PE down but there exists a session logged
on in the DBC.Session table. Reconfig will not make it to the Calculate New Hash Bucket Phase.
Generated By: RCOCkSes.
For Whom: Support Representative.
Remedy: Contact your Support Representative. The session needs to be removed the DBC.Session table for Reconfig to
continue.

6147 Reconfig has encountered an invalid header in the DBC.Session Table
Explanation: This error occurs in FigCkSes when Reconfig attempts to read the DBC.Session table across all Amps.
Generated By: FigCkSes.
For Whom: Support Representative.
Remedy: Contact your Support Representative. The DBC.Session table needs to be repaired before continuing with the
Reconfig.

6148 Reconfig has encountered an invalid row in the DBC.Session Table
Explanation: This error occurs in FigCkSes when Reconfig attempts to read the DBC.Session table across all Amps.
Generated By: FigCkSes.
For Whom: Support Representative.
Remedy: Contact your Support Representative. The DBC.Session table needs to be repaired before continuing with the
Reconfig.

6149 Reconfig Cancelled, there is more than one AMP down in a cluster
Explanation: This error occurs in RCOCkDwn when Reconfig can not continue due to a cluster being inoperable.
Generated By: RCOCkDwn.
For Whom: Support Representative.
Remedy: Contact your Support Representative. At least the AMPs in the cluster which is forcing us down need to be
brought up.

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