scan setup

8/13/2019 Scan Setup

http://slidepdf.com/reader/full/scan-setup 1/21

Step by step DNS Configuration on Linux

Step by step DNS Configuration on Linux RHEL5/OEL5

Welcome to our page !n t"is page #e are going to $iscuss about Domain Name Ser%er&DNS' configuration Later t"e same DNS

configuration going to use Oracle ((g Release ) Real *pplication Cluster &R*C' !nstallations

Step 1 : Login as root and install below listed Bind RPM's.

rpm -Uvh bind-9.3.3-7.el5.i386.rpm \bind-chroot-9.3.3-7.el5.i386.rpm \bind-devel-9.3.3-7.el5.i386.rpm \bind-libbind-devel-9.3.3-7.el5.i386.rpm \bind-libs-9.3.3-7.el5.i386.rpm \bind-sdb-9.3.3-7.el5.i386.rpm \system-config-bind-4.0.3-.el5.no!rch.rpm \c!ching-n!meserver-9.3.3-7.el5.i386.rpm \

postgres"l-libs-8.#.4-#.#.i386.rpm Step 2: Verify the IP address for the !S ser"er. #se following $o%%and to $he$& the IP address.

$root%dnc &'( ifconfig

eth0 )in* enc!p+,thernet !ddr 00+0/+9+7+60+13

inet !ddr+192.168.1.100 2c!st+#9.#68.#.55 !s*+55.55.55.0

inet6 !ddr+ fe80++0c+9ff+fe7d+60f364 cope+)in*

U 2/: U;;<;= U):</: :U+#500 etric+#

> p!c*ets+8 errors+0 dropped+0 overr?ns+0 fr!me+0

:> p!c*ets+39 errors+0 dropped+0 overr?ns+0 c!rrier+0

collisions+0 t@"?e?elen+#000

> bytes+49#9 A4.8 Bi2C :> bytes+568 A5.4 Bi2C

<nterr?pt+67 2!se !ddress+0@04

Step : (here are fo)r files we ha"e to edit. *ind the below easy steps to $onfig)re the !S ser"er.

1. +reate a na%ed.$onf file )sing sa%ple na%ed.$a$hing,na%eser"er.$onf file.

$root%dnc &'( cd v!rn!medchrootetc

$root%dnc etc'( ls

loc!ltime n!med.c!ching-n!meserver.conf n!med.rfc#9#.Dones rndc.*ey

$root%dnc etc'(cp n!med.c!ching-n!meserver.conf n!med.conf

2. -dit the na%ed.$onf file based on yo)r $onfig)ration. *or ea%ple.

options E

listen-on port 53 E #9.#68.#.#00F GF

( listen-on-v6 port 53 E ++#F GF

directory Hv!rn!medHF

d?mp-file Hv!rn!medd!t!c!cheId?mp.dbHF

st!tistics-file Hv!rn!medd!t!n!medIst!ts.t@tHF

memst!tistics-file Hv!rn!medd!t!n!medImemIst!ts.t@tHF

:hose options sho?ld be ?sed c!ref?lly bec!?se they dis!ble port

r!ndomiD!tion

"?ery-so?rce port 53F

"?ery-so?rce-v6 port 53F

!lloJ-"?ery E !nyF GF

!lloJ-"?ery-c!che E loc!lhostF GF



GF

logging E

ch!nnel def!?ltIdeb?g E

file Hd!t!n!med.r?nHF

severity dyn!micF

GF

GF

vieJ loc!lhostIresolver E m!tch-clients E !nyF GF

m!tch-destin!tions E #9.#68.#.#00F GF

rec?rsion yesF

incl?de Hetcn!med.rfc#9#.DonesHF

GF

. -dit na%ed.rf$1/12.0ones file. Sa%ple file gi"en below.

Done H.H <; E

type hintF

file Hn!med.c!HF

GF

Done Hindi!.comH <; E type m!sterF

file HforJ!rd.DoneHF

!lloJ-?pd!te E noneF GF

GF

Done Hloc!lhostH <; E

type m!sterF

file Hloc!lhost.DoneHF


GF

Done H#.#68.#9.in-!ddr.!rp!H <; E

type m!sterF

file Hreverse.DoneHF


GF..

. +hange the per%ission to the abo"e two files.

chgrp n!med n!med.conf

. +hange the dire$tory to below lo$ation

cd v!rn!medchrootv!rn!med

cp loc!ldom!in.Done forJ!rd.Done

cp n!med.loc!l reverse.Done

3. Modify the forward.0one file. ea%ple

K::) 86400

% <; dnc.indi!.com. root.dnc.indi!.com. A

4 F seri!l Ad. !d!msC

3 F refresh

#5 F retry

# F e@piry

# C F minim?m

<; ; dnc.indi!.com.

dnc <; #9.#68.#.#00



7. Modify the reverse.zone file

K::) 86400

% <; dnc.indi!.com. root.dnc.indi!.com. A

#9970700 F eri!l

8800 F efresh

#4400 F etry

3600000 F ,@pire

86400 C F inim?m

<; ; dnc.indi!.com.

#00 <; : dnc.indi!.com.

4. +hange the ownership for both the files.

chgrp n!med reverse.Done

chgrp n!med forJ!rd.Done

/. %a&e an entry to both 5et$5hosts and 5et$5resol"e.$onf files. (he sa%ples are below.

c!t etchosts

#9.#68.#.#00 dnc.indi!.com dnc

c!t etcresolve.conf

se!rch indi!.com

n!medserver #9.#68.#.#00

16. Restart the na%ed ser"i$es )sing below state%ent.

service named restart

11. Verify the !S ser"er )sing below state%ents

$root%dnc n!med'( dig dnc.indi!.com

F LM i= 9.3.6-#-ed!t-9.3.6-4.#.el5I4. LM dnc.indi!.com

FF glob!l options+ printcmd

FF =ot !nsJer+

FF -M,,L- opcode+ NU,OP st!t?s+ ;,P id+ #483

FF fl!gs+ "r !! rd r!F QUERY: 1, ANSWER: 1P U:<:O+ #P <:<;)+ 0

FF NU,:<; ,/:<;+

Fdnc.indi!.com. <;

FF ;, ,/:<;+

dnc.indi!.com. 86400 <; #9.#68.#.#00

FF U:<:O ,/:<;+

indi!.com. 86400 <; ; dnc.indi!.com.

