Oracle migration phases
A migration job in Oracle Cloud Infrastructure Database Migration runs in operational phases as a work flow.
The phases in Database Migration are shown in the console with user-friendly names (DMS Phase), and in the REST API with the codes prefixed with "ODMS_", as shown in the table below.
Note that Database Migration harnesses the Zero Downtime Migration tool to run the migration job work flow, so in the logs the migration phase names will have a "ZDM_" prefix. Also note that one Database Migration phase corresponds to one or more Zero Downtime Migration phases, which will give you a more granular look at the work flow.
Table 9-1 Database Migration Process Phase Descriptions
DMS Phase NameConsole (API Codes) | Description | ZDM Phase Name | Description |
---|---|---|---|
Validate ( |
Performs validation of the source and target database, the GoldenGate Hub, and Data Pump configuration. |
Validate Source ( |
Validates the source database access credentials, database parameter
settings, |
Validate Target ( |
Verifies that the target database exists and that the database type is Autonomous Database, and validates access credentials, security, and connectivity. |
||
Validate Pre-migration Advisor
( |
Cloud Pre-Migration Advisor Tool is run. |
||
Validate GoldenGate Hub ( |
Verifies GoldenGate Microservices REST endpoints, software configuration, health, and connectivity to the source and target databases. |
||
Validate Datapump Source Settings
( |
Validates the export directory object (if applicable), and checks for sufficient space and permission for specified user in the source database to export dumps. Checks if the specified Oracle Cloud Object Store buckets, data bucket, and wallet bucket are accessible from the source. Also validates the proxy configuration if applicable. |
||
Validate Datapump Target Settings
( |
Verifies that the Data Pump import directory object exists. If a pre-existing DBLINK was specified, checks if it exists and is valid, and ensures that the ADB requirements for the DBLINK and wallet files are met. |
||
Prepare ( |
Prepares for and starts the GoldenGate Extract process, and enables supplemental logging |
Prepare GoldenGate Hub ( |
Registers database connection details and credentials with GoldenGate Microservices. |
|
Creates GoldenGate heartbeat table in the source database. If the table already exists, sets update frequency to 60 seconds. |
||
|
Prepares the source database schemas for instantiation by enabling schema level supplemental logging. |
||
Create GoldenGate Source Extract
( |
Starts the GoldenGate Extract process at the source database |
||
Prepare
(ODMS_PREPARE_INITIAL_LOAD )
|
Creates any necessary directory objects for Data Pump, and creates a DBLINK, if applicable. |
Prepare Source Datapump
( |
Creates a new directory object for Data Pump, if required. Creates OCI Auth Token to access OCI OSS bucket if required. |
Prepare Target Datapump
( |
Creates a new directory object for Data Pump, if required. Stores OCI Auth token in the database for secure OSS access. If migrating via DBLINK, and a DBLINK must be created, creates the necessary database credentials to access the source and create a new DBLINK. Ensures Autonomous Database security requirements are met using DBLINK over SSL. |
||
Datapump Source Export
( |
Starts and monitors the Data Pump Export on the source database. |
Datapump Source Export |
Starts and monitors the Data Pump Export on the source database. |
Upload Source Dump Files
( |
Uploads Data Pump dump files from the source to OCI OSS. |
Upload Source Dump Files ( |
Uploads Data Pump dump files from the source to OCI OSS. |
Datapump Target Import
( |
Starts import of Data Pump Dumps to the target database, either from the OCI OSS bucket or via DBLINK, and monitors the Data Pump import progress. |
Datapump Target Import ( |
Starts import of Data Pump Dumps to the target database, either from the OCI OSS bucket or via DBLINK, and monitors the Data Pump import progress. |
Post Datapump
( |
Removes directory objects, access credentials, and DBLINK that were created for Data Pump by Database Migration. |
Post Source Datapump ( |
Removes any Data Pump directory object created by Database Migration. |
Post Target Datapump ( |
Fixes any invalid objects in the target database. Removes the database access and OCI OSS access credentials that were created for the migration. Removes any DBLINK created by Database Migration. Optionally, removes source database dumps stored in OCI OSS bucket. |
||
Prepare GoldenGate ( |
Prepares for GoldenGate replication. |
|
Creates the GoldenGate heartbeat table in the target database. If the table already exists, sets update frequency to 60 seconds. |
|
Creates GoldenGate checkpoint table in the target database to track Replicat progress. |
||
|
Creates GoldenGate Replicat process for the target database. |
||
ZDM_START_GG_REPLICAT_TGT |
Starts GoldenGate Replicat process for the target database. |
||
Monitor GoldenGate Lag
( |
Polls the GoldenGate checkpoint and heartbeat data to measure end-to-end apply lag until lag decreases below desired threshold. |
Monitor GoldenGate Lag ( |
Polls the GoldenGate checkpoint and heartbeat data to measure end-to-end apply lag until lag decreases below desired threshold. |
Switchover App ( |
If the source database is idle, stops GoldenGate Extract, waits for GoldenGate Replicat to complete apply, and stops GoldenGate Replicat. |
Switchover App ( |
If the source database is idle, stops GoldenGate Extract, waits for GoldenGate Replicat to complete apply, and stops GoldenGate Replicat. |
Cleanup ( |
Performs cleanup operations such as deleting GoldenGate Extract and GoldenGate Replicat processes and connection details on source and target database respectively, removing Autonomous Database access to wallet, and so on. |
Post Switchover ( |
Performs post-switchover actions for the target database. |
|
Deletes GoldenGate Extract process on source database |
||
|
Deletes GoldenGate Replicat process on target database |
||
|
Disables schema level supplemental logging on source database |
||
|
Drops the GoldenGate heartbeat table in source database, if the table was created by Database Migration. Otherwise, resets update frequency to original setting. |
||
|
Drops the GoldenGate checkpoint table in the target database. |
||
|
Drops the GoldenGate heartbeat table in the target database, if the table was created by Database Migration. Otherwise, resets the update frequency to the original value. |
||
Clean GoldenGate Hub ( |
Deletes the database connection details and credentials saved with GoldenGate Microservices |
||
Post Actions ( |
Removes Autonomous Database access wallet from Database Migration. |
||
ZDM_CLEANUP_SRC
|
Deletes the Cloud Pre-Migration Advisor Tool related binaries on source database servers. |
Parent topic: Monitoring job status