Você está na página 1de 14

################################################################################ ################# # Objetivo: Procedimento de adio de node em um ambiente Oracle RAC 10gR2 em Linux x86 # # Autor: Eder dos

Santos Ferreira # # Data: 14/07/2011 # # Revisao 1 # # Revisado por: # # Data da Reviso: # # Alterao: # ################################################################################ ################# Indice 1. Instalar o Sistema Operacional no novo servidor (rac2) que ser adicion ado. Verifique os pacotes e altere os parmetros de kernel de acordo com as recomendaes da Oracle para o Linux utilizado. 2. Certificar que os discos do OCR, Votingdisk, spfile e ASM sejam entre gues ao novo servidor. 3. Criar o usurio oracle no novo servidor. 4. Configurar a equivalncia do usurio oracle. 5. Criar os diretrios pertinentes ao cluster oracle. 6. Instalar e configurar o ASMLib 2.0 no novo node (rac2). 7. Configurar o Oracle Cluster no novo node. 8. Configurar o Software Oracle Database no novo node (rac2). 9. Configurar o Oracle Database no novo node (rac2).

1. Instalar o Sistema Operacional no novo servidor (rac2) que ser adicion ado. Verifique os pacotes e altere os parmetros de kernel de acordo com as recomendaes da Oracle para o Linux utilizado. Configurar o date ti me do novo servidor de acordo com os demais nodes. 2. Certificar que os discos do OCR, Votingdisk, spfile e ASM sejam entre gues ao novo servidor. 3. Criar o usurio oracle no novo servidor: 3.1 Pegar os ids do usurio oracle e dos grupos no node j existente : # hostname rac1.localdomain <------------------------ Observe que o node j existente # id oracle uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) 3.2 Criar o usurio oracle no novo node: # hostname rac2.localdomain <------------------------ Observe que n o novo node # groupadd -g 500 oinstall # groupadd -g 501 dba # useradd -m -u 500 -g oinstall -G dba -d /home/oracle -

s /bin/bash -c "Oracle Software Owner" oracle uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) # passwd oracle Changing password for user oracle. New UNIX password: <---------------------- Especifiqu e uma senha para o usurio oracle BAD PASSWORD: it is based on a dictionary word Retype new UNIX password: <----------------- Especifiqu e novamente a senha para o usurio oracle passwd: all authentication tokens updated successfully. 3.3 Copiar o arquivo de variis de ambiente do usurio oracle, do no de existente para o novo node: $ hostname rac1.localdomain <------------------------ Observe que o node j existente $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <--- Observe que com o usurio oracle $ scp ~/.bash_profile rac2:/home/oracle Password: xxxxx <----------------------- Especifica r a senha do usurio oracle $ ssh rac2 Password: xxxxx <----------------------- Especifica r a senha do usurio oracle $ hostname rac2.localdomain <----------------------- Observe qu e no novo node $ vi ~/.bash_profile <----------------------- Altere a v arivel ORACLE_SID para o correspondente do novo node 4. Configurar a equivalncia do usurio oracle: 4.1 Criar a chave dsa no novo servidor: $ hostname rac2.localdomain <------------------------ Observe que n o novo node $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <--- Observe que com o usurio oracle $ mkdir -p ~/.ssh $ chmod 700 ~/.ssh $ /usr/bin/ssh-keygen -t dsa Generating public/private dsa key pair. Enter file in which to save the key (/home/oracle/.ssh/i d_dsa): <---------Enter passphrase (empty for no passphrase): <------------------------------ -- Observe que nestes pontos, a senha foi deixada em branc o Enter same passphrase again: <-------------------------------------------Your identification has been saved in /home/oracle/.ssh/ id_dsa. Your public key has been saved in /home/oracle/.ssh/id_d sa.pub. The key fingerprint is: 69:d2:c0:da:46:c1:9b:82:c0:85:24:92:58:5b:37:b3 oracle@r ac2.localdomain 4.2 Copiar a chave criada no novo servidor para o node j existent

