Teradata SQL Error and Failure Codes from Error 5727 To 5734

5727 Missing the last range end.
Explanation: For a RANGE_N function or an ALTER TABLE, the last range must specify a range end preceded by the
keyword AND. **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.

5728 Partitioning violation for table %DBID.%TVMID.
Explanation: 1) An insert or update occurred to a table whose primary index partitioning definition does not allow that
data. Or, 2) an ALTER TABLE statement attempted to alter the primary index partitioning but there are existing rows that
are not allowed by the new partitioning expression and a WITH DELETE/INSERT clause was not specified.
For rows of a table with a single-level, 2-byte partitioned primary index, there is an implied check constraint of
“(CAST((partitioning expression ) AS INTEGER) ) BETWEEN 1 AND max” where max is 65535 or smaller. The CAST is not
included if the partitioning expression is already INTEGER or consists solely of a RANGE_N function. A smaller value for
max is used when the partitioning expression consists solely of a RANGE_N or CASE_N function; in that case, max is the
number of ranges/partitions defined by the function. Note that if the partitioning expression results in NULL, the constraint
is violated.
For rows of a table with a multilevel or 8-byte partitioned primary index, there is an implied check constraint of
“partitioning_expression_1 IS NOT NULL [AND partitioning_expression_n IS NOT NULL]…”.
A row that violates this constraint is not allowed to occur in the table and, therefore, cannot be inserted into the table or, for
an update, replace a row in the table. Additionally, if an existing row violates a new partitioning expression and a WITH
DELETE/INSERT clause is not specified for the ALTER TABLE statement, the new partitioning cannot be applied.
%TVMID indicates the table with the partitioning constraint violation. %DBID indicates the database containing the table.
**DR62813-bessc**
Generated By: STP modules.
For Whom: End User.
Remedy: For 1), correct the values of the columns referenced in the partitioning expressions and resubmit the request.
For 2), alter the table with a new partitioning expressions that allows for all existing rows or use a WITH DELETE/INSERT
clause.

5729 The table is not row partitioned.
Explanation: For an ALTER TABLE statement with the REVALIDATE PRIMARY INDEX clause, the specified table must
have a partitioned primary index. This clause is not valid for a nonpartitioned primary index.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Remedy: Examine the SQL statement and verify that the request is correct. Either submit another request or change the
statement to reference a table that does have a partitioned primary index and resubmit the request.

