Oracle Database 12c Global Data Services PDF

1 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Integrate Your Globally Distributed Databases

for Key Cloud Computing Benefits
Oracle Database 12c

Global Data Services
Srinagesh Battula
Senior Principal Product Manager - Oracle
Cris Pedregal Martin

CMTS - Oracle
Sarah Brydon
Database Engineer - PayPal
The following is intended to outline our general product direction. It is
intended for information purposes only, and may not be incorporated into
any contract. It is not a commitment to deliver any material, code, or
functionality, and should not be relied upon in making purchasing
decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole
discretion of Oracle.

Agenda
 Challenges of Databases in Distributed Environments

 Introduction to Global Data Services (GDS)
 GDS Use Cases, Concepts, and Architecture
 Attributes of Global Services
 GDS Capabilities: Load Balancing and Failover in a Global Scope
 Customer’s GDS Case Study - PayPal
 Summary

Distributed Environments
Data Center #1 Data Center #2
 Challenges
– No seamless way to
Active Active
Data Guard Data
Active efficiently use all the
Data Guard
Guard databases
RAC Reader Farm – No automated load

Local Standby Single Instance
Primary balancing and fault tolerance
– No complete centralized
Active management
Oracle Active
Data Guard Data Guard
GoldenGate
 Resulting in
Master Master
– Sub-optimal resource
Local Standby Local Standby
utilization
– Hampered or no enterprise-
wide data integration
Solution – Unclear strategy for
A framework that transparently manages consolidation versus
client workloads across replicated databases distribution

Global Data Services (GDS)
New availability and scalability feature in Oracle Database 12c
 Based on two foundations:
– Services: proven concept for dynamic workload management for RAC
– Replication: Active Data Guard, Oracle GoldenGate
 What it does:
– Extends RAC-style failover, load balancing (within and across data centers),
and management capabilities to database services on replicated databases
– Takes into account network latency, replication lag, and service placement
 This results in:
– Higher Availability via service failover across local / global databases
– Better Scalability via multi-database integrated load balancing
– Better Manageability via centralized administration of global resources

Application Workload Suitability for GDS
GDS is best for applications that:
 Are replication-aware
– Designed to work in replicated environments
 Can separate their work into read-only and read-write services
– Example: read-only loads on an Active Data Guard standby
 Are aware of and avoid or resolve update conflicts
– Example: Oracle GoldenGate multi-master configurations
 Can tolerate some replication lag
– Many reporting applications can work with slightly out-of-date data

Concept
Unified Framework
Sales Service Sales Service Sales Global Service
GoldenGate GoldenGate
Without GDS With GDS

GDS Use Cases
Some Examples
 With Active Data Guard

– Service failover and load balancing within local data center
– Service failover and load balancing across data centers
– Automatic role-based Services upon Data Guard role transitions
– Load balancing for reader farms
 With Oracle GoldenGate
– Load balancing across data centers

GDS – Use Case with Active Data Guard
Service Failover and Load Balancing within Local Data Center
• Read Write Service runs on
Primary
• Read Only Services load
Connection Pool balanced across all standby
databases
GDS Framework • If a Physical Standby fails,
GDS fails over Read Only
Read Only Read Only
Service to an available
Service Service
Read Write
Read Only
Service
database
Active Service Load
Load Data Guard Load
• Integrate Active Data Guard
Active
Physical Primary Data Guard Physical
standby
replicated databases into a
standby
scalable and highly available
private data cloud

Service Failover and Load Balancing across Data Centers
Data Center 1 Data Center 2
• Read Write Service
runs on Primary
• Read Only Services
Connection Pool Connection Pool load balanced across
all standby databases
GDS Framework • If a physical Standby
fails, GDS fails over
Read Only Read Only Read Only Service to
Service Service Read Only
Active
Read Write
Service
Active Service Primary
Load Data GuardLoad Data Guard Load
• Integrate Active Data

Physical Primary Physical
standby
Guard replicated
standby
databases (local and
remote) into a scalable
and highly available
private data cloud

