467,868 Members | 1,305 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 467,868 developers. It's quick & easy.

Migrating tablespace from dictionary managed to locally managed

Metalink says that, whenever we migrate from dictionary managed to
locally managed tablespaces, 'Migrated tablespaces are not subject to
the UNIFORM/SYSTEM policy of newly created locally managed
tablespaces. you should see "USER" value in the ALLOCATION_TYPE column
for migrated tablespaces'.

Oracle documentation says that parameters like INITIAL, NEXT ,
MINEXTENTS, MAXEXTENTS will not apply to locally managed tablespaces.

Suppose I already have some objects, reaching their MAXEXTENT limit in
dictionary managed tablespace. After migrating to locally managed
tablespace, will they still give 'MAXEXTENTS reached error'?

I can specify all these parameters for newly created objects. In that
case, they will be accepted. But if I dont give these parameters what
will happen to newly created object? Will it behave like an object in
newly created locally managed tablespace?

Thanks,
Shailesh
Jul 19 '05 #1
  • viewed: 2905
Share:

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

5 posts views Thread by Srini | last post: by
1 post views Thread by Jens H. Hamann | last post: by
reply views Thread by Zvika Glickman | last post: by
4 posts views Thread by Ulrich Sprick | last post: by
6 posts views Thread by Shai Levi | last post: by
6 posts views Thread by Konstantin Andreev | last post: by
3 posts views Thread by Asphalt Blazer | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.