RE: dbimport feature/bug on 9.40HC3
Posted in 2005
Topics: Storage & Space Management, Migration, Import/Export & Data Conversion
Neil
There are different numbers of rows in each of these tables. One could
assume that they are imported from different exports and the sql files have
different extent size and next size.
MW
> -----Original Message-----
> From: owner-informix-list@iiug.org
> [mailto:owner-informix-list@iiug.org] On Behalf Of scottishpoet
> Sent: Thursday, 28 April 2005 10:59 a.m.
> To: informix-list@iiug.org
> Subject: Re: dbimport feature/bug on 9.40HC3
>
> could well be a bug
>
> set the extent size in the .sql file before running the
> dbimport, does that help?
>
>
> Neil Truby wrote:
> > This problem has been driving me mad for days!
> >
> > I am doing a dbimport. dbimport works differently from 9.40HC3 to
> HC4.
> > Basically, HC3 for some tables uses far more disk space to store the
> data.
> > This can be seen from the onchecks below.
> >
> > The 9.40HC3 instance is making a wild over-estimate of the
> necessary
> first
> > extent size. Although I truncated the dbimport after a few seconds
> in both
> > cases for the purposes of retrieving the onchecks for this posting,
> you can
> > see that the HC3 instance has allocated triple the size for
> the first
> extent
> > than HC4. In fact, the HC4 estimate - 215k pages - is a slight
> > under-estimate for the 1.52 million rows, which actually take 250k
> pages, so
> > in this case HC3 wastes 1GByte in storing 0.5GByte of data!
> >
> > 9.40 HC3
> >
> > TBLspace Report for cats_small:informix.productsales
> >
> > Physical Address 1:113708
> > Creation date 05/02/2005 21:56:35
> > TBLspace Flags 801 Page Locking
> > TBLspace use 4 bit
> bit-maps
> > Maximum row size 26
> > Number of special columns 0
> > Number of keys 0
> > Number of extents 1
> > Current serial value 1
> > First extent size 788896
> > Next extent size 78889
> > Number of pages allocated 788896
> > Number of pages used 60
> > Number of data pages 59
> > Number of rows 3925
> > Partition partnum 1048856
> > Partition lockid 1048856
> >
> > 9.40HC4
> >
> > TBLspace Report for cats_small:informix.productsales
> >
> > Physical Address 1:113708
> > Creation date 05/02/2005 22:04:40
> > TBLspace Flags 801 Page Locking
> > TBLspace use 4 bit
> bit-maps
> > Maximum row size 26
> > Number of special columns 0
> > Number of keys 0
> > Number of extents 1
> > Current serial value 1
> > First extent size 215908
> > Next extent size 21590
> > Number of pages allocated 215908
> > Number of pages used 95
> > Number of data pages 94
> > Number of rows 6280
> > Partition partnum 1048856
> > Partition lockid 1048856
>
>
>
sending to informix-list
"Murray Wood (IList)" <ifxmaillist@quanta.co.nz> wrote in message
news:1114656421.915165f9c3750e6843d085e7be61a87a@teranews...
>
> Neil
>
> There are different numbers of rows in each of these tables. One could
> assume that they are imported from different exports and the sql files
> have
> different extent size and next size.
I poointed out in the original mail that I aborted the dbimports after a few
seconds simply to be able to generate the oncheck reports that illustrate
the point about the initial allocations. I realise this makes is slightly
confusing: I assure you that both imports were done from the same export.