Re: Oracle DB_BLOCK_SIZE and it's relationship to TS/table initial extent

Thanks, but we do want to compress to eliminate the fragmentation :-)

holders wrote:

> Run export with COMPRESS=N (without compression). This will create the table with
> the original settings
> SH
>
> bopeep wrote:
>
> > Thanks for the reply, but to be a little more clear:
> > 1. Maxextents unlimited is set.
> > 2. Export with compress has been done (this is just a one table export for
> > now), and the initial extent size is obviously defined.
> > 3. The problem isn't creating extents, it's creating the INITIAL extent size
> > of what it needs to (in this case it's roughly 8GB). Can't do it via creating
> > the table first either.
> >
> > Thanks!
> >
> > holders wrote:
> >
> > > bopeep wrote:
> > >
> > > > We are running Oracle 8.0.6 on Solaris 2.6
> > > >
> > > > We're in the process of moving our databases to a new server, and
> > > > the professional service team building our initial test databases built
> > > > them
> > > > with 2K db_block_size. However, the actual block size will need to be
> > > > recreated eventaully as at least 8K.
> > > > They want to test failover (Oracle HA), and have asked for an export of
> > > >
> > > > the data on the existing machine, and want me to import on the new
> > > > machine db
> > > > My question is, with 2K block size, what will be max, if there one, of
> > > > the Initial extents within tablespaces/tables? What is the
> > > > relationship between db block size and initial extent (multiple of?).
> > > > We have a table that through export wants to create an initial extent of
> > > > nearly 10GB, (the tablespace itself is built to 25GB), and when
> > > > attempting to import it is obviously not able to create an initial
> > > > extent of the size that it wants to.
> > > > Will the Database have to be recreated to even allow this import?
> > > >
> > > > TIA
> > >
> > > Hello,
> > >
> > > 1. You can specify UNLI MITED in you MAXEXTENTS which chains the extent
> > > maps. If UNLIMITED is not secified the the block size will determine the
> > > number of extents and for 2K its 121 extents whilst 8K is 505.
> > >
> > > 2. If you run the export with the parameter COMPRESS set to N, then it will
> > > use
> > > the table defaults for initial and next, otherwise it will compress which
> > > mean it will
> > > make the initial extent the size of the sum of all extents. An alternative,
> > > which we often use to resize is export, drop and recreate new table (in new
> > > or old database) with new parameters and import it again
Received on Thu Jul 27 2000 - 00:00:00 CDT