srvctl start/stop/status home

Learning new things by actually reading the log files.

[oracle@rac02:emu2:/home/oracle]
$ srvctl status home -o /u01/app/oracle/product/11.2.0.4/db_1 -s ~/statushome.txt -n rac01; cat ~/statushome.txt
Service emu_svc is running on node rac01
Database emu is running on node rac01
svc-emu_svc
db-emu


[oracle@rac02:emu2:/home/oracle]
$ srvctl stop home -o /u01/app/oracle/product/11.2.0.4/db_1 -s ~/stophome.txt -n rac01 -t immediate -f
PRKO-3244 : The -s  option value "/home/oracle/stophome.txt" already exists


[oracle@rac02:emu2:/home/oracle]
$ rm -f ~/stophome.txt; srvctl stop home -o /u01/app/oracle/product/11.2.0.4/db_1 -s ~/stophome.txt -n rac01 -t immediate -f; cat ~/stophome.txt
svc-emu_svc
db-emu


[oracle@rac02:emu2:/home/oracle]
$ srvctl start home -o /u01/app/oracle/product/11.2.0.4/db_1 -s ~/stophome.txt -n rac01; cat ~/stophome.txt
svc-emu_svc
db-emu


[oracle@rac02:emu2:/home/oracle]
$ srvctl status home -o /u01/app/oracle/product/11.2.0.4/db_1 -s ~/statushome.txt -n rac01; cat ~/statushome.txt
Service emu_svc is running on node rac01
Database emu is running on node rac01
svc-emu_svc
db-emu

Advertisement

RAC1Node Conversion/Relocation/Termination

RAC1Node Conversion/Relocation/Termination

Instance Name changes during RAC One Node Failover/Switchover

Just a quick note to self.

INSTANCE / NODE CRASH (FAILOVER):

     When the node goes down due to abnormal termination (  kill -9 or due to unknown reasons) Grid Infrastructure performs the following:

•  First cluster tries to restart the instance in same node.
  
•  If it is unsuccessful then it will start the instance in other node.
•  If the instance name is orcl_1, when it failover to node 2 it will be still orcl_1.
  

INSTANCE RELOCATE MANUALLY(SWITCHOVER):

    When Manually switchover is performed for relocating orcl_1 from Node1 to Node 2 (Instance Relocation) Grid Infrastructure performs the following:

• It will first create pfile( init.ora) automatically in node 2.
• In node 2 it will use the new pfile and start instance with a new name, i.e. orcl_2, this is due to both instances are required to be up and running for active sessions on the original node to complete or time out.
  
• Post switchover, it uses new instance name i.e. orcl_2   

Reference:

(31-May-2016). Retrieved November 3, 2016, from https://support.oracle.com/epmos/faces/DocContentDisplay?id=1540629.1