Teradata SQL Error and Failure Codes from Error 5714 To 5726

5714 Invalid partitioning expression for PARTITION BY.
Explanation: A partitioning expression must be deterministic and based on one or more columns in the table (these columns
are called the partitioning columns). Conditional expressions in a partitioning expression which compare character
data must not contain columns or expressions using CHARACTER SET KANJI1 or KANIJSJIS. Expressions and columns
referenced in a partitioning expression must not have BLOB, CLOB, or user-defined data types. It must not contain built-in
functions (such as TIME, ACCOUNT, etc.) other than DATE, CURRENT_DATE, and CURRENT_TIMESTAMP. It must also
not contain user-defined functions, the RANDOM function, aggregate functions (such as COUNT, AVERAGE, etc.),
grouped-row OLAP functions (such as MAVG, MSUM, etc.), attribute functions (BYTES, CHARACTERS, FORMAT, etc.),
HASHAMP function, or HASHBAKAMP function. ROWID system-derived columns, PARTITION[#Ln] system-derived
columns , set operators, and subqueries are not allowed. Certain uses of EXTRACT, CAST, Teradata conversion, and AT
clause are also not allowed when they are not deterministic. The partitioning expression may contain HASHROW and
HASHBUCKET functions.
Generated By: RES/OPD/GEN modules.
For Whom: End User.
Notes: Other limits will be exceeded (such as the request text size limit) before this limit is exceeded.
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the partitioned
primary index rules and resubmit the request.

5715 PARTITION BY CASE_N defines more than 2147483647 partitions.
Explanation: For a CREATE TABLE or ALTER TABLE statement, a partitioning expression that is the CASE_N function
must not define more than 2147483647 partitions.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Notes: Other limits will be exceeded (such as the request text size limit) before this limit is exceeded.
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the partitioned
primary index rules and resubmit the request.

5716 PARTITION BY RANGE_N defines more than %VSTR partitions.
Explanation: For a CREATE TABLE or ALTER TABLE statement, a partitioning expression that is the RANGE_N function
with INTEGER data type must not define more than 2147483647 partition (including the NO RANGE, UNKNOWN,
and NO RANGE OR UNKNOWN partitions if specified). In this case, the value for VSTR is “2147483647”. Note that, for 2-
byte single-level partitioning, the RANGE_N function cannot not define more than 65533 range partitions (otherwise, it
would be 8-byte partitioning). For 2-byte single-level partitioning, the total number of partitions defined can be up to 65535
if both the NO RANGE and UNKNOWN partitions are defined.
For a CREATE TABLE or ALTER TABLE statement, a partitioning expression that is the RANGE_N function with BIGINT
data type must not define more than 9223372036854775805 range partitions (not including the NO RANGE, UNKNOWN,
and NO RANGE OR UNKNOWN partitions). In this case, the value for VSTR is “9223372036854775805 range”. Note that,for single-level partitioning, the total number of partitions defined for such a partitioning expression can be up to
9223372036854775807 if both the NO RANGE and UNKNOWN partitions are specified.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Notes: Other limits may be exceeded (such as the limit on the number of combined partitions) before this limit is
exceeded.
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the partitioned
primary index rules and resubmit the request.

5717 Ranges are not constant.
Explanation: For a RANGE_N function, a range value must be a constant expression or * (an asterisk is only allowed in
the start of the first range and the end of the last range). Also, a range size value must be a constant expression.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the
RANGE_N rules and resubmit the request.

5718 Ranges overlap, are not increasing, or are NULL.
Explanation: Ranges in a RANGE_N function or ALTER TABLE statement must be in increasing order and are not
allowed to overlap. A range value or range size must not be NULL. The range sizes in an EACH clause must not all be
zeros; otherwise, there would be overlapping ranges. **DR62813-bessc**
Generated By: RES and EVL modules.
For Whom: End User. **DR62813-bessc**
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.

5719 Both NO RANGE OR UNKNOWN and UNKNOWN clauses may not be specified.
Explanation: In a RANGE_N function or an ALTER TABLE statement, both the NO RANGE OR UNKNOWN and
UNKNOWN clauses may not be specified. **DR62813-bessc**
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
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.

5720 Both NO CASE OR UNKNOWN and UNKNOWN clauses may not be specified.
Explanation: In a CASE_N function, both the NO CASE OR UNKNOWN and UNKNOWN clauses may not be specified.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the
CASE_N function rules and resubmit the request.

5721 BLOB and CLOB data not allowed in function arguments.
Explanation: For a RANGE_N or CASE_N function or in a DROP/ADD RANGE clause of an ALTER TABLE statement,
expressions and referenced columns must not have BLOB or CLOB data type. **DR62813-bessc**
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the
RANGE_N and CASE_N function rules and resubmit the request.

5722 Number of range values does not match the number of test values.
Explanation: For a RANGE_N function or an ALTER TABLE statement, the number of range values in a range start or
range end must be the same as the number of test values. **DR62813-bessc**
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
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.

5724 Number of range sizes does not match the number of test values.
Explanation: For a RANGE_N function or an ALTER TABLE, the number of range sizes in an EACH clause must be the
same as the number of test values. **DR62813-bessc**
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
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.

5725 Data type of range size is incompatible for adding to the corresponding range value.
Explanation: For a RANGE_N function or an ALTER TABLE, the data type of a range size in an EACH clause must be
compatible for adding to the corresponding range start (after casting the range start as needed to the data type of the test
value). A range size is not compatible for adding to a range start that is an asterisk. **DR62813-bessc**
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
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.

5726 A range value is an asterisk in other than the first range start or in the last range end.
Explanation: For a RANGE_N function or an ALTER TABLE, a range value may only be an asterisk in the first range
start or in the last range end. **DR62813-bessc**
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
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.

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