Teradata Database Message 3933 - 3933 - Analytics Database - Teradata Vantage

Message

The available data bytes in the table's perm row has exceeded the %VSTR byte limit.

Explanation

During a CREATE, or ALTER TABLE the user has tried to specify a table whose total potential perm row data only bytes length is greater than allowed. Normally the limit is approximately 1,000,000 as the 1MB Perm and Response Rows feature is enabled. If it is not, the limit is approximately 64,256 bytes. Except for LOBs, data only means the value only includes data and does not include the perm row overhead of row header fields, presence/compress bits, pad bytes for alignment, variable length offsets, unused bytes, and load isolation info. For LOBs, it includes just the overhead (OID). Compressed fields use the uncompressed data length. Columnar fields use the length of the data in the logical row, i.e., as if it was in a non-columnar table. For example: CREATE TABLE TooLong ( A VARCHAR(64000), B VARCHAR(64000), C VARCHAR(64000), ... , Z VARCHAR(64000) ); Produces this error because if allowed it could create a table with a row length of 1.6MB. Our current maximum data row length is limited to approximately 1MB.

Generated By

Optimizer.

For Whom

End User.

Notes

None

Remedy

Either remove some of the fields defined in the table or decrease the length of some of the Character, graphic, and Byte fields.