03 a SC Enablement Exadata RAC

8/22/2019 03 a SC Enablement Exadata RAC

1/66

Oracle Real Application Clusters

NAME, Title


2/66

Agenda

What is RAC?

RAC for Scalability

RAC for High Availability

Consolidation with Oracle Clusterware andRAC

RAC as the Grid Infrastructure


3/66

Real Application Clusters

Benefits

Highest Availability

On-demand flexible

scalability Lower computing costs

World record performance

Database

Storage


4/66

0

3,000

6,000

9,000

12,000

15,000

FY02 FY03 FY04 FY05 FY06 FY07 FY08 FY09

(Q2)

RAC Adoption Rate Growing

Source:Oracle Internal Reporting, FY09


5/66

RAC: The Cluster Database

Clustered

Database Servers

Mirrored Disk

Subsystem

High Speed

Switch or

Interconnect

Hub or

SwitchFabric

Network

Centralized

Management

Console

Drive and Exploit

Industry Advances in

Clustering

Users

No Single

Point Of Failure

Interconnect

Storage Area Network


6/66

ASM & RAC, Understand the Architecture

public network

Node1

shared storage

redo logs all instances

database & control files

OCR & voting disk

(oracle_home)

Operating System

CRS

cluster

interconnectDatabase

instance 1

ASM instance 1

cluster

interconnect . . .

VIP1

Node 2

Operating System

CRS

Database

instance 2

ASM instance 2

Node3

Operating System

CRS

Database

instance 3

ASM instance 3

VIP3VIP2