FF N?ery time+ # msec

FF ,Q,+ #9.#68.#.#00(53A#9.#68.#.#00C

FF ,;+ on ?g 7 3+54+49 0#

FF = <R, rcvd+ 6#

12. (o $he$& re"erse the 0one

$root%dnc n!med'( dig -@ #9.#68.#.#00

F LM i= 9.3.6-#-ed!t-9.3.6-4.#.el5I4. LM -@ #9.#68.#.#00

FF glob!l options+ printcmd

FF =ot !nsJer+



FF -M,,L- opcode+ NU,OP st!t?s+ ;,P id+ 55949

FF fl!gs+ "r !! rd r!F NU,O+ #P ;,+ P U:<:O+ #P <:<;)+ #

FF NU,:<; ,/:<;+

F#00.#.#68.#9.in-!ddr.!rp!. <; :

FF ;, ,/:<;+

#00.#.#68.#9.in-!ddr.!rp!. 86400 <; : dnc-priv.indi!.com.

#00.#.#68.#9.in-!ddr.!rp!. 86400 <; : dnc.indi!.com.

FF U:<:O ,/:<;+#.#68.#9.in-!ddr.!rp!. 86400 <; ; dnc.indi!.com.

FF <:<;) ,/:<;+

dnc.indi!.com. 86400 <; #9.#68.#.#00

FF N?ery time+ # msec

FF ,Q,+ #9.#68.#.#00(53A#9.#68.#.#00C

FF ,;+ on ?g 7 3+57+7 0#

FF = <R, rcvd+ #4

1. (o "erify !S Ser"er )sing nsloo&)p

$root%dnc n!med'( nsloo*?p dnc.indi!.com

erver+ #9.#68.#.#00

ddress+ #9.#68.#.#00(53

;!me+ dnc.indi!.comddress+ #9.#68.#.#00

DNS server working fine now. Finally we got success.

14. For Oracle 11gR2 RAC Installation adding node Information in/var/named/cr!!t/var/named/"!r#ard.$!ne "i%e

!n DNS server.

K::) 86400

% <; dnc.indi!.com. root.dnc.indi!.com. A 4 F seri!l Ad. !d!msC

3 F refresh #5 F retry

# F e@piry # C F minim?m <; ; dnc.indi!.com.

dnc <; #9.#68.#.#00*r!cnode# <; #9.#68.#.50

*r!cnode <; #9.#68.#.5#

*r!cnode#-vip <; #9.#68.#.60*r!cnode-vip <; #9.#68.#.6#

*r!cnode-sc!n <; #9.#68.#.70*r!cnode-sc!n <; #9.#68.#.7#

*r!cnode-sc!n <; #9.#68.#.7

15. Restart named service as a root user.

$root%dnc n!med'( service n!med rest!rttopping n!med+ $ B '

t!rting n!med+ $ B '

16. Verify the SCAN names using nslookup.

$root%dnc n!med'( nsloo*?p *r!cnode-sc!n



erver+ #9.#68.#.#00ddress+ #9.#68.#.#00(53

;!me+ *r!cnode-sc!n.indi!.comddress+ #9.#68.#.7


;!me+ *r!cnode-sc!n.indi!.comddress+ #9.#68.#.7#

17. Add below files in /etc/resolv.conf file on all the nodes.

se!rch indi!.com

n!meserver #9.#68.#.#00

$or!cle%*r!c# '( c!t etcresolv.conf

se!rch indi!.comn!meserver #9.#68.#.#00

$root%*r!c# bin'( nsloo*?p *r!cnode-sc!nerver+ #9.#68.#.#00

ddress+ #9.#68.#.#00(53

;!me+ *r!cnode-sc!n.indi!.com

ddress+ #9.#68.#.7#;!me+ *r!cnode-sc!n.indi!.com

ddress+ #9.#68.#.7


18. DNS server ready for Oracle 11gR2 RAC setup go ahead and start RAC installation using below blog.

Creating a RAC Database Manually (without dbca)

Step by Step Creating a RAC Database Manually(without dbca)

If you would like to by-pass the Database Configuration Assistant (dbca), youcan use the following steps - with appropriate alterations - to create yourRAC databases. his e!a"ple assu"es that you already ha#e a cluster withthe appropriate clusterware and shared storage, etc. configured.

If not already present, Refer below link for "ore details.

Oracle((gR(&(((+,+' R*C !nstallation Steps onLinux

$anual Database creation steps as follows.

%tep &' n#iron"ent #ariable %ettings ( irst *ode).

http://dnccfg.blogspot.in/2012/09/oracle-11gr1111060-rac-installation.html




e@port /),I2,S?0!ppor!cle

e@port /),I,SK/),I2,prod?ct##.#.0dbI#

e@port /),I<S,Q2#

%tep +' erify e!ist RAC setup. or "ore details about RAC installationguideCIC/R

$or!cle%*r!c# dbs'K crsIst!t -t;!me :ype :!rget t!te ost------------------------------------------------------------or!....)#.inst !pplic!tion ;)<;, ;)<;, *r!c#or!....).inst !pplic!tion ;)<;, ;)<;, *r!cor!./).db !pplic!tion ;)<;, ;)<;, *r!c#or!....#.!sm !pplic!tion ;)<;, ;)<;, *r!c#or!..../#.lsnr !pplic!tion ;)<;, ;)<;, *r!c#or!.*r!c#.gsd !pplic!tion ;)<;, ;)<;, *r!c#or!.*r!c#.ons !pplic!tion ;)<;, ;)<;, *r!c#or!.*r!c#.vip !pplic!tion ;)<;, ;)<;, *r!c#or!.....!sm !pplic!tion ;)<;, ;)<;, *r!cor!..../.lsnr !pplic!tion ;)<;, ;)<;, *r!c

or!.*r!c.gsd !pplic!tion ;)<;, ;)<;, *r!cor!.*r!c.ons !pplic!tion ;)<;, ;)<;, *r!cor!.*r!c.vip !pplic!tion ;)<;, ;)<;, *r!c

$or!cle%*r!c# dbs'K olsnodes -i -p*r!c# *r!c#-priv *r!c#-vip*r!c *r!c-priv *r!c-vip

$or!cle%*r!c# dbs'K . or!env/),I< S $T#' T#:he r!cle b!se for /),I,S?0!ppor!cleprod?ct##.#.0!smI# is?0!ppor!cle

