Patrice,
That is what I did:
1. Install 8.1.7.
2. Create new DB.
3. Migrate old DB from 7.3.4 to 8.1.7.
4. Create new LMTs for tables and indexes.
5. Move all tables to new tablespaces (adjust PCTFREE and PCTUSED) according the size.
6. Rebuild all indexes to new tablespaces (adjust PCTFREE and PCTUSED) according the size.
7. Additional cleaning.
8. Export new tablespaces as transportable.
9. Import new tablespaces as transportable into new DB.
There are more details if you need.
Alex.
-----Original Message-----
From: Boivin, Patrice J [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 23, 2001 5:16 AM
To: Multiple recipients of list ORACLE-L
Subject: Cleaning up before upgrades / migrations; avoiding upgrade
proble ms
Hi,
We are preparing to upgrade our databases here from 7.3.4. to 8.1.6..
Do you have any suggestions re. re-organization, "cleaning up" before the
migration is done, or just after it is done, and before I release the
servers to the developers and end users? If you have done this type of
upgrade before, any problems encountered?
e.g. separating indexes and tables, right now they are all lumped in the
same tablespace. Ensuring that extent sizes are appropriate.
I intend to use export / import to do the transition instead of the
migration utility. I am testing that today with a few schemas on NT, will
test it again later with full exports / imports on Tru64 when we receive our
new Digital servers.
TIA
Patrice Boivin
Systems Analyst (Oracle DBA)
Bedford Institute of Oceanography
Fisheries and Oceans Canada
