Could someone please help to explain the pattern below from an oncheck
-pt:
Yes, old OS, old Informix.....
Initial extent size is: 115000
Next extent size is: 25000
After the first next extent it allocates 3X8000 extents and 6X4000
extents and then the final added extent is 25000.
Why did it not allocate the 2nd next extent as 25000 and so on?
No extra dbspace has been added during the period.
The next extent size has not been altered during the period of growth.
Thanks,
Bernard.
> oncheck -pt tnt_egl:trackerstats
TBLspace Report for dbase:informix.tablename
Physical Address 200028
Creation date 07/10/2005 06:33:03
TBLspace Flags 901 Page Locking
TBLspace contains
VARCHARS
TBLspace use 4 bit
bit-maps
Maximum row size 346
Number of special columns 2
Number of keys 0
Number of extents 12
Current serial value 1
First extent size 115000
Next extent size 25000
Number of pages allocated 213000
Number of pages used 209141
Number of data pages 127949
Number of rows 1432857
Partition partnum 2097189
Partition lockid 2097189
Extents
Logical Page Physical Page Size
0 d60a92 115000
115000 f0e675 25000
140000 e222fc 8000
148000 f02895 8000
156000 f0b284 8000
164000 c3219e 4000
168000 c3323e 4000
172000 d0ae4c 4000
176000 d0f087 4000
180000 d1303f 4000
184000 d15c15 4000
188000 100493b 25000
> uname -a
HP-UX servername B.10.20 E 9000/888 8-user license
>onstat -b
Informix Dynamic Server Version 7.31.UC2A -- On-Line -- Up 5 days
14:41:42 -- 52000 Kbytes
Buffers
address userthread flgs pagenum memaddr nslots pgflgs xflgs owner
waitlist
23 modified, 0 resident, 6000 total, 8192 hash buckets, 2048 buffer
size
david@smooth1.co.uk - 28 Jan 2006 02:41 GMT
"Why did it not allocate the 2nd next extent as 25000 and so on? "
There was not enough contiguous free space in the dbspace
when the new extent was allocated. I assume a large enough
amount of contiguous free space was available when the
last new extent was added.