$or!cle%*r!c# dbs'K !smcmd/V ls -ltrt!te :ype eb!l ;!meU;:, ,>:,; ; 1U;:, ,>:,; ; :/V

*ote ' Do"ain na"e is dbprod.co" ( e!a"ple ' krac&. dbprod.co" ).

%tep 0 ' 1repare initiali2ation para"eter file (initDD3&.ora) and store itin 45RAC6/5$7dbs directory.

dbIbloc*IsiDeS8#9cl?sterId!t!b!seIinst!ncesSremoteIlistenerS)<:,;,I,Q2openIc?rsorsS300dbIdom!inS2./dbIn!meS,Q2dbIcre!teIfileIdestST:dbIrecoveryIfileIdestST1dbIrecoveryIfileIdestIsiDeS#47483648





comp!tibleS##.#.0.0.0di!gnosticIdestS?0!ppor!cleprocessesS#50sg!It!rgetS635437056!?ditIfileIdestS?0!ppor!cle!dmin,Q2!d?mp!?ditItr!ilSdbremoteIloginIp!ssJordfileSe@cl?sivedisp!tchersSHA:/)S:/C A,Q</,S,Q2>2CHpg!I!ggreg!teIt!rgetS##8#35,Q2#.inst!nceIn?mberS#,Q2.inst!nceIn?mberS,Q2.thre!dS,Q2#.thre!dS#,Q2#.?ndoIt!blesp!ceSU;:2#,Q2.?ndoIt!blesp!ceSU;:2

%tep 8' Creating password file.

$or!cle%*r!c# dbs'K or!pJd fileSK/),I,dbsor!pJK/),I<

p!ssJordSor!cle

%tep 9 ' Configure both listener.ora and tnsna"es.ora file for all nodes incluster.

-- ;ode (# )istener.or!.

)<:,;,IB/# S A,/<:<;I)<: S

A,/<:<; S

A, S A:/) S :/CA: S *r!c#-vipCA: S #5#CA< S 1<:CC A, S A:/) S :/CA: S #5.#68.#.50CA: S #5#CA< S 1<:CC

C C

;ode ( )istener.or!.

)<:,;,IB/ S A,/<:<;I)<: S

A,/<:<; S A, S A:/) S :/CA: S *r!c-vipCA: S #5#CA< S 1<:CC

A, S A:/) S :/CA: S #5.#68.#.5#CA: S #5#CA< S 1<:CC

C C

tnsna"es.ora file

)<:,;,I,Q2 S A,I)<: S

A, S A:/) S :/CA: S *r!c#-vipCA: S #5#CC A, S A:/) S :/CA: S *r!c-vipCA: S #5#CC

C

,Q2 S

A,/<:<; S A, S A:/) S :/CA: S *r!c#-vipCA: S #5#CC



A, S A:/) S :/CA: S *r!c-vipCA: S #5#CC A)I2);/, S yesC

A/;;,/:I: S

A,Q, S ,</:,C A,Q</,I;, S ,Q2.2./C

C C

,Q2 S A,/<:<; S

A, S A:/) S :/CA: S *r!c-vipCA: S #5#CC A/;;,/:I: S

A,Q, S ,</:,C A,Q</,I;, S ,Q2.2./C

A<;:;/,I;, S ,Q2C

C C

,Q2# S

A,/<:<; S

A, S A:/) S :/CA: S *r!c#-vipCA: S #5#CC

A/;;,/:I: S A,Q, S ,</:,C A,Q</,I;, S ,Q2.2./C

A<;:;/,I;, S ,Q2#C

C C

%tep : ' Create directory for database files and diagnostic files.

$or!cle%*r!c# &'K m*dir -p K/),I2,!dminK/),I<E!d?mpPdpd?mpPhd?mpG$or!cle%*r!c# &'K cd K/),I2,!dminK/),I<$or!cle%*r!c# ,Q2#'K ls -ltrtot!l #drJ@r-@r-@ or!cle oinst!ll 4096 ct #6 #8+4 hd?mp

drJ@r-@r-@ or!cle oinst!ll 4096 ct #6 #8+4 dpd?mpdrJ@r-@r-@ or!cle oinst!ll 4096 ct #6 #8+4 !d?mp

$or!cle%*r!c# dbs'K . or!env/),I< S $T#' T#:he r!cle b!se for /),I,S?0!ppor!cleprod?ct##.#.0!smI# is?0!ppor!cle$or!cle%*r!c# dbs'K !smcmd m*dir T:,Q2$or!cle%*r!c# dbs'K !smcmd ls T:&E'&(/ )) &irect!r* as +een created./)$or!cle%*r!c# dbs'K

%tep ;' !ecute Create database co""and.

$or!cle%*r!c# dbs'K s"lpl?s H !s sysdb!H

N)Wl?s+ ele!se ##.#.0.6.0 - rod?ction on :?e ct #6 #9+0+5 0#

/opyright AcC #98P 007P r!cle. ll rights reserved.

/onnected to !n idle inst!nce.



N)V st!rt?p nomo?nt/), inst!nce st!rted.

:ot!l ystem =lob!l re! 640949# bytes1i@ed iDe #30#784 bytesQ!ri!ble iDe #7#96708 bytes

!t!b!se 2?ffers 46#373440 bytesedo 2?ffers 565480 bytesN)V /,:, :2, H,Q2H ><;:;/, 3 3 >)=<:O # 4 >)=1<), #9 5 >)=,2, 3 6 >:1<), #04 7 :1<), <R, 300 U:,>:,; ; ;,>: #04 ><R, U;)<<:, 8 ,>:,;: ;=,,;: )/) 9 OU> :1<), <R, #0 U:,>:,; ; ;,>: #04 ><R, U;)<<:, #0 ))1<), ,1U): :,O :2),/, :, :,1<), <R, 0 U:,>:,;; ;,>: 640B ><R, U;)<<:,

## ))1<), U; :2),/, HU;:2#H :1<), <R, 00 U:,>:,; ;;,>: 5#0B ><R, U;)<<:, # ,1U): :2),/, U, :1<), <R, #00 #3 //:, ,: ,8<;#5 #4 ;:<;) //:, ,: )#6U:1#6 #5 )=1<), =U # <R, 500P #6 =U <R, 500 #7 U, O <,;:<1<, 2O /), #8 U, O:, <,;:<1<, 2O /),F

