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

David Williams wrote: > > In article <350905BE.5236DF3B@unisys.com>, Frank Clarijs > <frank.clarijs@unisys.com> writes > >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 ...) > > > > Create a temporary dbspace (flag it as TEMP=Y or use -t option to > onspaces. > > Then in ONCONFIG set DBSPACETEMP to this dbspace. > If you do not want to keep a large enough temp dbspace around just for these index builds you can use the PSORT_DBTEMP environment variable to present a list (like a PATH list) of filesystems to use for sort-work files. Specifying at least three will speed sorting sersus a single temp dbspace. The filesystems are used round-robin. Art S. Kagel