Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Very Large Next Extent
Sorry your right..
In article <37F38CCC.50B0663C_at_us.oracle.com>,
Pete Sharman <psharman_at_us.oracle.com> wrote:
> This is a multi-part message in MIME format.
> --------------B8CAC48693EC307F1F812A54
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> There is no OPTIMAL clause for indexes, only for rollback segments, so
this
> suggestion won't work.
>
> Pete
>
> tjmxyz_at_my-deja.com wrote:
>
> > A few suggestions...
> > Us ethe storage clause in the create table statement.
> > I would make a temp table with the same struct and use a different
> >
> > SOMETHING LIKE
> > CREATE TABLE TEMP AS SELECT *
> > from mytable STORAGE (INITIAL XX NEXT XX PCTFREE 1 MINEXTENT XX
> > MAXEXTENT XX);
> >
> > Thus you could in theopry create a table with all the rows locate in
> > consecutive blocks (maybe 1 huge extent.)
> >
> > As for the index I would recreat it using the OPTIMAL Clause..
> >
> > Sorry as to not be more helpful but I assume
> > you could figure it out from here...
> >
> > Hint the extent size should be both a multiple of the block size and
> > perhaps large enough to place the table in 1 or 2 extents...
> >
> > This is completely in my opinion.
> >
> > (You'll have to look up the storage clause I can't remember)
> >
> > In article <37F29320.F337F23D_at_abbnm.com>,
> > Tapan Trivedi <tapan.trivedi_at_abbnm.com> wrote:
> > > This is a multi-part message in MIME format.
> > > --------------28EC1BFD4731F69854710893
> > > Content-Type: text/plain; charset=us-ascii
> > > Content-Transfer-Encoding: 7bit
> > >
> > > Hey Guys,
> > > I ran the following query on one of my instances and I got the
> > following
> > > results. I have a table with a next extent of 52428800 which is
> > really
> > > very big. What do I do about this as export/import is not an
option
> > for
> > > this table (9 million rows ) and always being written to and other
> > > application constraints. Any hints , suggestions, experiences,
> > comments
> > > welcome.
> > >
> > >
Thank
> > you.
> > >
> > Tapan H Trivedi
> > >
> > > select
> > >
> >
SEGMENT_NAME,SEGMENT_TYPE,BYTES,BLOCKS,EXTENTS,INITIAL_EXTENT,NEXT_EXTEN
> > T,MAX_EXTENTS,PCT_INCREASE
> > > from dba_segments
> > > where extents > 20
> > > order by extents desc;
> > >
> > > SEGMENT_NAME SEGMENT_TYPE BYTES BLOCKS
EXTENTS
> > > INITIAL_EXTENT NEXT_EXTENT MAX_EXTENTS PCT_INCREASE
> > >
> >
Sent via Deja.com http://www.deja.com/
Before you buy.
Received on Mon Oct 04 1999 - 02:03:43 CDT
![]() |
![]() |