!t!b!se cre!ted.

%tep <' Adding -NR-ES para"eter in pfile.

N)V set linesiDe 048FN)V col?mn ctlIfiles ;,IQ)U, ctlIfilesFN)V select conc!tAXcontrolIfilesSXXXP conc!tArepl!ceAv!l?eP XP XP XXXPXXXCPXXXXCC ctlIfiles from vKp!r!meter Jhere n!me SXcontrolIfilesXFN)V host echo YctlIfiles VV K/),I,dbsinit,Q2#.or!F

%tep =' Create a >*D5 tablespace for re"aining nodes.

N)V /,:, ))1<), U; :2),/, HU;:2H :1<), <R, #00F

:!blesp!ce cre!ted.

%tep &?' Run following script as SYS user.

N)V /;;,/: O2/onnected.

N)V %rdbms!dminc!t!log.s"lN)V %rdbms!dminc!tbloc*.s"l



N)V %rdbms!dminc!tproc.s"lN)V ,:, /,

;, :O, Q)U,------------------------------------ ----------- ------------------------------secIc!seIsensitiveIlogon boole!n :U,

N)V ):, O:, ,: secIc!seIsensitiveIlogonS1),F

ystem !ltered.

%tep &&' Run following script as SYSE3 user.

N)V connect systemor!cle/onnected.N)V %s"lpl?s!dminp?pbld.s"lN)V %s"lpl?s!dminhelphlpbld.s"l help?s.s"l

%tep &+' Adding redo log file for re"aining nodes andrun catc%4st.s5% script as SYS.

N)V /;;,/: O2/onnected.N)V ):, :2, )=1<), :, =U 3 <R, 500P =U 4 <R, 500F

!t!b!se !ltered.

N)V ):, :2, ,;2), U2)</ :, F

!t!b!se !ltered.

N)V %rdbms!dminc!tcl?st.s"l

%tep &0' Create a %1I and copy those files to re"aining nodes.

N)V cre!te spfileSXT:,Q2spfile,Q2.or!X from pfileF

1ile cre!ted.

N)V sh?tdoJn immedi!teF!t!b!se closed.!t!b!se dismo?nted./), inst!nce sh?t doJn.N)V host echo H1<),SXT:,Q2spfile,Q2.or!XH VK/),I,dbsinit,Q2#.or!

N)V st!rt?p/), inst!nce st!rted.

:ot!l ystem =lob!l re! 640949# bytes

1i@ed iDe #30#784 bytesQ!ri!ble iDe #7#96708 bytes!t!b!se 2?ffers 46#373440 bytesedo 2?ffers 565480 bytes!t!b!se mo?nted.!t!b!se opened.N)V select v!l?e from vKp!r!meter Jhere n!meSXspfileXF

Q)U,--------------------------------------------------------------------------------T:devdbspfiledevdb.or!



N)V host scp K/),I,dbsinit,Q2#.or! *r!c+K/),I,dbsinit,Q2.or!

N)V host scp K/),I,dbsor!pJ,Q2# *r!c+K/),I,dbsor!pJ,Q2

%tep &8' ogin as oracle user on node+(krac+) and e!ecute belowstate"ents.

$or!cle%*r!c &'K e@port /),I<S,Q2$or!cle%*r!c &'K e@port /),I,S?0!ppor!cleprod?ct##.#.0dbI#

$or!cle%*r!c &'K m*dir -p K/),I2,!dminK/),I<E!d?mpPdpd?mpPhd?mpG$or!cle%*r!c &'K s"lpl?s H !s sysdb!H

N)Wl?s+ ele!se ##.#.0.6.0 - rod?ction on :?e ct #6 0+5#+#9 0#


/onnected to !n idle inst!nce.

N)V st!rt?p

/), inst!nce st!rted.

:ot!l ystem =lob!l re! 640949# bytes1i@ed iDe #30#784 bytes

Q!ri!ble iDe #6777904 bytes

!t!b!se 2?ffers 465567744 bytesedo 2?ffers 565480 bytes

!t!b!se mo?nted.!t!b!se opened.

N)V col hostIn!me for !5

N)V col inst!nceIn!me for !0N)V select inst!nceIn!mePhostIn!me from gvKinst!nceF

<;:;/,I;, :I;,

-------------------- -------------------------

,Q2 *r!c.dbprod.com,Q2# *r!c#.dbprod.com

N)V sh?tdoJn immedi!te!t!b!se closed.

!t!b!se dismo?nted.

*ote ' $ake sure that all the instance in down before continue below steps. If not bring it allthe instance down.

$or!cle%*r!c# &'K e@port /),I,S?0!ppor!cleprod?ct##.#.0dbI#

$or!cle%*r!c# &'K srvctl !dd d!t!b!se -d ,Q2 -o K/),I, -m 2./$or!cle%*r!c# &'K srvctl !dd inst!nce -d ,Q2 -i ,Q2# -n *r!c#

$or!cle%*r!c# &'K srvctl !dd inst!nce -d ,Q2 -i ,Q2 -n *r!c$or!cle%*r!c# &'K crsIst!t -t -v

;!me :ype 11: :!rget t!te ost----------------------------------------------------------------------or!....2#.inst !pplic!tion 05 00 11)<;, 11)<;,

or!....2.inst !pplic!tion 05 00 11)<;, 11)<;,or!.,Q2.db !pplic!tion 00 0# 11)<;, 11)<;,

or!....)#.inst !pplic!tion 05 00 ;)<;, ;)<;, *r!c#

or!....).inst !pplic!tion 05 00 ;)<;, ;)<;, *r!cor!./).db !pplic!tion 00 0# ;)<;, ;)<;, *r!c#

or!....#.!sm !pplic!tion 05 00 ;)<;, ;)<;, *r!c#or!..../#.lsnr !pplic!tion 05 00 ;)<;, ;)<;, *r!c#



or!.*r!c#.gsd !pplic!tion 05 00 ;)<;, ;)<;, *r!c#or!.*r!c#.ons !pplic!tion 03 00 ;)<;, ;)<;, *r!c#

or!.*r!c#.vip !pplic!tion 00 00 ;)<;, ;)<;, *r!c#

or!.....!sm !pplic!tion 05 00 ;)<;, ;)<;, *r!cor!..../.lsnr !pplic!tion 05 00 ;)<;, ;)<;, *r!c