GDS – Use Case with GoldenGate (Multi-Master)
Load Balancing across Data Centers
Data Center 1 Data Center 2 • Application handles
multi-master conflict
resolutions
Connection Pool Connection Pool load balanced on both
Masters
GDS Framework
• Integrate Oracle
GoldenGate replicated
Oracle Read Write databases (local and
Read Write Service Load
Service Load GoldenGate remote) into a
Read Write
Read Write
Service
Load
Service scalable and highly
Load
available private data
cloud
Master Master

Global Data Services - Concepts
 GDS Region: Group of databases and clients in close network proximity, e.g., East, West
 GDS Pool: Databases that offer a common set of global services, e.g., HR, Sales
 Global Service: Database Service provided by multiple databases with replicated data
– Local service + {region affinity, replication lag, database cardinality}
 Global Service Manager (GSM): Provides main GDS functionality: service management
and load balancing
– Regional listener to the incoming database connections
– At least one GSM per region or multiple GSMs for High Availability
– All databases/services register to all GSM Listeners
 GDS Catalog: stores all metadata, enables centralized global monitoring & management
– Global service configuration stored in GDS Catalog
 GDSCTL: Command-line Interface to administer GDS

Globally Distributed, High Availability Architecture
Data Center #1 Data Center #2
APAC EMEA
Active
SALES POOL (sales_reporting_srvc, sales_entry_srvc)
• GDS Framework
Active Active
Data Guard Data
Guard
Data Guard dynamically balances user
requests across multiple
Local Standby
RAC
Primary Single Instance
Reader Farm
replicated sites
– Based on location, load,
and availability
All GDS databases connected to all GSMs
• Provides global availability
GSM GSM
GSM GSM – Supports automatic
GDSCTL GDS Catalog
Database GDS Catalog service failover
Standby
• GDS integrates disparate

HR POOL(hr_apac_srvc, hr_emea_srvc)
Oracle
databases into a unified
Active Active
Data
Guard
GoldenGate
Data Guard data cloud
Local Standby Master Master Local Standby GSM - Global Service Manager

GDS Configuration Flow
4. GDSCTL modifies the
3. GDSCTL establishes catalog
connection to catalog DB Cloud
Catalog DB
2. GSM routes
request to catalog
1. GDSCTL 5. Catalog
connects to notifies GSMs
catalog DB via GSM of changes GSM
GSM listener
6. Master GSM
Pool modifies Pool
Database Databases Pool
Database

Client Connectivity in GDS
 Clients connect to GSM listener instead of
(DESCRIPTION=
to the database listener (FAILOVER=on)
 GDS forwards the connection to the local (ADDRESS_LIST= APAC’s GSMs
listener (bypassing the SCAN listeners) (LOAD_BALANCE=ON)
 GSM listeners endpoints must be specified (ADDRESS=(global_protocol_address_information))

(ADDRESS=(global_protocol_address_information)))
 Client will load balance among local GSMs
(ADDRESS_LIST=
and use the remote GSMs if all the local EMEA’s GSMs
(LOAD_BALANCE=ON)
GSMs are unavailable
(ADDRESS=(global_protocol_address_information))
 Clients specify global service name and (ADDRESS=(global_protocol_address_information)))
which region they want to connect (CONNECT_DATA=
 All current FAN events (instance, service, (SERVICE_NAME=global_service_name)
net, node - up/down) are supported (REGION=region_name)))

Global Service Manager (GSM)
 Maintains GDS configuration

 Manages cardinality and failover of global services
 Measures network latency between its own and other regions and
exchanges this information with other regions’ GSMs
 Performs connection load balancing based on Connection Load
Balancing metrics (from database instances), network latency, region
 Monitors database instances, generates and publishes normalized
Runtime Load Balancing events for clients in local region

Agenda

 Summary

Service Placement
Attributes of Global Services
 Preferred Databases: designated to provide the Global Service
