Relinking the 12c Grid
In this Practice have have used 2 Nodes with the Hp-ux Itanium as the O/S with the 12c grid and 12c database with The standard cluster .. Before starting the re linking process we need to stop all the cluster services running in all the Nodes ..check the CRS and make sure that the crs had been in all the NodesStep 1 Unlock the grid infrastructure
We need to unlock all the nodes in the grid infrastructure to perform the relink .. the unlocking can be done by the O/S root user ..before unlock the grid make sure that all the services had been stopped correctly
As the root user navigate to the GRID_HOME/crs/install directory and run the command perl rootcrs.pl -unlock In all the nodes
Node1
root @ db01/prod01/oracle/12.1.0/12.1.0/grid/crs/install >perl rootcrs.pl -unlock
Using configuration parameter file: ./crsconfig_params
2014/06/29 11:50:07 CLSRSC-347: Successfully unlock /prod01/oracle/12.1.0/12.1.0/grid
root @ db01./prod01/oracle/12.1.0/12.1.0/grid/crs/install >
Node2
root @ db02/prod01/oracle/12.1.0/12.1.0/grid/crs/install >perl rootcrs.pl -unlock
Using configuration parameter file: ./crsconfig_params
2014/06/29 11:53:39 CLSRSC-347: Successfully unlock /prod01/oracle/12.1.0/12.1.0/grid
root @ db02/prod01/oracle/12.1.0/12.1.0/grid/crs/install >
Step 2 Relink for the grid owner[O/S]
Switch the user to the grid owner and set the environment variable for ORACLE_HOME and path for the grid user and navigate to ORACLE_HOME/bin and execute the command relink all in all the nodes
Node1
oragrid @ db01/home/oragrid >echo $ORACLE_HOME
/prod01/oracle/12.1.0/12.1.0/grid
oragrid @ db01/prod01/oracle/12.1.0/12.1.0/grid/bin >relink all
writing relink log to: /prod01/oracle/12.1.0/12.1.0/grid/install/relink.log
Node2
oragrid @ db02/prod01/oracle/12.1.0/12.1.0/grid >echo $ORACLE_HOME
/prod01/oracle/12.1.0/12.1.0/grid
oragrid @ db01/prod01/oracle/12.1.0/12.1.0/grid/bin >relink all
writing relink log to: /prod01/oracle/12.1.0/12.1.0/grid/install/relink.log
Once the Re-link is done check the relink.log to find where any discard or any error Messages if there are error or discard messages fix the problem and move to next step .. else Proceed to the next step
Step 3 Rootadd and rootcrs execution
Once the relink command had been successfully completed then we need to run the rootadd and rootcrs again from the o/s root user
Run the rootadd_rdbms.sh from the GRID_HOME/rdbms/install as the root user run the command on all the nodes of the grid
Node1
Run the rootadd_rdbms.sh from the GRID_HOME/rdbms/install as the root user run the command on all the nodes of the grid
Node1
root @ db01/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install >pwd
/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install
root @ db01/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install >./rootadd_rdbms.sh
Node2
After the execution of the rootadd_rdbms.sh we need to execute the perl rootcrs.pl -patch it will start the all the Custer services .. we need to execute this command in all the nodes in the cluster
Node1
root @ db02/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install >pwd
/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install
root @ db02/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install >./rootadd_rdbms.sh
After the execution of the rootadd_rdbms.sh we need to execute the perl rootcrs.pl -patch it will start the all the Custer services .. we need to execute this command in all the nodes in the cluster
Node1
root @ db01/prod01/oracle/12.1.0/12.1.0/grid/crs/install >perl rootcrs.pl -patch
Using configuration parameter file: ./crsconfig_params
CRS-4123: Starting Oracle High Availability Services-managed resources
CRS-2672: Attempting to start 'ora.mdnsd' on 'db01'
CRS-2672: Attempting to start 'ora.evmd' on 'db01'
CRS-2676: Start of 'ora.mdnsd' on 'db01' succeeded
CRS-2676: Start of 'ora.evmd' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'db01'
CRS-2676: Start of 'ora.gpnpd' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.gipcd' on 'db01'
CRS-2676: Start of 'ora.gipcd' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'db01'
CRS-2676: Start of 'ora.cssdmonitor' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'db01'
CRS-2672: Attempting to start 'ora.diskmon' on 'db01'
CRS-2676: Start of 'ora.diskmon' on 'db01' succeeded
CRS-2789: Cannot stop resource 'ora.diskmon' as it is not running on server 'db01'
CRS-2676: Start of 'ora.cssd' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'db01'
CRS-2672: Attempting to start 'ora.ctssd' on 'db01'
CRS-2676: Start of 'ora.ctssd' on 'db01' succeeded
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'db01'
CRS-2676: Start of 'ora.asm' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.storage' on 'db01'
CRS-2676: Start of 'ora.storage' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'db01'
CRS-2676: Start of 'ora.crsd' on 'db01' succeeded
CRS-6023: Starting Oracle Cluster Ready Services-managed resources
CRS-6017: Processing resource auto-start for servers: db01
CRS-2672: Attempting to start 'ora.scan1.vip' on 'db01'
CRS-2672: Attempting to start 'ora.ons' on 'db01'
CRS-2672: Attempting to start 'ora.db01.vip' on 'db01'
CRS-2672: Attempting to start 'ora.db02.vip' on 'db01'
CRS-2672: Attempting to start 'ora.cvu' on 'db01'
CRS-2676: Start of 'ora.cvu' on 'db01' succeeded
CRS-2676: Start of 'ora.scan1.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.LISTENER_SCAN1.lsnr' on 'db01'
CRS-2676: Start of 'ora.db02.vip' on 'db01' succeeded
CRS-2676: Start of 'ora.db01.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.LISTENER.lsnr' on 'db01'
CRS-2672: Attempting to start 'ora.LISTENER_OMPRD.lsnr' on 'db01'
CRS-2676: Start of 'ora.ons' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.scan3.vip' on 'db01'
CRS-2672: Attempting to start 'ora.scan2.vip' on 'db01'
CRS-2676: Start of 'ora.LISTENER_OMPRD.lsnr' on 'db01' succeeded
CRS-2676: Start of 'ora.LISTENER.lsnr' on 'db01' succeeded
CRS-2676: Start of 'ora.LISTENER_SCAN1.lsnr' on 'db01' succeeded
CRS-2676: Start of 'ora.scan3.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.LISTENER_SCAN3.lsnr' on 'db01'
CRS-2676: Start of 'ora.scan2.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.LISTENER_SCAN2.lsnr' on 'db01'
CRS-2676: Start of 'ora.LISTENER_SCAN3.lsnr' on 'db01' succeeded
CRS-2676: Start of 'ora.LISTENER_SCAN2.lsnr' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.omprd.db' on 'db01'
CRS-2676: Start of 'ora.omprd.db' on 'db01' succeeded
CRS-6016: Resource auto-start has completed for server db01
CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources
CRS-4123: Oracle High Availability Services has been started.
Oracle Clusterware active version on the cluster is [12.1.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [0].
Node2
root @ db02.oasiserp.com/prod01/oracle/12.1.0/12.1.0/grid/crs/install >perl rootcrs.pl -patch
CRS-4123: Starting Oracle High Availability Services-managed resources
CRS-2672: Attempting to start 'ora.mdnsd' on 'db02'
CRS-2672: Attempting to start 'ora.evmd' on 'db02'
CRS-2676: Start of 'ora.evmd' on 'db02' succeeded
CRS-2676: Start of 'ora.mdnsd' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'db02'
CRS-2676: Start of 'ora.gpnpd' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.gipcd' on 'db02'
CRS-2676: Start of 'ora.gipcd' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'db02'
CRS-2676: Start of 'ora.cssdmonitor' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'db02'
CRS-2672: Attempting to start 'ora.diskmon' on 'db02'
CRS-2676: Start of 'ora.diskmon' on 'db02' succeeded
CRS-2789: Cannot stop resource 'ora.diskmon' as it is not running on server 'db02'
CRS-2676: Start of 'ora.cssd' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'db02'
CRS-2672: Attempting to start 'ora.ctssd' on 'db02'
CRS-2676: Start of 'ora.ctssd' on 'db02' succeeded
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'db02'
CRS-2676: Start of 'ora.asm' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.storage' on 'db02'
CRS-2676: Start of 'ora.storage' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'db02'
CRS-2676: Start of 'ora.crsd' on 'db02' succeeded
CRS-6017: Processing resource auto-start for servers: db02
CRS-2672: Attempting to start 'ora.ons' on 'db02'
CRS-2673: Attempting to stop 'ora.db02.vip' on 'db01'
CRS-2672: Attempting to start 'ora.ASMNET1LSNR_ASM.lsnr' on 'db02'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN1.lsnr' on 'db01'
CRS-2677: Stop of 'ora.LISTENER_SCAN1.lsnr' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.scan1.vip' on 'db01'
CRS-2677: Stop of 'ora.db02.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.db02.vip' on 'db02'
CRS-2677: Stop of 'ora.scan1.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.scan1.vip' on 'db02'
CRS-2676: Start of 'ora.db02.vip' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.LISTENER.lsnr' on 'db02'
CRS-2672: Attempting to start 'ora.LISTENER_OMPRD.lsnr' on 'db02'
CRS-2676: Start of 'ora.scan1.vip' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.LISTENER_SCAN1.lsnr' on 'db02'
CRS-2676: Start of 'ora.ASMNET1LSNR_ASM.lsnr' on 'db02' succeeded
CRS-2676: Start of 'ora.ons' on 'db02' succeeded
CRS-2676: Start of 'ora.LISTENER_SCAN1.lsnr' on 'db02' succeeded
CRS-2676: Start of 'ora.LISTENER.lsnr' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'db02'
CRS-2676: Start of 'ora.LISTENER_OMPRD.lsnr' on 'db02' succeeded
CRS-2676: Start of 'ora.asm' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.omprd.db' on 'db02'
CRS-2676: Start of 'ora.omprd.db' on 'db02' succeeded
CRS-6016: Resource auto-start has completed for server db02
CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources
CRS-4123: Oracle High Availability Services has been started.
Oracle Clusterware active version on the cluster is [12.1.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [0].
Step 4
check the cluster now all the services should be up automatically
root @ db01/prod01/oracle/12.1.0/12.1.0/grid/bin >./crs_stat -t -v
root @ db01/prod01/oracle/12.1.0/12.1.0/grid/bin >./crs_stat -t -v
Name Type R/RA F/FT Target State Host
----------------------------------------------------------------------
ora....SM.lsnr ora....er.type 0/5 0/ ONLINE ONLINE db01
ora.DATA.dg ora....up.type 0/5 0/ ONLINE ONLINE db01
ora.FLASH.dg ora....up.type 0/5 0/ ONLINE ONLINE db01
ora....ER.lsnr ora....er.type 0/5 0/ ONLINE ONLINE db01
ora....RD.lsnr ora....er.type 0/5 0/ ONLINE ONLINE db01
ora....N1.lsnr ora....er.type 0/5 0/0 ONLINE ONLINE db02
ora....N2.lsnr ora....er.type 0/5 0/0 ONLINE ONLINE db01
ora....N3.lsnr ora....er.type 0/5 0/0 ONLINE ONLINE db01
ora.asm ora.asm.type 0/5 0/0 ONLINE ONLINE db01
ora.cvu ora.cvu.type 0/5 0/0 ONLINE ONLINE db01
ora....SM1.asm application 0/5 0/0 ONLINE ONLINE db01
ora....01.lsnr application 0/5 0/0 ONLINE ONLINE db01
ora....01.lsnr application 0/5 0/0 ONLINE ONLINE db01
ora.db01.ons application 0/3 0/0 ONLINE ONLINE db01
ora.db01.vip ora....t1.type 0/0 0/0 ONLINE ONLINE db01
ora....SM2.asm application 0/5 0/0 ONLINE ONLINE db02
ora....02.lsnr application 0/5 0/0 ONLINE ONLINE db02
ora....02.lsnr application 0/5 0/0 ONLINE ONLINE db02
ora.db02.ons application 0/3 0/0 ONLINE ONLINE db02
ora.db02.vip ora....t1.type 0/0 0/0 ONLINE ONLINE db02
ora.gns ora.gns.type 0/5 0/0 ONLINE ONLINE db01
ora.gns.vip ora....ip.type 0/0 0/0 ONLINE ONLINE db01
ora....network ora....rk.type 0/5 0/ ONLINE ONLINE db01
ora.oc4j ora.oc4j.type 0/1 0/2 OFFLINE OFFLINE
ora.omprd.db ora....se.type 0/2 0/1 ONLINE ONLINE db01
ora.ons ora.ons.type 0/3 0/ ONLINE ONLINE db01
ora.scan1.vip ora....ip.type 0/0 0/0 ONLINE ONLINE db02
ora.scan2.vip ora....ip.type 0/0 0/0 ONLINE ONLINE db01
ora.scan3.vip ora....ip.type 0/0 0/0 ONLINE ONLINE db01
No comments:
Post a Comment