Re: SYSTEM tablespace always has to be dictionary managed?

Dictionary-managed SYSTEM is still the default in 9i, but you can ask for it to be Locally Managed if you wish. (The Database Creation Assistant however has its own rules: it defaults to creating new databases with a locally managed system tablespace).

If SYSTEM is locally managed, then you *can* have data dictionary tablespaces in the database, but they must pre-exist or be added via transportable tablespace techniques. And they can only be read-only. You can't create new data dictionary-managed tablespaces, whether declared to be read-only or not.

Since dictionary-managed tablespaces are a Very Bad Idea, this is not a major drama.

However, I wouldn't strive very hard to convert a dictionary-managed SYSTEM tablespace into being a locally-managed one. You shouldn't have anything in SYSTEM which is acquiring a bazillion extents like crazy in any case, and therefore the advantages are negligible.

That said, all my databases have LMT SYSTEM, and I'm not exactly suffering as a result, either.

Regards
HJR "Peter" <peter_at_nomorenewsspammin.ca> wrote in message news:chrvbvsupggoaj9r8g4sdtr65kfq54jhnm_at_4ax.com...
>
> I have some conflicting information here.
> Does the SYSTEM tablespace always have to be dictionary managed?
> Version compatibility 9.0.0 or above?
> If the system tablespace is locally managed, then the other
> tablespaces in the database cannot be dictionary managed?
>
> Thanks
>
Received on Tue May 13 2003 - 05:12:58 CDT