By Laura Ramsey-Oracle on Jun 01, 2015
Oracle has released the Database Migration Assistant for Unicode (DMU) 2.1.
Here's what you need to know:
DMU provides an end-to-end solution for migrating your databases from legacy encodings to Unicode. Its user-interface greatly simplifies the migration process and lessens the need for character set migration expertise by guiding the DBA through the entire migration process as well as automating many of the migration tasks. Oracle DMU is the officially supported method for migrating Oracle 12c Pluggable Databases (PDBs) to the Unicode character set. Oracle DMU also supports migrating selected prior releases of Oracle Database 10.2, 11.1 and 11.2.
NOTE: The DMU repository schema has been updated in release 2.1. If you have an old repository installed with the 2.0 release, you will need to upgrade the repository using DMU 2.1 before you can perform any migration tasks with the DMU 2.1 software.
Here's what's interesting: Migration to the Unicode character set is an intricate process that involves many time-consuming and resource intensive operations. Any misstep along the way can lead to data loss. Oracle DMU provides an end-to-end workflow that guides the DBA through a detailed and customizable migration process with real-time progress updates. Additional recovery and diagnostic mechanisms enable a fault-tolerant migration in the event of runtime contingencies.
New features in Oracle DMU 2.1 include:
- DMU 2.1 offers a solution to achieve a near-zero downtime migration to Unicode by leveraging the DMU migration functionality in conjunction with the Oracle GoldenGate replication technology.
- A DMU migration profile can be exported from one database instance and imported into another database instance created as a clone of the original instance.
- Problem Data Report feature has been introduced to allow the detailed information about the data in the database objects containing convertibility issues to be generated into a spreadsheet file.
- DMU 2.1 can detect and upgrade any existing DMU 2.0 repository in the database to the DMU 2.1 format and preserve the migration information so that the upgrade process is mostly transparent to the user without having to re-install the repository again.
Anything else you need to know about Oracle DMU 2.1? Go to the Oracle DMU page on OTN.
Ciao for now!