You are responsible for migrating your on-premises legacy databases on 11.2.0.4 version to Autonomous Transaction Processing "" Dedicated (ATP""D) in Oracle Cloud Infrastructure (OCI)
As a solution architect, you need to plan your migration approach.
Which two options do you need to implement together to migrate your on-premises databases to OCI? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.BC.
Sure, I'd be happy to explain the options for migrating on-premises legacy databases to Autonomous Transaction Processing Dedicated (ATP-D) in Oracle Cloud Infrastructure (OCI).
Option A: Use Oracle GoldenGate replication to keep on-premises database online during migration. Oracle GoldenGate is an Oracle product that enables real-time data replication and integration across heterogeneous IT environments. It can be used to capture changes made to an on-premises database and apply them to the target ATP-D database in OCI. This approach allows for zero downtime migration because the on-premises database can continue to operate while the migration is taking place.
Option B: Convert on-premises databases to PDB, upgrade to 19c, and encrypt. This option involves converting the on-premises databases to pluggable databases (PDBs), upgrading them to Oracle Database 19c (the current long-term support release), and encrypting the data before migrating to ATP-D in OCI. This approach ensures that the migrated data is secure, and is running on the latest stable version of Oracle Database.
Option C: Use Oracle Data Guard to keep on-premises database always active during migration. Oracle Data Guard is another Oracle product that enables real-time data protection and disaster recovery. It can be used to create a standby database in OCI, and keep it synchronized with the on-premises production database using real-time replication. When the migration is complete, the standby database can be promoted to the new production database in OCI.
Option D: Retain changes to Oracle shipped privileges, stored procedures or views in the on-premises databases. This option involves making sure that any changes made to Oracle shipped privileges, stored procedures, or views in the on-premises database are retained during migration. This can be done by comparing the on-premises database schema with the target ATP-D database schema in OCI, and making any necessary changes to ensure compatibility.
Option E: Retain all legacy structures and unsupported features (e.g. legacy LOBs) in the on-premises databases for migration. This option involves retaining all legacy structures and unsupported features (e.g. legacy large objects or LOBs) in the on-premises database during migration. This can be done by identifying any features or structures that are not supported in ATP-D and making any necessary changes to ensure compatibility.
In summary, options A, B, and C are the most viable options for migrating on-premises legacy databases to ATP-D in OCI. Option D and E are also important considerations for ensuring compatibility and minimizing disruption during migration. Ultimately, the best approach will depend on the specific requirements and constraints of the migration project.