Re: Examining the space allocation within individual Extents

Jimbo1 wrote:
> Okay, good point.
>
> Thanks for your response.
>
> The Answers to your questions are as follows:
>
> 1. Oracle 8i (Version 8.1.7)
> 2. Dictionary Managed.
> 3. Which parameters would you like? I've configured it to autoextend by
> 112MB up to a maximum file size of 3.072GB. PCTUSED = 50% PCTFREE=5%
> INITIAL EXTENT=112MB NEXT EXTENT=112MB
> 4. Table attributes: Range Partitioned on month (12 partitions).
> INITIAL EXTENT=112MB (per partition) NEXT EXTENT 28MB.
>
> This is a new table and is contained within a new tablespace (the
> parameters are defined in 3. above).
>
> How can wanting to know the used vs free space allocation within an
> extent be meaningless if any free space in that extent is not going to
> be used? I'm trying to figure out whether or not I should go for a
> smaller NEXT EXTENT size than 28MB, and I would like to do this via an
> informed decision making process?
>
> Once a partition in this range-partitioned table has been populated for
> a given month, then that is it storage wise. It isn't going to grow,
> and it certainly isn't going to be updated (Hence the PCTFREE = 5% in
> the table definition; I don't need to reserve free space for updates to
> reduce the risk of row chaining).
>
> Please can you define what you mean by "Properly Configured", as that
> phrase covers an awful lot of subject matter, and in itself could be
> subjective?
>
> Thanks.
>
> James

If 8i and dictionary managed I can understand why you might care.

But the simplest solution would be to created locally managed tablespaces and move your tables. Well upgrading to 10g but likely you have some ugly app. that is not supported on any current Oracle platform.

-- 
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)