Re: switching to locally managed tablespaces

Glen A Stromquist wrote:
>
> Daniel Morgan wrote:
>
> > Glen A Stromquist wrote:
> >
> >> On the database that I am upgrading from 7.3.3 to 8.1.7 I just created
> >> DMTS's on the 8.1.7 instance then did my import. all went ok, but since
> >> there is no mad panic to get this into production I was thinking on
> >> blowing the tablespaces away, re creating the tablespaces as locally
> >> managed, then redoing the import.
> >>
> >> Any particular gotcha's I should look out for here?
> >>
> >> This DB is less than 4 gig, so I am not talking a huge database here.
> >>
> >> Is this the best method?, or should I use the Oracle supplied package to
> >> convert the tablespaces from DMTS to LMTS instead?
> >>
> >> TIA
> >
> > I would definitely use LMT with uniform extents.
> >
> > The only gotcha I have found is that if you decide to make the rollback
> > tablespace LMT, and I always do, you must have at least one rollback
> > segment in a dictionary managed tablespace that can be used for the
> > creation other than the SYSTEM rollback segment. As soon as one new
> > rollback segment is on-line you can drop the temporary one.
> >
> > Daniel Morgan
>
> Thanks Daniel...
>
> Is there any particular reason you'd go with uniform extents over auto
> allocation?

The difficulty of knowing when you are going to run out of space is one reason (ie next_extent is null), also uniform sizes make extrapolation into the future (capacity planning) easier

hth
connor

-- 
==============================
Connor McDonald

http://www.oracledba.co.uk

"Some days you're the pigeon, some days you're the statue..."