Donald K. Burleson
Test the Oracle Migration
I bet the Donner party wished they
could have tested their migration plan; and I’ll bet the lemmings
that dashed off the cliff into the sea did as well. If at all
possible, even if it is on a small database that you create
specifically for the test (in fact, this is the best way), test your
migration path. Repeat the test until you are sure exactly what you
are doing. I know the bosses will be yelling if you are a bit late
with the production migration, but I’ll bet the Donner party wished
they had been late for their date with history. Hurrying to meet a
schedule is probably the best path to meet disaster I know of. When
we rush, we forget important steps, overlook potential problems, and
just do stupid things.
Test the Migrated Test Instance
If you are lucky enough to have the space available to do a
nonproduction test migration, be sure to have test plans available
to verify that what you ended up with is at least as good as what
you started with. Find the causes of any anomalous behavior and fix
them before you spend all weekend migrating your production database
only to have it malfunction--when the boss is looking of course.
Protect Your Retreat Path
Damn the torpedoes! Full speed ahead! May be fine for Naval
engagements but it is no way to migrate an Oracle instance. Protect
your retreat path by ensuring you have a complete backup of your
Oracle8i or earlier release instance.
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.