Other factors

Understanding the tools and products available for use under current Oracle license agreements will be helpful in choosing the right migration strategy to AWS. For example, if you have a license and the skills to use Oracle GoldenGate, it could be an alternative to using AWS DMS as the migration tool. For more information, see the Performing the migration section of this guide.

In addition, we recommend that you collect the details of all inbound and outbound interfaces to your database on Exadata. This includes all application components that connect to the database, interdatabase connectivity using database links, and foreign database connectivity. You should also include these interfaces in your functional and load testing on the target instance, in case an existing interface requires changes to work in the target architecture. For example, Amazon RDS for Oracle doesn't support foreign database connectivity using Oracle Database Gateway products, so you might need to rearchitect the interface to use other solutions such as AWS Glue or migrate those databases to Amazon RDS Custom for Oracle or self-managed Oracle databases on Amazon EC2.

We also recommend that you consider the database features that your workload uses in order to choose the right target environment on AWS. If your workload has a dependency on Oracle Database add-on features, it should be migrated to an AWS service that supports those features. For example, if your workload has a dependency on Oracle Database Vault, you should host it on Amazon RDS Custom for Oracle or as a self-managed database on Amazon EC2.

For information about supported features, see the Amazon RDS for Oracle and Amazon RDS Custom for Oracle documentation.