RE: Extent size of locally managed tablespaces

Bitmaps require 64K. Create the datafiles as a multiple of the uniform extent size
then add 64K for the bitmap. I've found the same behavior that you've just encountered,
i.e., if you don't have that 64K allocated, it will grab one extent for the bitmap.    

Jeff T.
thomasje_at_tce.com <mailto:thomasje_at_tce.com>  

-----Original Message-----
From: Chuck Hamilton [mailto:chuck_hamilton_at_yahoo.com] Sent: Thursday, July 20, 2000 10:43 AM
To: Multiple recipients of list ORACLE-L Subject: Extent size of locally managed tablespaces

I want to set up a locally managed tablespace that allocates data in 50m chunks. When I create it with "extent management local uniform size 50m" however, the first extent is allocated (for the bitmap?) at 50m. That's a lot of space to waste on a bitmap. Is there some way to reduce the bitmap size and still keep the extents large?

Do You Yahoo!?
Get Yahoo! Mail <http://mail.yahoo.com/> - Free email you can access from Received on Thu Jul 20 2000 - 15:27:59 CDT