e: $ hostname rac1.localdomain <------------------------ Observe que o node j existente $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <----------------- Observe que com o usurio oracle $ ssh rac2 cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_ke ys The authenticity of host 'linux3 (192.168.0.222)' can't be established. DSA key fingerprint is f5:38:37:e8:84:4e:bd:6d:6b:25:f7: 94:58:e8:b2:7a. Are you sure you want to continue connecting (yes/no)? y es <-------------------- Confirme com 'yes' Warning: Permanently added 'rac2,192.168.0.222' (DSA) to the list of known hosts. oracle@rac2's password: xxxxx <----------------------------------------------- Digite aqui a senha do udurio oracle 4.3 Copiar o arquivo authorized keys completo no node1 para todo s os nodes do cluster, neste caso, apenas node2 (novo servidor): $ hostname rac1.localdomain <------------------------ Observe que o node j existente $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <----------------- Observe que com o usurio oracle $ scp ~/.ssh/authorized_keys rac2:.ssh/authorized_keys Enter passphrase for key '/home/oracle/.ssh/id_dsa': xxx xx <--------------------- Digite aqui a senha do udurio oracle authorized_keys 100 % 669 0.7KB/s 00:00 4.4 Alterar a permisso do arquivo authorized_keys no novo servido r: $ hostname rac2.localdomain <------------------------ Observe que n o novo node $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <----------------- Observe que com o usurio oracle $ chmod 600 ~/.ssh/authorized_keys $ exec /usr/bin/ssh-agent $SHELL $ /usr/bin/ssh-add Identity added: /home/oracle/.ssh/id_dsa (/home/oracle/. ssh/id_dsa) 4.5 Habilitar a equivalencia no node j existente e que ir executar o script addNode.sh: $ hostname rac1.localdomain <------------------------ Observe que o node j existente $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <------------ Observe que com o usurio oracle $ exec /usr/bin/ssh-agent $SHELL $ /usr/bin/ssh-add Identity added: /home/oracle/.ssh/id_dsa (/home/oracle/. ssh/id_dsa)

4.6 Testar a conectivade confivel para todos os nodes: 4.6.1 Node1 $ hostname rac1.localdomain <------------------------ Obser ve que o node j existente $ id uid=500(oracle) gid=500(oinstall) groups=500(oin stall),501(dba) <------------ Observe que com o usurio oracle $ ssh rac2 date <------------------------ No dev e pedir senha 4.6.2 Node2 $ hostname rac2.localdomain <------------------------ Obser ve que no novo node $ id uid=500(oracle) gid=500(oinstall) groups=500(oin stall),501(dba) <------------ Observe que com o usurio oracle $ ssh rac1 date <------------------------ No dev e pedir senha 5. Criar os diretrios pertinentes ao cluster oracle: 5.1 Pegar os diretrios no servidor j existente: $ hostname rac1.localdomain <------------------------ Observe que o node j existente $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <--- Observe que com o usurio oracle $ echo $ORACLE_HOME /oracle/products/db <---------------- Pega o diretrio d o Software de Banco de Dados $ echo $CRS_HOME /oracle/products/crs <---------------- Pega o diretrio d o Software de Cluster 5.2 Criar os diretrios no novo servidor: # hostname rac2.localdomain <------------------------ Observe que n o novo node # id uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon), 3(sys),4(adm),6(disk),10(wheel) <--- Observe que com o usurio root # mkdir -p /oracle/products/db <---------------- Cria o diretrio do Software de Banco de Dados # mkdir -p /oracle/products/crs <---------------- Cria o diretrio do Software de Cluster # chown -R oracle:oinstall /oracle/products/db # chown -R oracle:oinstall /oracle/products/crs 6. Instalar e configurar o ASMLib 2.0 no novo node (rac2): 6.1 Instalar e configurar o ASMLib: # hostname rac2.localdomain <------------------------ Observe que n o novo node # id uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon), 3(sys),4(adm),6(disk),10(wheel) <---- Observe que o usurio root # rpm -Uvh oracleasm-2.6.18-53.el5-2.0.4-1.el5.i686.rpm

