Set Up the Future Primary Database
About Oracle Zero Downtime Migration Prerequisites
The following are the most critical Oracle Zero Downtime Migration (ZDM) prerequisites for a successful migration:
- ZDM Host Server
Provision a dedicated host or VM to host the ZDM installation, which includes a small Oracle Clusterware footprint, a MySQL database, and Fleet Patching and Provisioning. This server should have the latest Oracle Linux 7 image installed. This VM shape can be small, 2 cores with 16GB of physical RAM are sufficient. The ZDM server orchestrates all of the database migration tasks at both the source and target systems.
- Network ConnectivityThe type of network connectivity you have from on-premises to resources on OCI will determine your ZDM migration method and data transfer options. Oracle Zero Downtime Migration allows for different network connectivity topologies including direct connections throughOCI FastConnect or IPSec VPN, use of SSH tunnels, proxy servers, and bastion hosts.
Note:
It is extremely important to understand how your on-premises systems will access OCI resources and whether OCI resources must access specific on-premises systems, and if so, by what network path.Consider the following:- The ZDM host sever must be able to access both on-premises source and OCI target systems
- For ONLINE migration methods using Oracle Data Guard, the source and target systems must be able to access each other.
- Transparent Data Encryption (TDE)
OCI requires that all databases are encrypted. If it is not possible to encrypt the data itself before the database is transferred into OCI, you can create a TDE keystore wallet at the source and the ZDM migration process will encrypt the data files at the target. A TDE wallet is required at the source for database versions 12.2 and higher, but you can use this method for earlier database releases.
For the steps for setting the TDE keystore, see "Setting Up the Transparent Data Encryption Keystore" in Move to Oracle Cloud Using Zero Downtime Migration.
- Placeholder DatabaseYou must create a placeholder database on the target Oracle Exadata Database Service on Dedicated Infrastructure before migrating with Oracle Zero Downtime Migration. ZDM will removed the placeholder database's data structures as part of the migration process, with the source database’s structures restored in its place. Its metadata will remain in place. Use the OCI Console to create it, with these constraints:
- The database home must be at the same software version, release, and patch level as the primary.
- The
DB_NAME
must be the same as on the primary database. - The
DB_UNIQUE_NAME
can be left blank or specified, but it must be different from the primary. - The
SYS
password must be the same as on the primary, as we are using Oracle Data Guard. - Do not create a pluggable database (PDB) in this container database (CDB).
- Do not configure automatic backups when provisioning this database
- SSH access
Oracle Zero Downtime Migration requires SSH access to both the source and target systems. For the target, you will use the
opc
cloud user and passwordless SSH keys. For an on-premises source, you will use theroot
user. You can configure passwordless SSH keys and use them without passphrases, or you can use theroot
user and password. See Oracle Zero Downtime Migration to set up SSH access and ensure the ZDM host server can access the source and target systems.
Note:
See Move to Oracle Cloud Using Zero Downtime Migration for a complete description of the prerequisites for Oracle Zero Downtime Migration.
Configure Oracle Zero Downtime Migration for the Database Migration
Once your prerequisites are addressed and you've installed Oracle Zero Downtime Migration, you can create a response file to configure your database migration.
Test the Configuration and Oracle Zero Downtime Migration Parameter File
To test your preparation steps and configuration file, run Oracle Zero Downtime Migration in evaluation mode.
-eval
command line option
instructs Oracle Zero Downtime Migration to perform prechecks only for all its migration process phases, then to stop. No
changes are made to the systems. Oracle Zero Downtime Migration prechecks are performed on both source and target databases and, if DATA_TRANSFER_MEDIUM
is set to OSS
, on OCI Object Storage.
Migrate the PeopleSoft Database
You can use Oracle Zero Downtime Migration to migrate the database. By default, it will migrate the database and then switch over to it.
Note:
We DO NOT want Oracle Zero Downtime Migration to perform the switchover, so will use the
-stopafter
clause to stop after
the phase ZDM_CONFIGURE_DG_SRC
is
complete.
When this command complete the ZDM_CONFIGURE_DG_SRC
step, Oracle Zero Downtime Migration has copied the source database into OCI, set it up as a standby
of the source, configured Data Guard Broker, and started
redo apply
. The new OCI standby is being
synchronized with the source primary.
Oracle Zero Downtime Migration also completed the following tasks:
- Registered the migrated database into Oracle Clusterware
- Updated the OCI control plane metadata with updated information including any pluggable databases (PDBs) that are within the standby database
- Encrypted the data files of the standby database using Transparent Data Encryption (TDE), as noted in the Oracle Zero Downtime Migration prerequisites.
Note:
TheWALLET_TYPE
in the viewV$ENCRYPTION_WALLET
is set toAUTOLOGIN
.