Teradata SQL Error and Failure Codes from Error 9204 To 9215

SQLServerF1_Header_Small

9204 The role has not been granted to the proxy user.
Explanation: The proxy user has not been granted connect through privilege using the role.
Generated By: OPD modules.
For Whom: End User.
Remedy: Use a role in the CONNECT THROUGH privilege for the proxy user and resubmit the request.

9205 ProxyRole must be a role in the connect through privilege.
Explanation: The role must be a role in the connect through privilege.
Generated By: OPD modules.
For Whom: End User.
Remedy: Use a role in the CONNECT THROUGH privilege for the proxy user and resubmit the request.

9206 Setting both a session and txn proxy user at the same time is not supported.
Explanation: A proxy user can be set by the session query band or the transaction query band but not both at the same
time.
Generated By: OPD modules.
For Whom: End User.
Remedy: Correct the query band statement and resubmit.

9207 PROXYROLE can only be set in a proxy connection.
Explanation: The PROXYROLE can only be set when in a proxy connection.
Generated By: OPD modules.
For Whom: End User.
Remedy: Correct the query band statement and resubmit.

9208 SET ROLE is not supported in a proxy connection.
Explanation: The SET ROLE statement cannot be used when the session is in a proxy connection.
Generated By: OPD modules.
For Whom: End User.
Remedy: Use the query band PROXYROLE name/value pair to set a role.

9210 COMPILE ONLY operation not permitted on a Java UDF/XSP.
Explanation: The COMPILE ONLY option is not valid for a Java XSP or UDF, because there are no source files to compile.
The COMPILE option is permitted.
Generated By: OPD and RES modules.
For Whom: End User.
Remedy: Use the COMPILE option instead with a Java XSP/UDF.

9211 Session mode does not match PPI session mode.
Explanation: An operation on a character partitioned primary index was attempted that is not allowed because the PPI
was created in a session with transaction semantics (ANSI or Teradata) which do not match the session mode of the
requested operation.
Generated By: OPT modules.
For Whom: End User.
Notes: In ANSI mode, strings are by default CASESPECIFIC, while the default in Teradata mode is NOT CASESPECIFIC.
The mode in effect when partitioning is defined or altered affects how comparison operations in a character partitioned
primary index are evaluated. The PPI session mode of the permanent table or join index can be looked up in column
SessionMode of DBC.IndexConstraints.
Remedy: Retry the operation using the same transaction semantics as were in effect when the PPI was created or last
altered.

9212 Illegal use of %DBID.%TVMID. The table or join index has a type of partitioning not supported
in the current release.
Explanation: A partitioned table or join index defined in a later release with a form of partitioning not supported in the
current release may not be used. This situation can occur upon a back down from a later release to the current release. The
only operations that may be performed on the table in the current release are to drop it or to INSERT SELECT its rows to
another table.
Generated By: RES modules.
For Whom: End User.
Remedy: All references to the specified table or join index should be removed from the SQL request.

9213 Connect Through privilege for %VSTR not found.
Explanation: No connect though privilege was found for the proxy user through the trusted user.
Generated By: OPD modules.
For Whom: End User.
Remedy: Verify that the correct names were used.

9214 Duplicate proxy user name %VSTR.
Explanation: Proxy user names granted connect through privilege to a trusted user must be unique. Granting both a
permanent user and an application user with the same name to a trusted user is not supported.
Generated By: OPD modules.
For Whom: End User.
Remedy: Use a unique name for the proxy user.

9215 Maximum roles for proxy user %VSTR exceeded.
Explanation: The addition of these roles for the proxy user causes the number of roles for the user to exceed the 15 role
limit.
Generated By: OPD modules.
For Whom: End User.
Remedy: Use REVOKE CONNECT THROUGH to remove roles from the privilege for the proxy user.

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