Understanding Oracle RAC Internals - Part 1 - Slides PDF

1
Copyright 2011, Oracle and/or its affiliates. All rights reserved.
Understanding Oracle RAC Internals Part 1

for the Oracle RAC SIG
Markus Michalewicz (Markus.Michalewicz@oracle.com)
Senior Principal Product Manager Oracle RAC and Oracle RAC One Node
2
Safe Harbor Statement
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 Oracles products remains at the sole discretion of Oracle.
Agenda
The Oracle RAC Architecture
VIPs and Networks
Listeners and SCAN
and Services

Typical hardware architecture
Network
Client
Public Lan
Node 1
Node 2
Node N-1
Interconnect
with switch
SAN switch
Shared Storage
Node N

Typical software deployment 11g Release 2
Oracle Real Application Clusters (RAC)

Oracle Grid Infrastructure
OS
OS
OS
Shared Storage
OS

Typical software deployment 11g Release 2
Oracle Real Application Clusters (RAC)

Oracle Automatic Storage Management (ASM)
Oracle Clusterware
OS
OS
OS
Oracle ASM managed

Shared Storage
7
OS

Oracle RAC 11g Release 2 per node layer
Cloud File System
(aka ASM Cluster File
File System - ACFS)
DB Instance
Oracle RAC
ASM Instance

OS
OS
HA Framework
Node
Membership
OS
For all other files

11.2.0.3: For Backup Sets
Oracle Clusterware files

Voting Files (disks)
Cluster Registry (OCR)
Database Files
Redo / Archive Logs

Oracle ASM managed
Shared Storage
8
Control Files
etc.

Oracle Grid Infrastructure 11g Release 2 process overview
ASM Instance

OS
OS
HA Framework
Node
Membership
My Oracle Support (MOS)
OS
Note 1053147.1 - 11gR2 Clusterware
and Grid Home - What You Need to Know
Note 1050908.1 - How to Troubleshoot
Grid Infrastructure Startup Issues
9

Local and Cluster Resources (11.2.0.2 list)
LISTENER_SCAN1
LISTENER_SCAN2
LISTENER_SCAN3
ora.oc4j
If database is deployed:
ora.SCAN1.VIP
ora.SCAN2.VIP
ora.SCAN3.VIP
ora.cvu
ora.Dbname.db
ora.node1.vip
ora.node2.vip
ora.node3.vip
ora.node4.vip
ora.asm
ora.asm
ora.asm
ora.asm
ora.dgname.dg
ora.dgname.dg
ora.dgname.dg
ora.dgname.dg
ora.listener.lsnr
ora.listener.lsnr
ora.listener.lsnr
ora.listener.lsnr
ora.ons
ora.ons
ora.ons
ora.ons
ora.gsd
ora.gsd
ora.gsd
ora.gsd
ora.net1.network
ora.net1.network
ora.net1.network
ora.net1.network
ora.registry.acfs
ora.registry.acfs
ora.registry.acfs
ora.registry.acfs

OS
10
OS
OS
OS
ora.Dbname.Srvcname.svc
Command to list:
crsctl stat res -t
VIPs and Networks
11
VIPs and Networks

Oracle VIPs
SCAN and node VIPs are cluster resources
SCAN VIPs can float in the cluster
rac1
Node VIPs per default run on specific nodes

All VIPs on the public network (SCAN, node,
user or application VIPs) depend on the Oracle
network resource.
The network resource monitors
the public network interface(s).
IOCTL based checks vs. default gateway ping
Default gateway checks as backup
racgvip for backward compatibility only
12
rac2
LISTENER_SCAN1
LISTENER_SCAN2
ora.SCAN1.VIP
ora.SCAN2.VIP
ora.rac1.vip
ora.rac2.vip
ora.listener.lsnr
ora.listener.lsnr
ora.net1.network
ora.net1.network

OS
OS
VIPs and Networks

Node VIP Details
1
2
3
[GRID]> crsctl status res ora.rac1.vip -p

