Teradata SQL Error and Failure Codes from Error 9474 To 9487

SQLServerF1_Header_Small

9474 SQL cannot be captured for replication. Reason: %VSTR.
Explanation: This error covers exceptions for capturing SQL for replication.
Generated By: OpuRSSQL modules.
For Whom: End User.
Remedy: One of the following actions can be taken depending on the reason. 1. Establish connection for replication
group in maximum protection mode. 2. Rewrite the SQL and resubmit the request. 3. If SQL can’t be rewritten, submit it
with OVERRIDE REPLICATION ON on the primary and apply the same manually on the subscriber.

9475 Non-deterministic UDFs/UDMs not allowed in inserted column value(s).
Explanation: Non-deterministic UDFs/UDMs can not be used to 1.) For creating a PI column value in a simple insert
statement like, insert t1 (NUDF(1,10),…) 2.) For insert/update of column(PI or non-PI) value(s) through mload.
As the non-deterministic UDFs/UDMs produces inconsistent results in this case.
Generated By: OptIns, OphEdIns, OphEdUpd
For Whom: End User.
Remedy: Use insert select if you have to use non-deterministic UDFs/UDMs in PI columns insert into t1 select
(NUDF(1,10),…);

9476 Request Cache is corrupted. Avoiding the Cache Path if possible. Purge the Cache or Restart
DBS to fix.
Explanation: This warning is generated when due to some unknown problem request Cache is corrupted. When the
request Cache corruption is identified Request Cache will be bypassed and the query will be parsed each time.
Generated By: PAR modules.
For Whom: End User.
Remedy: Purge the Cache. If the problem persists restart the database.

9477 A column must not occur more than once in a column partition.
Explanation: A column must not be specified to occur more than once in a column partition.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9478 Table must be column partitioned.
Explanation: The table referenced in this statement must be column partitioned.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit

9479 Too many column partitions.
Explanation: An ALTER TABLE statement attempted to add another column partition to a column-partitioned table but
the number of column partitions specified by the user plus three exceeds the maximum allowed for the column partitioning
level.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9480 ROWID must be specified with an alias for a column-partitioned join index.
Explanation: The system-derived column ROWID with an alias must be specified in the select expression list of a CREATE
JOIN INDEX statement when column partitioning is specified for the join index. The name ROWID must not be referenced
in the column grouping if column grouping is specified in the COLUMN clause of the PARTITION BY clause; use
the alias instead.
Generated By: RES module.
For Whom: End User.
Remedy: Specify an alias for ROWID in the select expression list and, if column grouping is specified in the COLUMN
clause of the PARTITION BY clause and you want to reference it in the grouping clause, reference its alias (not ROWID) in
the column grouping and resubmit.

9481 Target table must be a table with no primary index when a HASH BY or LOCAL ORDER BY
clause is specified.
Explanation: The target table must be a table with no primary index when a HASH BY or LOCAL ORDER BY clause is
specified for an INSERT-SELECT statement.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9482 DROP RANGE/ADD RANGE clause has no corresponding level that is a RANGE_N function.
Explanation: For an ALTER TABLE statement altering ranges, the first alter ranges clause (DROP RANGE and/or ADD
RANGE) when it doesnt specify a specific level defaults to apply to the first level that has a partitioning expression consisting
solely of a RANGE_N function but no such level occurs in the existing partitioning. Or, if not the first alter ranges
clause, it defaults to apply to the next level after the default or specified level of the preceding alter ranges clause that has a
partitioning expression consisting solely of a RANGE_N function but no such level occurs in the remaining levels of existing
partitioning.
Generated By: RES module.
For Whom: End User.
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the multilevel
partitioning rules and resubmit the request.

9487 The constraint ’%DBID’ does not have a function defined for %VSTR operations.
Explanation: The query involves access of protected data and a constraint function controlling the query is not recognized
by the system. Probable causes are: a) no constraint function is defined for the statement action (INSERT, SELECT, UDPATE, or DELETE), b) there is some incompatibility between the SQL definition of the constraint UDF and the C language
definition of the UDF routine. A constraint UDF must be defined for the constraint before the operation is permitted.
Generated By: RES module.
For Whom: User.
Remedy: Correct the error and re-submit the request.

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