So,
We're taking the leap from 8.0.6 to 8.1.7. For various reasons, we will be
using the export/import method of migration.
Since I'll have the DB all to myself for the weekend, I want to also
partition most of our larger tables (1M-7M rows each -- it's not a huge DB)
in the migration. My
As I impose order on our servers, (moving from project-managed to dba-managed
db's) I perform this sort of task for individual schemas. The short form is the
same as yours except:
3.5) create schemas where tables or tablespace assignments will change.
4.5) create tables that are to have storage
for precreatng the users, pull the create users statements out
of the .dmp file.
joe
[EMAIL PROTECTED] 07/05/01 02:35PM
So,We're taking the leap from 8.0.6 to 8.1.7. For
various reasons, we will beusing the export/import method of
migration.Since I'll have the DB all to myself for the
Hey Don!
GREAT info! I'm wiping out my test DB right now to try it out. I already
have the scripts to create the TSs (I've learned a little in three years),
so that's no biggie. I'll letcha know what happens.
THANKS! :)
Rich Jesse System/Database Administrator
Since you mentioned partitioned tables, watch out for:
Bug 973502 THE PARTITIONED INDEX IS NOT IMPORTED AS A PARTITIONED INDEX
If you are happy with the storage parameters, you can skip steps 3 and 4, because step
5 creates everything for you - except the above !!
[EMAIL PROTECTED]