oracleasm-support-2.1.7-1.el5.i386.rpm oracleasmlib-2.0.4-1.el5.i386.rpm Preparing... ############## ############################# [100%] 1:oracleasm-support ############## ############################# [ 33%] 2:oracleasm-2.6.18-53.el5-2.0.4-1.EL5 ############## ############################# [ 67%] 3:oracleasmlib ############## ############################# [100%] # /etc/init.d/oracleasm configure Configuring the Oracle ASM library driver. This will configure the on-boot properties of the Oracle ASM library driver. The following questions will determine whether the driver is loaded on boot and what permissions it will have. The c urrent values will be shown in brackets ('[]'). Hitting <ENTER> witho ut typing an answer will keep that current value. Ctrl-C will abort. Default user to own the driver interface []: oracle <-------------- Especifique o usurio oracle Default group to own the driver interface []: oinstall <-------------- Especifique o grupo oinstall Start Oracle ASM library driver on boot (y/n) [n]: y <-------------- --- Entre com 'y' Fix permissions of Oracle ASM disks on boot (y/n) [y]: y <-------------Writing Oracle ASM library driver configuration: [ OK ] Creating /dev/oracleasm mount point: Loading module "oracleasm": [ OK ] Mounting ASMlib driver filesystem: [ Scanning system for ASM disks: [ OK # /etc/init.d/oracleasm scandisks Scanning system for ASM disks [ OK # /etc/init.d/oracleasm listdisks DADOS INDICES [ OK ] OK ] ] ]

7. Configurar o Oracle Cluster no novo node: 7.1 Verificar o acesso remoto e a equivaLencia de usurio: $ hostname rac1.localdomain <------------------------ Observe que o node j existente $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <--- Observe que com o usurio oracle $ ssh rac1 date <------------------------ No deve pedir senha $ ssh rac2 date <------------------------ No deve pedir senha 7.2 Verificar se o X est disponvel ou se a varivel DISPLAY est setad a pois uma interface grfica ser exibida. 7.3 Adicionar o novo node: $ hostname rac1.localdomain <------------------------ Observe que o

node j existente $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <--- Observe que com o usurio oracle $ cd $CRS_HOME/oui/bin $ ./addNode.sh @ Next @ Public Node Name - rac2 @ Private Node Name - rac2-priv @ Virutal host name - rac2-vip @ Next @ Install - A partir do Node2 # hostname rac2.localdomain <----------------------- Observe que no novo node # id uid=0(root) gid=0(root) groups=0(root),1 (bin),2(daemon),3(sys),4(adm),6(disk),10(wheel) <---- Observe que o usurio root # /oracle/oraInventory/orainstRoot.sh Changing permissions of /oracle/oraInven tory to 770. Changing groupname of /oracle/oraInvento ry to oinstall. The execution of the script is complete - A partir do Node1 # hostname rac1.localdomain <----------------------- Observe que node j existente # id uid=0(root) gid=0(root) groups=0(root),1 (bin),2(daemon),3(sys),4(adm),6(disk),10(wheel) <---- Observe que o usurio root # /oracle/products/crs/install/rootaddno de.sh clscfg: EXISTING configuration version 3 detected. clscfg: version 3 is 10G Release 2. Attempting to add 1 new nodes to the con figuration Using ports: CSS=49895 CRS=49896 EVMC=49 898 and EVMR=49897. node <nodenumber>: <nodename> <private i nterconnect name> <hostname> node 2: rac2 rac2-priv rac2 Creating OCR keys for user 'root', privg rp 'root'.. Operation successful. /oracle/products/crs/bin/srvctl add node apps -n rac2 -A rac2-vip/255.255.255.0/eth0 -o /oracle/products/crs - A partir do Node2 # hostname rac2.localdomain <----------------------

