Re: Clustered index problems

David Williams wrote: > > In article <01bcebcc$40e20020$723aacc7@richntpc>, Rich Newell > <richn@northv.com> writes > >I ISAM error code is 0 > > > Then it sounds like a bug. I would except the ISAN error code to be > non-zero and give more information. Talk to Informix Technical Support. > > >David Williams <djw@smooth1.demon.co.uk> wrote in article > ><IPMHvGAP3lY0EwZN@smooth1.demon.co.uk>... > >> In article <01bceac8$265625b0$723aacc7@richntpc>, Rich Newell > >> <richn@northv.com> writes > >> >I have a large table where data is inserted all day and at night I have > >a > >> >cron that executes "ALTER INDEX xxx TO CLUSTER;" . This process runs > >very > >> >well until the sixth time it is run. On the sixth night I receive the > >> >following error " 502: Cannot cluster index". I will receive this error > >> >every night until I bring Informix down and up, then it will run fine > >for > >> >six more days. Any ideas as to what is going on??? > >> > > >> >Thanks > >> > > >> > Rich > >> > >> What is the ISAM error code? Sounds to me more like you are running out of sort space by the sixth set of additions the table is either too large for the sort space (DBSPACETEMP or PSORT_DBTEMP) or there is not enough room in the table's dbspace for 2 copies of the table. Keep in mind that like all ALTER TABLE commands, before 7.3 comes out anyway, ALTER INDEX TO CLUSTER must create a new table, sort the rows and write to the new table, drop the old table, and rename the new one. You must have room for two copies of your data and indexes and enough sort-work space. Art S. Kagel