| |
 |
|
Donald K. Burleson
Oracle Tips |
Test the Oracle Migration
Process
Take Flight! (or Fall off the
Cliff): Migrate the Source Database
Following the pretested methodology, migrate the source database to
its new Oracle home. Immediately after the migration completes
successfully, shut down and perform a complete cold backup. This
gives you a starting point should something go awry with subsequent
testing. An export will do nearly as well; but don’t use a hot
backup, because a hot backup will not afford full recoverability at
this stage of migration! The backup should contain all datafiles,
control files, redo logs, parameter files, and SQL scripts used to
build any of the database objects.
The Three Ts: Tune, Tweak, and Test the New Database
Using the knowledge you gained from your thorough review of the
documents, readme files, and utility scripts, tune and tweak the new
Oracle instance to optimum performance. Once the database is
tuned, test using your predeveloped test cases.
What Next?
Once the database is migrated to the Oracle instance structure,
you need to consider which features you want to implement (after
all, if you didn’t want the new features, why migrate?) and how you
are going to implement them.
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.
|
