| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Q: Reorg an SAP tablespace
So you are saying if I started with a 64K extent
create tablespace PSAPODSD
datafile ‘c:\oradata\blahblah.dbf’ size 2G
extent management local
autoallocate;
it would take into account all the available chunks and actually use smaller chunks when trying to allocate for a lager table? Won't I end up in the same situation I am now with the developers always adding/removing data and therefore changing the sizing requirements?
This sounds like it might be the way to go.
Thanks
Vince
On Thu, 25 May 2006 20:11:46 GMT, Brian Peasland <oracle_dba_at_nospam.peasland.net> wrote:
>Instead of a LMT with UNIFORM extent sizes, consider using AUTOALLOCATE.
>Your extent sizes will not all be the same size, but that is no problem.
>And you won't have the fragmented free space problem you are running
>into with DMT's. If Oracle is attempting to allocate a 1MB extent and
>there are only smaller free extents available, Oracle will automatically
>break this up and use that smaller space.
>
>HTH,
>Brian
 |
 |