| |
 |
|
Donald K. Burleson
Oracle Tips |
Oracle MIG utility
* You don’t have enough space in the
SYSTEM tablespace when using MIG or ODMA to migrate. The MIG or ODMA
will complain and abort if it doesn’t have the space to create the
new dictionary tables. You will need at least two times the space
your current dictionary occupies as free space in the SYSTEM
tablespace to use MIG. You can run MIG in CHECK_ONLY mode to verify
available space (among other nice-to-knows). The Oracle binaries
take up to three times the size of Oracle7 binaries, so make sure
there is enough free space on the disk to accommodate them.
* If you are not using the export/import method, both databases must
have matching block sizes, and block size must be at least 2048
bytes. Oracle will not accept a smaller block size than 2048
bytes.
* If you are attempting to migrate from a 32-bit machine to a 64-bit
machine using MIG, come on, get serious. The only methods that work
are export/import or sqlloader. I opt for export/import in this
situation.
* Going from one character set to another is verboten
(forbidden…don’t you learn a lot reading this stuff?). For MIG, this
isn’t a problem, but for the other methods it could be. Be sure to
check your NLS parameters.
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.
|
