Teradata SQL Error and Failure Codes from Error 9408 To 9418

SQLServerF1_Header_Small

9408 UDF “%VSTR” specified with an invalid function type.
Explanation: A security constraint option in the statement specifies a UDF for execution of the security policy which is
not a scalar function. Aggregate, table, or overloaded functions are not supported for implementation of a constraint security
policy.
Generated By: Parser Modules
For Whom: User
Remedy: Change the function definition or name to one that is a scalar function

9409 Invalid constraint name ’%VSTR’ defined in the statement.
Explanation: A statement has been submitted which contains a constraint name that does not exist. All security constraints
must be defined before they can be assigned to users, profiles or tables.
Generated By: Parser Modules
For Whom: User
Remedy: Define the named constraint or change the specified name to an existing

9410 Too many constraint columns are defined for the table.
Explanation: A create or alter table statement has been submitted which defines more constraints than are currently
allowed for a table. The maximum allowed is 5.
Generated By: Parser Modules
For Whom: User
Remedy: Reduce the number of constraints and re-submit the statement.

9411 Duplicate constraint name has been defined for a table.
Explanation: A create or alter statement has been submitted which contains a duplicate constraint name for the table. A
constraint can only be defined once in a table.
Generated By: Parser Modules
For Whom: User
Remedy: Drop or change the duplicate constraint name to make it unique within the

9412 Referenced constraint column does not exist in table.
Explanation: A Security Constraint column name which does not exist has been referenced in the statement.
Generated By: Parser Modules
For Whom: User
Remedy: Change the constraint name to one that does exist in the table and

9413 An invalid constraint name has been assigned to the user.
Explanation: A create/modify user statement has been submitted which constains an invalid security constraint name.
Generated By: Parser modules.
For Whom: User.
Remedy: Change the constraint name in the statement to one that

9414 A value name which does not exist has been defined for a security constraint.
Explanation: A statement assigned a constraint been submitted. The statement contains a non-existent value name for a
security constraint.
Generated By: Parser modules.
For Whom: User.
Remedy: Change the value name in the statement to one that

9415 More than one default value has been defined for a security constraint.
Explanation: A statement assigned a constraint has been submitted. The statement attempts to define more than one
value name as the default for the constraint.
Generated By: Parser modules.
For Whom: User.
Remedy: Change the statement to define only a single default value

9416 The same security name has been assgined more than once to a user.
Explanation: A create/modify user statement has been submitted which constains multiple instances of the same security
constraint name.
Generated By: Parser modules.
For Whom: User.
Remedy: Change the statement to define the security constraint only

9417 User has not been assigned the security credential ’%DBID(%VSTR)’.
Explanation: A set session statement has been submitted which contains a value name that is not assigned to the user.
Generated By: Parser modules.
For Whom: User.
Remedy: Change the statement to use an assigned value and re-submit

9418 The total number of %VSTR constraints assigned is over the limit.
Explanation: This error is returned when a CREATE USER, MODIFY USER, CREATE PROFILE, MODIFY PROFILE, or
SET SESSION CONSTRAINT statement exceeded the maximum allowable constraint assignments. Assignments are limited
to a total of 6 non-set and 2 set constraints per user or profile.
VSTR can be “non-set”, “set” or a null string.
Generated By: Parser modules.
For Whom: User.
Remedy: Change the statement to define a lesser number of security

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