Teradata SQL Error and Failure Codes from Error 6606 To 6653


6606 Not enough space was provided to receive the data into
Explanation: The RCI receive interface relies on the caller providing enough space to receive data as required. The
length parameter is used to make that determination. If too small an area is provided the data will be returned but truncated
to the maximum length.
Generated By: Replication Services Call Interface (RCI)
For Whom: RSG (Relay Services Gateway)

6607 Replication internal error (see traceback)
Explanation: One of the RSG/RCI software’s many sanity checks has failed, indicating an internal inconsistency in data
or processing state. This error causes a system restart.
Generated By: RSG/RCI software
For Whom: User.
Notes: One of many fatal error conditions detected by sanity checks in Replication software could have caused this error
message. Because this error is non-specific, it is necessary to qualify any error with the associated traceback.
Remedy: Contact your Support Representative. Save the crashdump for offloading. Have all traceback information
ready. Then contact your Support Representative.

6608 Not all changed rows have been seen for Transaction
Explanation: An Control command such as a Phase 1 Vote was submitted to the RCI interface for a transaction for which
the change rows seen did not match the expected row count as provided in the control message.
Generated By: RSG/RCI software
For Whom: RSG (Relay Services Gateway)

6609 Close out Batch running out of resources
Explanation: The resources used by this batch is running low. This is a request to close out the asynchronous batch now.
However the current transaction will be accepted. The resource in question could be spool space, group IDs channel IDs,
semaphores and the maximum number of transactions allowed for a batch.
Generated By: RSG/RCI software
For Whom: RSG (Relay Services Gateway)

6610 The commit sequence number is invalid
Explanation: The commit sequence number for this replicated transaction is zero. Zero is not allowed for a commit
sequence number for asynchronous batch transactions.
Generated By: RSG/RCI software
For Whom: RSG (Relay Services Gateway)

6611 Stop sending change rows for transaction
Explanation: This is a request by TD software to ask RS to not send anymore change rows for this synchronous transaction
until a RepTrCOntinue message is received by RCIRxCtrl for the specified transaction. This will happen if AMPs cannot apply the change rows as fast as RS can send them. It usually means that the AMPs are very busy doing other work or
the transaction is being blocked by a lock it is waiting for.
Generated By: RSG/RCI software
For Whom: RSG (Relay Services Gateway)

6612 Still unfinished transactions for batch
Explanation: Means there are still asynchronous immediate transactions in the batch that have not seen a RepPhase2 or
RepAbortTran control message.
Generated By: RSG/RCI software
For Whom: RSG (Relay Services Gateway)

6650 RSG could not fork send or receive task
Explanation: RS Gateway vProc Control Task could not spawn a Primary Send, or Receive task.
Generated By: RSG
For Whom: System Administrator
Remedy: Determine why Linux will not allow RSG to spawn processes

6651 RSI interface did not respond
Explanation: Not used. RSG simply retries the RSI startup routine until it succeeds.
Generated By: RSG (Relay Services Gateway) vProc
For Whom: System Administrator
Remedy: None required

6652 Not currently in use
Explanation: Not used.
Generated By: Not currently generated.
For Whom: No user.
Remedy: None required

6653 Call to RsiServer failed in RSG
Explanation: A receiver task in RSG called to RsiServer and received a failure.
Generated By: RSG (Relay Services Gateway) vProc
For Whom: System Administrator
Remedy: Diagnose the communication problem by viewing the log files located in the directory /etc/opt/teradata/

Above are list of Teradata Errors or Failure Codes from Error 6606 To 6653 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.

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 *