Prospects select AWS for working their Oracle database workload to assist improve resiliency, efficiency, and scalability of the database layer. A excessive availability (HA) answer for the database stack is a vital facet to contemplate when migrating or deploying Oracle databases in AWS to assist be sure that the structure can meet the service stage settlement (SLA) of the applying. Prospects who run their Oracle databases on Amazon Elastic Compute Cloud (Amazon EC2) generally select Oracle Information Guard bodily standby databases to assist meet the HA and catastrophe restoration (DR) for his or her Oracle database workloads.
As mentioned on this Oracle documentation, role-based providers with a number of listener endpoints within the connection URL or
tnsnames.ora entry is the popular option to transparently hook up with the database layer that’s a part of a Information Guard configuration. Nonetheless, some software elements and driver configurations don’t assist a number of hostnames within the connection URL. These functions require a single hostname or IP for the shoppers to connect with the Information Guard atmosphere.
This submit talks in regards to the idea of utilizing an Amazon Route 53 CNAME report in a Information Guard atmosphere on EC2 and lists the artifacts to robotically route the connection between main and standby environments in a Information Guard configuration based mostly on the database function.
To assist keep away from the handbook efforts to replace DNS entries or
tnsnames.ora file after a failover or switchover operation in a Information Guard atmosphere, the answer makes use of…