I85PREP
⌘ K
Oracle Autonomous Database Professional study materials
Oracle Autonomous Database Professional study resources

Oracle Autonomous Database Professional: Migrating and Loading Data into Autonomous Databases

Oracle Autonomous Database Professional · Work through your exam, one topic at a time.

All guide sections

Migrating and Loading Data into Autonomous Databases

Domain 4: Migrating and Loading Data into Autonomous Databases

This domain tests how data gets into Autonomous Database and how to choose a migration method by size, downtime, and source. Expect Data Pump, object storage, Database Actions, and minimal-downtime replication.

Core rules and concepts

  • Oracle Data Pump is the standard bulk migration path for Oracle sources. Stage the export dump in OCI Object Storage, create a DBMS_CLOUD credential, and import into Autonomous Database. Validate object counts, row counts, invalid objects, and grants afterward.
  • Database Actions Data Load handles CSV and spreadsheet-style loads for smaller datasets. SQL Developer can load and browse data. For large files in Object Storage, use DBMS_CLOUD procedures such as COPY_DATA or external tables created with CREATE_EXTERNAL_TABLE.
  • Oracle GoldenGate is for continuous replication and minimal downtime. Zero Downtime Migration can orchestrate supported migrations. Non-Oracle sources need schema conversion, often with SQL Developer Migration Workbench.
  • Autonomous Database has no customer-managed operating system or local file system. Stage files in Object Storage or use supported client tools; do not plan on copying dump files to a local database server directory.
  • Plan for character sets, schema remapping, edition/version compatibility, and sequence/identity values.

Worked example

A 2 TB Oracle data warehouse must move with a four-hour cutover. Use Data Pump: export to Object Storage, import into a pre-created Autonomous Data Warehouse, then run validation queries and rebuild invalid objects. If the business instead allows only minutes of downtime, use GoldenGate to replicate changes after the initial load. Reasoning: Data Pump is efficient for bulk; GoldenGate addresses the downtime constraint, not the bulk size alone.

Traps that cost marks

  • Trying to use a local filesystem path for a dump file.
  • Forgetting the Object Storage credential or bucket permissions.
  • Choosing Data Pump when near-zero downtime is mandatory.
  • Skipping post-load validation of row counts and invalid objects.
  • Assuming tablespaces and storage are managed exactly as on-premises.