Cluster Server 8.0 Application Note: Dynamic Reconfiguration for Oracle Servers - Solaris

Last Published:
Product(s): InfoScale & Storage Foundation (8.0)
Platform: Solaris

Stopping VCS in SF for Oracle RAC environment

If you must stop VCS on a domain where SF for Oracle RAC is running, the Oracle RAC application on the domain being reconfigured must be brought offline. In addition, the GAB, LLT, LMX, and VXFEN modules must be unconfigured. Performing these steps ensures that other instances do not attempt communication with the stopped instance. This could cause the application to hang, when the instance does not respond.

You need to perform these prerequisites before you stop VCS in SF for Oracle RAC environment.

Note:

You need to log in as administrator into the domain that needs to be reconfigured.

Stopping Oracle Instances outside VCS control

  • If the database is not managed by VCS, stop the Oracle database using the following command:
    # srvctl stop database -d db_name

Stopping the applications that use CVM or CFS (outside of VCS control)

  1. Stop the applications that use CVM volumes or CFS mount points that are not controlled by VCS, using native application commands.
  2. Verify that no processes use the CFS mount point using the following command:
    # fuser -c mount_point

Unmounting CFS file systems (outside of VCS control)

You need to unmount the CFS file systems that are not under VCS control on all nodes.

  1. Determine the file systems that need to be unmounted by verifying the output of the mount command. The command lists the mounted clustered file systems.

    Note:

    Check the main.cf file for identifying the files that are under VCS control.

    # mount -v | grep vxfs | grep cluster

  2. Unmount each file system that are not controlled by VCS using the following command:

    # umount mount_point

To stop VCS in a SF for Oracle RAC environment

  1. Log in as administrator to the domain being reconfigured (dom1, for example).
  2. List the configured VCS service groups and see which are online in the domain:

    # hagrp -list

  3. Based on the output of step 2, bring each service group that is online to offline in the domain dom1. Use the following command:

    # hagrp -offline service_grp_name -sys dom1

  4. Stop VCS.

    # hastop -local

    In addition to port h, this command stops the CVM drivers using ports v and w.

  5. If any CFS file systems outside of VCS control are mounted, unmount them.
  6. Stop ODM using the following command:

    # svcadm disable -t vxodm

  7. Unconfigure the VCSMM and I/O fencing drivers, which use ports b and o, respectively:

    # /sbin/vxfenconfig -U

    # /sbin/vcsmmconfig -U

  8. Unconfigure the LMX driver:

    # /sbin/lmxconfig -U

  9. Verify that the drivers h, v, w, f, q, d, b, and o are stopped. They should not show memberships when you use the gabconfig -a command:

    # gabconfig -a

    GAB Port Memberships
============================================================
Port a gen 4a1c0001 membership 01
  10. Stop cluster fencing, VCSMM, LMX, ODM, and GAB modules if required.

    # svcadm disable -t system/vxfen

    # svcadm disable -t system/vcsmm

    # svcadm disable -t system/vxodm

    # svcadm disable -t system/gab

    # svcadm disable -t system/llt

  11. Unload the VCSMM, I/O fencing, and LMX modules.

    Determine the module IDs for VCSMM, I/O fencing, and LMX:

    # modinfo | egrep "lmx|vxfen|vcsmm"

    237 783e4000 25497 237 1 vcsmm (VERITAS Membership
Manager)
238 78440000 263df 238 1 vxfen (VERITAS I/O Fencing)
239 7845a000 12b1e 239 1 lmx (LLT Mux 3.5B2)

    Unload the VCSMM, I/O fencing, and LMX modules based on their module IDs:

    # modunload -i 237

    # modunload -i 238

    # modunload -i 239

  12. Unconfigure GAB

    # /sbin/gabconfig -U

  13. Unconfigure LLT

    # /sbin/lltconfig -U

  14. Remove the GAB and LLT modules from the kernel.

    Determine the IDs of the GAB and LLT modules:

    # modinfo | egrep "gab|llt"

    305 78531900 30e 305 1 gab
292 78493850 30e 292 1 llt

    Unload the GAB and LLT modules based on their module IDs:

    # modunload -i 305

    # modunload -i 292

  15. You can begin performing dynamic reconfiguration.