NAME=ora.rac1.vip
TYPE=ora.cluster_vip_net1.type
...
AGENT_FILENAME=%CRS_HOME%/bin/orarootagent%CRS_EXE_SUFFIX%
...
rac1
CHECK_INTERVAL=1
CHECK_TIMEOUT=30
...
ora.rac1.vip
START_DEPENDENCIES=hard(ora.net1.network)
pullup(ora.net1.network)
ora.listener.lsnr
...
STOP_DEPENDENCIES=hard(ora.net1.network)
...
ora.net1.network
USR_ORA_VIP=rac1-vip
VERSION=11.2.0.2.0
Oracle Grid
OS
13
rac2
ora.rac2.vip
ora.listener.lsnr
ora.net1.network
Infrastructure
OS
VIPs and Networks

The network resource
The Oracle network resource monitors the
public network interface(s) (e.g. eth0).
The default is network number 1 (net1)
There is one network resource per subnet:
rac2
[GRID]> srvctl config network
Network exists:
1/192.168.0.0/255.255.255.0/eth0, type static
ora.rac1.vip
ora.rac2.vip
ora.listener.lsnr
ora.listener.lsnr
ora.net1.network
ora.net1.network
New in 11.2.0.2:
Direct management of the network resource
srvctl verb network
Network type support (static, dhcp, mixed)
14
rac1

OS
OS
VIPs and Networks

How to enable multiple networks in the cluster?
1
[GRID]> srvctl add network h

Adds a network configuration to the Oracle Clusterware.
Usage: srvctl add network
-k <net_num>
network number
(default number is 1)
-S <subnet>/<netmask>/[if1[|if2...]]
NET address spec for network
-w <network_type>
The network type

(static, dhcp, mixed)
-h
Print usage
-v
Verbose output
For example:
srvctl add network -k 2 -S 10.1.1.0/255.255.255.0
15
ora.net1.network
ora.net1.network
ora.net2.network
ora.net2.network

OS
OS
VIPs and Networks

How to enable multiple networks in the cluster?
2
[GRID]> srvctl add vip -h

Adds a VIP to the Oracle Clusterware.
Usage: srvctl add vip
-n <node_name>
Node name
-A <vip_name|ip>/<netmask>/[if1[|if2...]]
VIP address spec for node applications
-k <net_num>
network number
(default number is 1)
ora.rac2.vip
ora.rac2-vip2.vip
-h
Print usage
ora.net1.network
ora.net1.network
-v
Verbose output
ora.net2.network
ora.net2.network
For example:
srvctl add vip -n rac1 -k 2 -A rac1-vip2/255.255.255.0
srvctl add vip -n rac2 -k 2 -A rac2-vip2/255.255.255.0
16
ora.rac1.vip
ora.rac1-vip2.vip

OS
OS
VIPs and Networks

Application / user and node VIPs
1
[GRID]> crsctl stat res ora.rac1-vip2.vip -p

NAME=ora.rac1-vip2.vip
TYPE=ora.cluster_vip_net2.type
...
HOSTING_MEMBERS=rac1
This is a node vip!
...
START_DEPENDENCIES=hard(ora.net2.network)
pullup(ora.net2.network)
...
STOP_DEPENDENCIES=hard(ora.net2.network)
...
USR_ORA_VIP=rac1-vip2
VERSION=11.2.0.2.0
17
ora.rac1.vip
ora.rac1-vip2.vip
ora.rac2.vip
ora.rac2-vip2.vip
ora.net1.network
ora.net1.network
ora.net2.network
ora.net2.network

OS
OS
VIPs and Networks

2
[GRID]> appvipcfg create

-network=1
-ip 192.168.0.66
-vipname=myVIP
-user=root
This is an application vip!

[GRID]> appvipcfg create
-network=2
-ip 10.1.1.88
-vipname=myNewVIP
-user=root
ora.rac1.vip
ora.rac1-vip2.vip
myVIP
ora.rac2.vip
ora.rac2-vip2.vip
myNewVIP
ora.net1.network
ora.net1.network
ora.net2.network
ora.net2.network

OS
18
OS
VIPs and Networks

