Teradata SQL Error and Failure Codes from Error 3217 To 3228

SQLServerF1_Header_Small

3217 The stored procedure returned a response that has an invalid state.
Explanation: This error occurs if the the phase of a result set request is not correct.
Generated By: Dispatcher.
For Whom: System Support Representative.
Notes: The phase of a returned result set is unexpected.
Remedy: Contact your support representative.

3219 A left-over dynamic resource was released upon detection.
Explanation: After request processing has concluded, all dynamic resources that were used should have been released.
Specifically, channels, semaphores, and groups. Here, one such dynamic resource was left-over. To avoid a resource leakage,
the left-over dynamic resource was released upon detection. Also, the associated SQL request text will be logged conditionally
through a distinct ERRDISODDBALLSQL (3215) log event entry.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Save the request that caused the problem, and contact your support representative.

3220 RCT program fault.
Explanation: A generic error code for RCT system fault.
Generated By: RCT modules.
For Whom: User.
Remedy: Check RCT.

3221 Replication group does not exist.
Explanation: While processing any RDDL requests, except ADD group, if the specified group or the group of the specified
table is not defined, an error is returned.
Generated By: RCT modules.
For Whom: User.
Remedy: Check RCT GDO file to see if the replication group has been defined.

3222 The specified table does not belong to any replication groups.
Explanation: While processing all table level RDDL requests, expect ADD table, if the specified table does not belong to
a replication group, an error is returned.
Generated By: RCT modules.
For Whom: User.
Remedy: Check RCT GDO file to see if the specified table has been added as an replicated table.

3223 This is an acceptable error.
Explanation: This is actually not an error. This is used internally in the RCT. User and other DBS components should not
receive this error.
Generated By: RCT modules.
For Whom: RCT
Remedy: None since this is not an error.

3224 Incorrect replication group or table status.
Explanation: While processing any RDDL requests, if the current state of the specified replication group or replication
table is not in the appropriate state for the RDDL request, an error is returned.
Generated By: RCT modules.
For Whom: User.
Remedy: Check RCT GDO file or TVM for the status of group or table.

3225 The ReConnect message doesn’t match the Connect message.
Explanation: One of the fields in the RepReConnect message doesn’t match the original RepConnect message for the
group.
Generated By: RCT modules.
For Whom: User.
Remedy: Check the CONNECT command for the replication group.

3226 The requested session is not indoubt.
Explanation: While committing or aborting a RDDL request, if the status of that particular group or table is not RCTIn-
Doubt, then an error is returned.
Generated By: RCT modules.
For Whom: User.
Remedy: Check RCT GDO file for the current status of the group or table.

3227 The specified table does not exist.
Explanation: The system does not recongnized the specified table.
Generated By: RCT modules.
For Whom: User.
Remedy: Check request.

3228 The Copy ReConnect message does not match the Copy Connect message.
Explanation: One of the fields in the Copy ReConnect message doesn’t match the original Copy Connect message for the
table.
Generated By: RCT modules.
For Whom: User.
Remedy: Check the Copy Connect command for the table.

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