or!.*r!c.gsd !pplic!tion 05 00 ;)<;, ;)<;, *r!cor!.*r!c.ons !pplic!tion 03 00 ;)<;, ;)<;, *r!c

or!.*r!c.vip !pplic!tion 00 00 ;)<;, ;)<;, *r!c$or!cle%*r!c# &'K srvctl st!rt d!t!b!se -d ,Q2$or!cle%*r!c# &'K crsIst!t -t -v

;!me :ype 11: :!rget t!te ost----------------------------------------------------------------------

or!....2#.inst !pplic!tion 05 00 ;)<;, ;)<;, *r!c#or!....2.inst !pplic!tion 05 00 ;)<;, ;)<;, *r!c

or!.,Q2.db !pplic!tion 00 0# ;)<;, ;)<;, *r!c

or!....)#.inst !pplic!tion 05 00 ;)<;, ;)<;, *r!c#or!....).inst !pplic!tion 05 00 ;)<;, ;)<;, *r!c

or!./).db !pplic!tion 00 0# ;)<;, ;)<;, *r!c#or!....#.!sm !pplic!tion 05 00 ;)<;, ;)<;, *r!c#

or!..../#.lsnr !pplic!tion 05 00 ;)<;, ;)<;, *r!c#

or!.*r!c#.gsd !pplic!tion 05 00 ;)<;, ;)<;, *r!c#

or!.*r!c#.ons !pplic!tion 03 00 ;)<;, ;)<;, *r!c#or!.*r!c#.vip !pplic!tion 00 00 ;)<;, ;)<;, *r!c#or!.....!sm !pplic!tion 05 00 ;)<;, ;)<;, *r!c

or!..../.lsnr !pplic!tion 05 00 ;)<;, ;)<;, *r!c

or!.*r!c.gsd !pplic!tion 05 00 ;)<;, ;)<;, *r!cor!.*r!c.ons !pplic!tion 03 00 ;)<;, ;)<;, *r!c

or!.*r!c.vip !pplic!tion 00 00 ;)<;, ;)<;, *r!c$or!cle%*r!c# &'K s"lpl?s systemor!cle%devdb

N)Wl?s+ ele!se ##.#.0.6.0 - rod?ction on :?e ct #6 +5+#9 0#


/onnected to+r!cle !t!b!se ##g ,nterprise ,dition ele!se ##.#.0.6.0 - rod?ction

ith the !rtitioningP e!l pplic!tion /l?stersP )P !t! ining!nd e!l pplic!tion :esting options

N)V col hostIn!me for !5

N)V col inst!nceIn!me for !0

N)V select inst!nceIn!mePhostIn!me from gvKinst!nceF

<;:;/,I;, :I;,-------------------- -------------------------

,Q2 *r!c.dbprod.com,Q2# *r!c#.dbprod.com

$or!cle%*r!c# &'K srvctl st!t?s d!t!b!se -d devdb

<nst!nce ,Q2# is r?nning on node *r!c#<nst!nce ,Q2 is r?nning on node *r!c

$or!cle%*r!c# &'K srvctl st!t?s !sm -n *r!c#

inst!nce T# is r?nning on node *r!c#.$or!cle%*r!c# &'K srvctl st!t?s !sm -n *r!c

inst!nce T is r?nning on node *r!c.$or!cle%*r!c# &'K srvctl st!t?s inst!nce -d devdb -i devdb#

<nst!nce devdb# is r?nning on node *r!c#

$or!cle%*r!c# &'K srvctl st!t?s inst!nce -d devdb -i devdb



<nst!nce devdb is r?nning on node *r!c$or!cle%*r!c# &'K srvctl config d!t!b!se -d devdb

*r!c# ,Q2# ?0!ppor!cleprod?ct##.#.0dbI#

*r!c ,Q2 ?0!ppor!cleprod?ct##.#.0dbI#$or!cle%*r!c# &'K

S INGL C LIN! A CCSS N AM (SCAN)

%ingle Client Access *a"e (%CA*) is a new 5racle Real Application Clusters (RAC) &&g Release + feature

that pro#ides a single na"e for clients to access 5racle Databases running in a cluster. he bene"it is that the

client@s connect infor"ation does not need to change if you add or re"o#e nodes in the cluster. /a#ing a single

na"e to access the cluster allows clients to use the Connect client and the si"ple BD3C thin >R to access any

database running in the cluster, independently of which ser#er(s) in the cluster the database is acti#e. %CA*

pro#ides load balancing and failo#er for client connections to the database. he %CA* works as a cluster alias for

databases in the cluster.

SCAN Concepts• %ingle client access na"e (%CA*) is the #irtual hostna"e to pro#ide forall clients connecting to the cluster (as opposed to the #ip hostna"es in &?gand &&gR&).

• %CA* is a do"ain na"e registered to at least one and up to three I1addresses, either in the do"ain na"e ser#ice (D*%) or the rid *a"ing%er#ice (*%).

• 3y default, the na"e used as the %CA* is also the na"e of the clusterand "ust be globally uniue throughout your enterprise. he default #aluefor the %CA* is based on the local node na"e. %CA* na"e "ust be at leastone character long and no "ore than &9 characters in length, "ust bealphanu"eric - cannot begin with a nu"eral and "ay contain hyphens (-). Ifyou reuire a %CA* that is longer than &9 characters, then select anAd#anced installation.

• or installation to succeed, the %CA* "ust resol#e to at least oneaddress.

• %CA* I1 addresses "ust be on the sa"e subnet as #irtual I1addresses and public I1 addresses.

• 5racle strongly reco""ends that you do not configure %CA* I1addresses in the hosts file. 3ut if you use the hosts file to resol#e %CA*na"e, you can ha#e only one %CA* I1 address.

• If hosts file is used to resol#e %CA* hostna"e, you will recei#e Clustererification >tility failure at end of installation (see *ote' <<;8;&.& for "oredetails)

• or high a#ailability and scalability, 5racle reco""ends that youconfigure the %CA* to use D*% Round Robin resolution to three addresses.

• 3ecause the %CA* is associated with the cluster as a whole, ratherthan to a particular node, the %CA* "akes it possible to add or re"o#enodes fro" the cluster without needing to reconfigure clients. It also addslocation independence for the databases, so that client configuration doesnot ha#e to depend on which nodes are running a particular database.

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=887471.1