3
[GRID]> crsctl stat res myVIP -p

NAME=myVIP
TYPE=app.appvip_net1.type
...
HOSTING_MEMBERS=rac1
...
This is an application vip!
ora.rac1.vip
ora.rac1-vip2.vip
myVIP
RESTART_ATTEMPTS=0
ora.rac2.vip
ora.rac2-vip2.vip
myNewVIP
...
USR_ORA_VIP=192.168.0.66
ora.net1.network
ora.net1.network
ora.net2.network
ora.net2.network
VERSION=11.2.0.2.0

You can modify it as needed!
19
OS
OS
Listeners and SCAN
20
Listeners
Listeners and dependencies
In Oracle RAC 11g Release 2 there have been
three major changes regarding listeners:
1.
Listeners per default now run from the

Oracle Grid Infrastructure (GRID) home
rac2
LISTENER_SCAN1
LISTENER_SCAN2
ora.SCAN1.VIP
ora.SCAN2.VIP
ora.rac1.vip
ora.rac2.vip
2.
Listeners are managed by an Oracle agent
3.
SCAN Listeners were introduced
ora.listener.lsnr
ora.listener.lsnr
ora.net1.network
ora.net1.network
A listener depends on a VIP

A listener depends indirectly on a network
21
rac1

OS
OS
Listeners
The default LISTENER
[GRID]> srvctl config listener
Name: LISTENER
Network: 1, Owner: oracle Grid Software Owner
Home: <CRS home>
rac1
End points: TCP:1521
rac2
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network

OS
22
OS
Listeners
The default LISTENER FAQ
Can you define another port? - YES
rac1
Can you define another owner? YES

Can you define another home? YES, if really needed.
Can I add another listener on another port? - YES
rac2
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network

OS
23
OS

1
[GRID]> srvctl modify listener -l LISTENER -p TCP:1545

Name: LISTENER
rac1
Network: 1, Owner: oracle
rac2
Home: <CRS home>

Check: <CRS HOME>/network/admin/endpoints_listener.ora before:
LISTENER_RAC1=(DESCRIPTION=(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=rac1-vip)
(PORT=1521))(ADDRESS=(PROTOCOL=TCP)
(HOST=192.168.0.51)(PORT=1521)(IP=FIRST))))
# line added by Agent
24
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network

OS
OS

2
[GRID]> srvctl modify listener -l LISTENER -p TCP:1545

Name: LISTENER
rac1
rac2
Home: <CRS home>

Check: <CRS HOME>/network/admin/endpoints_listener.ora after restart:
LISTENER_RAC1=(DESCRIPTION=(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=rac1-vip)
(PORT=1545))(ADDRESS=(PROTOCOL=TCP)
(HOST=192.168.0.51)(PORT=1545)(IP=FIRST))))
25
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network

OS
OS

Can you define another owner? - YES
[GRID]>
srvctl modify listener -l LISTENER -u root

You need to be root
[GRID]>
srvctl config listener
Name: LISTENER
rac1
Network: 1, Owner: root For demonstration

purposes only
rac2
Home: <CRS home>

ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network

OS
26
OS

Can you define another home? - YES
[GRID]> srvctl modify listener -l LISTENER
-o /u01/app/oracle/product/11.2.0/dbhome_1

Name: LISTENER
rac1
rac2

Home: /u01/app/oracle/product/11.2.0/dbhome_1
This may not be required.
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network
Instead, create a new listener from a separate home, if needed

and use the SRVCTL command as shown, but try using the GI home.
27
OS
OS
Listeners
Can I add another listener on another port? - YES
Name: LISTENER
Home: <CRS home>
rac1
rac2
Name: LISTENER2011
Home: <CRS home>
MOS Note 220970.1 - RAC: Frequently Asked Questions
How to use SCAN and node listeners with different ports?
28
Add additional node listeners to the system using different ports
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.LISTENERK2.lsnr
ora.LISTENERK2.lsnr
ora.net1.network
ora.net1.network

