Re: newbie Q: Oracle 6.x; percent_increase and next_extent settings

: >
: >What is the standard method of protecting against such situations?
: >Under Sybase SQL Server extent sizes are fixed at 16k. Does anyone
: >find a flaw in standardizing all Oracle tables to have a 16k
: >extent_size and 0% percent_increase?
: >
 

:  One known flaw of this method is the maximum number of extents 
:  (this is operating system specific - consult your manual. On VMS
:  it is 121) can easily be exceeded using 16K static chunks 
:  for the table and/or any index. This would only allow for the table
:  to grow to 1936K - not very big.

one correction to the above statement about maximum number of extents: the maximum number of extents allowed on a given Oracle segment is not o/s specific but is rather dependent on the Oracle block size. The larger the block size, the higher this maximum is. By default, on almost all platforms, the block size is 2K, which translates to 121 extents. I've created databases with 4K block sizes, and the maximum number of extents increases to 259.

Johnny Chan
Independent Database Specialist Received on Wed May 24 1995 - 00:00:00 CEST