Teradata SQL Error and Failure Codes from Error 9419 To 9431

9419 Set session statement has defined more than one value name for a non-set constraint.
Explanation: A set session statement has been submitted which contains more than one value name for the same non-set
security constraint.
Generated By: Parser modules.
For Whom: User.
Remedy: Change the statement to include only a single value name

9420 A UDF defined for a security constraint does not exist or it is invalid.
Explanation: A security constraint has been assigned to a table which was an object of the DML statement. The constraint
defined a UDF which covered the action of the DML statement. Either the UDF could not be found because it had
been deleted or moved or the UDF had been changed so that it no longer met the requirements for a UDF written to enforce
the security policy of a constraint.
Generated By: RES module.
For Whom: End User.
Remedy: Double-check constraint function definitions and their C source codes and rectify any inconsistency. If there is
no inconsistency, determine if any constraint should be altered to add a missing constraint function.

9421 Duplicate constraint name has been specified in %VSTR statement.
Explanation: A statement has been submitted which constains a duplicate constraint name.
Generated By: RES module.
For Whom: End User.
Remedy: Re-submit the statement with only unique constraint names.

9422 Request size exceeds the maximum of 12500 characters
Explanation: The user specified a request that exceeds the specified limit.
Generated By: OPD
For Whom: End User
Remedy: The request size in bytes exceeds the limit

9423 Column ’%VSTR’ is not a constraint column.
Explanation: The user tried to grant an Override privilege on a column that is not a constraint column.
Generated By: RES
For Whom: End User
Remedy: Do not resubmit the request.

9424 Security column ’%VSTR’ cannot be renamed in a %FSTR.
Explanation: An alias is defined in the view or derived table definition for a security column in the base table.
Generated By: RES module.
For Whom: End User.
Remedy: Remove the alias and re-submit the statement.

9425 Row Level Security privilege cannot be granted to PUBLIC.
Explanation: The user tried to grant one of the following privileges to PUBLIC: CONSTRAINT DEFINITION CONSTRAINT
ASSIGNMENT OVERRIDE INSERT OVERRIDE SELECT OVERRIDE UPDATE OVERRIDE DELETE
Generated By: RES
For Whom: End User
Remedy: Do not resubmit the request.

9427 An Override Constraint privilege can only be granted on a protected table or constraint column.
Explanation: The following privileges can only be granted on a protected table: OVERRIDE INSERT CONSTRAINT
OVERRIDE SELECT CONSTRAINT OVERRIDE UPDATE CONSTRAINT OVERRIDE DELETE CONSTRAINT
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

9428 Security constraint %DBID is not set in the current session.
Explanation: The user must specify a session valuename for the non-nullable constraint column.
Generated By: Resolver.
For Whom: End User.
Remedy: Use SET SESSION CONSTRAINT to set a valuename for the

9429 Duplicate function name “%VSTR” within a security constraint.
Explanation: A security constraint can be defined with a user defined function (UDF) for each of the statement actions.
However, the name of each constraint UDF must be unique within the constraint definition.
Generated By: Parser Modules
For Whom: End User
Remedy: Change the duplicate UDF name in the statement to a unique name

9430 The database specified for the UDF “%VSTR” is invalid.
Explanation: A security constraint statement specifies a UDF for execution of the security policy which is not contained
in the SYSLIB database.
Generated By: Parser Modules
For Whom: User
Remedy: Change the UDF database to SYSLIB and re-submit the statement.

9431 Duplicate statement action within a security constraint.
Explanation: A security constraint can be defined with a statement action user defined function (UDF). However, only
one constraint UDF may be specified for each statement action.
Generated By: Parser Modules
For Whom: User
Remedy: Correct the duplicate statement action in the constraint DDL statement

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