• Clients can continue to access the cluster in the sa"e way as withpre#ious releases, but 5racle reco""ends that clients accessing the clusteruse the %CA*. Clients using the %CA* can also access the cluster usingC5**C.

• rid Infrastructure will start local listener I%*R on all nodes to

listen on local I1, and %CA* listener I%*R6%CA*& (up to three clusterwide) to listen on %CA* I1(s)E &&gR+ database by default will setlocal6listener to local I%*R, and re"ote6listener to %CA* listener.

• %CA* listener will be running off RID6/5$, and by default, in &&gR+local listener will be running off RID6/5$ as well.

,Rconnet s5%%4s s*stem/mana7errac)scan:121/-R.N&A.-3 Z2/ connect ;d+c:!rac%e:tin:rac)scan:121/-R.N&A.-3

N!#$R% R&'IRMN!S $R 'SING SCAN

he %CA* is configured during the installation of 5racle ridInfrastructure that is distributed with 5racle Database &&g Release+. 5raclerid Infrastructure is a single 5racle /o"e that contains 5racle Clusterwareand 5racle Auto"atic %torage $anage"ent. Fou "ust install 5racle ridInfrastructure first in order to use 5racle RAC &&g Release +. During theinter#iew phase of the 5racle rid Infrastructure installation, you will bepro"pted to pro#ide a %CA* na"e. here are + options for defining the%CA*'

&. Define the %CA* in your corporate D*% (Do"ain *a"e %er#ice)+. >se the rid *a"ing %er#ice (*%)

De"ine the SCAN in your corporate DNS (Doain Nae Ser*ice)

If you choose 5ption &, you "ust ask your network ad"inistrator tocreate a single na"e that resol#es to 0 I1 addresses using a round-robinalgorith". hree I1 addresses are reco""ended considering load balancingand high a#ailability reuire"ents regardless of the nu"ber of ser#ers in thecluster. he I1 addresses "ust be on the sa"e subnet as your public networkin the cluster. he na"e "ust be &9 characters or less in length, notincluding the do"ain, and "ust be resol#able without the do"ain suffi! (fore!a"ple' Gkrac-scan@ "ust be resol#able as opposed to Gkrac-scan.india.co"H). he I1s "ust not be assigned to a network interface (on

the cluster), since 5racle Clusterware will take care of it.*r!cnode-sc!n #9.#68.#.7 #9.#68.#.70 #9.#68.#.7#

Fou can check the %CA* configuration in D*% using GnslookupH. If your D*%is set up to pro#ide round-robin access to the I1s resol#ed by the %CA* entry,then run the GnslookupH co""and at least twice to see the round-robin



algorith" work. he result should be that each ti"e, the GnslookupH wouldreturn a set of 0 I1s in a different order.

irst nsloo+up

$root%*r!cnode &'( nsloo*?p *r!cnode-sc!n

erver+ #9.#68.#.#00ddress+ #9.#68.#.#00(53

;!me+ *r!cnode-sc!n.indi!.comddress+ #9.#68.#.7;!me+ *r!cnode-sc!n.indi!.comddress+ #9.#68.#.70;!me+ *r!cnode-sc!n.indi!.comddress+ #9.#68.#.7#

Second nsloo+up

$root%*r!cnode &'( nsloo*?p *r!cnode-sc!nerver+ #9.#68.#.#00

ddress+ #9.#68.#.#00(53

;!me+ *r!cnode-sc!n.indi!.comddress+ #9.#68.#.70;!me+ *r!cnode-sc!n.indi!.comddress+ #9.#68.#.7#;!me+ *r!cnode-sc!n.indi!.comddress+ #9.#68.#.7

Note, If your D*% ser#er does not return a set of 0 I1s as shown in figure 0or does not round-robin, ask your network ad"inistrator to enable such asetup. D*% using a round-robin algorith" on its own does not ensure failo#erof connections. /owe#er, the 5racle Client typically handles this. It is

therefore recoended that the "ini"u" #ersion of the client used is the5racle Database &&g Release + client. Refer about D*%configuration Click/ere.

!- GRID NAMING SR.IC (GNS)

If you choose option +, you only need to enter the %CA* during the inter#iew.During the cluster configuration, three I1 addresses will be acuired fro" aD/C1 ser#ice (using *% assu"es you ha#e a D/C1 ser#ice a#ailable onyour public network) to create the %CA* and na"e resolution for the %CA*will be pro#ided by the *%.

I /$' D$ N$! -A. A DNS SR.R A.AILA0L A!INS!ALLA!I$N !IM 5racle >ni#ersal Installer (5>I) enforces pro#iding a %CA* resolutionduring the 5racle rid Infrastructure installation, since the %CA* concept isan essential part during the creation of 5racle RAC &&g Release + databasesin the cluster. All 5racle Database &&g Release + tools used to create a

http://dnccfg.blogspot.in/2012/08/dns-configuration-on-linux.html.html





database (e.g. the Database Configuration Assistant (D3CA), or the *etworkConfiguration Assistant (*etCA)) would assu"e its presence. /ence, 5>I willnot let you continue with the installation until you ha#e pro#ided a suitable%CA* resolution. /owe#er, in order to o#erco"e the installation reuire"ent without

setting up a D*%-based %CA* resolution, you can use a hosts-file basedworkaround. In this case, you would use a typical hosts-file entry to resol#ethe %CA* to only & I1 address and one I1 address only. It is not possible tosi"ulate the round-robin resolution that the D*% ser#er does using a localhost file. he host file look-up the 5% perfor"s will only return the first I1address that "atches the na"e. *either will you be able to do so in oneentry (one line in the hosts-file). hus, you will create only & %CA* for thecluster. (*ote that you will ha#e to change the hosts-file on all nodes in thecluster for this purpose.) his workaround "ight also be used when perfor"ing an upgradefro" for"er (pre-5racle Database &&g Release +) releases. /owe#er, it is

strongly reco""ended to enable the %CA* configuration as described underG5ption &H or G5ption +H abo#e shortly after the upgrade or the initialinstallation. In order to "ake the cluster aware of the "odified %CA*configuration, delete the entry in the hosts-file and then issue' srvctl modifyscan -n <scan_name> as the root user on one node in the cluster. hescan6na"e pro#ided can be the e!isting fully ualified na"e (or a newna"e), but should be resol#ed through D*%, ha#ing 0 I1s associated with it,as discussed. he re"aining reconfiguration is then perfor"ed auto"atically.

