Teradata SQL Error and Failure Codes from Error 9236 To 9246

9236 Connect Through has been revoked for PROXYUSER %VSTR.
Explanation: The Connect Through privilege for the Proxy User has been revoked.
Generated By: OPD modules.
For Whom: End User.
Remedy: Reissue the SET QUERY_BAND statement with a valid proxy user.

9238 Cannot DROP a user that is a ProxyUser in a Connect Through privilege.
Explanation: The user tried to drop a user which is defined as a Proxy User in a Connect Through privilege.
Generated By: OPD modules.
For Whom: The DBA and the End User.
Remedy: Revoke the Connect Through privilege(s) for the user, as shown by SEL * FROM DBC.CONNECTRULES.
Resubmit the DROP USER request.

9239 Cannot modify the logon user when in a proxy connection.
Explanation: The MODIFY USER statement cannot be used for the logged on user when the session is in a proxy connection.
Generated By: OPD modules.
For Whom: The DBA and the End User.
Remedy: Do not submit the MODIFY USER statement when in a proxy connection.

9240 Cannot alter the protection mode of a Java UDF/XSP to NOT PROTECTED.
Explanation: The EXECUTE NOT PROTECTED option is not valid for a Java UDF/XSP. Only EXECUTE PROTECTED
is permitted.
Generated By: RES modules.
For Whom: End User.
Remedy: Use the PROTECTED option instead with a Java UDF/XSP.

9241 Check output for possible warnings encountered in Installing or Replacing a JAR.
Explanation: After Installing or Replacing a Jar, the content of the installed/replaced Jar was displayed.
Generated By: CUFTsk
For Whom: Java XSP/Java UDF developer
Remedy: Check if the Jar’s content was correct.

9242 The partitioning expression references a column that is not defined for this table.
Explanation: This error occurs when an attempt is made to CREATE or ALTER a PPI table with referential integrity, and
the partitioning expression includes a column belonging to the parent table.
Generated By: OPT modules.
For Whom: System Support Representative.
Remedy: Rewrite the table definition so that the partitioning expression only references columns defined in the table.
Partitioning on columns defined in parent tables of referential integrity references is not supported.

9243 Field mode is not supported in FastExport.
Explanation: This error occurs when trying to execute a statement in field mode for FastExport.
Generated By: pardrivr.c
For Whom: End User.
Remedy: Do not use field mode in FastExport.

9244 Unable to revalidate PPI table header.
Explanation: While checking the table header of the specified character PPI table or join index during an ALTER TABLE
with the REVALIDATE PRIMARY INDEX option, a change in the PPI collation was detected. The PPI collation is the session
collation that was in effect at the time the PPI was created, and defines ordering of character data for comparisons
within the partitioning expression.
With a change in the definition of the PPI collation, it is likely that some rows will be incorrectly partitioned, and must be moved to their correct partitions. If not, incorrect results may result from queries involving partition elimination. This error can also occur upon back-down from a minor release of Teradata to an earlier minor release, when there is a difference in the definition of Unicode character set between the two releases (additional code points are defined in the later release), and the partitioning expression include Unicode character expressions or literals.
Generated By: OPT modules.
For Whom: End User and System Support Representative.
Remedy: Re-run ALTER TABLE … REVALIDATE PRIMARY INDEX with the option to correct partitioning errors in the
table, namely, adding either the ’WITH DELETE’ or ’WITH INSERT [INTO]’ phrase. These options will move incorrectly
partitioned rows into their correct partitions and either delete or save rows that belong to no partition (are undefined by the partitioning expression). If the error is due to a difference in the Unicode character set definition, then the ’WITH DELETE’ option must be used. If the partitioning expression contains character literals that are undefined at the current release, then revalidation is not an option, and this error will still occur when the ’WITH DELETE’ option is specified. If full revalidation in this manner is not an option, an INSERT … SELECT with no WHERE clause predicates into a new table may be done.

9245 The maximum number of concurrent allowable Variant_Type UDT instances has been exceeded.
Explanation: The maximum number of concurrent instances of Variant_Type UDTs has been exceeded. Current logic
supports up to 32 concurrent instances.
Generated By: Resolver.
For Whom: End User.
Remedy: Resubmit request with less Variant_Type UDTs.

9246 Incorrect usage of Variant_Type parameters: %VSTR
Explanation: This error occurs due to either: – the maximum number of allowable Variant_Type UDT input parameters
being exceeded. – Number of parameters for Variant_Type cannot be more than 128. – An attempt being made to define a
result parameter as a Variant_Type UDT. – The first expression is a LOB,UDT, or LOB-UDT expression. Note: Current logic
supports up to 8 Variant_Type UDT input parameters.
Generated By: Resolver.
For Whom: End User.
Remedy: Resubmit request with less Variant_Type Input Parameters UDTs

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