thanks to all for your reply
i think i will wait it for the next migration to 9i oracle version , i
dont want something will happen on the prod server. but try it on test
environment.
thks again

david..

Yes, that is because locally managed tablespaces use a bitmap to keep
track of space. Dictionary tablespaces use FET$ and UET$ tables (free
extents / used extents).

When you use oracle's stored procedure to convert a tablespace, it
amounts to putting the bitmap where it has space, (not at the file
beginning as with a new tablespace), and then using it for new extents /
segments).

All the old segments will still use the dictionary, so until you move
and/or export/import etc. you have a 'hybrid'.



Joel Patterson
Database Administrator
joel.[Email address protected]
x72546
904 727-2546

-----Original Message-----
From: Hudspith Adam
[mailto:oracledba-ezmlmshield-x59809417.[Email address protected]
Sent: Tuesday, January 02, 2007 12:40 PM
To: LazyDBA Discussion
Subject: RE: dictionnary mode to extent_management_local mode.


Hi David,

It is possible to convert dictionary managed tablespaces to locally
manages
ones - but it's a bit of a mess.

You would be far better off MOVING tables and REBUILDING indexes into
new
locally managed tablespaces if you can afford the downtime.

-----Original Message-----
From: David NGUYEN
[mailto:oracledba-ezmlmshield-x12499273.[Email address protected]
Sent: 02 January 2007 16:59
To: LazyDBA Discussion
Subject: dictionnary mode to extent_management_local mode.

hello experts,

HAPPY NEW YEAR 2007 .

i use 8i oracle version and dictionnary_management mode for all
tablespaces in database
could i change it to extent_management_local mode ..? if yes what is
the
query ..? and what do i have to do..?

thanks in advance

david...

Oracle LazyDBA home page