{Managed by ASM

{


7/66

Single system command: srvctl

Start/stop the database and all enables instances

Start the instance PROD2

Display the current status

Start/stop VIP, GSD, TNS listener etc.

You can do a lot wi th srv ct l , see manual for more info

srvctl start|stop|status database -d prod

srvctl start instance -d prod -i PROD2

srvctl status|config database -d prod

srvctl start|stop|status nodeapps -n


8/66

Single Client Access Name


9/66

Connection Load Balancing

Clients

SCAN

Listeners

Oracle RAC

Database

Application Server

Local

Listeners


10/66

Connection Load Balancing

Clients

SCAN

Listeners

Oracle RAC

Database

Application Server

Listeners


11/66

Front

Offic

e

DW

Back

Offic

e

Free

AppServers

Oracle Database 11g Release 2Single Client Access Name (SCAN)

Used by clients to connectto any database in thecluster

Removes the requirementto change the clientconnection if clusterchanges

Load balances across the

instances providing aservice

Provides failover betweenmoved instances

2009 Oracle Corporation Proprietary and Confidential

RAC

ONEA

RAC

ONEB

RAC

ONEC

RAC

ONED

RAC

ONEE

RACONEF

RACONEG

RAC

ONEH

RAC

ONEI

RAC

ONEJ

RAC

ONEK

RACONEL

my

cluster.myco.com


12/66

Single Client Access Name (SCAN)

A DNS entry is required (unless using GNS) A single name defined to resolve to 3 addresses (the

scanvips)

Each cluster will have 3 scan listeners, each having a

scanvip defined as cluster resources A SCAN VIP/LISTENER will failover to another node

in cluster

Cluster Resources

--------------------------------------------ora.LISTENER_SCAN1.lsnr 1 ONLINE ONLINE node1

ora.LISTENER_SCAN2.lsnr 1 ONLINE ONLINE node2

ora.LISTENER_SCAN3.lsnr 1 ONLINE ONLINE node3


13/66

Oracle Clusterware SCAN Resources

Created by root script during Grid Infrastructure Installation

$srvctl config scan_listener

SCAN Listener LISTENER_SCAN1 exists. Port: TCP:1521



$srvctl config scanSCAN name: sales1-scan, Network: 1/192.87.58.0/255.255.255.0/

SCAN VIP name: scan1, IP: /sales1-scan.mycompany.com/192.87.58.143

SCAN VIP name: scan2, IP: /sales1-scan.mycompany.com/192.87.58.99SCAN VIP name: scan3, IP: /sales1-scan.mycompany.com/192.87.58.100


14/66

Single Client Access Name (SCAN)

SCAN listener is the load balancer for the cluster.

Allows clients to use EZConnect or simple JDBCconnections

Instance registers with local listener on its node

Database remote_listener registers instances with

all SCAN listeners

sqlplus system/manager@ sales1-scan:1521/oltp

jdbc:oracle:thin:@sales1-scan:1521/oltp


15/66

SQL*NET and SCAN

SQL*NET will retrieve the IP addresses from DNS or

GNS, it will then load balance and failover across theIP addresses.

For MAA implementations, if client uses both primary

and standby in address list, SQL*NET will retrieve all

6 IPs, it will then load balance and failover across the6 IP addresses

sales.mycompany.com =(DESCRIPTION=(CONNECT_TIMEOUT=10)(RETRY_COUNT=3)

(ADDRESS_LIST= (LOAD_BALANCE=on)(FAILOVER=ON)

(ADDRESS=(PROTOCOL=tcp)(HOST=scan1)(PORT=1521))

(ADDRESS=(PROTOCOL=tcp)(HOST=scan2)(PORT=1521)))

(CONNECT_DATA=

(SERVICE_NAME= sales.mycompany.com)))


16/66

SQL*NET and SCAN

If load_balance is OFF, SQL*NET will retrieve the IP

addresses for the SCAN and sequentially go through

the list.

For EZConnect, Load_balance is OFF

sales.mycompany.com =(DESCRIPTION=(ADDRESS_LIST=

(LOAD_BALANCE=OFF)(FAILOVER=ON)

(ADDRESS=(PROTOCOL=tcp)(HOST=scan1)(PORT=1521))

(CONNECT_DATA=(SERVICE_NAME= sales.mycompany.com)))


17/66

Oracle RAC Services


18/66

Service is an abstraction that customers use to divide

work into logical workloads

globally unique name

service quality levels (performance, Priority, availability)

Unit of Management

Location Transparency

Traditional HA(stop/start/relocate) operations

Workload Management

Dependencies and notification Fast, lights-out recovery operation

Enterprise Grid Services


19/66

PROD

PRODGLCRM

GLCRM

GL CRM

Instance parameter :

SERVICE_NAMES=PROD,GL,CRM

tnsnames.ora

CRM=(DESCRIPTION=(ADDRESS=

(PROT=TCP)(HOST=BLEU)PORT=1521)

)(CONNECT_DATA=(SERVICE_NAME=CRM)

))

tnsnames.ora

GL=(DESCRIPTION=(ADDRESS=

(PROT=TCP)(HOST=BLEU)PORT=1521)

)(CONNECT_DATA=(SERVICE_NAME=GL)

))

Database services


20/66

Use EM to Define Services


21/66

Published services


22/66

Oracle RAC for Scalability


23/66

Real Application ClustersFlexible Scalability for Applications

Applicationscalability byload balancingwork acrosscluster

Cache Fusionperformanceimprovementswith 11g

Order Entry Supply ChainBatch

As workloadincreases,easily add newnode(s) to thecluster

Order Entry Supply Chain


24/66

RAC ProvisioningSimple, Accurate, Reliable Capacity on Demand

Automate RAC provisioning while providing service

Convert DB to RAC

One-click-extend RAC to meet increased demand

De-provision RAC nodes

Simplified way to scale up or down RAC

Integrated provisioning of RAC, ASM, and Clusterware

Bare metal provisioning integrated with RAC provisioning

Gold image based initial RAC and Clusterware provisioning

Flexible and Adaptable to your IT environment


25/66

ADDM for Oracle RAC

AWR 1 AWR 2 AWR 3

Inst 1 Inst 2 Inst 3

Self-Diagnostic Engine

Database-LevelADDM

11g

Performance expert in abox

Identify the mostGlobally Significantperformance problems forthe entire Oracle RACdatabase

Database-wide analysis of:

Global cacheinterconnect issues

Global resourcecontention, e.g. IObandwidth, hot blocks

Globally high-load SQL

Skew in instance

response times Runs proactively every

hour when taking AWRsnapshots (default)

Instance-Level

ADDM

New in 11g


26/66

Load Balancing Advisory

Load Balancing Advisory is an advisory for balancing work

across Oracle RAC instances.

Load balancing advice

Is available to ALL applications that send work.

Directs work to where services are executing well and resources are

available.

Adjusts distribution for different power nodes, different priority and

shape workloads, changing demand.

Stops sending work to slow, hung, failed nodes early.

Client connection pool is integrated with Oracle RAC load

balancing advisory

When application does getConnection, the connection given is

the one that will provide the best service.


27/66

Automatic Workload ManagementRuntime Connection Load Balancing

Supported by JDBC, ODP.NET, OCI

Client connection pool is integrated with Oracle RAC

load balancing advisory

When application does getConnection, the

connection given is the one that will provide the best

service.

Policy defined by setting GOAL on Service

Need to have Connection Load Balancing


28/66

PQ integration with Services

Parallel Query slaves will only execute on nodeswhere the service of the query owner is active.

No longer have to code instance_groups

DW

OLTP 1

OLTP 2

OLTP 3OLTP 4

Node-4Node-3Node-2Node-1 Node-6Node-5

BatchRepor

ting


29/66

Mercado LibreLoad Distribution

Marketplace

Searches, Listings, Bidding, ReportingCustomer

Service

Newer nodes are faster and have more memory

Marketplace workload is not partitioned


30/66

Extract

Servers

1. Extract

from source

systems

2. Integrate, transform, de-normalize,

query and analyze

4. Data access

and publishing

ETL

Manager

Having a 3rd copy allows us to buy 1.5x the amount of processing power instead of 2x.

We replace the oldest cluster every year to keep up with growing requirements

Amazon Data Warehouse Superstack 3rd Cluster

17nodes, 8CPUs, 16-32 GB RAM, 100+ TB, 1Gb IC

16 nodes, 16 CPUs, 64GB RAM, 100+ TB, IB IC

Amazon S3Amazon DCS


31/66

Oracle RAC for High Availability


32/66

High AvailabilityRemoves Server as Single Point of Failure

Integral part of Oracles

Maximum Availability

Architecture

Enables applications to mask

component failures in

infrastructure

Order Entry Supply ChainSpare

Server Failure


33/66

Automatic Workload ManagementService fails over to surviving Node

Order Entry Supply Chain

Re-allocate spare to Order Entry


34/66

Oracle: High Availability

Without the High Cost

Traditionally High Quality = High Cost

High quality systems were built by combining high quality, high

cost parts

Mainframe model

Oracle enables a new model: High Quality + Low Cost

Oracles vision is to attain the highest possible availability using

software that can also easily scale out to meet additional load

requirements Fully integrated and simple to manage

Enable widespread deployment of HA configurations


35/66

Fast Application Notification (FAN)Immediate Notification to Clients

Oracle Real Application Clusters

Application Connection Pool

c

c

c

cc

c

c ccc

c c

FAN

Event


36/66

Fast Connection Failover

Supports multipleconnection caches

Datasource for each cachemapped to a service

Keeps track of service andinstance for each connection

Cleans up connections whenfailures occur

Distributes new workrequests across availableinstances

SERVICE 1

SERVICE 2

SERVICE 3

Mid-Tier Database Tier

INST X

INST Z

INST Y

CACHES

JDBC, ODP.NET, OCI


37/66

Order Entry Bus

Trading Application

Pool A Pool B

Connection

Cache

2 node RAC

ASM

Service A Service C Service B Service C

FAN

Pool C

APPLICATION TODAY


38/66

Notification Callouts

Users can write callout programs that are invoked

when notifications occur

Notifications include node up/down, instance up/down, or

service up/down

Example usages: Send email, page

Log status info

Start / stop programs

EM d i O l RAC R lli P t hi


39/66

EM driven Oracle RAC Rolling Patching

1 2

4

EM

3

Both nodes running Node 1 shut down/patched/started

Nodes in mixed modeNode 2 shut down & patched

a

a a


40/66

Consolidation with

Oracle Clusterware and

Oracle RAC


41/66

Cluster Consolidation

Be careful to size your servers to fit the required

capacity.

listener

Protected App A

listener

Protected App B

cluster database

listener

database

Protected App C

cluster database

Consolidated Pool of Storage

with

Automatic Storage Management

listener

cluster database 2 cluster database 2


42/66

Oracle Clusterware Licensing

See Oracle Database Licensing Information B14199-01

At a minimum, one of the machines involved in thecluster must be licensed using the appropriate metric

forany Oracle Server Technology product in either its

Standard Edition or Enterprise Edition, or all of the

machines in the cluster must be supported via OracleUnbreakable Linux support.

A cluster is defined to include all the machines that

share the same Oracle Cluster Registry (OCR) andVoting Disk

Managing a Single Instance in a Cluster


43/66

Managing a Single Instance in a Cluster

1 2

43

Single Instance

OS/Clusterware Upgrade ?

Add Instance

Failover Clients to NewInstance, shutdown original

Move Back to Original Node

a


44/66

Consolidated Clusters

8 SKU databases consolidated into two 18 node Linux clusters.

ASM provides pooled storage

Database consolidation next


45/66


Instances are brought up on nodes as workload

or maintenance requires.


46/66


In case of outage, Data Guard recovers, and work is

adjusted over remaining nodes


47/66

ProvisioningBetween Systems

Corporate DW (9i + raw)

SAP SEM/BI (9i + ocfsv1)

Siebel Brazil (10g + asm)

SAP ISU (10g + asm)

Grid Architecture

Production Servers Development/Test

Electricity Dispat. (10g + asm)Combined

OLTP & DW

Siebel Brazil planned production Feb 07, SAP ISU Mid 07Provisioning Nodes is Future Plans


48/66

Oracle Real Application Clusters One Node

Better Virtualization for Databases

O l RAC O N d


49/66

Oracle RAC One Node

New single-instance Oracle RACconfiguration :

Database Relocation migratedatabase to another server,supports:

Different processorgeneration,

Different OS and DB levels.

Rolling patches for single instanceand OS

Built-in high availability

Online upgrade to Oracle RAC

Allows customer to standardize onone database deployment andmanagement model

Supported in both physical andvirtual environments

Oracle Clusterware

OracleRAC One

Node

OracleRAC One

Node

OracleRAC One

Node

Automatic StorageManagement

O l RAC O N d


50/66

Oracle RAC One Node

Always On Single Instance Database Online replacement of servers and storage

Online patching and upgrades of operating systemand infrastructure software

Online database patching

Automated cluster failover

Better consolidation Extreme consolidation of servers & storage

Load balancing to protect service levels

Enhanced virtualization

Extends and improves database availability andflexibility when running in a virtual server

O l RAC O N d


51/66

Oracle RAC One Node

DB-A DB-B

Common Shared Storage

Single Cluster

DB- D DB- EDB-C

Server 1 Server 2 Server 3

Key Attributes:

InstanceCaging

Single Cluster

Shared storage

O l RAC O N d


52/66

Oracle RAC One Node:

Database Relocation

DB-A DB-B


Single Cluster

DB-D DB-EDB-C

Client Connections


O l RAC O N d


53/66


Database Relocation

DB-A DB-B


Single Cluster

DB-B DB-D DB-EDB-C

Client Connections

Server 1 Server 3Server 2

O l RAC O N d


54/66


Database Relocation

DB-A DB-B


Single Cluster

DB-B DB-D DB-EDB-C

Client Connections


O l RAC O N d


55/66


Database Relocation

DB-A DB-B


Single Cluster

DB-B DB-D DB-EDB-C

Client Connections


O l RAC O N d


56/66


Database Relocation

DB-A


Single Cluster

DB-B DB-D DB-EDB-C

Client Connections




57/66


Online Rolling Patches

DB-A


Single Cluster

DB-B DB-D DB-EDB-C

Client Connections


Database

Binaries



58/66



DB-A


Single Cluster

DB-B DB-D DB-EDB-C

Client Connections


Database

Binaries

Patch



59/66



DB-A


Single Cluster

DB-B DB-D DB-EDB-C

Client Connections


PatchedDatabaseBinaries



60/66



DB-A DB-B


Single Cluster

DB-B DB-D DB-EDB-C

Client Connections





61/66



DB-A DB-B


Single Cluster

DB-B DB-D DB-EDB-C

Client Connections





62/66



DB-A DB-B


Single Cluster

DB-B DB-D DB-EDB-C

Client Connections





63/66



DB-A DB-B


Single Cluster

DB-D DB-EDB-C

Client Connections





64/66


Cluster Failover

DB-A DB-B

Server 1


Single Cluster

DB-C DB-D

Server 2 Server 3



65/66


Cluster Failover

DB-A DB-B

Server 1


Single Cluster

DB-C DB-D

Server 2 Server 3



66/66


Cluster Failover

DB-A DB-B

Server 1


Single Cluster

DB-D

Server 2 Server 3

DB-C

Key Capabilities:

Database failover

Fast storagefailover

Date post:	08-Aug-2018
Category:	Documents
Upload:	rahul-naik
View:	213 times
Download:	0 times

03 a SC Enablement Exadata RAC

Documents