-- Observe que no novo node # id uid=0(root) gid=0(root) groups=0(root),1 (bin),2(daemon),3(sys),4(adm),6(disk),10(wheel) <---- Observe que o usurio root # /oracle/products/crs/root.sh WARNING: directory '/oracle/products' is not owned by root WARNING: directory '/oracle' is not owne d by root Checking to see if Oracle CRS stack is a lready configured /etc/oracle does not exist. Creating it now. OCR LOCATIONS = /dev/raw/raw1 OCR backup directory '/oracle/products/c rs/cdata/crs' does not exist. Creating now Setting the permissions on OCR backup di rectory Setting up NS directories Oracle Cluster Registry configuration up graded successfully WARNING: directory '/oracle/products' is not owned by root WARNING: directory '/oracle' is not owne d by root clscfg: EXISTING configuration version 3 detected. clscfg: version 3 is 10G Release 2. assigning default hostname rac1 for node 1. assigning default hostname rac2 for node 2. Successfully accumulated necessary OCR k eys. Using ports: CSS=49895 CRS=49896 EVMC=49 898 and EVMR=49897. node <nodenumber>: <nodename> <private i nterconnect name> <hostname> node 1: rac1 rac1-priv rac1 node 2: rac2 rac2-priv rac2 clscfg: Arguments check out successfully . NO KEYS WERE WRITTEN. Supply -force para meter to override. -force is destructive and will destroy a ny previous cluster configuration. Oracle Cluster Registry for cluster has already been initialized Startup will be queued to init within 90 seconds. Adding daemons to inittab Expecting the CRS daemons to be up withi n 600 seconds. CSS is active on these nodes. rac1 rac2 CSS is active on all nodes. Waiting for the Oracle CRSD and EVMD to

start Oracle CRS stack installed and running u nder init(1M) Running vipca(silent) for configuring no deapps IP address "rac2-vip" has already been u sed. Enter an unused IP address. <----- Este erro na verdade um bug e pode ser ignorado @ OK @ Exit @ Yes 7.3 Verificar a adio do novo node: $ hostname rac2.localdomain <------------------------ Observe que n o novo node $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <------------ Observe que com o usurio oracle $CRS_HOME/bin/olsnodes -n rac1 1 rac2 2 <--------------- Novo node $ $CRS_HOME/bin/crs_stat -t Name Type Target State Host ----------------------------------------------------------ora.orcl.db application ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE crs ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE rac1 rac1 rac1 rac1 rac1 rac1 rac1 rac1 rac1 rac2 rac2 rac2 ora....l1.inst application ora....erv1.cs application ora....cl1.srv application ora....SM1.asm application ora....C1.lsnr application ora.rac1.gsd ora.rac1.ons ora.rac1.vip application application application

ora.rac2.gsd application <--------------- Adicionado ora.rac2.ons application <--------------- Adicionado ora.rac2.vip application <--------------- Adicionado $ $CRS_HOME/bin/crsctl check CSS appears healthy CRS appears healthy EVM appears healthy $ ls -l /etc/init.d/init.* -r-xr-xr-x 1 root root 1951 it.crs

Jul 14 07:51 /etc/init.d/in

-r-xr-xr-x 1 root root 4707 Jul 14 07:51 /etc/init.d/in it.crsd -r-xr-xr-x 1 root root 35387 Jul 14 07:51 /etc/init.d/in it.cssd -r-xr-xr-x 1 root root 3183 Jul 14 07:51 /etc/init.d/in it.evmd 8. Configurar o Software Oracle Database no novo node (rac2): 8.1 Verificar o acesso remoto e a equivaLencia de usurio: $ hostname rac1.localdomain <------------------------ Observe que o node j existente $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <--- Observe que com o usurio oracle $ ssh rac1 date <------------------------ No deve pedir senha $ ssh rac2 date <------------------------ No deve pedir senha 8.2 Verificar se o X est disponvel ou se a varivel DISPLAY est setad a pois uma interface grfica ser exibida. 8.3 Adicionar o Software Oracle no novo node: $ hostname rac1.localdomain <------------------------ Observe que o node que j existia no cluster $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <--- Observe que com o usurio oracle $ cd $ORACLE_HOME/oui/bin $ ./addNode.sh @ Next @ Public Node Name - rac2 <---------- Marque este node @ Next @ Install - A partir do Node2 # hostname rac2.localdomain <----------------------- Observe que no novo node # id uid=0(root) gid=0(root) groups=0(root),1 (bin),2(daemon),3(sys),4(adm),6(disk),10(wheel) <---- Observe que o usurio root # /oracle/products/db/root.sh Running Oracle10 root.sh script... The following environment variables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /oracle/products/db Enter the full pathname of the local bin directory: [/usr/local/bin]: Copying dbhome to /usr/local/bin ... Copying oraenv to /usr/local/bin ... Copying coraenv to /usr/local/bin ...

