Teradata SQL Error and Failure Codes from Error 9216 To 9235

SQLServerF1_Header_Small

9216 Source and target table definitions did not match.
Explanation: This error occurs when Source and Target tables differ in structure while copying the stats from Source
table to Target table.
Generated By: opdctat.c
For Whom: End User.
Remedy: correct the statement or match the table descriptions and resubmit.

9217 Attempt to access a down Table or Index
Explanation: A statement has attempted to access a table or index that has been set down. It is not currently accessible
for SQL statements.
Generated By: Parser.
For Whom: End User.
Remedy: Reset the down table or index status before resubmitting the SQL statement. Some of the ways to reset the
down status are: – ALTER TABLE SQL statement – Fast path DELETE ALL/ DROP table SQL statement – Rebuild the Table
– Restore the table from backup – Drop and recreate the index

9219 Query executed in degraded mode without using the index
Explanation: This is only a warning. The request has taken a degraded non-index access path as the index is either
down or has down regions in it.
Generated By: Opt modules
For Whom: End User
Remedy: Repair the down regions or reset the down status of the index, so that the query can take the index access path.

9220 Ruleset already exists for replication group.
Explanation: The used tried to create a replication ruleset with that name already existed for the replication group.
Generated By: RES modules
For Whom: End User.
Remedy: Examine the Teradata SQL statement and verify that the request is correct. Change the statement to specify a
different name and resubmit the request.

9221 Ruleset does not exist for replication group.
Explanation: The user referenced a ruleset that does not exist for the replication group.
Generated By: RES modules
For Whom: End User.
Remedy: Correct the Teradata SQL statement by using a valid name for the replication group. Correct the request and
resubmit it.

9222 LIKE/NOT LIKE pattern string length is too long.
Explanation: The used defined a rule with LIKE or NOT LIKE pattern string greater than the maximum allowable
length.
Generated By: RES modules
For Whom: End User.
Remedy: Shorten the match pattern string for the rule and resubmit the request.

9223 Conflict detected for an object rule defined.
Explanation: The user defined a rule with conflicting LIKE and NOT LIKE pattern string. For example,
CREATE REPLICATION RULESET Sales FOR MyRepGroup AS TABLE LIKE ’SalesDB.%’ AND NOT LIKE ’SalesDB.%’;
Generated By: RES modules
For Whom: End User.
Remedy: Correct the Teradata SQL statement and resubmit the request.

9224 Invalid SET SESSION SUBSCRIBER option is specified. It can either be ON or OFF.
Explanation: The option of the SET SESSION SUBSCRIBER is being checked in the resolver phase. The valid options are
ON and OFF. Otherwise, an error is returned to the user.
Generated By: RES modules
For Whom: End User.
Remedy: Correct and resubmit the request.

9225 Object name can not match capture rule from multiple replication groups.
Explanation: The object name of a DDL statement matches capture rule from more than one replication group.
Generated By: OPD/OPU modules
For Whom: End User.
Remedy: Correct ruleset definition to avoid duplicate rules defined in multiple replication groups, then resubmit the
request.

9226 Replicated table cannot contain %VSTR data type columns.
Explanation: The following data types are not supported for replication in this release: Array, Number.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the table definition(s) and resubmit the request.

9235 DBC is not supported as the trusted or proxy user.
Explanation: The DBC user cannot be set as the trusted user or the proxy user in the connect through privilege.
Generated By: OPD modules.
For Whom: End User.
Remedy: Specify a different user for the trusted user or proxy user.

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