Re: Is it possible to create a System tablespace with Local managed extent?

The reason is that a locally managed SYSTEM tablespace can only be used to manage a database that has ALL tablespaces locally managed. This caused a potential migartion problem for people coming up from earlier versions, and would also make a downgrade hard, hence the decision was made not to set the SYSTEM tablespace to locally managed by default.

> From: "Howard J. Rogers" <howardjr_at_www.com>
> Organization: CWO Customer - reports relating to abuse should be sent to
> abuse_at_cwo.net.au
> Newsgroups:
> comp.databases.oracle,comp.databases.oracle.misc,comp.databases.oracle.server,
> comp.databases.oracle.tools
> Date: Thu, 8 Mar 2001 17:27:16 +1100
> Subject: Re: Is it possible to create a System tablespace with Local managed
> extent?
>
> I dare say that if you dig around long and hard enough, you might be able to
> make it happen.
>
> Sensible people might ask themselves, however, why, if it was that easy or
> that desirable, Oracle didn't simply make it happen automatically in the
> first place.
>
> Net result: leave it dictionary managed, and concentrate on getting the rest
> of your database locally managed.
>
> Regards
> HJR
>
>
> "Tim Lee" <timothy.yw.lee_at_philips.com> wrote in message
> news:9877oq$fvq104_at_imsp212.netvigator.com...

>> Dear all:
>> 
>> Is it possible to create a System tablespace with Local managed extent?
>> Is it better off to have the system tablespace to be dictionary managed?
>> 
>> Thanks!
>> 
>>