– The number of preferred databases defines the cardinality of the Global Service
 Available Databases: provide Global Service if not enough Preferred are

running
– If one of the preferred databases fails, then GSM maintains the cardinality of the
Global service by starting the service on an available database
 Preferred_All: All the databases in a Pool are used for the Global Service
 Role-based Global Service
– Can be started on a database if its role is the global service’s role attribute
– Oracle Clusterware not required for this scenario

Replication Lag for Active Data Guard
 An asynchronous standby may lag behind its primary database

 Applications may choose between real-time vs. slightly out-of-date data
 Applications can set maximum acceptable lag limit for a Global Service
 GDS routes requests to replicas whose replication lag is below the limit
 When replication lag exceeds the lag limit, service is brought down
 New requests are routed to a database that satisfies the lag limit

Region Affinity
 For Local-Region affinity, services are restricted to the local region

– Regardless of load, GDS will not route to databases in other regions
 For Any-Region affinity, client connections and work requests are
routed to any region for load balancing or failover
 For Local with Inter-Regional Failover affinity, client connections and
work requests are routed to another region in the following cases:
– Singleton services (for example, only one master site for update)
– All databases in a region have failed

Agenda

 Summary

Global Service Failover
 When a global service fails, GDS will restart it on an available database in the
cloud (across regions)
 Notifications will be sent so that client connection pools can reconnect to new
database
– Allows synchronized failover of mid-tiers and applications
– Can support all connection pools or applications that can process FAN events
 GDS Catalog ensures consistent view of the configuration across the cloud
 GDS supports role-based global services
– Automatically starts a global service only when db role matches the role specified for
the service

Global Service Failover
Clients connected to the
Application Server
App Server GSM via Oracle Notification Services (ONS) notifies connection
pool that service SALES is UP with database Sales-2
Connection Pools have

established GSM
connections to Sales-1
Database with the
service SALES GSM finds another
database to service SALES
Workloads are redirected

Sales-1 to Sales-2 database GSM starts service SALES
Sales-2
Global Service : SALES Global Service : SALES

Global Connection Load Balancing (CLB)
Client-Side Load Balancing
 CLB balances connection requests across GSM listeners

– includes connect-time failover
 Client tries to connect to any of the local-region GSMs first
– If local GSMs don’t respond, client tries a GSM in another region
 TNS-entries must contain two lists of addresses:
– one list of local GSMs for load balancing and intra-region failover, and
– another list of addresses for remote GSMs for inter-region failover

Global Connection Load Balancing (GCLB)
Server-side Load Balancing
 Every GSM receives load statistics from all databases in the GDS pool
and measures network latency between regions to provide CLB
functionality
 GSM Listener directs connection requests DB1
GSM
to the best database in the GDS cloud CLB
 Server-side CLB goals

DB5 (RAC)
– “LONG” for applications with long-lived connections
e.g. connection pools and SQL*Forms sessions
Client
– “SHORT” for applications with short-lived connections Connection
Pool

Client Connections
Server-side Load Balancing
1.Client connects to a random GSM in the

same region
(sales_read_service.salespool.oradbcloud)
GSM GSM
2. Based on CLB
information, GSM
redirects client to an
optimal instance.
SHORT, LONG
REGION Affinity
Instance Performance All databases
connected to all
Sales-1 GSMs Sales-2
Global Service : SALES_READ_SERVICE Global Service : SALES_READ_SERVICE

Global Runtime Load Balancing (RLB)
 GDS supports balancing of work requests at runtime for a global
service
 GSM receives per-service performance data from all database
instances in the cloud
– Measures inter-region network latency
– Creates an array that specifies what percentage of client requests
each instance should get
– Sends the array to regional clients as RLB event via ONS Channels*
 Allows client connection pools to route database requests based on
real-time load information
* OCI and ODP.NET will be using ONS instead of AQ in 12.1 – simplifying configuration

