Teradata SQL Error and Failure Codes from Error 6180 To 6192

SQLServerF1_Header_Small

6180 Reconfig Order Subsystem – Bad OrderType.
Explanation: The Reconfig Order Subsystem has encountered an internal error – invalid OrderType.
Generated By: Reconfig Order Subsystem.
For Whom: End User.
Remedy: Contact support representative.

6181 Reconfig Order Subsystem – Bad OrderGroup.
Explanation: The Reconfig Order Subsystem has encountered an internal error – invalid OrderGroup.
Generated By: Reconfig Order Subsystem.
For Whom: End User.
Remedy: Contact support representative.

6182 Reconfig Order Subsystem – Bad OrderNumber.
Explanation: The Reconfig Order Subsystem has encountered an internal error – invalid OrderNumber.
Generated By: Reconfig Order Subsystem.
For Whom: End User.
Remedy: Contact support representative.

6183 Reconfig Order Subsystem – Bad table ID.
Explanation: The Reconfig Order Subsystem has encountered an internal error – invalid table ID.
Generated By: Reconfig Order Subsystem.
For Whom: End User.
Remedy: Contact support representative.

6184 Reconfig Order Subsystem – Bad database name.
Explanation: The Reconfig Order Subsystem has encountered an internal error – invalid database name.
Generated By: Reconfig Order Subsystem
For Whom: End User
Remedy: Contact support representative.

6185 Reconfig Order Subsystem – Bad table name.
Explanation: The Reconfig Order Subsystem has encountered an internal error – invalid table name.
Generated By: Reconfig Order Subsystem
For Whom: End User
Remedy: Contact support representative.

6186 Reconfig Order Subsystem – Bad spool.
Explanation: The Reconfig Order Subsystem has encountered an internal error related to spool. It can be a bad spool ID,
a bad spool header, etc.
Generated By: Reconfig Order Subsystem
For Whom: End User
Remedy: Contact support representative.

6187 Reconfig Order Subsystem – Number of responses exceeds limit.
Explanation: The number of responses for a Reconfig Order Subsystem command has exceeded the limit. For instance,
if the Order Spool size is bigger than expected, a “Read” command of the Spool may require more responses than the
defined limit.
Generated By: Reconfig Order Subsystem
For Whom: End User
Remedy: Contact support representative.

6188 Reconfig Order Subsystem – row count mismatch.
Explanation: Row count mismatch. For instance, when the row count recorded in the Reconfig Control Block does not
match the actual row count of an Order dictionary table.
Generated By: Reconfig Order Subsystem
For Whom: End User
Remedy: Contact support representative.

6189 Reconfig Order Subsystem – user defined ordering not supported for DBC tables.
Explanation: DBC.ReconfigRedistOrderTbl or DBC.ReconfigDeleteOrderTbl contain user defined ordering for DBC
table(s).
Generated By: Reconfig Order Subsystem
For Whom: End User
Remedy: User should examine DBC.ReconfigRedistOrderTbl and DBC.ReconfigDeleteOrderTbl for rows referencing
DBC tables and delete those rows.

6191 Changing PE(s) is only allowed during offline reconfig.
Explanation: If reconfig will be run solely to change PE(s), then make sure that logons are disabled and that no logon
sessions are active before starting reconfig.
Generated By: RCOinput.
For Whom: End User.
Remedy: Check the Teradata Database state to ensure that no logon if reconfig running with changing Pes Only.

6192 AMP deletion is not allowed during online reconfig.
Explanation: This error occurs if the system have deleted AMPS during system logons.
Generated By: RCOSvc.
For Whom: End User.
Remedy: Check the Teradata Database state to ensure that there are no deletion AMPS during online reconfig.

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