Archives of the TeradataForum

Message Posted: Mon, 11 Jun 2007 @ 12:36:09 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Dear John,

See if the below explanation helps. Otherwise provide the DDLs and the sample row that you are trying to insert.

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 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. 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. 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.

Generated By: STP modules.

For Whom: End User.

Remedy:

For 1), correct the values of the columns referenced in the partitioning expression and resubmit the request.

For 2), alter the table with a new partitioning expression that allows for all existing rows or use a WITH DELETE/INSERT clause.

With Regards,

Rajesh Jain

	<Prev	Next>		<<First	<Prev	Next>	Last>>