Teradata SQL Error and Failure Codes from Error 6654 To 6666

SQLServerF1_Header_Small

6654 RSG could not send data to MDS
Explanation: When RSG attempted to send data to MDS, a failure was returned by MDS.
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/
tdconfig/rsg.

6655 RSG received invalid message class
Explanation: The class field of a message header is not of the expected type SYSMSGREPCLASS. Message was placed
on either the RSG_CONTROL_MBOX or on one of the RSG sender task mailboxes. Error is recognized in RsgPSProcessMsg,
or RsgCTRLProcessMsg and occurs because msgrxseg() in the main processing loop of the control task or one of
the sender tasks returned an unknown message class in the message header.
Generated By: RSG
For Whom: TD System Administrator

6656 RSG received invalid message kind
Explanation: The kind field of a message header was not the expected type. Message was placed on either the
RSG_CONTROL_MBOX or on one of the RSG sender task mailboxes. Error is recognized in Primary sender, or RSG Control
task which is called after a msgrxseg() in the main processing loop of the control task or one of the sender tasks.
Generated By: RSG
For Whom: TD System Administrator

6657 RSG received invalid message type from RSI
Explanation: RSI sent a message to an RSG receiver and the message type was not expected. Occurs in RsgServiceReq
(synchronous response is needed) or RsgServiceMsg (no response or an asynchonous response is needed).
Generated By: RSG (Relay Services Gateway) vProc
For Whom: System Administrator
Remedy: Verify RSI functionality

6658 RSG received an unexpected response to TD message
Explanation: RSG sent a message to TD which required a response. The response was not the correct type.
Generated By: RSG (Relay Services Gateway) vProc
For Whom: System administrator

6659 RSG could not allocate a TIB for a transaction
Explanation: RSG attempted to allocate a TIB data structure for a transaction ID or a utility ID and none is available.
There is a limit of 500 active TIB’s on a node, this limit was exceeded.
Generated By: RSG (Relay Services Gateway) vProc
For Whom: System administrator
Remedy: Limit the number of active transactions to 500

6660 RSG did not find the TIB information for this transaction
Explanation: RSG attempted to locate TIB data structure for a transaction ID. This error occurs when more than 500
transactions are active on the node, or when TIB information for the transaction has been lost.
Generated By: RSG (Relay Services Gateway) vProc
For Whom: System Administrator
Remedy: None.

6661 Incomplete connection processing to this Replication group
Explanation: RSG data connections wait for RepConnect/RepCopyConnect messages in the control command before
they can complete their processing. If the RepConnect/RepCopyConnect messages do not arrive in 1 minute, an error is
return by the message subsystem as the awaiting messages timed out.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Correct the control connection and re-establish connection to the replication group.

6662 Tables containing Large Objects and User Defined Data Types cannot be copied
Explanation: There was an attempt to run table copy operation on a table that contains either large objects or user
defined data types
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Avoid running Table copy on a table that has LOBs/UDTs

6665 RSG failed to locate the TD AMP Worker Task’s well-known mailbox
Explanation: RSG attempted to locate the well-known mailbox for the TD AMP worker task. The call to tosgdoget()
returned a count of zero AMPs.
Generated By: RSG (Relay Services Gateway) vProc
For Whom: System Administrator
Remedy: Determine the problem within the Teradata system

6666 The RSG configuration file is not accessible (/etc/opt/teradata/tdconfig/rsg/rsg.cfg)
Explanation: RSG has attempted to open the Linux configuration file for reading and the open failed. File is located in
/etc/opt/teradata/tdconfig/rsg and the name is rsg.cfg.
Generated By: RSG Control task during startup
For Whom: System administrator
Remedy: Add the rsg_config_file or verify the permissions of the file

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