Donald K. Burleson
Test the Oracle Migration
Ensure you parse out enough time to
allow multiple reinstalls and migrations as needed. If you plan the
time you need to the nearest second, chances are you won’t make your
schedule. I’m not saying use the Scottie method (for those non-Star
Trek aficionados, Scottie was the chief engineer on the Star Ship
Enterprise; he would always pad his repair estimates by a factor of
3 or 4, then deliver ahead of schedule). Better to finish early than
to have everyone breathing down your neck because you didn’t meet
Again, cut a full backup or a full export of your source database. I
cannot stress this point enough. At worst, having a full backup
wastes some disk or tape space for a while; at best, it will save
your hide from falling over the cliff with the lemmings.
Prepare the source database as completely as possible. Remove
unneeded tables, views, and users. Do space management (why take
problems with you?). Consolidate multiple datafiles, or, conversely,
split up datafiles that are too big to perform properly. Tune your
source as well as you can and have it running at tip-top
This is an
excerpt by Mike Ault’s book “Oracle
Administration & Management”. If you want more current Oracle tips
by Mike Ault, check out his new book “Mike
Ault’s Oracle Internals Monitoring & Tuning Scripts” or
Ault’s Oracle Scripts Download.
Copyright © 1996 - 2014 by
Burleson. All rights reserved.
Oracle® is the registered trademark
of Oracle Corporation.