Teradata SQL Error and Failure Codes from Error 9488 To 9498

SQLServerF1_Header_Small

9488 CREATE text for the specified constraint is too long for SHOW CONSTRAINT.
Explanation: The text that would be used in a single CREATE CONSTRAINT statement for the specified constraint is
too long to return via SHOW CONSTRAINT.
Generated By: OPT modules.
For Whom: End User.
Remedy: Do not re-submit the request.

9489 The specified audit frequency for a protected table is illegal.
Explanation: ’LAST’ and ’FIRST AND LAST’ cannnot be specified in a BEGIN LOGGING statement if the object under
audit is a protected table.
Generated By: Parser module.
For Whom: End User.
Remedy: Change the frequency to ’FIRST’ or ’EACH’ and

9490 The FOR CONSTRAINT clause may only be specified for auditing a protected table.
Explanation: The object of access logging must be a protected table if the FOR CONSTRAINT clause is specified.
Generated By: Parser module.
For Whom: End User.
Remedy: Do not re-submit the request.

9491 Statements that administer Row Level Security are not allowed in macros or stored
procedures.
Explanation: DDL and DCL statements for RLS administration will not be allowed to be defined in macros or stored
procedures.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the error and re-submit the request.

9492 The UDF “%VSTR” is already defined for the security constraint being altered.
Explanation: When trying to add a UDF for the security constraint the UDF name should be valid i.e. it must be unique
within the constraint definition.
Generated By: Parser Modules
For Whom: User
Remedy: Change the UDF name in the ALTER, statement to a
9493 The statement action %VSTR is already defined for the security constraint being altered.
Explanation: When trying to add a UDF with a statement action for the security constraint, that action should not be
already defined for the constraint. If it is defined then a ’REPLACE’ action should be used instead.
Generated By: Parser Modules
For Whom: User
Remedy: Change the ADD option to a REPLACE option or change

9494 The column level privilege cannot be granted on the security constraint %VSTR.
Explanation: It is not allowed to grant any column level DML privilege i.e. INSERT, UPDATE and SELECT on a column
defined as a RLS constraint.
Generated By: RES.
For Whom: End User.
Remedy: Do not re-submit the request.

9495 Constraint column ’%VSTR’ cannot be defined with any column attribute.
Explanation: A security constraint column cannot have any of the column attributes such as compress, default, unique
etc.
Generated By: RES.
For Whom: End User.
Remedy: Remove any column attribute from the constraint column

9496 Cannot add a constraint column to a protected table with a join or hash index.
Explanation: Constraint columns cannot be added to a protected table with a join index or a hash index because the join
or hash index definition has to include all constraint columns in the table.
Generated By: RES module.
For Whom: User.
Remedy: Drop the join or hash index before adding a constraint

9497 The datatypes of the constraint ’%VSTR’ and an input parameter of the constraint function
’%TVMID’ do not match.
Explanation: The datatype of the constraint function’s input parameter must be the same as the datatype of the constraint.
Generated By: RES module.
For Whom: User.
Remedy: Change the datatype of the UDF’s input paramater to be the same as the datatype of the security constraint.

9498 The XML plan feature is disabled.
Explanation: The user specified IN XML when the XML PLAN feature is disabled through the internal Dbscontrol flag,
DisableXMLPLANLogging.
Generated By: PAR module.
For Whom: End User.
Remedy: Re-submit the statement with feature enabled.

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