Which two methods are supported for migrating your on-premises Oracle database to an Oracle Autonomous Transaction Processing (ATP) database in Oracle Cloud Infrastructure? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.CD.
https://docs.oracle.com/en/solutions/migrate-to-atp/index.html#GUID-28E5A683-6DC6-4A07-BB1C-55F020D4C1CDSure, I'd be happy to provide you with a detailed explanation of the two methods that are supported for migrating your on-premises Oracle database to an Oracle Autonomous Transaction Processing (ATP) database in Oracle Cloud Infrastructure.
Method 1: Use RMAN duplicate RMAN (Recovery Manager) duplicate is a method for creating a copy of a database in a new location using backups. The process involves backing up the source database to the cloud, then restoring it to a new instance of Oracle ATP using RMAN. The restored database is identical to the source database, including its schema, data, and configuration. RMAN duplicate can be used for any size of database, and it minimizes downtime and data loss during migration.
Method 2: Use Oracle Data Pump Oracle Data Pump is a tool that enables high-speed data and metadata movement between Oracle databases. The Data Pump Export utility extracts data and metadata from the source database into a set of operating system files, which can then be imported into the target database using the Data Pump Import utility. Data Pump Export can be used to export the source database to the cloud, and Data Pump Import can be used to import the database into Oracle ATP. This method can be used for any size of database, and it provides a high degree of control over the migration process.
The other answer options listed in the question are not supported methods for migrating an on-premises Oracle database to Oracle ATP. Here is a brief explanation of why they are not supported:
A. Load text files into ATP using SQL Developer: This method involves manually exporting data from the source database as text files and then importing them into Oracle ATP using SQL Developer. It is not a recommended approach for large databases because it is time-consuming and error-prone.
D. Transfer the physical database files and re-create the database: This method involves copying the physical database files from the source database to the target database and then re-creating the database on the target. It is not recommended because it can result in data corruption, and it does not support changes in the database schema or configuration.
E. Use database backup and restore: This method involves taking a backup of the source database and then restoring it to the target database. While it is a valid method for migrating smaller databases, it can be time-consuming for larger databases, and it does not provide granular control over the migration process.