Re: LOAD & IMPORT results in different disk space, occupied by a table: why? "Konstantin Andreev" <plafcow4odno@datatech.ru> wrote in message
news:e8ina8$n6e$1@dns.comcor.ru...
>
> Can not be true. One reason and one confirmation:
>
> - The intermediate data format (DEL,IXF) intended to be interoperable.
> This allows moving data between different platforms and on-disk
> structures. It (data format) by definition does not contain page and block
> information. Thus LOAD operation must reconstruct any data blocks
> specifically for target platform.
>
> - I just checked - the source table F42199, when exported, occupied:
> npages=1399252, fpages=1399430. If you are right, LOAD'ed table would
> occupy the same number of pages, but it occupies just half of them. This
> is because VALUE COMPRESSION option for target table. Thus, the data pages
> for pages *were* reconstructed by LOAD.
>
> Cheers,
> --
> Konstantin Andreev.
Let me amend my response to be more accurate.
The load utility loads data a page at a time. It takes the data from the
input file and formats the pages to be loaded. New rows are not placed on
existing pages.
The import utility does regular SQL inserts, and therefore may use existing
space on pages that already have some rows, but where the page is not full. |