Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Download
Standard view
Full view
of .
Look up keyword
Like this
9Activity
0 of .
Results for:
No results containing your search query
P. 1
SINGLE CLIENT ACCESS NAME (SCAN)

SINGLE CLIENT ACCESS NAME (SCAN)

Ratings: (0)|Views: 489|Likes:
Published by ittichai
SINGLE CLIENT ACCESS NAME (SCAN)
SINGLE CLIENT ACCESS NAME (SCAN)

More info:

Published by: ittichai on Apr 13, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

09/29/2010

pdf

text

original

 
 Page 1 Oracle Technical Paper 
SS
IINNGGLLEE 
CC
LLIIEENN T T 
 A  A 
CCCCEESSSS 
NN
 A  A MMEE 
((SSCC A  A NN)) 
Single Client Access Name (SCAN) is 
s a new Oracle Real Application Clusters (RAC) 11
 
Release 2 feature that providesa single name for clients to access an Oracle Database running in a cluster. The
benefit
is clients using SCAN do notneed to change if you add or remove nodes in the cluster. Having a single name to access the cluster allows clients touse the EZConnect client and the simple JDBC thin URL to access any database running in the clusters independently of which server(s) in the cluster the database is active. SCAN provides load balancing and failover of clientconnections to the database. The SCAN works as an IP alias for the cluster.
sqlplus system/manager@sales1-scan:1521/oltp
 
jdbc:oracle:thin:@sales1-scan:1521/oltp
 
Figure 1 Sample EZConnect and Thin JDBC Connect Strings
 
N
ETWORK 
EQUIREMENTS FOR 
U
SING
SCAN
 The SCAN is configured during the installation of the grid infrastructure that is distributed with Oracle Database 11g Release2. The grid infrastructure is a single binary distribution that contains Oracle Clusterware and Oracle AutomaticStorage Management. You must install the grid infrastructure in order to use Oracle RAC 11g Release 2. During theinterview phase of the grid infrastructure installation, you will be prompted for the SCAN. There are 2 options fordefining the SCAN:1.
 
Define the SCAN in your corporate DNS (Domain Name Service)2.
 
Use the Grid Naming Service (GNS).If you choose Option 1, you must ask your network administrator to create a single name that resolves to 3 IPaddresses using a round robin algorithm. The IP addresses must be on the same subnet as your public network in thecluster. The name must be 15 characters or less in length not including the domain and must be resolvable without thedomain suffix (I.E. sales1-scan must be resolvable). The IPs should not be configured to a network interface on thecluster, the Oracle Clusterware will take care of it.
sales1-scan.example.com IN A 133.22.67.194IN A 133.22.67.193IN A 133.22.67.192
 
Figure 2 Sample DNS entry for SCANNote:
DNS using a round robin algorithm on its own does not supply failover of connections however this is takencare of by the Oracle Client. It is
recommended
that the client used is the Oracle Database 11g Release 2 version of the client.If you choose option 2, you only need to enter the SCAN during the interview. During cluster configuration, three IPaddresses will be acquired from a DHCP service (using GNS assumes you have a DHCP service available on yourpublic network) to create the SCAN and name resolution for the SCAN will be provided by the GNS
1
.
SCAN
 
C
ONFIGURATION
I
N THE
C
LUSTER 
 
During cluster configuration, several resources are created in the cluster for SCAN. For each of the 3 IP addressesthat the SCAN resolves to, a SCAN VIP resource is created and a SCAN Listener is created. The SCAN Listener isdependent on the SCAN VIP and the 3 SCAN VIPs (along with their associated listeners) will be dispersed across thecluster. This means we will try to run each pair of resources on a different node in the cluster. If the node where aSCAN VIP is running fails, the SCAN VIP and its associated listener will failover to another node in the cluster.
$srvctl config scan_listenerSCAN Listener LISTENER_SCAN1 exists. Port: TCP:1521SCAN Listener LISTENER_SCAN2 exists. Port: TCP:1521
1
Please read the Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for details on how to install a cluster using theGrid Naming Service http://download.oracle.com/docs/cd/E11882_01/install.112/e10812/prelinux.htm#BABFDGHJ
 
 Page 2 Oracle Technical Paper 
SCAN Listener LISTENER_SCAN3 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.143SCAN VIP name: scan2, IP: /sales1-scan.mycompany.com/192.87.58.99SCAN VIP name: scan3, IP: /sales1-scan.mycompany.com/192.87.58.100
 
Figure 3 Sample SCAN configuration
D
 ATABASE
C
ONFIGURATION USING
SCAN
For Oracle Database 11g Release 2, the REMOTE_LISTENER parameter should be set to the SCAN. This allowsthe instances to register with the SCAN Listeners to provide information on what services are being provided by theinstance, the current load, and a recommendation on how many incoming connections should be directed to theinstance. Note: This is using the easy connect naming method, if you need to modify your SQLNET.ORA, ensurethat EZCONNECT is in the list if you specify the order of the naming methods used for client name resolutionlookups (11g Release 2 default is NAMES.DIRECTORY_PATH=(tnsnames, ldap, ezconnect)). TheLOCAL_LISTENER parameter should be set to the node VIP. If you need fully qualified domain names, ensure thatLOCAL_LISTENER is set to the fully qualified domain name (node-vip.mycompany.com). By default a local listeneris created during cluster configuration that runs out of the grid infrastructure home and listens on the specified port(default is 1521) of the node VIP. SCAN only works on the initial public network (net1). Do not set yourREMOTE_LISTENER to a TNSNAMES alias that has the HOST=SCAN in the ADDRESS, setREMOTE_LISTENER=SCAN:PORT for proper listener registration.
C
ONNECTION
L
OAD
B
 ALANCING
U
SING
SCAN
For client connections, SQL*Net (11g Release 2) will get the 3 IP addresses that the SCAN resolves to. It will gothrough the list is receives from the DNS and try connecting to that listener. If the client receives an error, it will try the other addresses before returning an error to the client. This is similar to how client connection failover works inprevious releases when an address list is provided in the client connection string. When a SCAN Listener receives a connection request, the SCAN Listener will check for the least loaded instanceproviding the requested service. It will then re-direct the connection request to the local listener on the node wherethe least loaded instance is running. The client will be given the address of the local listener and must be able toresolve the node VIP address it is given. The local listener will create the connection to the database instance.
Alication ServeClientSCAN ListenersOracle RAC

Activity (9)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
hanyattia35 liked this
boumedi liked this
momer_alb liked this
ALi liked this
dzafir liked this
juniocesar liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->