Re: Upgrade 8.1.6 -> 9.2 via exp/imp

"Walt" <walt_at_boatnerd.com> wrote in message news:3FA1883E.C032BFE8_at_boatnerd.com...
> Tom McCready wrote:
> >
> > Walt wrote:
> >
> > >I'm upgrading a production Oracle database from 8.1.6 on WinNT to 9.2
on
> > >W2k.
>
> >
> > If you import an Oracle 8 into Oracle 9, you might lose some of the
> > benefits of locally-managed tablespaces. Even if you set up tablespaces
> > to be locally-managed, and then import tables into them, these tables
> > will carry their attributes, which they had in Oracle 8.1.6, with them
> > into Oracle 9, potentially overriding any attributes, which they might
> > have had in locally-managed tablespaces. One workaround is to create
> > the tables in Oracle 9 using DDL, and then import into them, specifying
> > IGNORE=Y. Disclaimer: I am new to this.
>
> Right now I'm running into the problem that I created the database with
> a locally managed system tablespace and the export dump file wants to
> create the tablespaces as dictionary managed tablespaces. This is
> apparently illegal and I get an ORA-12913 error.
>
> There seem to be two ways out of this dilemma:
>
> 1) recreate the database with the system tablespace dictionary managed
> or
>
> 2) create the tablespaces as locally managed, run imp with ignore =n.
>
> I'm looking into which way makes more sense Dictionary Managed vs.
> Locally Managed ...any advice or pointers to a good discussion of the
> issue is greatly appreciated
>
> --
> //-Walt
> //
> // The Volkl Conspiracy

locally managed all the way my friend (in 10g DMT's are gone so there's are a hint for you) with LMT you can totally ignore extent management and you will have no worries about a fragmented tablespace anymore Received on Thu Oct 30 2003 - 17:15:56 CST