Teradata SQL Error and Failure Codes from Error 7704 To 7799

SQLServerF1_Header_Small

7704 The RepPhase1 message indicates fewer RepDDL than already received.
Explanation: The RepPhase1 message indicated fewer RepDDL for the transaction than actually received.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7705 MDS received more DDLs than expected for a transaction.
Explanation: MDS received more RepDDL messages than expected.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7706 Multiple RepBegTrans received for the same transaction before RepPhase1.
Explanation: Multiple RepBegTrans received for the same transaction before RepPhase1.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7707 Multiple RepBegTrans received for the same transaction after RepPhase1.
Explanation: Unexpected second RepBegTrans received for the same transaction.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7708 Transaction previously asynchronously aborted. Now transaction aborted with RepPhase1Rsp message.
Explanation: Transaction previously asynchronously aborted. Now transaction aborted with RepPhase1Rsp message.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7711 MDS received unexpected message after the RepPhase1 message.
Explanation: MDS received unexpected message after the RepPhase1 message.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7712 MDS received unexpected message before the RepPhase1 message.
Explanation: MDS received unexpected message before the RepPhase1 message.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7719 MDS received a TD message with incorrect length.
Explanation: The transactional message received by MDS is too long or not enough characters. Transaction was aborted.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7723 MDS received a DDL message with no AffectedDBName.
Explanation: The DDL message received by MDS did not have the AffectedDBName set. MDS expected the AffectedDBName
field in the DDL message to be set. Transaction was aborted.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7724 The RepDDL message indicates fewer DDL chunks than already received.
Explanation: The RepDDL message indicated fewer DDL chunks for the transaction than actually received.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7725 MDS received more DDL chunks than expected for a transaction.
Explanation: MDS received more DDL chunks than expected.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7799 MDS error range values end.
Explanation: Not used. Place holder for end of MDS error values.
Generated By: None
For Whom: None
Remedy: None

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