Teradata SQL Error and Failure Codes from Error 9392 To 9407

9392 NONTEMPORAL operations are not allowed with triggered SPs.
Explanation: NONTEMPORAL operations are not allowed with triggered SPs.
Generated By: PAR modules.
For Whom: End user.
Remedy: Remove the NONTEMPORAL operations and resubmit the request.

9393 Diagnostic CURRENT VALIDTIME SELECT that uses the latest Date/Timestamp is applied on this Select.
Explanation: This is a warning message and not an error. When the CURRENT VALIDTIME SELECT diagnostic message
is displayed(with the diagnostic also on),the SELECT statement on Temporal tables uses current date/timestamp
instead of temporal date/temporal_timestamp.
Generated By: QRW modules.
For Whom: End user.
Remedy: Not an error. This message is for information only.

9400 The statement involves a Row Level Security functionality that is not supported.
Explanation: The submitted SQL statement involves a Row Level Security functionality that is not supported yet. This
error code is returned in the following instances in the first release(14.0) of RLS: a) Triggers involving a protected table, b)
Replication. c) Abort statement referencing a constraint column.
Generated By: Parser modules.
For Whom: End User.
Remedy: Discontinue use of the statement for the defined tables.

9401 Illegal operation on a table secured at row level.
Explanation: A data table under Row Level Security in a post 13.0 release was reverted (backed down) to a 13.0 release.
As RLS was introduced in 13.1, a reverted table will be exposed to unauthorized access if DMLs are allowed on it. The only
operation allowed on such a table is DROP TABLE.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

9402 The constraint object name “%VSTR” specified in the Create Constraint statement is a duplicate of an existing name.
Explanation: The submitted SQL statement contains a constraint name which already exists in the server.
Generated By: Parser Modules
For Whom: User
Remedy: Assign a different constraint name and re-submit the statement.

9403 The specified security constraint “%VSTR” does not exist.
Explanation: The constraint name specified in the statement does not exist in the dictionary tables.
Generated By: Parser modules
For Whom: User
Remedy: Change the constraint name in the statement to one that

9404 Duplicate value name “%VSTR” within a security constraint.
Explanation: A security constraint can be defined with multiple value names and their corresponding codes. However,
the name of each value must be unique within the constraint definition.
Generated By: Parser Modules
For Whom: User
Remedy: Change the duplicate value name in the statement to a unique name

9405 Duplicate value code for value name “%VSTR” within a security constraint.
Explanation: A security constraint can be defined with multiple value names and their corresponding codes. However,
the name and code of each value must be unique within the constraint definition.
Generated By: Parser Modules
For Whom: User
Remedy: Change the duplicate code in the constraint statement to a unique

9406 Invalid value code for value name “%VSTR” within a security constraint.
Explanation: A security constraint can be defined as either a smallint or a byte array data type. The value code specific
in the constraint statement is invalid for the defined data type. The acceptable value code for a smallint constraint type is
between 1 and 10000 inclusive. The acceptable value code for a byte array data type is an integer bit number which is
between 1 and 8 inclusive times the number of bytes in the constraint.
Generated By: Parser Modules
For Whom: User
Remedy: Change the value code to one which is not invalid and re-submit the statement.

9407 UDF specified in constraint option does not exist.
Explanation: A security constraint option in the statement specifies a UDF for execution of the security policy. The specified
function does not exist.
Generated By: Parser Modules
For Whom: User
Remedy: Correct the function name or add a database name so that the correct UDF is specified.

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