Creating /etc/oratab file... Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root.sh script. Now product-specific root actions will b e performed. @ OK @ Exit @ Yes

8.3 Adicionar o Listener no novo node: $ hostname rac1.localdomain <------------------------ Observe que o node que j existia no cluster $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <--- Observe que com o usurio oracle $ cd $ORACLE_HOME/bin $ ./netca @ Cluster configuration @ Next @ Node(s) - rac2 <------------ Selecione apenas o novo no de Next Listener configuration Next Add Next Listener name - LISTENER @ Next @ Selected Protocols - TCP @ Next @ Use the standard port number of 1521 <---------- Marq ue esta opo ou selecione outra porta @ Next @ Would you like to configure another listener? - No @ Next @ Next @ Finish 8.4 Verificar a adio no novo Listener: $ hostname rac1.localdomain <------------------------ Observe que o node que j existia no cluster $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <--- Observe que com o usurio oracle $ $CRS_HOME/bin/crs_stat ora.rac1.LISTENER_RAC1.lsnr NAME=ora.rac1.LISTENER_RAC1.lsnr @ @ @ @ @ @

TYPE=application TARGET=ONLINE STATE=ONLINE on rac1 $ $CRS_HOME/bin/crs_stat ora.rac2.LISTENER_RAC2.lsnr <----NAME=ora.rac2.LISTENER_RAC2.lsnr ---TYPE=application ---- ----------- Indica que o Listener do novo node foi criado TARGET=ONLINE ---STATE=ONLINE on rac2 ---$ $CRS_HOME/bin/crs_stat -t -v Name Type R/RA ate Host --------------------------------------------------------------------ora.orcl.db LINE LINE LINE LINE LINE LINE LINE LINE LINE LINE LINE LINE LINE rac1 ora....l1.inst application rac1 ora....erv1.cs application rac1 ora....cl1.srv application rac1 ora....SM1.asm application rac1 ora....C1.lsnr application rac1 ora.rac1.gsd rac1 ora.rac1.ons rac1 ora.rac1.vip rac1 ora....C2.lsnr application rac2 <------------- Listener adicionado ora.rac2.gsd application rac2 ora.rac2.ons application rac2 ora.rac2.vip application rac2 0/5 0/5 0/3 0/0 0/0 0/0 0/0 0/0 ONLINE ONLINE ONLINE ONLINE ON ON ON ON application 0/0 0/0 ONLINE ON application 0/3 0/0 ONLINE ON application 0/5 0/0 ONLINE ON 0/5 0/0 ONLINE ON 0/5 0/0 ONLINE ON 0/1 0/0 ONLINE ON 0/1 0/1 ONLINE ON 0/5 0/0 ONLINE ON application 0/1 0/1 ONLINE ON F/FT Target <-<-<-<--

St

9. Configurar o Oracle Database no novo node (rac2): 9.1 Verificar o acesso remoto e a equivaLencia de usurio: $ hostname rac1.localdomain <------------------------ Observe que o node j existente $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <--- Observe que com o usurio oracle $ ssh rac1 date <------------------------ No deve pedir senha $ ssh rac2 date <------------------------ No deve pedir senha

