Storage Foundation for Oracle® RAC 8.0.2 Configuration and Upgrade Guide - Linux

To perform a rolling upgrade

1. If you want to upgrade the operating system, perform the following steps:

   • Change to the /opt/VRTS/install directory on the node where you want to upgrade the operating system:

     # cd /opt/VRTS/install

   • Stop SF Oracle RAC:

     # ./installer -stop

   • Upgrade the operating system. For instructions, see the operating system documentation.

   • Restart the nodes, if required:

     # shutdown -r now

2. Phase 1 of rolling upgrade begins on the first subcluster. Complete the preparatory steps on the first subcluster.
3. Log in as superuser and mount the SF Oracle RAC 8.0.2 installation media.
4. From root, start the installer.

   # ./installer

5. From the menu, select Upgrade a Product and from the sub menu, select Rolling Upgrade.
6. The installer suggests system names for the upgrade. Press Enter to upgrade the suggested systems, or enter the name of any one system in the cluster on which you want to perform a rolling upgrade and then press Enter.
7. The installer checks system communications, release compatibility, version information, and lists the cluster name, ID, and cluster nodes. Type y to continue.
8. The installer inventories the running service groups and determines the node or nodes to upgrade in phase 1 of the rolling upgrade. Type y to continue. If you choose to specify the nodes, type n and enter the names of the nodes.
9. The installer performs further prechecks on the nodes in the cluster and may present warnings. You can type y to continue or quit the installer and address the precheck's warnings.
10. Review the end-user license agreement, and type y if you agree to its terms.
11. If the boot disk is encapsulated and mirrored, you can create a backup boot disk.

    If you choose to create a backup boot disk, type y. Provide a backup name for the boot disk group or accept the default name. The installer then creates a backup copy of the boot disk group.

12. After the installer detects the online service groups, the installer prompts the user to do one of the following:

    • Manually switch service groups

    • Use the CPI to automatically switch service groups

    The downtime is the time that it normally takes for the service group's failover.

    Note:

    It is recommended that you manually switch the service groups. Automatic switching of service groups does not resolve dependency issues if any dependent resource is not under VCS control.

13. The installer prompts you to stop the applicable processes. Type y to continue.

    The installer evacuates all service groups to the node or nodes that are not upgraded at this time. The installer stops parallel service groups on the nodes that are to be upgraded.

14. The installer stops relevant processes, uninstalls old kernel RPMs, and installs the new RPMs. The installer asks if you want to update your licenses to the current version. Select Yes or No. Veritas recommends that you update your licenses to fully use the new features in the current release.
15. If the cluster has configured Coordination Point Server based fencing, then during upgrade, installer may ask the user to provide the new HTTPS Coordination Point Server.

    The installer performs the upgrade configuration and starts the processes. If the boot disk is encapsulated before the upgrade, installer prompts the user to reboot the node after performing the upgrade configuration.

    Note:

    The Oracle service group is offline as the AutoStart attribute is set to 0 to prevent the service group from starting automatically. The service group is started later in the process.

16. Reboot the nodes on the subcluster being upgraded.

    If some processes fail to start, you may need to reboot the nodes and manually check the cluster's status.

    If the installer reboots the nodes, restart the installer.

17. Manually mount the VxFS and CFS file systems that VCS does not manage.
18. Relink the SF Oracle RAC libraries with Oracle by choosing the option Relink Oracle Database Binary from the program menu.

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

19. If the boot disk is encapsulated, the installer strongly recommends a restart of the nodes. Restart the nodes as prompted by the installer.

20. Bring the Oracle database service group online.

    • If VCS manages the Oracle database:

      # hagrp -online oracle_group -sys node_name

    • If VCS does not manage the Oracle database:

      $ srvctl start instance -db db_name \
      -node node_name

21. Start all applications that are not managed by VCS. Use native application commands to start the applications.
22. Complete the preparatory steps on the nodes that you have not yet upgraded.
23. The installer begins phase 1 of the upgrade on the remaining node or nodes. Type y to continue the rolling upgrade. If the installer was invoked on the upgraded (rebooted) nodes, you must invoke the installer again.

    Note:

    In case of an FSS environment, phase 1 of the rolling upgrade is performed on one node at a time.

    The installer repeats step 8 through step 21.

    For clusters with larger number of nodes, this process may repeat several times. Service groups come down and are brought up to accommodate the upgrade.

    This completes phase 1 of the upgrade.

24. • If VCS manages the Oracle database, reset the AutoStart value to 1 to enable VCS to bring the database service group online when VCS starts:

      # haconf -makerw
      # hagrp -modify oracle_group AutoStart 1
      # haconf -dump -makero

    • If VCS does not manage the Oracle database, change the management policy for the database to automatic:

      $ srvctl modify database -db db_name -policy AUTOMATIC

25. Migrate the SFDB repository database.

26. Phase 2 of the upgrade begins here. This phase includes downtime for the VCS engine (HAD), which does not include application downtime. Type y to continue.
27. The installer determines the remaining RPMs to upgrade. Press Enter to continue.
28. The installer displays the following question before the installer stops the product processes. If the cluster was configured in secure mode and version is prior to 6.2 before the upgrade, these questions are displayed.

    • Do you want to grant read access to everyone? [y,n,q,?]

      • To grant read access to all authenticated users, type y.

      • To grant usergroup specific permissions, type n.

    • Do you want to provide any usergroups that you would like to grant read access?[y,n,q,?]

      • To specify usergroups and grant them read access, type y

      • To grant read access only to root users, type n. The installer grants read access read access to the root users.

    • Enter the usergroup names separated by spaces that you would like to grant read access. If you would like to grant read access to a usergroup on a specific node, enter like 'usrgrp1@node1', and if you would like to grant read access to usergroup on any cluster node, enter like 'usrgrp1'. If some usergroups are not created yet, create the usergroups after configuration if needed. [b]

29. The installer stops Cluster Server (VCS) processes but the applications continue to run. Type y to continue.

    The installer performs prestop, uninstalls old RPMs, and installs the new RPMs. It performs post-installation tasks, and the configuration for the upgrade.

30. If you have network connection to the Internet, the installer checks for updates.

    If updates are discovered, you can apply them now.

31. A prompt message appears to ask if the user wants to read the summary file. You can choose y if you want to read the install summary file.