SCAN C$NIG'RA!I$N IN !- CL'S!R

During cluster configuration, se#eral resources are created in the cluster for %CA*. or each of the 0 I1

addresses that the %CA* resol#es to, a %CA* I1 resource is created and a %CA* istener is created. he %CA*

istener is dependent on the %CA* I1 and the 0 %CA* I1s (along with their associated listeners) will be dispersed

across the cluster. his "eans, each pair of resources (%CA* I1 J istener) will be started on a different ser#er in

the cluster, assu"ing the cluster consists of three or "ore nodes. In case, a +-node-cluster is used (for which 0 I1s

are still reco""ended for si"plification reasons), one ser#er in the cluster will host two sets of %CA* resources

under nor"al operations. If the node where a %CA* I1 is running fails, the %CA* I1 and its associated listener will

failo#er to another node in the cluster. If by "eans of such a failure the nu"ber of a#ailable ser#ers in the cluster

beco"es less than three, one ser#er would again host two sets of %CA* resources. If a node beco"es a#ailable in

the cluster again, the for"erly "entioned dispersion will take effect and relocate one set accordingly.

$or!cle%*r!cnode# &'K srvctl config sc!nIlistener/; )istener )<:,;,I/;# e@ists. ort+ :/+#5#/; )istener )<:,;,I/; e@ists. ort+ :/+#5#/; )istener )<:,;,I/;3 e@ists. ort+ :/+#5#

$or!cle%*r!cnode# &'K srvctl config sc!n/; n!me+ *r!cnode-sc!n.indi!.comP ;etJor*+ ##9.#68.#.055.55.55.0eth0/; Q< n!me+ sc!n#P <+ #9.#68.#.70#9.#68.#.70/; Q< n!me+ sc!nP <+ #9.#68.#.7##9.#68.#.7#/; Q< n!me+ sc!n3P <+ #9.#68.#.7#9.#68.#.7$or!cle%*r!cnode# &'K

DA!A0AS C$NIG'RA!I$N 'SING SCAN



or 5racle Database &&g Release +, %CA* is an essential part of theconfiguration and therefore the R$56I%*R para"eter is set to the%CA* per default, assu"ing that the database is created using standard5racle tools (e.g. the for"erly "entioned D3CA). his allows the instances toregister with the %CA* isteners as re"ote listeners to pro#ide infor"ation

on what ser#ices are being pro#ided by the instance, the current load, and areco""endation on how "any inco"ing connections should be directed tothe instance. In this conte!t, the 5CA6I%*R para"eter "ust be considered. he 5CA6I%*R para"eter should be set to the node-I1. If you needfully ualified do"ain na"es, ensure that 5CA6I%*R is set to the fullyualified do"ain na"e (e.g. node-I1.e!a"ple.co"). 3y default, a nodelistener is created on each node in the cluster during cluster configuration.Kith 5racle rid Infrastructure &&g Release + the node listener run out of the5racle rid Infrastructure ho"e and listen on the node-I1 using thespecified port (default port is &9+&).

>nlike in for"er database #ersions, it is not reco""ended to set yourR$56I%*R para"eter to a ser#er side *%*A$% alias that resol#esthe host to the %CA* (/5%Lkracnode-scan for e!a"ple) in the address listentry, but use the si"plified G%CA*'portH

N)V shoJ p!r!meter listener

;, :O, Q)U,

------------------------------------ ----------- ------------------------------listenerInetJor*s string

loc!lIlistener string A,/<:<;SA,I)<:SA ,SA:/)S:/CA:S*r!c

node#-vipCA:S#5#CCCC

remoteIlistener string *r!cnode-sc!n.indi!.com+#5#

Note' if you are using the easy connect na"ing "ethod, you "ay need to "odify your %M*.5RA to ensure thatC5**C is in the list when specifying the order of the na"ing "ethods used for the client na"e resolutionlookups (the 5racle &&g Release + default is *A$%.DIRC5RF61A/L(tnsna"es, ldap, e2connect)).

-$# C$NNC!I$N L$AD 0ALANCING #$R%S 'SING SCAN

or clients connecting using 5racle %MN*et &&g Release +, three I1addresses will be recei#ed by the client by resol#ing the %CA* na"e throughD*% as discussed. he client will then go through the list it recei#es fro" theD*% and try connecting through one of the I1s recei#ed. If the client recei#esan error, it will try the other addresses before returning an error to the user

or application. his is si"ilar to how client connection failo#er works inpre#ious releases when an address list is pro#ided in the client connectionstring.

Khen a %CA* istener recei#es a connection reuest, the %CA* istener willcheck for the least loaded instance pro#iding the reuested ser#ice. It willthen re-direct the connection reuest to the local listener on the node wherethe least loaded instance is running. %ubseuently, the client will be gi#en



the address of the local listener. he local listener will finally create theconnection to the database instance.

Note, his e!a"ple assu"es an 5racle &&g Release + client using a default

*%*A$%. ora'

/) S A,/<:<; S A, S A:/) S :/CA: S *r!cnode-sc!n.indi!.comCA: S #5#CC A/;;,/:I: S A,Q, S ,</:,C A,Q</,I;, S /).<;<./C C C

.RSI$N AND 0AC%#ARD C$M1A!I0ILI!/

he successful use of %CA* to connect to an 5racle RAC database in thecluster depends on the ability of the client to understand and use the %CA*as well as on the correct configuration of the R$56I%*R para"etersetting in the database. If the #ersion of the 5racle Client connecting to thedatabase as well as the 5racle Database #ersion used are both 5racleDatabase &&g Release + and the default configuration is used as described inthis paper, no changes to the syste" are typically reuired.

he sa"e holds true, if the 5racle Client #ersion and the #ersion of the5racle Database that this client is connecting to are both pre-&&g Release +

#ersion (e.g. 5racle Database &&g Release & or 5racle Database &?g Release+, or older). In this case, the pre-&&g Release + client would use a *%connect descriptor that resol#es to the node-I1s of the cluster, while the5racle pre-&&g Release + database would still use a R$56I%*R entrypointing to the node-I1s. he disad#antage of this configuration is that%CA* would not be used and hence the clients are still e!posed to changese#ery ti"e the cluster changes in the backend. %i"ilarly, if an 5racleDatabase &&g Release + is used, but the clients re"ain on a for"er #ersion. he solution is to change the 5racle client and 7 or 5racle DatabaseR$56I%*R settings accordingly. he following cases need to beconsidered'



