RAC Attack - Oracle Cluster Database at Home/Increase CRS Fencing Timeout (Shared Filesystem)

From Wikibooks, open books for an open world
Jump to: navigation, search


These steps are not necessary for a test or production environment. However they might make your VMware test cluster just a little more stable and they will provide a good learning opportunity about Grid Infrastructure.



  1. Grid Infrastructure must be running on only one node to change these settings. Shutdown the clusterware on collabn2 as user root.

    [oracle@collabn1 ~]$ ssh collabn2
    Last login: Wed Mar 30 14:50:49 2011
    Set environment by typing 'oenv' - default is instance RAC1.
    
    collabn2:/home/oracle[RAC1]$ su -
    Password: racattack
    
    [root@collabn2 bin]# crsctl stop crs
    CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources
              on 'collabn2'
    CRS-2673: Attempting to stop 'ora.crsd' on 'collabn2'
    CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on 'collabn2'
    ...
    ...
    ...
    CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'collabn2' has completed
    CRS-4133: Oracle High Availability Services has been stopped.
    


  2. Return to node collabn1. As the root user, increase the misscount so that CRS waits 1.5 minutes before it reboots. (VMware can drag a little on some laptops!)

    [root@collabn1 ~]# crsctl get css misscount
    30
    [root@collabn1 ~]# crsctl set css misscount 90
    Configuration parameter misscount is now set to 90.
    


  3. Increase the disktimeout so that CRS waits 10 minutes for I/O to complete before rebooting.

    [root@collabn1 ~]# crsctl get css disktimeout
    200
    [root@collabn1 ~]# crsctl set css disktimeout 600
    Configuration parameter disktimeout is now set to 600.
    


  4. Restart CRS on the other node.

    [root@collabn1 bin]# ssh collabn2
    [root@collabn2 bin]# crsctl start crs