Teradata SQL Error and Failure Codes from Error 9453 To 9463


9453 ALC is not supported with specified data type on column %VSTR.
Explanation: Algorithmic compression clause is supported on the following data types only: a)CHAR/GRAPHIC
Generated By: RES.
For Whom: End User.
Remedy: Remove the algorithmic compression clause on the data type.

9454 Compress Attribute cannot be changed on column ’%VSTR’ when table has data.
Explanation: ALTER TABLE cannot change the compress attribute on a column that has data. This is when either the old
or new compress attribute has ALC.
Generated By: RES.
For Whom: End User.
Remedy: Take a backup of data, delete it, change the compression attribute, and reload the data.

9455 ALC specification has invalid options: %VSTR.
Explanation: The algorithmic compression specification should coincide with below: a)DETERMINISTIC Flag b)NULL
with output parameter of VARBYTE f)Decompress UDF with input parameter of VARBYTE g)Column data type should be
compatible with decompress UDF output parameter type h)UDF input and output parameter length should be less than
column length i)The column CharSet should match with Compress UDF’s output parameter CharSet.
Generated By: RES.
For Whom: End User.
Remedy: Fix the problem, and submit the SQL again.

9456 Compression not possible
Explanation: The compression specification is unable to compress the input string. The error could be returned when 1.
Compressed string exceeds the length of the input string
WARNING: This error is only to be set for ALC fastpath compres s UDFs. In other cases setting this might result in undefined
Generated By: fast path UDFs
For Whom: End User.
Remedy: Possibly try different compression algorithm for the input.

9457 Override Update Constraint privilege is required for update of constraint column ’%VSTR’.
Explanation: Constraint columns can only be updated if the user has the OU privilege.
Generated By: RES module.
For Whom: User.
Remedy: Do not resubmit the request.
9458 Parameter style of UDF ’%TVMID’ is incompatible with security column’s nullability attribute.
Explanation: A constraint column’s nullability attribute must match up with its INSERT or UPDATE constraint function’s
parameter style as follows: Nullable – parameter style must be SQL. Non-nullable – parameter style must be TD
Generated By: RES module.
For Whom: User.
Remedy: The Security Administrator must correct either the

9459 The constraint being altered does not have a %VSTR function.
Explanation: An ALTER CONSTRAINT statement is trying to drop a constraint function that is not defined for the constraint.
Generated By: Parser Modules
For Whom: User
Remedy: Correct the invalid statement and re-submit the request.

9460 Source is a query referencing a protected table.
Explanation: If the source references a protected table, only ’CREATE TABLE <table2> AS <table1> … ;’ is legal. ’CREATE
TABLE <table2> AS (<subquery on table1>) … ;’ is illegal.
Generated By: Parser Modules
For Whom: User
Remedy: Do not re-submit the request.

9461 Default value cannot be defined on a set constraint.
Explanation: A statement assigning a constraint has been submitted. The statement attempts to define a default value
on a set constraint. The DEFAULT keyword is applicable to non-set constraints only.
Generated By: Parser modules.
For Whom: User.
Remedy: Remove the DEFAULT keyword from the set constraint

9462 Data type of range boundary is incompatible with the test value type.
Explanation: For a RANGE_N function or an ALTER TABLE, the data type of a range boundary in an EACH clause
must be compatible for casting to the data type of the test value, and not result in a precision loss. For example, casting of a
REAL number with digits to the right of of the decimal place, to an integer, would result in truncation of the fractional digits
and loss in precision.
Generated By: OPT modules.
For Whom: End User.
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the
RANGE_N function rules and resubmit the request.

9463 Invalid Options Parcel Length
Explanation: Request Options Parcel of an unexpected byte length was received by the parser. As of TD release 13.10 the
expected byte lengths follow. Note that the header lengths are included in these lengths (Standard is 4, alternate is 8).
Starting with Using the Using the this release standard parcel alternate parcel header header Any pre-12.0 14 18 12.0 15 19
13.10 19, or greader 23, or greater
Generated By: Pardrivr, Pfmutsr modules
For Whom: System Support Representative
Remedy: Correct the program and resubmit the request

Above are list of Teradata Errors or Failure Codes from Error 9453 To 9463 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.

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 *