In this session, we shall perform Migration on-premises database to Oracle Cloud using level 0 and then using archive log backups, these method is used at most of the client places

Migration Methods

Many methods exist to migrate Oracle databases to Oracle Database Exadata Cloud at Customer.

Which of these methods apply to a given migration scenario depends on several factors, including the version, character set, and platform endian format of the source and target databases.

• Conventional RMAN Backup and Recovery

• Conventional Data Pump Export and Import

• Transportable Tablespaces

• Data Pump Full Transportable Export and Import

• Transportable Tablespaces with Cross-Platform Incremental Backup

• Transportable Database

• Data Guard Physical Standby

• Advanced Data Guard Migration Options

• Unplugging and Plugging a Pluggable Database

• Plugging in a Non-CDB

• Cloning a Remote PDB or Non-CDB

Conventional RMAN Backup and Recovery

You can migrate data to Exadata Cloud at Customer by using Oracle Recovery Manager (RMAN). RMAN facilitates a physical migration approach, which is favored in migration scenarios where physical database re-organization is not necessary.

RMAN is an Oracle Database client that performs backup and recovery tasks on Oracle databases. You can use RMAN to migrate data to Exadata Cloud at Customer simply by transferring a backup of your source database to Exadata Cloud at Customer and restoring it there. You can also restore from backups stored in Oracle Database Backup Cloud Service.

If your source database resides on Linux x86–64 (like Exadata Cloud at Customer), and it uses Oracle Database 11g Release 2, or later, you can use RMAN to restore a backup of your source database on Exadata Cloud at Customer.

If you use conventional RMAN backup and recovery to create a database on Exadata Cloud at Customer, note that it is not automatically registered with the Exadata Cloud at Customer console and cannot use cloud tooling for database administration. To enable the Exadata Cloud at Customer console and cloud tooling, see Registering a Database.

RMAN also provides an active database duplication feature, which performs duplication over a network link between the source and target databases. You must consider the size of your source database, and the speed and reliability of your network connection to determine the feasibility of this approach.