Client Redirection
Run-time Load Balancing RLB based on
SERVICE_TIME,
THROUGHPUT,
Instance Performance,
other GSM parameters
As a Master GSM,
compute and publish
FAN RLB events as an
array of normalized %
GSM of clients to services.
Client has established
connection to the
service (CLB enabled GSM
Workload redirected
by GSM) and based on RLB
workloads are
directed to this
database instance
All databases connected to

all GSMs and provides
Sales-1 Sales-2
performance information

GDS Runtime Load Balancing Graph (I)
Standalone Identical Database Servers - Simple External Load
Routing responds gracefully to changing system conditions

GDS Runtime Load Balancing Graph (II)
Standalone Asymmetrical Database Servers - No External Load
DB b: 4 CPUs DB c: 3 CPUs DB d: 2 CPUs
GDS does intelligent load balancing even across asymmetrical database servers

Agenda

 Summary

Global Database Services in
Oracle Database 12c
Sarah Brydon, PayPal Database Engineer
Who am I?
• Oracle/Unix DBA since 1996
• Worked with every Oracle version from 7.1 on
• Oracle Certified Master (and more)
– Oracle Certified Professional 7, 8, 8i, 9i, 11g; Managing
Oracle on Linux; Oracle Certified Master
• Specialist in RAC deployments, 24x7 environments,
Oracle security
• Member of the Paypal Database Engineering team
34
Tier-1 Oracle Database HA at PayPal (2012)
Primary Data Center
Mission-critical Payment Active Data Guard Standby

Processing Databases • Offload queries – eg balance, other
Supporting up to 300K Data Guard payment-related queries, industry-
SQL executions per sec Redo Transport specific analytics, etc.
Production Databases
• RAC, ASM, FRA ETL
• 10-40 TB Targets
GoldenGate Replication
WAN, 650+ miles Data Guard ASYNC Redo Transport

DR Data Center
Active Data Guard Standby Data Guard Active Dataguard Standby

• Offload queries and reads Cascaded Redo Transport • Supports DR and batch, ETL
ETL
Targets
GoldenGate
35
PayPal’s Business Challenge
• Support read services on multiple Active Data Guard
databases
• Meet defined SLAs for lag on read-only services
• Manage services in multiple data centers
– Balance load across Active Data Guard copies
– direct connections to local region
• Service location transparency to clients
– Manage service availability during planned maintenance
– Relocate primary database and perform tech refreshes ‘in the
cloud’
36
The Case for Global Data Services
• Simple, centralized management of services
– Define the service once in GDS and specify all preferred
and available databases
– Data Guard Broker integration for role-aware service
definitions
• Performance management
– Specify a maximum lag and the service will automatically
be disabled if the lag is exceeded
– Connection and Runtime Load Balancing options
– Region affinity for global services with inter-region failover
37
PayPal Lab setup – Oracle Database 12c Beta
Databases
------------------------
lablnxa
lablnxb
lablnxc
11.2 jdbc clients,no UCP 11.2 jdbc clients,no UCP
12.1 jdbc thin clients , UCP 12.1 jdbc thin clients , UCP
Services
read connections read connections
------------------------
srv_lablag15
srv_labroregion
srv_labrw (primary read-
GDSCAT
write service)
GSM
ADG STANDBY (LABLNXC) PRIMARY (LABLNXA) ADG STANDBY (LABLNXB)

Data Guard
Region B
Redo Transport
Region C
ASYNC
38
Simple, centralized management
-- add a service once in GDSCTL and it deploys to every appropriate instance
add service -service srv_lablag15 -gdspool lab -preferred lablnxb,lablnxc -available lablnxa -role
PHYSICAL_STANDBY -lag 15 -loadbalance LONG
add service -service srv_roregion -gdspool lab -preferred lablnxb,lablnxc -available lablnxa -role
PHYSICAL_STANDBY -loadbalance LONG -locality LOCAL_ONLY -region_failover
GDSCTL>services
…
Service "srv_lablag15.lab.oradbcloud" has 2 instance(s). Affinity: ANYWHERE
Instance "lab%17", name: "LABLNXC", db: "lablnxc", region: "scfc", status: ready.
Instance "lab%9", name: "LABLNXB", db: "lablnxb", region: "scfb", status: ready.
Service "srv_roregion.lab.oradbcloud" has 2 instance(s). Affinity: LOCALPREF
Instance "lab%17", name: "LABLNXC", db: "lablnxc", region: "scfc", status: ready.
Instance "lab%9", name: "LABLNXB", db: "lablnxb", region: "scfb", status: ready.
-- location neutral connection strings
jdbc:oracle:thin:@<gsm address and failover settings>

