|
-
Hi:
In one of our production database has storage problem.
Tablespace was created with intial 500M next 2M, due to the next extent
size we have so many extents.
I know one of the solution for this
1)get the tablename which are in this tablespace.
2)export those tables.
3)take the tablespace offline.
4)drop the tablespace
5)create a new tablespace with new storage parameter
6)import those tables.
If I change the next extent then it will affect when object need more space
but it will not change the used extent.
Is there any better way to change the storage parameter?
How about TRASPORT_TABLESPACE? will it work?
Let me know.
Thanks.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|