OS
OS
Listeners
Can I add another listener on another network? - YES
[GRID]> srvctl add listener -l ListenerK2 -p 1544 -k 2
Name: LISTENER
rac1
Home: <CRS home>

Name: LISTENERK2
ora.LISTENER.lsnr
ora.LISTENER.lsnr
Ora.LISTENERK2.lsnr
ora.LISTENERK2.lsnr
ora.net1.network
ora.net1.network
ora.net2.network
ora.net2.network
Home: <CRS home>

MOS Note 1063571.1 - How to Configure A Second

Listener on a Separate Network in 11.2 Grid Infrastructure
29
rac2

OS
OS
Listeners
Remember its just another listener
1

Name: JUSTALISTENER
Network: 1, Owner: root
Home: <CRS home>
rac2
LISTENER_SCAN1
LISTENER_SCAN2
...
ora.SCAN1.VIP
ora.SCAN2.VIP
ora.rac1.vip
ora.rac2.vip
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network
[GRID]> vi /u01/app/11.2.0/grid/network/admin/listener.ora
JUSTALISTENER=(DESCRIPTION=(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=IPC)(KEY=JUSTALISTENER))))
[GRID]> vi /u01/app/11.2.0/grid/network/admin/endpoints_listener.ora
JUSTALISTENER_RAC1=(DESCRIPTION=(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=rac1-vip)(PORT=1522))
(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.0.51)(PORT=1522)(IP=FIRST))))
30
rac1

OS
OS
Listeners
Remember its just another listener
2
(ADDRESS=(PROTOCOL=IPC)(RATE_LIMIT=10) For demonstration purposes only
(KEY=JUSTALISTENER)))) # line added by Agent
...
[GRID]> srvctl stop listener -l JustAListener
rac2
LISTENER_SCAN1
LISTENER_SCAN2
ora.SCAN1.VIP
ora.SCAN2.VIP
ora.rac1.vip
ora.rac2.vip
...
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network
[GRID]> srvctl start listener -l JustAListener

(ADDRESS=(PROTOCOL=IPC)(RATE_LIMIT=10)
(KEY=JUSTALISTENER)))) # line added by Agent
31
rac1

OS
OS
SCAN
The basics and overview
In Oracle RAC 11g Release 2
SCAN Listeners were introduced
SCAN
There is one SCAN setup per cluster
Read about SCAN:
http://www.oracle.com/technetwork/database/
clustering/overview/scan-129069.pdf
MOS Note 887522.1
11gR2 Grid Infrastructure Single Client
Access Name (SCAN) Explained
SCAN consists of a bundle containing:
32
1.
SCAN IP
2.
Associated (dependency) SCAN Listener
rac2
rac1
rac3
LISTENER_SCAN1
LISTENER_SCAN2
LISTENER_SCAN3
ora.SCAN1.VIP
ora.SCAN2.VIP
ora.SCAN3.VIP
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network
ora.net1.network

OS
OS
OS
SCAN
The SCAN bundle
1 3 SCANs are the default for HA and LB
SCAN
Regardless of number of nodes

You can define less or more, if really needed.
SCAN listener resources run with
an active dispersion dependency
If you use more nodes in the cluster than
SCAN listeners are defined, no node should
run more than one SCAN bundle at a time
If you use less nodes in the cluster than
SCAN listeners are defined, there will be
nodes running more than one SCAN bundle
at a time.
SCAN VIP moves with the listener, if possible.
33
rac2
rac1
rac3
LISTENER_SCAN1
LISTENER_SCAN2
LISTENER_SCAN3
ora.SCAN1.VIP
ora.SCAN2.VIP
ora.SCAN3.VIP
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network
ora.net1.network

OS
OS
OS
SCAN
The SCAN bundle
2
[GRID]> srvctl config scan

SCAN name: cluster1, Network: 1/192.168.0.0/255.255.255.0/eth0
SCAN VIP name: scan1, IP: /cluster1.us.oracle.com/192.168.0.41
rac1
rac2
[GRID]> srvctl modify scan
LISTENER_SCAN1
Modifies the SCAN name.
ora.SCAN1.VIP
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network
Usage: srvctl modify scan

