Teradata SQL Error and Failure Codes from Error 5747 To 5754

5747 The product of the number of partitions at each level exceeds %VSTR.
Explanation: For a CREATE TABLE, if more than one partitioning expression is specified in the PARTITION BY clause,
the product of the number of partitions defined by each partitioning expression must not exceed 9223372036854775807. For
an ALTER TABLE statement, if more than one new partitioning expression is specified in the PARTITION BY clause or partitioning
expressions of a multi-level partitioned table are altered, the product of the number of partitions defined by each
new partitioning expression must not exceed 65535 if the table has a 2-byte partitioning and 9223372036854775807 if the
table has 8-byte partitioning.
Generated By: RES modules.
For Whom: End User.
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the multilevel
partitioned primary index rules and re-submit the request.

5748 The number of partitions for level %VSTR is less than two.
Explanation: For a CREATE TABLE, if more than one partitioning expression is specified in the PARTITION BY clause,
the number of partitions at each level must be at least two. For an ALTER TABLE statement, if more than one new partitioning
expression is specified in the PARTITION BY clause or partitioning expressions of a multi-level partitioned table are
altered, the number of resulting partitions at each level must be at least two.
Generated By: RES modules.
For Whom: End User.
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 re-quest.

5749 DROP RANGE level %VSTR is not in increasing order.
Explanation: For an ALTER TABLE statement, if DROP RANGE#Ln is specified in other than the first alter partitioning
expression clause, n must be at least one more than the default or specified level associated with the preceding alter partition-
ing expression clause.
Generated By: RES modules.
For Whom: End User.
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 re-quest.

5750 ADD RANGE level %VSTR is not in increasing order.
Explanation: For an ALTER TABLE statement, if ADD RANGE#Ln without a DROP RANGE[#Ln] is specified in other
than the first alter partitioning expression clause, n must be at least one more than the default or specified level associated
with the preceding alter partitioning expression clause.
Generated By: RES modules.
For Whom: End User.
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 re-quest.

5751 A table may not have more than one Identity Column.
Explanation: The user tried to create a table with more than one Identity Column, or add an Identity Column to a table
that already has one, or add more than one Identity Column.
Generated By: RES module.
For Whom: End User.
Remedy: Modify the CREATE TABLE or ALTER TABLE statement to eliminate multiple Identity Columns and re-submit
the request.

5752 Invalid column attribute, %VSTR, specified for an Identity Column.
Explanation: The user submitted either a CREATE TABLE or ALTER TABLE statement with an illegal attribute for an
identity column. An identity column may not be declared with NULLABLE and/or DEFAULT column attributes. In addition,
an identity column is not allowed to be foreign key of a referential constraint.
Generated By: SYN/RES module.
For Whom: End User.
Remedy: Modify the CREATE TABLE or ALTER TABLE statement to eliminate the illegal identity column attribute and
re-submit the request.

5753 Numbering for Identity Column %VSTR is over its limit.
Explanation: A system-generated number for an identity column has exceeded its limit set by the column’s MAXVALUE/
MINVALUE parameter or, if not specified, by the default limit of the identity column’s data type.
Generated By: EXP module.
For Whom: End User.
Remedy: If the data type of the identity column is smaller than DECIMAL(18,0) or NUMERIC(18,0) create a new table
with a larger data type for the identity column.

5754 No alias name can be derived/obtained.
Explanation: The Merge-Into statement did not provide valid or derivable alias names.
Generated By: Syn module.
For Whom: End User.
Remedy: Re-submit the query with valid or derivable alias names.

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