Teradata SQL Error and Failure Codes from Error 5615 To 5626

SQLServerF1_Header_Small

5615 The %VSTR right cannot be granted to a %FSTR.
Explanation: The CREATE ROLE, DROP ROLE, CREATE PROFILE, DROP PROFILE, CREATE USER and DROP USER
rights may not be granted to a role or database.
Generated By: opdgrant module.
For Whom: End User.
Remedy: Replace right with another legitimate right, or change grantee to a user.

5616 The user is not authorized to grant or revoke role ’%VSTR’.
Explanation: Only the user DBC, or a user granted a role WITH ADMIN OPTION, or a user with an applicable role (current
role or a role nested within it) that is granted a role WITH ADMIN OPTION has the right to GRANT/REVOKE the role
to/from another user or role.
Generated By: OPD modules.
For Whom: End User.
Remedy: Have an authorized user re-submit the request.

5617 Grantee is not a valid user or role.
Explanation: A role grantee may only be a user or another role.
Generated By: OPD modules.
For Whom: End User.
Remedy: Re-submit the request with a valid user or role as a grantee.

5618 A role may not be granted to itself.
Explanation: A role grantee may only be a user or another role.
Generated By: OPD modules.
For Whom: End User.
Remedy: Re-submit the request with a valid user or role as a grantee.

5619 Role nesting exceeded single-level.
Explanation: Multiple levels of role nesting is not allowed, i.e., only parent-child role nesting relationships are allowed.
Generated By: OPD modules.
For Whom: End User.
Remedy: Re-submit the request with a grant that results in a single-level role nesting.

5620 Role ’%VSTR’ does not exist.
Explanation: The user referred to a role as %VSTR. That role does not exist.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Correct the Teradata SQL statement by using a valid name for the role and re-submit the request.

5621 User has not been granted a specified role.
Explanation: The role has not been previously granted to the current user.
Generated By: OPD modules.
For Whom: End User.
Remedy: Specify a role that has previously been granted to the user and re-submit the request.

5622 The user does not have the right to drop the specified role.
Explanation: The user does not have the proper access rights to execute this request. This statement is authorized for: a)
DBC, b) any user granted the role WITH ADMIN OPTION, c) any user with an applicable role (current role or a role nested
within in) that is granted the role WITH ADMIN OPTION, d) any user granted DROP ROLE right.
Generated By: RES and OPT modules.
For Whom: End User.

5623 User or role ’%VSTR’ does not exist.
Explanation: The user referred to a user or role as %VSTR. That user or role does not exist.
Generated By: RES module.
For Whom: End User.
Remedy: Correct the Teradata SQL statement by using a valid name for the user or role and re-submit the request.

5624 The Branch offset is very long.
Explanation: The query has generated a branch whose displacement is greater than 2^18 on a SPARCV9 system.
Generated By: GNX module.
For Whom: End User.
Remedy: Run the quey in Interpreter mode.

5625 Column “%VSTR” has duplicate values for COMPRESS.
Explanation: The list of compress value defined for a column contains duplicates.
Generated By: SYN modules.
For Whom: End User.
Remedy: Examine and correct the SQL statement to eliminate duplicate compress values.

5626 An invalid role identifier is found in DBC.RoleGrants table.
Explanation: A search of DBC.RoleGrants has found a role id that does not have a corresponding entry in DBC.Roles.
Generated By: MGC module.
For Whom: End User.
Remedy: Contact your support representative.

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