-n <scan_name>
Domain name qualified SCAN name
-h
Print usage
http://www.oracle.com/technetwork/database/
clustering/overview/scan-129069.pdf page 2
34
SCAN

OS
OS
SCAN
The SCAN bundle
3
[GRID]> srvctl add scan -h

Adds a SCAN VIP to the Oracle Clusterware.
Usage: srvctl add scan -n <scan_name>
-n <scan_name>
Domain name qualified SCAN name
-k <net_num>
network number (default number is 1)
SCAN
rac1
rac2
LISTENER_SCAN1
-S <subnet>/<netmask>/[if1[|if2...]]
NET address spec for network
ora.SCAN1.VIP
-h
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network
Print usage
Note: SCAN can only operate on one network / in one subnet.

OS
35
OS
SCAN
The SCAN FAQ
1 From MOS Note 220970.1
RAC: Frequently Asked Questions
SCAN
With Oracle RAC 11g Release 2 using SCAN is the default.

As with other listeners, there is no direct communication
between the node (listeners) and the SCAN listeners.
Listeners are only aware of the instances and services served,

since the instances (PMON) register themselves and the services
they host with the listeners.
The instances use the LOCAL and REMOTE Listener
parameters to know with which listeners to register.
Listeners used for a client connection to Oracle RAC should be
managed by Oracle Clusterware and should be listening on an
Oracle managed VIP.
36
rac1
rac2
LISTENER_SCAN1
ora.SCAN1.VIP
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network

OS
OS
SCAN
The SCAN FAQ
2 Can you define another port? - YES
See MOS Note 220970.1
Use srvctl modify scan_listener p <newPort>
Can you define another owner? NO

Can you define another home? NO
Can you have more than one node listener with SCAN? YES
Can the SCAN and the node listener ports differ? - YES
See also MOS Note 972500.1 How to
Modify SCAN Setting or SCAN Listener Port after Installation
37
SCAN
rac1
rac2
LISTENER_SCAN1
ora.SCAN1.VIP
ora.LISTENER.lsnr
ora.LISTENER.lsnr
ora.net1.network
ora.net1.network

OS
OS
Listeners and Instance Registration

Listener changes may require instance changes
See MOS Note 220970.1
Whenever you change an instance parameter configuration

a change to the LOCAL_LISTENER or REMOTE_LISTENER
per database (instance) may be required.
Note that using server-side TNSANMES aliases to
resolve the listener configuration is not recommended.
The use of the TNSNAMES connector string is the default:
local_listener = (DESCRIPTION= (ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.0.61)(PORT=2011))
))'
38
SCAN
rac1
rac2
DB Instance
DB Instance
LISTENER_SCAN1
ora.SCAN1.VIP
ora.LISTENER.lsnr
ora.LISTENER.lsnr

OS
OS

EXAMPLE
1 Taken from MOS Note 220970.1 RAC: FAQ
srvctl add listener -l LISTENER2011 -p 2011
srvctl start listener -l LISTENER2011
srvctl status listener -l LISTENER2011
lsnrctl status LISTENER2011
rac1
rac2
DB Instance
DB Instance
LISTENER_SCAN1
ora.SCAN1.VIP
ora.LISTENER.lsnr
ora.LISTENER.lsnr
Name: LISTENER2011

Home: <CRS home>
39
SCAN

OS
OS

EXAMPLE
SCAN
rac1
rac2
New node listener does not serve any database instance

You must alter the LOCAL_LISTENER parameters
for each instance accordingly:
alter system set local_listener =
(DESCRIPTION= (ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.0.61)(PORT=2011))))
' scope=BOTH SID='OCRL1';
alter system register;
DB Instance
LISTENER_SCAN1
ora.SCAN1.VIP
ora.LISTENER.lsnr
ora.LISTENER.lsnr

OS
40
DB Instance
OS

EXAMPLE
SCAN
rac1
rac2
Note: Use spaces between the various segments of the command

DB Instance
LISTENER_SCAN1
ora.SCAN1.VIP
If the string looks unaltered it will reset these parameters