Saple !NSNAMS2ora "or $racle Database pre3 44g Release 5Clients

/).<;<./SA,/<:<;SA,I)<:S A)I2);/,SonCA1<)Q,S;CA,SA:/)StcpCA:S#9.#68.#.70CA:S#5#CCA,SA:/)StcpCA:S#9.#68.#.7#CA:S#5#CCCA/;;,/:I:SA,Q</,I;,S /).<;<./CCC

Common Questions Regarding SCAN

The following is a list of commonly asked questions regarding SCAN:

How can we configure the SCAN and SCAN listener?

During Typical installation, you are prompted to confirm the default Single Client Access Name

(SCAN, which is used to connect to data!ases within the cluster irrespecti"e of which nodes

they are running on# $f you change the SCAN from the default, then the name that you use must !e glo!ally unique throughout your enterprise#

$racle Client.ersion

$racle Database.ersion

Coent

5racle Database &&gRelease +


*o change reuired.


1re3 5racle Database &&gRelease +

Add the %CA* I1s as hoststo the

R$56I%*Rpara"eter.

1re3 5racle Database&&g Release +


Change the client *%*A$%.ora to includethe %CA* I1s (N seebelow).I the database wasupgraded using the D3>Afro" a pre-&&g Rel. +database, the D3>A willconfigure theR$56I%*Rpara"eter to point to thenode-I1s as well as the

%CA*.1re3 5racle Database&&g Release +

1re3 5racle Database &&gRelease +

If you want to "ake use of%CA*(reco""ended)' add the%CA* I1s as hosts to theR$56I%*Rpara"eter.A*D Change the client

*%*A$%.ora toinclude the %CA* I1s (N seebelow). 5therwise, nochange reuired.



$f the SCAN name resol"es to one $% address, root script (root#sh or rootupgrade#sh will create

the num!er of SCAN &$% resources(ora#scan'#"ip and corresponding SCAN listenerresource(ora#$ST)N)*+SCAN'#lsnr depend on how many $% address the SCAN name

resol"es to, i#e#if the SCAN name resol"es to two $% addresses, it will create two SCAN &$%

resources and two corresponding SCAN listener resource#

SCAN &$% and the corresponding SCAN listener works like a pair, when SCAN &$% fails o"er

to other node, the corresponding SCAN listener will also !e failed o"er to the same node#

hen SCAN &$% fails o"er happens, it will always select a node with least running SCAN &$%,i#e#, if SCAN &$% runs on node', node- and node. of a /0node cluster, if node. goes down, the

SCAN &$% and corresponding SCAN listener will !e failed o"er to node/ as the other two nodes

already ha"e one SCAN &$% running on each node#

Also we can use 1sr"ctl1 to add2modify the scan resource and the listeners# %lease refer to 3*eal

Application Clusters Admin and Deployment 4uide3 or Note '56.'/7#' for more information#

Do we still need to configure local listeners on each node?8es, you would need to configure independent local listeners for each node# SCAN listeners are

not replacements for the node listeners#

A new set of cluster processes called scan listeners will run on three nodes in a cluster (or all

nodes if there are less than .# $f you ha"e more than three nodes, regardless of the num!er of

nodes you ha"e, there will !e at most three scan listeners# The data!ase registers with the SCANlistener through the remote listener parameter in the init#ora2spfile# $f any of these clustered

processes fail, they are automatically restarted on a new node#

How does SCAN work ?

3hen a client su!mits a request, the SCAN listener listening on a SCAN $% address and theSCAN port is contracted on a client1s !ehalf# 9ecause all ser"ices on the cluster are registered

with the SCAN listener, the SCAN listener replies with the address of the local listener on the

least0loaded node ()ach scan listener keeps updated cluster load statistics where the ser"ice iscurrently !eing offered# inally, the client esta!lishes connection to the ser"ice through the

listener on the node where ser"ice is offered#All of these actions take place transparently to the

client without any e;plicit configuration required in the client#3

$or!cle%*r!cnode#'K srvctl ::U /;I)<:,;,/; )istener )<:,;,I/;# is en!bled/; listener )<:,;,I/;# is r?nning on node *r!cnode#

/; )istener )<:,;,I/; is en!bled/; listener )<:,;,I/; is r?nning on node *r!cnode/; )istener )<:,;,I/;3 is en!bled/; listener )<:,;,I/;3 is r?nning on node *r!cnode3$or!cle%*r!cnode#'K

Instead of DNS or GNS, Can we use !etc!hosts to resol"e SCAN?





<racle strongly recommends that you do not configure SCAN &$% addresses in the hosts file#

9ut if you use the hosts file to resol"e SCAN name, you can ha"e only one SCAN $% address#

failure at end of installation (See N<T) ==7/7'#' for more details

Can we use the #re"ious method $%sing &I'( for client connection?

Clients can continue to access the cluster in the same way as with pre"ious releases# &ips are stillused internally, and can still !e used for connections# 9ut <racle strongly recommends thatclients accessing the cluster use the SCAN# Clients using the SCAN can also access the cluster

using )>C<NN)CT#

Is it mandator) to use SCAN?

$t1s highly recommended to use SCAN unless there1s strong !usiness reason pre"enting it from

!eing used#

Is it su##orted to remo"e SCAN?

SCAN is an elementary part of ''g*- 4rid $nfrastructure, it1s not supported to remo"e SCAN#

Is it recommended to use C*S+ feature?

As a 9est %ractice, <racle recommends using the C<ST feature to restrict instance registration

with SCAN listeners as part of your standard listener configuration# *efer to note './5=.'#'formore details#

Sample TNS entry for SCAN

/) SA,/<:<;S

A,SA:/)StcpCA:S*r!cnode-sc!n.indi!./CA:S#5#CC

A/;;,/:I:SA,Q</,I;,S/).<;<./CCC

%a"ple *% ntry without %CA*

/) SA,/<:<;SA,I)<:SA,SA:/)StcpCA:S*r!cnode#-vip.indi!.comCA:S#5#CCA,SA:/)StcpCA:S*r!cnode-vip.indi!.comCA:S#5#CCCA/;;,/:I:SA,Q</,I;,S/).<;<./CCC






scan setup

Documents