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

Okay, I see what you mean. So, with datafiles of 2GB, I will not be able to create that initial extent size greater than that -- makes perfect sense now that it's in front of my face :-) In terms of our Datafiles, we keeps ours to 2GB as well.....I agree that it's best practice. So, it looks like the largest initial extent I will be able to use, will be 2GB.
I also agree in keeping extent sizes as multiples of db_block_size :-). Thanks for the info.

buckeye714 wrote:

> How big are your datafiles for the tablespace? If I am not
> mistaken, extents can not span datafiles. In our case, to avoid
> problems, we limit our datafiles to 2 GB. Around 2GB would be the
> maximum Initial extent size in our case. It sounds like you will
> have to pre-create the table in your target database with an
> initial extent that is smaller than you largest datafile. Then,
> use ignore = Y on the import.
>
> To answer your other questions, I believe it is a best practice
> to keep all of your extent sizes as a multiple of your
> db_block_size. There are plenty of other sources, that are
> better than me, to help you decide what db_block_size is best for
> you.
>
> Hope this helps.
>
> later .....
>
> -----------------------------------------------------------
>
> Got questions? Get answers over the phone at Keen.com.
> Up to 100 minutes free!
> http://www.keen.com
Received on Thu Jul 27 2000 - 00:00:00 CDT