Table extent config causing -566/-208 errors?!

Greetings -- A couple of weeks ago my company rolled out a fairly large Informix implementation (48 tables), and after ironing out some bugs everything seemed to be working pretty well. I went in a couple of days ago and noticed that "oncheck -pe" showed some pretty severe table fragmentation, so based on current and projected data volume, I recreated all the tables with the "EXTENT SIZE" and "NEXT SIZE" options set and reloaded the data (I projected 12 months of growth for the initial extent size). Everything seemed to be swell: The initial extents for the tables totaled 980 Mb (in a 1.8 Gb chunk), the data reloaded fine, and all our processes picked up right where they left off without complaint. What I don't understand is that since our re-load I've noticed some strange errors while trying to run some relatively simple queries. For example: -208 Memory allocation failed during query processing. ... and ... -566 Cannot initiate sort. I've never even SEEN these errors before, and they now occur sporadically in procedures that until recently worked just fine every time! Is this some very strange coincidence that I should try to ignore, or did I forget to do something critical in server configuration when I set up the extents? These errors are NOT reproducible: a procedure works fine time and time again, and then spits out one of these errors for no apparent reason. What did I forget to do? What do I need to reconfigure? Thanks for your time, Jay Online Workgroup Server Version 7.20.UC5 INFORMIX-4GL Version 6.05.UD1 SCO OpenServer 5.0 on Pentium II 233, 128 Mb RAM, 8Gb HD space -- Jay Hannah Quality Service Management, Inc. [v:] 402/397-7077 x29 [f:] 402/397-7576 [p:] 402/899-1793