with the default values that it determines on instance startup.
ora.LISTENER.lsnr
ora.LISTENER.lsnr
Slight modifications are therefore required. ER 11772838

has been filed to allow for a more convenient mechanism.
41
DB Instance
Reason: the database agent in Oracle Clusterware currently

determines whether the local_listener or remote_listener have
been manually set by a string comparison operation.

OS
OS

Using listeners in different subnets / networks
SCAN can only operate in one network / subnet
If listeners in different subnets are used,
use LISTENER_NETWORKS:
http://download.oracle.com/docs/cd/E11882_01
/server.112/e17110/initparams115.htm#REFRN10313
Note: Listeners specified by the LISTENER_NETWORKS

parameter should not be used in the LOCAL_LISTENER and
REMOTE_LISTENER parameters. Otherwise, cross registration
will happen and connections will be redirected cross networks.
For more information, see also

MOS Note 1063571.1 How to Configure A Second
Listener on a Separate Network in 11.2 Grid Infrastructure
42
rac1
rac2
DB Instance
DB Instance
LISTENER_SCAN1
ora.SCAN1.VIP
ora.LISTENER.lsnr
ora.LISTENER.lsnr
Ora.LISTENERK2.lsnr
ora.LISTENERK2.lsnr
ora.net1.network
ora.net1.network
ora.net2.network
ora.net2.network

OS
OS
Listeners, SCAN and Services
43
Listeners and Service Registration

A summary
Services depend on a database
Per default, the database instance will register
all services it hosts with all listeners it registers with.
SCAN
rac1
Services operate within the following boundaries:

Network (indirectly via dependency)
Server Pools (in policy-managed database environments)
Currently there is no support for service failover
Between Server Pools

Between networks
44
rac2
DB Instance
DB Instance
ora.Dbname.db
ora.Dbname.db
ora.LISTENER.lsnr
ora.LISTENER.lsnr

OS
OS
Services and Dependencies

Dependency on DB and Server Pool
1
[GRID]> srvctl config service -d ORCL -s MyService

Service name: MyService
Service is enabled
SCAN
Server pool: ORCL

rac1
Cardinality: 1
Disconnect: false
Service role: PRIMARY
Management policy: AUTOMATIC
...
Preferred instances: ORCL_1
Available instances:
rac2
DB Instance
ora.ORCL.db
ora.ORCL.db
ora.ORCL.MyService.svc
ora.LISTENER.lsnr
ora.LISTENER.lsnr

OS
45
DB Instance
OS
Services and Dependencies

Start / Stop dependencies
2
[GRID]> crsctl stat res ora.orcl.myservice.svc -p

...
DEFAULT_TEMPLATE=PROPERTY(RESOURCE_CLASS=service)
PROPERTY(SERVICE_NAME=%GEN_SERVICE_NAME%)
PROPERTY(DB_UNIQUE_NAME=CONCAT(PARSE(%NAME%, .,
2), STAT(ora.orcl.db, USR_ORA_DOMAIN), .))
ELEMENT(INSTANCE_NAME=STAT(ora.orcl.db,
GEN_USR_ORA_INST_NAME))
...
START_DEPENDENCIES=hard(ora.orcl.db,type:ora.cluster
_vip_net1.type) weak(type:ora.listener.type)
pullup(type:ora.cluster_vip_net1.type)
pullup:always(ora.orcl.db)
dispersion(type:ora.service.type)
STOP_DEPENDENCIES=hard(intermediate:ora.orcl.db,inte
rmediate:type:ora.cluster_vip_net1.type)
...
46
SCAN
rac1
rac2
DB Instance
DB Instance
ora.ORCL.db
ora.Dbname.db
ora.ORCL.MyService.svc
ora.LISTENER.lsnr
ora.LISTENER.lsnr

OS
OS
47
48

Understanding Oracle RAC Internals - Part 1 - Slides PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Understanding Oracle RAC Internals - Part 1 - Slides PDF

Uploaded by

Copyright:

Available Formats

1

Copyright 2011, Oracle and/or its affiliates. All rights reserved.