-
LMT versus DMT on system tablespace
Hi all,
If I export the database from 8.1.7 and the SYSTEM tablespace is DMT, can I import to 9.2.0.4 with LMT on SYSTEM tablespace??? I think, I can without haivng any problems but just want to clarify.
thanks
-
Lets think about this for a minute. What does export/import do with respect to the SYS objects?
Jeff Hunter
-
nothing,
so I would say it should be ok.
-
NO. You can not.
import does not create database or system tablespace.
it imports the data to the pre-created database.
-Raja
-
Raja,
you don't get my point. of course I have to precreate the database as well as the tablespace before the import. the question is if I create the database with LMT on SYSTEM, and my dump file was exported from 8.1.7 which is DMT on SYSTEM tablespace, will this work??? and the answer is "it will work "
thanks though
-
Another thought, although it may already have occurred to you, is that if you are moving to LMT's from a database that was previously DMT's (regular TS's, not SYSTEM) then the import process will leave you with segment sizes inhereted from the old DMT's, which would negate some of the LMT's segment management benefits.
-
slimdave,
if i export with "compress=y" will it retain the
segment size property?
-Raja
-
coalesce=y is a bad, bad thing. it would make the problem even worse.
-
Originally posted by rajabalachandra
slimdave,
if i export with "compress=y" will it retain the
segment size property?
-Raja
COMPRESS=Y will have only one impact: it causes the import to flag table data for consolidation into one INITIAL EXTENT.
The concept doesn't work for tables in Locally Managed Tablespaces. The COMPRESS=Y operation is ignored for segments in Locally Managed Tablespaces.
Oracle Certified Master
Oracle Certified Professional 6i,8i,9i,10g,11g,12c
email: ocp_9i@yahoo.com
-
Originally posted by slimdave
Another thought, although it may already have occurred to you, is that if you are moving to LMT's from a database that was previously DMT's (regular TS's, not SYSTEM) then the import process will leave you with segment sizes inhereted from the old DMT's, which would negate some of the LMT's segment management benefits.
Now thats a very good point.
I plan to move our 8.1.5 DBs (with DMTs) to 9.2 (LMTs hopefully) in the near future.
What would be the best route for this migration? I was planning to create the new DB schema on a new server, then take an 8.1.5 export and import into our new 9.2 schema.
I've already tested this and it worked ok, but is it the best way to upgrade the database? ( I have extra considerations - the system is moving to a new server as well so just upgrading the existing Oracle install on the old box is not an option.)
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
|