(PORT=1571)))(CONNECT_DATA=(SERVICE_NAME=srv_roregion.lab.oradbcloud)(REGION=scfb)))
39
Summary
• True enterprise-wide management of services
• Manage services in the cloud by abstracting
database connection strings
• Region-aware services supports the growing need for
management of services across databases that may
be physically widely separated
• Smart integration with broker configurations to
leverage Active Data Guard databases
40
Agenda

 Summary

GDS Additional Use Cases
Some Examples
 With Active Data Guard

– Service failover and load balancing within local data center
– Service failover and load balancing across data centers
– Automatic role-based services upon Data Guard role transitions
– Load balancing for reader farms
 With Oracle GoldenGate
– Load balancing across data centers

Data Guard Role Transition
Primary
• Read Only Service runs on
Standby
Connection Pool
GDS Framework
Read Write Active

Service Data Guard
Read Only
Service
Primary Physical
standby
- Global Service Management (GSM) Listeners

Data Guard Role Transition
Primary
• Read Only Service runs on
Standby
Connection Pool
• Upon Data Guard role change
via Broker, GDS fails over
GDS Framework Read Write Service to new
Primary and Read Only Service
Active to new Standby
Data Guard
Read Only
Service
Read Write • GDS performs automatic role
Service
based service management for
Physical
standby
Primary Data Guard configurations
(Oracle Clusterware not needed
for this scenario)

GDS – Use Case with Reader farms
Load Balancing in an Active Data Guard reader farm
runs on Primary
• Read Only Services
load balanced over
Connection Pool
standby database
GDS Framework
reader farm
Read Write
Active
• Results in effective
Service
Data Guard Reader Farm utilization of
Load Load Load Load Load Active Data Guard
Primary Read Only Read Only
Service
Read Only
Service
Read Only
Service
Read Only
Service Service standby databases
Physical Physical Physical Physical Physical
standby standby standby standby standby

Key Takeaways – Global Data Services
 GDS extends RAC-style load balancing, failover, and managing
capabilities for distributed environments of replicated databases:
– Better Scalability
 GDS balances workloads over any set of replicated databases
– Higher Availability
 GDS can failover Services across local and remote databases
– Global Manageability
 GDS centralizes management of global resources
 GDS is available with Oracle Database 12c Release 1

