sql error 1328
Hi Guyz, I have a 4gl report that bombs with error 1328. df -k reveals enough space in /tmp. The report runs fine when the number of row retrieved in the first select statement is one, however once it is more that one, i get the error. Any ideas. austin
> I have a 4gl report that bombs with error 1328. df -k reveals enough > space in /tmp. The report runs fine when the number of row retrieved > in the first select statement is one, however once it is more that > one, i get the error. Any ideas. What's the meaning of the error - I don't have the manuals at hand. If it is an out of disk space problem, I'm not sure. If it is an 'unable to allocate memory' problem, it may be that you're using olipcshm connections, and the SHMBASE value is too low, so your malloc() cannot allocate more space without bumping into the communication segment of shared memory. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN #include <disclaimer.h>
Austin Castro wrote: > > Hi Guyz, > I have a 4gl report that bombs with error 1328. df -k reveals enough > space in /tmp. The report runs fine when the number of row retrieved in > the first select statement is one, however once it is more that one, i get > the error. Any ideas. Error -1328 means that the program was unable to create the temp table needed to hold intermediate sort results. You probably have an ORDER BY clause in your report which creates an explicit temp table, named t_reportname. It works with one row because the sort is redundant for only one row and so not performed. There are two possibilities 1) there is not space it the DBSPACETEMP or ROOTDBS dbspaces or 2) the executing user does not have permission to create temp tables in the current database. Check these two things out. Also you can eliminate the report module's sorting by adding the ORDER BY clause to the SELECT statement driving the report and adding the EXTERNAL keyword to the ORDER BY clause in the report telling the report that the rows will be sorted by the engine when fetches so it will skip doing its own sorting. Art S. Kagel