Next extent size

The next extent size value as shown from sysptnhdr seems to be the one shown in oncheck MULTIPLIED BY the page size then DIVIDED by 2. eg: TBLspace Report for xxxx Table fragment partition vlatdbs01 in DBspace vlatdbs01 Physical Address 13:40 Creation date 08/21/2012 04:13:18 TBLspace Flags 8902 Row Locking TBLspace contains VARCHARS TBLspace use 4 bit bit-maps Maximum row size 462 Number of special columns 5 Number of keys 0 Number of extents 11 Current serial value 973476635 Current SERIAL8 value 1 Current BIGSERIAL value 1 Current REFID value 1 Pagesize (k) 8 First extent size 384442 Next extent size *** 166640 **** ========================== $ pt_info_neil -n xxxx-p H date epoch dbspace tabname hex_partnum dec_partnum nrows nextns pagesize nptotal npused npdata pctused nextsiz lockreqs lockwts deadlks lktouts isreads iswrites isrewrites isdeletes bufreads bufwrites seqscans pagreads pagwrites D 19102014_113450 1413714890 vlatdbs01 xxxx 0x00B00007 11534343 33101356 11 8192 998927 959837 956527 96.0868011300 ***666560*** 0 0 0 0 1630699257 229419 0 0 1900684822 377755 24 4724858 133325 …. 666560 = 166640 x 8 / 2 Seems to be the same for every object, of varying page sizes. Why would that be?

Extent sizing is saved in number of base pagesize pages. So is this an AIX, MacOS/x, or Windows system with a 4K pagesize? Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Sun, Oct 19, 2014 at 9:03 AM, NEIL TRUBY <neil.truby@ardenta.com> wrote: > The next extent size value as shown from sysptnhdr seems to be the one > shown > in oncheck MULTIPLIED BY the page size then DIVIDED by 2. > > eg: > > TBLspace Report for xxxx > > Table fragment partition vlatdbs01 in DBspace vlatdbs01 > > Physical Address 13:40 > > Creation date 08/21/2012 04:13:18 > > TBLspace Flags 8902 Row Locking > > TBLspace contains VARCHARS > > TBLspace use 4 bit bit-maps > > Maximum row size 462 > > Number of special columns 5 > > Number of keys 0 > > Number of extents 11 > > Current serial value 973476635 > > Current SERIAL8 value 1 > > Current BIGSERIAL value 1 > > Current REFID value 1 > > Pagesize (k) 8 > > First extent size 384442 > > Next extent size *** 166640 **** > ========================== > > $ pt_info_neil -n xxxx-p> > H date epoch dbspace tabname hex_partnum dec_partnum nrows nextns pagesize > nptotal npused npdata pctused nextsiz lockreqs lockwts deadlks lktouts > isreads > iswrites isrewrites isdeletes bufreads bufwrites seqscans pagreads > pagwrites > D 19102014_113450 1413714890 vlatdbs01 xxxx 0x00B00007 11534343 33101356 11 > 8192 998927 959837 956527 96.0868011300 ***666560*** 0 0 0 0 1630699257 > 229419 > 0 0 1900684822 377755 24 4724858 133325 > . > > 666560 = 166640 x 8 / 2 > > Seems to be the same for every object, of varying page sizes. Why would > that > be? > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e0160b3ba8d5eeb0505c664ab

RHEL, which is I believe is 512k. So that would add up ... Thanks Neil

Meaning it's shown in number of default pages. You need to multiply by the default page size (2KB in your case) to get the values in KB. Please check.... On Oct 19, 2014 2:07 PM, "NEIL TRUBY" <neil.truby@ardenta.com> wrote: > The next extent size value as shown from sysptnhdr seems to be the one > shown > in oncheck MULTIPLIED BY the page size then DIVIDED by 2. > > eg: > > TBLspace Report for xxxx > > Table fragment partition vlatdbs01 in DBspace vlatdbs01 > > Physical Address 13:40 > > Creation date 08/21/2012 04:13:18 > > TBLspace Flags 8902 Row Locking > > TBLspace contains VARCHARS > > TBLspace use 4 bit bit-maps > > Maximum row size 462 > > Number of special columns 5 > > Number of keys 0 > > Number of extents 11 > > Current serial value 973476635 > > Current SERIAL8 value 1 > > Current BIGSERIAL value 1 > > Current REFID value 1 > > Pagesize (k) 8 > > First extent size 384442 > > Next extent size *** 166640 **** > ========================== > > $ pt_info_neil -n xxxx-p> > H date epoch dbspace tabname hex_partnum dec_partnum nrows nextns pagesize > nptotal npused npdata pctused nextsiz lockreqs lockwts deadlks lktouts > isreads > iswrites isrewrites isdeletes bufreads bufwrites seqscans pagreads > pagwrites > D 19102014_113450 1413714890 vlatdbs01 xxxx 0x00B00007 11534343 33101356 11 > 8192 998927 959837 956527 96.0868011300 ***666560*** 0 0 0 0 1630699257 > 229419 > 0 0 1900684822 377755 24 4724858 133325 > . > > 666560 = 166640 x 8 / 2 > > Seems to be the same for every object, of varying page sizes. Why would > that > be? > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --047d7bd75584c1c99d0505c70eaf