N
nix1016
Guest
Yeah, I had assumed that it was something to do with the record sizes but when I tested it using the same table but a different field, it worked fine. Note that I did not have this issue in version 10.1B, although we have converted the codepage from ISO8895-1 to UTF-8 in the upgrade so that might have increased the record size slightly but I would have thought that this would give me the same issue if I were to query another field from the same table which it didn't? Ram, to answer your question, this if for the 11.6.3 schema. I ran a dbanalys and the table has about 214816 records totalling about 94.9MB with max record size of 32014 which is over the 32k limit (not even sure how that's possible), so I'm guessing if I find that records that are over 32k and truncate those to under 32k, it should hopefully fix the issue? How much would I have to truncate by with the overheads, etc?
Continue reading...
Continue reading...