Key HA Sessions and Demos by Oracle Development
Monday, 1 October – Moscone South Wednesday, 3 October – Moscone South
12:30p Oracle Data Guard Zero-Data-Loss Protection at Any Distance, 300 10:15a Operational Best Practices for Oracle Exadata, 102
12:30p Future of Exadata: OLTP, Warehousing, and Consolidation, 104 10:15a Maximize Availability by Minimizing Disruption for End Users
1:45p Automating ILM with the Latest Database Technology, 300 and Application, 301
1:45p Extracting Data in Oracle GoldenGate Integrated Capture Mode, 102 11:45a What’s New in the Latest Generation of Oracle RAC, 301
3:15p Maximize Availability with the Latest Database Technology, 303 11:45a Best Practices for HA w/ GoldenGate on Oracle Exadata, 102
3:15p Maximize Enterprise Availability with the Latest DB Technology, 303 1:15p Oracle Secure Backup: Integration Best Practices with
4:45p Mission-Critical Oracle Exadata OLTP Deployment at PayPal, 300 Engineered Systems, 300
4:45p Temporal Database Capabilities with the Latest DB Technology, 300 1:15p Application MAA Best Practices on Oracle Private Clouds, 200
Tuesday, 2 October – Moscone South 5:00p Tuning &Troubleshooting Oracle GoldenGate on Oracle, 102
10:15a Database Tables to Storage Bits: Data Protection Best Practices, 300 Thursday, 4 October – Moscone South
10:15a GoldenGate & Data Guard: Working Together Seamlessly, 305 11:15a Integrate Your Globally Distributed Databases for Key
11:45a Active Data Guard Zero-Downtime Database Maintenance, 300 Cloud Computing Benefits, 300
11:45a Using Automatic Storage Mgmt with the Latest DB Technology, 301 12:45p Backup and Recovery of Oracle Exadata: Experiences
1:15p The Four Ts of RMAN: Tips, Tuning, Troubleshooting, and … ?, 102 and Best Practices, 300
5:00p Maximum Availability Architecture Best Practices for Exadata, 303
Demos – Mon 10:00a-6:00p - Tue 9:45a-6:00p - Wed 9:45a-4:00p Oracle Secure Backup, S-014
Oracle Maximum Availability Architecture, S-011 Oracle Active Data Guard, S-007
GoldenGate 11gR2: Real-Time, Transactional DB Replication, S-027 Oracle Recovery Manager and Oracle Flashback Technologies, S-019
Oracle Database 12c: Global Data Services, S-010 Oracle Real Application Clusters and Oracle RAC One Node - S-008
Oracle Database 12c Application Continuity - S-009 Oracle Database 12c Xstream, Streams, Advanced Queing, S-018
48 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. After OpenWorld, visit oracle.com/goto/availability
Resources
 OTN HA Portal:
http://www.oracle.com/goto/availability
 Maximum Availability Architecture (MAA):
http://www.oracle.com/goto/maa
 MAA Blogs:
http://blogs.oracle.com/maa
 Exadata on OTN:
http://www.oracle.com/technetwork/database/exadata/index.html
 Oracle HA Customer Success Stories on OTN:
http://www.oracle.com/technetwork/database/features/ha-casestudies-
098033.html


Oracle Database 12c Global Data Services PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Oracle Database 12c Global Data Services PDF

Enviado por

Direitos autorais:

Formatos disponíveis

1 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Integrate Your Globally Distributed Databases

Oracle Database 12c

Cris Pedregal Martin

3 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 Challenges of Databases in Distributed Environments

4 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

RAC Reader Farm – No automated load

5 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

6 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

7 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Sales Service Sales Service Sales Global Service

Without GDS With GDS

8 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 With Active Data Guard

9 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

10 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

• Integrate Active Data

11 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

12 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 GDSCTL: Command-line Interface to administer GDS

13 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

• GDS integrates disparate

14 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

15 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 GSM listeners endpoints must be specified (ADDRESS=(global_protocol_address_information))

 All current FAN events (instance, service, (SERVICE_NAME=global_service_name)

net, node - up/down) are supported (REGION=region_name)))

16 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 Maintains GDS configuration

17 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 Challenges of Databases in Distributed Environments

18 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 Available Databases: provide Global Service if not enough Preferred are

19 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 An asynchronous standby may lag behind its primary database

20 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 For Local-Region affinity, services are restricted to the local region

21 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 Challenges of Databases in Distributed Environments

22 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

23 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Connection Pools have

Workloads are redirected

24 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 CLB balances connection requests across GSM listeners

25 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 Server-side CLB goals

26 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

1.Client connects to a random GSM in the

27 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

28 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

All databases connected to

29 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Routing responds gracefully to changing system conditions

30 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

31 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 Challenges of Databases in Distributed Environments

32 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Mission-critical Payment Active Data Guard Standby

WAN, 650+ miles Data Guard ASYNC Redo Transport

Active Data Guard Standby Data Guard Active Dataguard Standby

ADG STANDBY (LABLNXC) PRIMARY (LABLNXA) ADG STANDBY (LABLNXB)