
Review the on-prem Oracle 12c database to identify open schemas and their tablespaces; prepare the AWS RDS 19c target by creating needed tablespaces before import, then verify object parity.
create an s3 bucket in the aws console to host export dump files, using a general purpose bucket with a unique name such as hamid-dash-rds-s3.
Create an s3 bucket policy in the aws iam console to grant list, get object, and put object access for all objects in the bucket using arn and a wildcard.
Create an IAM role and attach an S3 bucket policy, then choose add role to database and assign the relevant policies, creating the role named Hamid Dash S3 dash role.
Create a custom parameter group for the BTS Oracle 19c instance to modify SGA, cursor sharing, and other parameters, since default groups cannot be modified.
Learn how to create an Oracle 19c AWS RDS instance from the console, configuring storage, instance class, public access, and enterprise edition options for a cost-conscious dev/test setup.
Attach the IAM role to the RDS instance to enable S3 integration for data pump export and import operations, using the Hamid S3 role as the external storage.
Connect an on-premises Linux server to an AWS RDS 19c instance via a DNS service by configuring environment variables and using the RDS endpoint hostname.
Connect an on-prem linux server to an AWS RDS Oracle 19c instance without DNS service, using a direct connect string with the RDS endpoint, port 1521, and the admin login.
Export the on-prem Oracle 12c database with data pump, creating a Linux directory, a database directory, and running a parallel schema export that produces four dump files and a log.
Install the aws cli on the Linux server to run aws commands and verify the installation by checking the cli version.
Upload data pump dump files to an S3 bucket by configuring AWS access keys in the bash profile, and verify the bucket is empty before running AWS S3 cp --recursive.
Download data pump export dump files from the S3 bucket into the RDS instance data pump directory and verify completion by checking the task ID, status, and log file.
Create all necessary tablespaces in the RDS instance prior to data pump import, expanding from five to 31 tablespaces and verifying 32 TB data files and four open schemas.
Perform data pump import to bring all on prem database objects into the RDS 19c instance, observing schema counts rise from 24 to 51 and confirming a successful import.
Validate the AWS RDS 19c database by comparing objects with the on-prem Oracle 12c database using data pump export import for cross-version migration, complemented by automated shell scripts.
Are you looking to migrate your on-premise Oracle 12c database to the cloud using Amazon RDS 19c? This hands-on course provides a complete, step-by-step guide to successfully perform the migration process using Oracle Data Pump expdp/impdp
Whether you're a Database Administrator (DBA), Cloud Engineer, or IT professional exploring AWS, this course walks you through the practical details and best practices of cloud migration using real-world scenarios.
We’ll cover everything from setting up your AWS RDS instance to exporting and importing data, handling schema-level migration, and validating post-migration integrity.
No prior AWS experience is required, but a basic understanding of Oracle databases and Linux command line is recommended. By the end of the course, you'll be able to confidently migrate Oracle databases to AWS RDS using data pump for future migrations.
What You Will Learn
Key differences between Oracle 12c (on-prem) and Oracle 19c in AWS RDS
Setting up AWS RDS for Oracle 19c
Preparing Oracle 12c for migration
Exporting data using Oracle Data Pump (expdp)
Importing data into AWS RDS 19c (impdp)
Perform an AWS RDS setup and configure the target Oracle 19c instance.
Handling pre- and post-migration validation
Monitoring, troubleshooting, and performance tuning
Creating a par file from the Data export
Crating a par file for the data pump import