Re: HPL Deluxe Mode

rboscia wrote: > > The extents were set incorrectly and we ran out (error code > 136). When we moved the data out and recreated the table (last > week) Informix suggested we set extents at 24 (which was WAY > incorrect & in my non-wisdom I did not know better at the time) > (I sure do now) > so we ran it up again. Moved the data out and in again using > HPL one more time. > > Our table is 100,000,000 records. So I guess you do not have enough logical log space to use ALTER FRAGMENT ON TABLE tabname INIT IN dbspace; Which is the fastest way to reorganize a table. That would do it. Art S. Kagel

I tried that once too and it took 12 hours and my table was only 70,000,000 at the time. We are a 7x24 operation and these tables must be able to be written to and accessed continuously or at least down for a very minimal amount of time. Robin > From: "Art S. Kagel" <kagel@bloomberg.net> > Organization: Bloomberg LP > Reply-To: kagel@bloomberg.net > Newsgroups: comp.databases.informix > Date: Fri, 30 Jun 2000 11:11:37 -0400 > To: rboscia <rbosciaNOrbSPAM@ems.att.com.invalid> > Subject: Re: HPL Deluxe Mode > > rboscia wrote: >> >> The extents were set incorrectly and we ran out (error code >> 136). When we moved the data out and recreated the table (last >> week) Informix suggested we set extents at 24 (which was WAY >> incorrect & in my non-wisdom I did not know better at the time) >> (I sure do now) >> so we ran it up again. Moved the data out and in again using >> HPL one more time. >> >> Our table is 100,000,000 records. > > So I guess you do not have enough logical log space to use > > ALTER FRAGMENT ON TABLE tabname INIT IN dbspace;> > Which is the fastest way to reorganize a table. That would do it. > > Art S. Kagel