Teradata SQL Error and Failure Codes from Error 6667 To 6681

SQLServerF1_Header_Small

6667 Contents of RSG configuration file are incorrect
Explanation: RSG read the configuration file and found a keyword that is not correct. File is located in /etc/opt/teradata/
tdconfig/rsg and the name is rsg.cfg. The following keywords are expected: MDSGWYNODE, RSGMASTERNODE
and DEBUGTRACE.
Generated By: RSG Control task during startup
For Whom: System administrator
Remedy: Correct the contents of the rsg_config_file.

6670 An RSG informational event was logged.
Explanation: This is an informational message which will be logged to the /var/log/message file and the console without
causing a TPA reset. The specific information is encoded within the event message.
Generated By: RSG
For Whom: System administrator
Remedy: This message is for information only.

6671 Invalid protocol.
Explanation: A protocol error was detected due to an unexpected message class or kind. This message could be sent
between RSG tasks, between an AMP and RSG, or between the intermediary and RSG.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Re-establish connection to the replication group.

6672 Invalid group identifier.
Explanation: The group context cannot be found.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Make sure the group identifier is valid.

6673 Invalid security token.
Explanation: The security token provided is invalid.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Make sure the security token is correct.

6674 RSG work queue storage exhausted.
Explanation: The internal storage structures that are used by the RSG to enqueue transactions that are ready to be sent
to the intermediary has reached its capacity. This condition can occur when the replication intermediary has disconnected from the RSG, causing a transmission backlog to accumulate. When this condition occurs, transactions that are awaiting
transmission of their data to the replication intermediary may be aborted.
Generated By: RSG
For Whom: System administrator or end user
Remedy: Insure that the intermediary (replication transport subsystem) is operational and then rerun the failed transaction.

6675 Exceeded maximum number of request-level aborts.
Explanation: A request was aborted in a session that is operating in ANSI transaction mode, but 5 requests is the same
transaction have already been aborted. The RSG can only support 5 request-level aborts per transaction. Therefore, the
transaction has been aborted.
Generated By: RSG
For Whom: End User
Remedy: Correct the application as necessary to enable it to run to completion with not more than 5 request aborts.

6676 Command connection to this Vproc is invalid.
Explanation: The command connection can only be done to the designated RSG Vproc i.e the highest numbered RSG
Vproc.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Make sure the command connection is sent to the designated RSG Vproc.

6677 Data connection to this Vproc is invalid.
Explanation: There is an attempt to resend data connection following a disconnect to an RSG Vproc, that is NOT the
same as the previous data connection RSG Vproc.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Make sure the data connection is sent to the RSG Vproc, where the data connectoin was first made

6680 Invalid table copy context.
Explanation: The table copy context is not found.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Make sure the table identifier provided for the copy operation is valid.

6681 No data connection.
Explanation: The CDA data connection does not exist.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Re-establish the apply connection to the replication group and re-try the operation.

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