Migrating an on-premises database to RDS Custom for Oracle (original) (raw)

Before you migrate an on-premises Oracle database to RDS Custom for Oracle, consider the following factors:

Based on these factors, you can choose physical migration, logical migration, or a combination. If you choose physical migration, you can use the following techniques:

RMAN duplication

Active database duplication doesn’t require a backup of your source database. It duplicates the live source database to the destination host by copying database files over the network to the auxiliary instance. The RMANDUPLICATE command copies the required files as image copies or backup sets. To learn this technique, see the AWS blog post Physical migration of Oracle databases to Amazon RDS Custom using RMAN duplication.

Oracle Data Guard

In this technique, you back up a primary on-premises database and copy the backups to an Amazon S3 bucket. You then copy the backups to your RDS Custom for Oracle standby DB instance. After performing the necessary configuration, you manually switch over your primary database to your RDS Custom for Oracle standby database. To learn this technique, see the AWS blog post Physical migration of Oracle databases to Amazon RDS Custom using Data Guard.

For general information about logically importing data into RDS for Oracle, see Importing data into Oracle on Amazon RDS.

Oracle time zone

Upgrading an RDS Custom for Oracle DB instance

Did this page help you? - Yes

Thanks for letting us know we're doing a good job!

If you've got a moment, please tell us what we did right so we can do more of it.

Did this page help you? - No

Thanks for letting us know this page needs work. We're sorry we let you down.

If you've got a moment, please tell us how we can make the documentation better.