RE: Extent size limit
Sorry, but my initial question is still on air. What will happen next time the engine try to increase the extent size? I understand can happen 3 diferents scenarios: It will stay at same size, It will adjust to chunk size (512,000 pages, or available space in chunk) or It will oversize chunk and create an error situation (after read your comments I can be sure this will not happen) Thanks! Octavio Gomez > From: art.kagel@gmail.com> Subject: Re: Extent size limit> Date: Tue, 12 Jun 2007 22:18:24 +0000> To: informix-list@iiug.org> > On Jun 12, 2:54 pm, Octavio Gomez <sogo...@hotmail.com> wrote:> > Hi,> >> > I'm using IDS 9.3 on Windows and I have a couple of tables with 262,144 pages of size in the last extents.> > The chunk size is 512,000 pages.> >> > Will the engine try to increase the extent size again or will be this the last increment?> > The engine will double the NEXT SIZE again to 524,288 pages, but the> largest actual extent can't exceed the largest chunk in the dbspace> and neither can it exceed the largest free extent available at> allocation time.> > Art S. Kagel> > _______________________________________________> Informix-list mailing list> Informix-list@iiug.org> http://www.iiug.org/mailman/listinfo/informix-list _________________________________________________________________ Hotmail to go? Get your Hotmail, news, sports and much more! Check out the New MSN Mobile! http://mobile.msn.com
On Jun 13, 1:14 am, Octavio Gomez <sogo...@hotmail.com> wrote: > Sorry, but my initial question is still on air. > What will happen next time the engine try to increase the extent size? > > I understand can happen 3 diferents scenarios: > > It will stay at same size, > It will adjust to chunk size (512,000 pages, or available space in chunk) or > It will oversize chunk and create an error situation (after read your comments I can be sure this will not happen) > octavio, extent doubling does not occur every time the engine allocates an extent Extent size doubling is allowed only if the total number of pages allocated so far is at least 16 times the current next extent size. This is a precautionary measure to limit the exponential doubling of next extent size,. What is your NEXT EXTENT size set to? (select nextsize from systables where tabname = "<the name of your table>" An extent is always entirely contained in a chunk; an extent cannot cross chunk boundaries. If the database server cannot find the contiguous disk space that is specified for the next-extent size, it searches the next chunk in the dbspace for contiguous space. If it can't space of an appropiate size it may give an out of space error http://publib.boulder.ibm.com/infocenter/idshelp/v10/topic/com.ibm.adref.doc/adref232.htm?resultof=%22%65%78%74%65%6e%74%22%20%22%64%6f%75%62%6c%69%6e%67%22%20%22%64%6f%75%62%6c%22%20