Teradata Database Message 3577 - 3577 - Analytics Database - Teradata Vantage

Message

Row size or Sort Key size overflow.

Explanation

The user request generated a row of data or a sort key that exceeded internal Teradata database limitations (presently approximately 1MB for a row). NOTE: This may be a response row or a row for an intermediate spool file needed to carry out the operation. The row size may be too large when the data fields would appear to fit, because of sort key fields. Note that currently the container row size of the column-partitioned table cannot exceed ~64k bytes even in 1MB rows. Consider the following example: CREATE TABLE TooBig ( x1 CHAR(500) NOT NULL, y1 CHAR(60000) NOT NULL, z1 CHAR(8000) ) PRIMARY INDEX ( x1 ) PARTITION BY COLUMN (COLUMN(y1,z1)) ; Since the size of column container (y1,z1) is greater than ~64k, this error is returned. In the case of FASTEXPORT where there is a UNION with an ORDER BY, the sort key size is too large (greater than 4096 BYTES) during vertical redistribution.

Generated By

GEN modules, OPT modules, and TAB AMPPastd modules.

For Whom

End User.

Notes

None

Remedy

Change the SQL and/or reduce the data field sizes and/or number of fields being returned and resubmit the request.