Teradata SQL Error and Failure Codes from Error 6682 To 6696

6682 Replication group is terminating.
Explanation: 1. If this error code is returned in the response to a SQL request, the transaction has updated a replicated
table, and the replication group is in the process of terminating. To prevent lock conflicts with the termination operation,
the transaction has been aborted.
2. If this error code is returned by the RSG in response to a Connect or DataSignon message from an intermediary, it indicates
that a previously submitted terminate command has not yet been completely processed. A new connection cannot be
established yet.
Generated By: RSG
For Whom: End User
Remedy: Re-submit the transaction or RSG operation that failed; it should succeed when the termination processing has
completed.

6683 RSG has detected an existing data connection to the Replication Group.
Explanation: Multiple RepDataSignon messages were received by RSG for the same replication group.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: The replication group is in a “pending” state and RSG expects to receive the RepConnect message for the
group. This pending state expires in one minute if RSG does not receive any RepConnect messsage.

6687 Invalid batch identifier.
Explanation: The batch identifier is invalid.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Re-establish the apply connection to the replication group and re-try the operation

6688 No currently open batch.
Explanation: All available batches are busy.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Re-establish the apply connection to the replication group and re-try the operation when a batch becomes
available.

6689 RSG detects an existing connection to the replication group.
Explanation: This error can be returned in the following cases:
1. Multiple RepConnect messages were received by RSG for the same replication group.
2. Multiple RepCopySignOn messages were received by RSG for the same replication group.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: 1. Both the data and command connections are established for the replication group, any subsequent RepData-
Signon or RepConnect messages are rejected.
2. TableCopy connection is in progress. Concurrent Table Copy connection are not allowed for the same Replication group.

6690 Invalid table identifier.
Explanation: A table id pair context for the table identifier provided is already created.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Re-establish the apply connection to the replication group and make sure the table id provided is correct.

6691 No transaction with a lower sequence number.
Explanation: The server does not have any outstanding transactions with a lower commit sequence number than provided
by the intermediary.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: This message is for information only.

6692 Transaction is aborted by the Replication transport.
Explanation: The server received the transaction commit response from the transport with the CanCommit flag set to
false. The transaction is aborted by the server. (Note: There should be no condition under which the transport will reject the transaction)
Generated By: Replication Transport
For Whom: End User
Remedy: None

6694 Transaction aborted due to disk space limit.
Explanation: Change Data Capture was unable to write the spill record to disk due to space limitation.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Cleanup or increase the space limit for the RSG spill file directory.

6695 Message encryption is not enabled on this RSG vproc.
Explanation: Change Data Capture was unable to load the TDGSS library during system startup, message encryption is
thus disabled.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Check if the TDGSS package is installed properly on the system.

6696 Unexpected response from RCT.
Explanation: RSG received an unexpected response message from RCT. This is a protocol error.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Re-establish the connection to the replication group and re-try the operation.

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