You plan to migrate an Oracle database that supports an online transaction processing (OLTP)
workload to your Database Machine.
Following are details for the source database:
Database version: 10.2.0
Byte order: Big Endian HP-UX (64-bit)
Database size: 24 TB
Storage: ASM with 1 MB allocation unit size
Which two are supported migration methods?
Physical migration using ASM online Migration
Physical migration using Transportable Database
Logical migration using Oracle Streams
Local migration using Oracle Streams
Logical migration using logical standby
* physical migration techniques (e.g. Data Guard Physical Standby, Transportable Database,
Transportable Tablespaces(B), Rapid Clone) vs. logical migration techniques(C)(e.g. Oracle Data
*You can use either Data Pump export/import or original export/import for Streams instantiations.
*The Oracle Exadata Database Machine runs the standard Oracle Database. Therefore, any
application that runs with the Oracle Database today can be seamlessly migrated to the Exadata
Database Machine with no changes to the application.
*There are several techniques for migrating data to a Database Machine. Migration can be done
using Oracle Recovery Manager (RMAN) to backup from traditional storage and restore the data
onto Exadata. Oracle Data Guard can also be used to facilitate a migration. This is done by first
creating a standby database based on Exadata storage. The standby can be using Exadata
and the production database can be on traditional storage. By executing a fast switchover, taking
just seconds, you can transform the standby database into the production database. This provides
a built-in safety net as you can undo the migration very gracefully if unforeseen issues arise.
Transportable Tablespaces(B)and Data Pump may also be used to migrate to Exadata. Any
technique used to move data between Oracle Databases can be used with Exadata.