Quantcast
Channel: Teradata Forums - All forums
Viewing all articles
Browse latest Browse all 27759

Oreplace limitation - response (3) by ulrich

$
0
0
From the manual:   3577 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 about 64230 BYTES for a row). >DR95940-BM230014-01< 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. 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. Remedy: Change the SQL and/or reduce   Are you sure that your row or sort key is below the number above?   Can you share your SQL? Do you use ODBC or .NET connection? I once had the issue that a SQL caused this issue with ODBC connection but not with .NET connection.    

Viewing all articles
Browse latest Browse all 27759

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>