5730 Invalid DROP RANGE WHERE partition condition for level %VSTR.
Explanation: For an ALTER TABLE statement with a DROP RANGE[#Ln] WHERE clause and a single-level partitioned
primary index, a partition conditional expression must be a conditional expression that references the system-derived column
PARTITION or PARTITION#L1 (but not both) and no other columns. If the table includes an explicit column named
PARTITION, PARTITION may not be used in the conditional expression. If the table includes an explicit column named
PARTITION#L1, PARTITION#L1 may not be used in the conditional expression. If the table includes explicit columns
named PARTITION and PARTITION#L1, this WHERE form may not be specified.For a multi-level partitioned primary index, a partition conditional expression must be a conditional expression that references
the system-derived column PARTITION#Ln where n is the default or specified level of the corresponding DROP
RANGE[#Ln] and no other columns. If the table includes an explicit column named PARTITION#Ln, this WHERE form
may not be used. Note that the system-derived column PARTITION may not be used in the conditional ex-pression.
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 partitioned
primary index rules and resubmit the request.

5731 DROP RANGE and ADD RANGE for level %VSTR are not allowed; partitioning expression, if any, at that level is not a RANGE_N function or involves comparison of character or graphic data.
Explanation: For an ALTER TABLE statement, DROP RANGE[#Ln] and ADD RANGE[#Ln] clauses are only allowed if
the table is partitioned solely with a RANGE_N partitioning expression at the level being altered and:
i. Does not involve comparision of character or graphic data. or ii. Involves only special partitions (e.g. NO RANGE,
UNKNOWN, NO RANGE OR UNKNOWN).
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 request.

5733 DROP RANGE specifies no existing range, part of an existing range, or a nonexisting NO RANGE, NO RANGE OR UNKNOWN, or UNKNOWN partition.
Explanation: For an ALTER TABLE statement, an existing range cannot be partially specified by DROP RANGE. That is,
existing ranges must be entirely within the dropped ranges or entirely outside the dropped ranges. Also, at least one existing
range must be dropped if ranges are specified to be dropped. If the NO RANGE, NO RANGE OR UNKNOWN, or
UNKNOWN partition is specified to be dropped, it must exist.
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 partitioned
primary index rules and resubmit the request.

5734 ADD RANGE for level %VSTR overlaps existing ranges or partitions.
Explanation: For an ALTER TABLE statement after applying DROP RANGE[#Ln] and expansion of ranges with EACH
clauses, the ranges specified by ADD RANGE[#Ln] must not overlap existing ranges and added partitions must not conflict
with or be the same as existing partitions. For example, an UNKNOWN partition may not be added if NO RANGE OR
UNKNOWN partition or an UNKNOWN partition is already in the partitioning expression for the table.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Remedy: Examine the SQL statement and verify that th

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

 

SQL Server Errors or Failures from Error: 6549 to Error: 6568

SQLServerF1

 

Error: 6549, Severity: 16, A .NET Framework error occurred during execution of user defined routine or aggregate ‘%.*ls’: %ls. User transaction, if any, will be rolled back.
Error: 6550, Severity: 16, %s failed because parameter counts do not match.
Error: 6551, Severity: 16, %s for “%.*ls” failed because T-SQL and CLR types for return value do not match.
Error: 6552, Severity: 16, %s for “%.*ls” failed because T-SQL and CLR types for parameter “%.*ls” do not match.
Error: 6553, Severity: 16, %s failed because of an invalid .NET Framework calling convention. Use the default .NET Framework calling convention.

Error: 6554, Severity: 16, SQL assembly name ‘%.*ls’, and .NET Framework assembly name ‘%.*ls’ do not match. Assembly names must match.
Error: 6555, Severity: 16, Assembly ‘%.*ls’ already exists for owner ‘%.*ls’ in database ‘%.*ls’.
Error: 6556, Severity: 16, %s failed because it could not find type ‘%s’ in assembly ‘%s’.
Error: 6557, Severity: 16, %s failed because type ‘%s’ does not conform to %s specification due to field ‘%s’.
Error: 6558, Severity: 16, %s failed because type ‘%s’ does not conform to %s specification due to method ‘%s’.
Error: 6559, Severity: 20, Could not find type ID %d in database %.*ls. This is due to a schema inconsistency.
Error: 6560, Severity: 16, Assembly “%.*ls” is a system assembly. This operation is permitted only with user assemblies.

Error: 6561, Severity: 16, Could not find file ‘%s’ in directory ‘%s%s’.
Error: 6562, Severity: 16, Version mismatch between files ‘%ls’ (%d.%d.%d) and ‘%ls’ (%d.%d.%d).
Error: 6563, Severity: 16, Method, property or field ‘%ls’ in class ‘%ls’ in assembly ‘%.*ls’ has invalid return type.
Error: 6564, Severity: 16, The method ‘%ls’ in class ‘%ls’ in assembly ‘%.*ls’ has some invalid parameter declaration for parameter number %d.
Error: 6565, Severity: 16, %s ASSEMBLY failed because the assembly source parameter %d is not a valid assembly.
Error: 6566, Severity: 16, %s ASSEMBLY failed because the assembly source parameter %d is not a valid expression.
Error: 6567, Severity: 16, %s failed because a CLR Procedure may only be defined on CLR methods that return either SqlInt32, System.Int32, System.Nullable, void.
Error: 6568, Severity: 16, A .NET Framework error occurred while getting information from class “%.*ls” in assembly “%.*ls”: %ls.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 6329 to Error: 6348

SQLServerF1

 

Error: 6329, Severity: 16, Unsupported usage of a QName typed value in node ‘%.*ls’
Error: 6330, Severity: 16, Column ‘%.*ls’ on table ‘%.*ls’ is not of type XML, which is required to create an XML index on it.
Error: 6331, Severity: 16, Primary XML Index ‘%.*ls’ already exists on column ‘%.*ls’ on table ‘%.*ls’, and multiple Primary XML Indexes per column are not allowed.
Error: 6332, Severity: 16, Table ‘%.*ls’ needs to have a clustered primary key with less than %d columns in it in order to create a primary XML index on it.
Error: 6333, Severity: 16, Could not find%ls XML index named ‘%.*ls’ on table ‘%.*ls’
Error: 6334, Severity: 16, Could not create the XML or spatial index on object ‘%.*ls’ because that object is not a table. Create the index on the base table column.

Error: 6335, Severity: 16, XML datatype instance has too many levels of nested nodes. Maximum allowed depth is %d levels.
Error: 6336, Severity: 16, Maximum size of primary index of table ‘%.*ls’ is %d bytes. CREATE XML INDEX requires that such size should be limited to %d bytes
Error: 6337, Severity: 16, ‘%.*ls’ is not a valid XML Index name because it starts with ‘%c’ character. XML Index name should not start with ‘#’ or ‘@’
Error: 6338, Severity: 10, XML DTD has been stripped from one or more XML fragments. External subsets, if any, have been ignored.
Error: 6339, Severity: 16, Specified collection ‘%.*ls’ cannot be modified because it is SQL Server built-in XML Schema Collection.

Error: 6340, Severity: 16, Xml schema collection ‘%.*ls’ referenced by table variable ‘%.*ls’ has been dropped or altered during the execution of the batch. Please re-run the batch.
Error: 6341, Severity: 16, Xml schema collection referenced by column ‘%.*ls’ of table variable ‘%.*ls’ has been dropped or altered during the execution of the batch. Please re-run the batch.
Error: 6342, Severity: 16, Cannot create primary xml, selective xml or spatial index ‘%.*ls’ on table ‘%.*ls’, column ‘%.*ls’, because the column is computed.
Error: 6343, Severity: 16, Cannot create secondary xml or secondary selective xml index ‘%.*ls’ without a USING XML INDEX clause.
Error: 6344, Severity: 16, The primary xml index ‘%.*ls’ does not exist on table ‘%.*ls’ column ‘%.*ls’.
Error: 6345, Severity: 16, The sparse column set ‘%.*ls’ in the table ‘%.*ls’ cannot be indexed by an XML index.
Error: 6346, Severity: 16, Cannot convert a primary XML index to a secondary XML index using the DROP_EXISTING option. ‘%.*ls’ is a primary XML index.
Error: 6347, Severity: 16, Specified collection ‘%.*ls’ cannot be altered because it does not exist or you do not have permission.
Error: 6348, Severity: 16, Specified collection ‘%.*ls’ cannot be created because it already exists or you do not have permission.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.