Re: "enable indexes" & /tmp on UW2.1

instead of using /tmp switch DBSPACETEMP parameter in the onconfig to a valid data space assigned for temp space , must be big enough to handle the alter .. I would set it at 300 Mb . This is of course if you are using the on-line engine. For SE there is a UNIX variable called DBTEMP , set it to a directory other then /tmp , same thing you must have a dedicated space for temp operations or just enlarge your /tmp. Mariusz Frank Clarijs <frank.clarijs@unisys.com> wrote in article <350905BE.5236DF3B@unisys.com>... > In order to force Informix (7.2 on UnixWare 2.1) to recreate the indexes > from time to time, a script run weekly disables, then re-enables the > indexes in all tables of my database, one table at a time. > > This script runs fine, but now we get error messages from the OS, saying > that all /tmp space is used during this operation. Some tracing revealed > that this happens during the "alter table ... enable indexes" for the > biggest table. This table has some 3M rows, of 61 bytes per row. The > /tmp space is 50MB. It is all used (from being nearly empty at the start > of the operation). > > Has anyone some explanation for this ? How can I avoid this (because > filling /tmp completely is not really ideal for a Unix kernel ...) > > Frank Clarijs, Unisys Belgium >