Migrating RAC Database to Oracle Cloud Infrastructure — Lesson 1: Source Assessment and OCI Target Architecture

Technical Scope

• RAC topology, versions, services, dependencies, data volume, and growth
• downtime and recovery objectives, compliance constraints, and migration eligibility
• OCI region, VCN, subnets, DNS, IAM, database service, and availability design
• compatibility findings, capacity model, risk register, and migration decision record

Instructor Demonstration

The instructor will inspect and explain RAC topology, versions, services, dependencies, data volume, and growth in the context of a mission-critical RAC database migrating to OCI under strict downtime, data-loss, security, and rollback constraints. The demonstration captures commands, configuration, transactions, output, logs, plans, or screenshots that prove both the intended behavior and the control boundary.

Applied Workshop

Learners complete a controlled exercise covering downtime and recovery objectives, compliance constraints, and migration eligibility and OCI region, VCN, subnets, DNS, IAM, database service, and availability design, then introduce a realistic exception involving compatibility findings, capacity model, risk register, and migration decision record. They record assumptions, exact steps, expected and observed results, a reversible correction, and the evidence required for operational acceptance.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration, development, analysis, or business-process task.
3. Capture reproducible technical or transaction evidence and compare it with the expected value.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

Acceptance for Source Assessment and OCI Target Architecture requires the result to be reproducible, traceable to approved inputs, consistent with the relevant Oracle or platform behavior, and supported by checks for security, data integrity, reliability, performance, and recoverability.

• The intended target, scope, and ownership are verified.
• Expected-value and negative-path checks pass.
• Security, reliability, performance, data quality, and support impacts are reviewed.
• Unexpected behavior is resolved before acceptance.

Failure Analysis

When the result differs from expectation, learners isolate the smallest proven cause across RAC topology, versions, services, dependencies, data volume, and growth, downtime and recovery objectives, compliance constraints, and migration eligibility, OCI region, VCN, subnets, DNS, IAM, database service, and availability design; they avoid speculative production changes, preserve evidence, apply the lowest-risk correction, rerun the test, and document prevention.

Practical Outcome

Complete and defend a validated result for Source Assessment and OCI Target Architecture with a reusable implementation record or runbook.