Re: Oracle sure loves disk space for storage, doesn't it?

Hi Nasir,

Start looking at the PCTINCREASE parameters on your objects. If this is set to non ZERO then this can cause some really strange space management. After this, check the PCTFREE which states how much of each block is reserved for rows which are updated. Oracle does not want to CHAIN the row if at all possible. Now look at the number of Indexes on the tables.

In your 560Mb are you just including Table and Index space or are you including SYSTEM, Rollback, Temporary spaces as well? All of these take up space as well, but export to just a couple of characters.

Andrew

NNOOR wrote:

> We have a schema whose data file has grown to about 560MB. Same data
> when exported using full export only takes about 43MB. And when this
> data is imported to local tables like under Paradox or Access, it
> only takes up about 50MB of space. The space taken by Oracle is after
> an import into an empty file (i.e. starting from scratch).
> Why does Oracle gobbles up all that space?
> The data files was set initialy to be 10MB and set to grow by
> 5MB each time. I know that the storage requirements could depend on
> a guzzilion different things, but we know the size of our data and
> to see an import file sized 43MB balloon to 560MB in a data file is
> really surprising. It realy throws off our storage estimates and
> planning. Where do you think we should start looking? Or, is this
> normal for Oracle? In the later case, I would love to know what the
> storage is being used for!
>
> Regards,
> Nasir Noor (nnoor_at_cris.com)
Received on Mon May 24 1999 - 18:46:34 CDT