Completing the Live Upgrade

At the end of the process:

When completing the Live Upgrade process, take the following limitations into consideration for Solaris 10 Update 10:

See the Veritas Storage Foundation for Oracle RAC Release notes for more details.

To complete the Live Upgrade

  1. Complete the Live Upgrade process using one of the following commands:

    If the primary root disk is not encapsulated, run the following command:

    # ./vxlufinish -u target_os_version
    Live Upgrade finish on the Solaris release <5.10>

    If the primary root disk is encapsulated by VxVM, run the following command:

    # ./vxlufinish -u target_os_version -g diskgroup
    Live Upgrade finish on the Solaris release <5.10>

    The Live Upgrade process encapsulates the alternate root disk if the primary root disk was encapsulated.

  2. If the system crashes or reboots before Live Upgrade completes successfully, you may remount the alternate disk using the following command:
    # ./vxlustart -r -u target_os_version

    Then, rerun the vxlufinish command:

    # ./vxlufinish -u target_os_version
  3. If the Oracle database is managed by VCS, modify the VCS configuration file on the alternate root disk (/altroot.5.10/etc/VRTSvcs/conf/config/main.cf) to set the AutoStart value to 0. This prevents the database service group from starting automatically when VCS starts:
    group oradb_grp (
            SystemList = { sys1 = 0, sys2 = 1 }
    								AutoStart = 0
            AutoFailOver = 0
            Parallel = 1
            AutoStartList = { sys1, sys2 }
            )
    .
    .

    If the database is not managed by VCS, change the management policy for the database to manual on the primary boot disk:

    $ srvctl modify database -d db-name -y manual
  4. Perform the following steps on the primary boot environment:

    • Stop Oracle Clusterware on each node in the cluster:

      # clus_home/bin/crsctl crs stop

      where clus_home is the path of the Oracle Clusterware/Grid Infrastructure home directory

    • Stop the applications using native application commands.

    • Make sure that no processes are running which make use of mounted shared file system or shared volumes.

      # fuser -cu mount-point
    • Take offline all VCS groups that contain CFSMount and CVMVolDg:

      # hagrp -offline group -sys sys1
      # hagrp -offline group -sys sys2
    • Unmount the VxFS file systems:

      # mount -v |grep vxfs
      # fuser -c /mount_point
      # umount /mount_point
    • Deport CVM disk groups:

      # vxdg deport diskgroup_name
    • Make sure that no disk groups are imported:

      # vxdg list
      NAME STATE ID
  5. Restart all the nodes in the cluster. The boot environment on the alternate disk is activated when you restart the nodes.

    Note:

    DO NOT use the reboot, halt, or uadmin commands to reboot the system. Use either the init or the shutdown commands to enable the system to boot using the alternate boot environment.

    # shutdown -g0 -y -i6
  6. Relink the SF Oracle RAC libraries with the Oracle RAC libraries:

    See Relinking Oracle RAC libraries with the SF Oracle RAC libraries.

  7. Start the database group on all nodes:
    # hagrp -online oradb_grpname -any
  8. If the Oracle database is managed by VCS, modify the VCS configuration file (/etc/VRTSvcs/conf/config/main.cf) to set the AutoStart value to 1.
    group oradb_grp (
            SystemList = { sys1 = 0, sys2 = 1 }
    								AutoStart = 1
            AutoFailOver = 0
            Parallel = 1
            AutoStartList = { sys1, sys2 }
            )
    .
    .

    If the database is not managed by VCS, change the management policy for the database to automatic on the primary boot disk:

    $ srvctl modify database -d db-name -y AUTOMATIC
  9. Complete the post-upgrade tasks.

    See the chapter "Performing post-upgrade tasks" in this document.

  10. If you are on an unsupported version of Oracle RAC, upgrade Oracle RAC.

    For instructions, see the chapter Upgrading Oracle RAC in this document.