Re: SQL010 - length of a table's record

I believe the only way to get a record larger than 32K is to use large object fields. Then you have a max record size of around 3GB. But LOB columns may not be as easy to use. I have never tried it, so they could be quite simple, but I am betting on not based on the locator syntax. The next problem you will come up against though is that a row in a result set is also limited to 32K whether you are retrieving data from a table or view with large objects or not. So the most you can retrieve at any one time in a single row is 32K. To deal with large objects, you can read them in 32K chunks using a locator. Sounds like a huge pain in the posterior. Probably best to break it up into multiple tables. Still can't retrieve it all at once, but the IO is simplified significantly vs. CLOBS.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx


-----Darryl Freinkel <dhfreinkel@xxxxxxxxx> wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Darryl Freinkel <dhfreinkel@xxxxxxxxx>
Date: 08/10/2016 11:38AM
Subject: SQL010 - length of a table's record


Something I have not had to deal with before.

I have to create a table that has about 400 fields which are mostly VARCHAR
and of length 100 to 2000 each. So I get SQL0101.

I have always heard that the table sizes can go into the yoda byte sizes
but never a record length maximum.

For now I have reduced the field sizes to 50 chars to get passed the issue.

This is a V5R4 system.

Is there a work around or different way to use these huge record sizes?

TIA