The following steps can be used as a guide to perform an Oracle database migration using Dbvisit Replicate. In this example we will use Oracle RMAN to perform the initial data synchronization. Before any migration is done, it is suggested that you run a test on a small database so that you can familiarize yourself with the steps involved. After you have tested on a small database, it is suggested to do a test database with a database that is similar to your production database so that you can now concentrate on the timings involved with the same volumes of data as the production site.
...
Run the Setup Wizard as directed and exclude any tables that contain columns that the datatypes are not supported. See Data Discovery - Pre-flight SQL script for datatypes that are not currently supported.
Step 3
After the Setup Wizard is completed, run the *-all.sh script and instantiate the target database as directed in Step 1.
...
Start the MINE & APPLY processes to enable target to catch up with source database.
Upgrade the target target database
Step 6
Once the MINE and APPLY processes are in sync, shutdown the APPLY process but leave the MINE process running.
...
After the upgrade successfully completes once again check the target database to ensure all TRIGGERS & DELETE CASCADE CONSTRAINTS are DISABLED before restarting the APPLY process.
Step 10
Check and correct the TNS_ADMIN variable in DDC configuration files if it has changed during the Oracle upgrade.
...
Restart APPLY process so that target database can catch up to source database, and to confirm that there are no issues.
Cutover to the upgraded target target database
Step 12
- Once data is in sync between the source and target databases. Shutdown any applications accessing the Source database.
- Perform a few log switches verify they have been applied then shutdown MINE & APPLY process.
- Shutdown replication (first MINE then APPLY) once SCN is in sync (see console).
...