Teradata SQL Error and Failure Codes from Error 9464 To 9473

9464 The operation failed because %VSTR is missing, run %FSTR.
Explanation: The operation failed because some object is missing.
Generated By: RES.
For Whom: End User.
Remedy: Run DIPUDT. Run DIPSYSFNC for TD_GETFUNCTIONCONTEXT function called in dip script.

9465 A DBQL diagnostic that prevents queries from executing is enabled.
Explanation: A DBQL diagnostic that prevents queries from executing is enabled.
Generated By: RES modules.
For Whom: End User.
Remedy: Contact your support representative.

9466 Concurrent change conflict on table — try again.
Explanation: During processing of a user’s transaction, another concurrent session had changed the table.
Generated By: RES modules.
For Whom: Internal error, users won’t see.
Notes: This error is similar to ERRTEQTABCHANGED, the difference in ERRTEQTABCHANGEDX is the info from DBC
tables was obtained by dirty read and not reliable. So, instead of returning the error to users, the request is internally resubmitted.
Remedy: Query will be automatically reparsed.

9467 The usage of security constraint “%FSTR” in the %VSTR is not allowed.
Explanation: The CREATE, or ALTER, statement contains an invalid usage of a security constraint. Security constraint
columns cannot be a component of: – a primary index definition – a primary key definition – a foreign key definition – a partitioning
expression – a UNIQUE constraint
Generated By: Parser Modules
For Whom: User
Remedy: Redefine the index/key definition without the security

9468 The usage of security constraint “%VSTR” in the CHECK constraint is not allowed.
Explanation: The CREATE, or ALTER, statement contains an invalid usage of a security constraint in a CHECK constraint
definition. Security constraint columns cannot be a component of an expression in a CHECK constraint.
Generated By: Parser Modules
For Whom: User
Remedy: Redefine the CHECK condition without the security

9469 A temporary or queue table definition cannot have any security constraint column.
Explanation: Security constraints are not allowed in the definition of a global temporary, volatile, or queue table. Queue
tables currently have a limitation that disallows a WHERE clause when a row is being CONSUMEd. This precludes the
addition of security constraint predicates when queue table rows are consumed.
Generated By: Parser Modules
For Whom: User
Remedy: Redefine the CREATE, or ALTER, statement without

9470 Warning: DBQL XMLPLAN encountered a problem %VSTR
Explanation: The DBQL XMLPLAN query logging feature encountered an unexpected problem.
Generated By: Parser and Dispatcher query logging modules.
For Whom: End User.
Notes: The request being logged is still executed despite the warning.
Remedy: Examine the logged XML document for further details.

9471 Algorithmic Compression feature not yet enabled.
Explanation: The algorithmic compression feature will be enabled only when the Dbscontrol internal flag
No13dotBackdown is set to TRUE.
Generated By: SYN/RES.
For Whom: End User.
Remedy: Enable No13dot0Backdown in Dbscontrol after understanding the limitations in so doing.

9472 Error in CREATE TABLE DDL, %VSTR.
Explanation: This error covers exceptions for creating a table using CT AS syntax from join indexes such as 1. Compressed
JI 2. JI with Value order 3. Hash Index
Generated By: OPD modules.
For Whom: End User.
Remedy: Consider the possibility of using CT-AS with subquery syntax.

9473 %VSTR has not yet been enabled.
Explanation: The indicated feature has not been enabled. The indicated feature and certain other features are enabled
only when the DBSControl general field No13dot0Backdown (65) is set to TRUE. If the feature is enabled, back down from
Teradata DBS 13.10 to Teradata DBS 13.0 without a sysinit is no longer allowed. After setting to TRUE, this general field
cannot be set back to FALSE. Some features that are not enabled until this general field is set to TRUE include algorithmic
compression, AT clause in CAST/conversion, time zone strings, and merge data blocks during full-file operations.
Generated By: SYN/RES.
For Whom: End User.
Remedy: Contact your Support Representative. Your Support Representative needs to contact the Global Support Center
to set the general field No13dot0Backdown (65) to TRUE in DBSControl when it is determined that being able to back
down from 13.10 to 13.0 without a sysinit is no longer required for this system.

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