When migrating an Oracle database to another server, various methods can be used depending on the requirements and constraints.
Options include Data Pump expdp/impdp, logical replication with tools like Golden Gate, setting up a Standby DB with Data Guard, or using refreshable PDBs.
RMAN backup and restore, RMAN duplicate, Data Pump Full Transportable, and Transportable tablespaces are also viable migration methods.
In addition, detaching ASM devices, relocating PDBs, and simple file copying to the new server are possible approaches.
Refreshable PDBs are recommended for their ease of use, minimal downtime during cutover, and flexibility in migrations.
Refreshable PDBs allow for individual PDB migrations, going to different releases, and moving from non-CDBs to PDBs smoothly.
The process of migrating a 19c database to 23ai using refreshable PDBs involves stages like preparing the source CDB, creating the refreshable PDB, and upgrading the PDB on the target server.
Post-upgrade steps include addressing violations, recompiling invalid objects, and ensuring the necessary patches are applied.
Migrating to the multitenant architecture and utilizing refreshable PDBs are recommended for simplified DBA tasks, low downtime migrations, and easy fallback options.
These methods provide high flexibility, minimal impact on the source PDB, and the ability to revert to the original state if needed.