Category: Oracle Database@AWS

Oracle Database@AWS places Oracle Exadata infrastructure inside AWS data centers, so SQL*Net latency between your application and the database can change after migration. This post presents the CRET methodology, a three-phase approach using AWR, Active Session History, and SQL Trace, to identify latency-sensitive SQL and quantify the impact before you migrate.

Today we’re announcing the general availability of Oracle Exadata Database Service on Exascale Infrastructure (ExaDB-XS) for Oracle Database@AWS. ExaDB-XS brings Exadata-class performance and availability through a consumption-based model, so you can scale compute and storage independently and pay only for what you use.

In a previous post, Implement network connectivity patterns for Oracle Database@AWS, we covered three connectivity patterns. These are direct peering between an application VPC and the Oracle Database@AWS network, single-Region connectivity using AWS Transit Gateway, and multi-Region connectivity using AWS Cloud WAN. This post walks you through two centralized inspection patterns that route traffic through a dedicated inspection VPC before it reaches its destination: one using AWS Transit Gateway and another using AWS Cloud WAN with service insertion.

In this post, we show you how to provision key components of the Oracle Database@AWS offering, including the ODB network, Oracle Exadata infrastructure, Exadata VM clusters and Autonomous VM clusters using Terraform.

In this post, we explore the key reasons why Oracle Database@AWS is a strong fit for organizations running Oracle workloads on AWS. We cover the business, technical, and licensing advantages it brings, and how it complements the existing AWS options you already know, such as Amazon RDS for Oracle and Amazon EC2.

In this post, we walk through the available options for sharing Oracle Database@AWS (ODB@AWS) resources across AWS accounts. We also cover common cross-account architecture patterns, along with best practices and key considerations. This helps you design your ODB@AWS architecture across your AWS accounts efficiently.

In this post, we explore Oracle Database@AWS high performance networking capabilities and provide a step-by-step guide to help you configure and deploy this feature.

Oracle Database@AWS (ODB@AWS) delivers Oracle Exadata infrastructure, managed by Oracle Cloud Infrastructure (OCI), directly within Amazon Web Services (AWS) data centers. In this post, we walk you through the backup and recovery options available for ODB@AWS services: Oracle Exadata Database Service on Dedicated Infrastructure (ExaDB-D) and Oracle Autonomous AI Database on Dedicated Exadata Infrastructure (ADB-D).

Oracle Database@AWS delivers enterprise-grade database capabilities through database services that use Oracle Exadata infrastructure managed by Oracle Cloud Infrastructure (OCI) within Amazon Web Services (AWS) data centers. High availability (HA) and disaster recovery (DR) options are important aspects to consider when migrating or deploying your critical database in Oracle Database@AWS to help make sure the architecture can meet the service level agreement (SLA) of the application. This post will help you implement and maintain Data Guard configurations that follow Oracle’s Maximum Availability Architecture (MAA) best practices and the AWS Well-Architected Framework. We will show how to select the right network architecture and configure Data Guard associations for both cross-AZ and cross-Region deployments, making sure your applications maintain seamless connectivity during role transitions.

In this post, we explain how to set up key components of Oracle Database@AWS offering including ODB network, Oracle Exadata infrastructure, Exadata VM clusters and Autonomous VM clusters using AWS CloudFormation template.