9.2 Verificar se o X est disponvel ou se a varivel DISPLAY est setad a pois uma interface grfica ser exibida. 9.3 Adicionar a instncia no novo node: $ hostname rac1.localdomain <------------------------ Observe que o node que j existia no cluster $ id uid=500(oracle) gid=500(oinstall) groups=500(oinstall),5 01(dba) <--- Observe que com o usurio oracle $ cd $ORACLE_HOME/bin $ ./dbca Oracle Real Application Clusters Database Next Instance Management Next Add an instance Next Database Name - orcl @ Username - sys @ Password - <especifique a senha do usurio sys> @ Next @ Next @ The default instance name is "orcl2". Edit the instanc e name if needed, select the node on wich to add the instance, and click Next. - Instance Name - orcl2 - Node Name - rac2 @ Next @ Expand the tree and click the Oracle database services from the left panel... - opcional @ Next @ Storage - Tablespace de Undo <---------------- Datafiles da Tablespace de Undo <---- ----------- Verifique essas informaes. - Grupos de Redo Log <---------------@ Finish @ OK @ ASM is present on the cluster but needs to be extended to the following nodes: [rac2]. Do you want ASM to be extended? - Yes @ Do you want to perform another operation? - No 9.4 Verificar a adio da nova instncia e servios, se houver: $ crs_stat -t Name Type Target State Host ----------------------------------------------------------ora.orcl.db application ONLINE ONLINE ONLINE ONLINE rac1 rac1 ora....l1.inst application @ @ @ @ @ @ @

ora....l2.inst application ONLINE ONLINE <----- Instncia de Banco de Dados adicionada e ativa no novo node ora....erv1.cs application ONLINE ONLINE ora....cl1.srv application ONLINE ONLINE

rac2 rac1 rac1

ora....cl2.srv application OFFLINE OFFLINE <----- Servio adicionado. Como um servio que j existia fora reconfigurado ora....SM1.asm application ONLINE ONLINE rac1 para o novo node, ele aparece aqui, para o novo node, como OFFLINE. ora....C1.lsnr application ONLINE ONLINE rac1 Se nenhum servio tivesse sido reconfigurado ou criado, no haveria ora.rac1.gsd application ONLINE ONLINE rac1 nenhuma entrada relativa servios nesta sada. ora.rac1.ons application ONLINE ONLINE rac1 ora.rac1.vip application ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE rac1 rac2 rac2 rac2 rac2 rac2

ora....SM2.asm application ONLINE <----- Instncia ASM adicionada e ativa no novo node ora....C2.lsnr application ONLINE ora.rac2.gsd ora.rac2.ons ora.rac2.vip application application application ONLINE ONLINE ONLINE

$ sqlplus / as sysdba SQL> select inst_id, instance_name, status,to_char(start up_time,'dd/mm/rrrr hh24:mi') startuptime from gv$instance order by inst_id; INST_ID INSTANCE_NAME STATUS STARTUPTIME ---------- ---------------- ------------ --------------1 orcl1 5 2 orcl2 8 <--------- Instncia adicionada OPEN 14/07/2011 11:4 OPEN 14/07/2011 05:1

9.5 Verificar os datafiles e a tablespaces adicionadas para a no va instnica: $ sqlplus / as sysdba SQL> select tablespace_name from dba_tablespaces order b y 1; TABLESPACE_NAME -----------------------------SYSAUX SYSTEM TEMP UNDOTBS1 UNDOTBS2 <---------------------- Tablespace adi cionada USERS 6 rows selected. 9.6 Verificar os redo logs adicionado para nova instncia: $ sqlplus / as sysdba

SQL> select inst_id, group#, member from gv$logfile orde r by 1,2,3; INST_ID GROUP# MEMBER ---------- ---------- ------------------------1 1 +INDICES/orcl/redo01.log 1 2 +INDICES/orcl/redo02.log 2 1 +INDICES/orcl/redo03.log <----------- --- Redo Logs adicionado 2 2 +INDICES/orcl/redo04.log <----------9.7 Inicializar o servio criado/reconfigurado para a nova instncia : $ ./srvctl start service -d orcl -s serv1 -i orcl2 $ crs_stat -t Name Type Target State Host ----------------------------------------------------------ora.orcl.db application ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE rac1 rac1 rac2 rac1 rac1 rac2 rac1 rac1 rac1 rac1 rac1 rac2 rac2 rac2 rac2 rac2 ora....l1.inst application ora....l2.inst application ora....erv1.cs application ora....cl1.srv application ora....cl2.srv application <---------- Servio inicializado ora....SM1.asm application ora....C1.lsnr application ora.rac1.gsd ora.rac1.ons ora.rac1.vip application application application

ora....SM2.asm application ora....C2.lsnr application ora.rac2.gsd ora.rac2.ons ora.rac2.vip ####### Boa Sorte! application application application

Você também pode gostar