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

From: buckeye714 <buckeye234NObuSPAM_at_zdnetmail.com.invalid>
Date: 2000/07/27
Message-ID: <28ced8bc.57e538dc@usw-ex0106-045.remarq.com>#1/1

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