Teradata SQL Error and Failure Codes from Error 5904 To 5931

5904 Replication group does not have the appropriate status for this RDDL statement.
Explanation: Each RDDL statement has it own rule about the replicated group status. To alter a replication group, its
status must not be “Terminated”. To drop a replication group, its status must be null, suspended or terminated. If the replication
group does not have the appropriate status, then an error is returned.
Generated By: RES modules.
For Whom: End User.
Remedy: Make sure the replication group status is valid for the particular RDDL statement.

5905 Invalid replication group ID specified.
Explanation: The RCT submitted an internal replication statement using an invalid replication group ID.
Generated By: RES modules.
For Whom: RCT/End User.
Remedy: Correct the internal replication statemenet by using a valid ID for the replication group and resubmit the
request.

5906 Concurrent change conflict on replication group — try again.
Explanation: During processing of the user’s transaction, another user changed the replication group.
Generated By: OPD modules.
For Whom: End User.
Remedy: Resubmit the transaction.

5907 Table list may not be specified for the RDDL statement.
Explanation: Table list may not be provided for the Initiate, Terminate, Fail or Reconnect RDDL statements by the RCT.
Generated By: RES modules.
For Whom: RCT.
Remedy: Check table list.

5908 Table does not belong to the replication group.
Explanation: The specified table does not belong to the replication group.
Generated By: RES modules.
For Whom: RCT.
Remedy: Check the specified table.

5909 Replicated tables for change data apply may not contain identity columns.
Explanation: Replicated tables for change data apply may not contain identity columns.
Generated By: RES modules.
For Whom: End User/RCT.
Remedy: Drop the identity columns and resubmit the request.

5910 A table cannot be referenced more than once in a replication DDL statement.
Explanation: A table cannot be referenced more than once in a create or alter replication group statement.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct and re-submit the statement.

5916 ALL, EXTERNAL, or NULL keyword in SET ROLE is non ANSI.
Explanation: ANSI does not allow the ALL, EXTERNAL or NULL keyword in the SET ROLE statement.
Generated By: SYN modules.
For Whom: User.
Remedy: If script is to be full ANSI compliant, change the indicated statement.

5920 Select and consume: ’%VSTR’.
Explanation: The request contains a syntax error. ’%VSTR’ identifies the syntax problem.
Generated By: Resolver modules.
For Whom: End User.
Notes: This error message is used as a generic message to catch various syntax errors in the SELECT AND CONSUME
request.
Remedy: Correct the syntax and resubmit the request.

5921 A SELECT AND CONSUME statement cannot be combined with a
Update/Delete/UpSert/Merge statement in a request.
Explanation: The multi-statement request contains UPDATE/DELETE/UPSERT/MERGE combined with SELECT
AND CONSUME statements and they are referring to the same queue table.
Generated By: RES modules.
For Whom: End User.
Remedy: Split the request into multiple requests.

5930 External role ’%VSTR’ may not be granted in the database.
Explanation: An external role may only be granted (assigned) to users in the Directory. It may not be granted in the
database.
Generated By: RES module.
For Whom: End User.
Remedy: Assign the external role in the Directory.

5931 Illegal operation on EXTUSER.
Explanation: SQL statements may not reference EXTUSER.
Generated By: RES module.
For Whom: End User.
Remedy: Replace EXTUSER with a valid user/database and re-submit request.

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