Serviceguard Extension for RAC Version A.11.
Legal Notices © Copyright 2009 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents 1 Serviceguard Extension for RAC Version A.11.19 Release Notes.......................................................7 Announcements....................................................................................................................7 SGeRAC Version and Components: Product Numbers .................................................7 Dependencies and Limitations........................................................................................
Steps for a Non-Rolling Upgrade Using DRD.........................................................25 Removing SGeRAC.......................................................................................................26 Removing Serviceguard Extension for RAC Without Removing Serviceguard...........27 Troubleshooting Tips ....................................................................................................27 Patches and Fixes in this Version..................................................
List of Tables 1-1 1-2 HP-UX 11i v2 Patches for SNOR.................................................................................28 SGeRAC A.11.19 Fixes................................................................................................
1 Serviceguard Extension for RAC Version A.11.19 Release Notes Announcements SGeRAC (formerly known as Serviceguard OPS Edition or MC/LockManager) is a specialized facility that provides the framework for using Oracle Real Application Cluster (RAC) software on HP 9000 and HP Integrity servers. This section announces the most important features and limitations of Serviceguard Extension for RAC (SGeRAC) A.11.19. For more information, see “What’s in this Version” (page 11).
Dependencies and Limitations NOTE: For the most complete and up-to-date list of support and compatibility requirements, see the Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility and Feature Matrix. Serviceguard and related documentation is available free at http://docs.hp.com -> High Availability -> Serviceguard • • • • There are operating-system dependencies; see “Operating-System Dependencies” (page 8) and“Announcements for HP-UX 11i v3”. Serviceguard version A.11.
NOTE: All nodes in a given cluster must be running the same version of HP-UX. See “Mixed Clusters not Supported” (page 9). SGeRAC can be installed on top of the HP-UX 11i v2 and 11i v3 Mission Critical Operating Environment (MCOE), and the 11i v3 High Availability Operating Environment (HAOE) or Data Center Operating Environment (DCOE). It is not necessary to uninstall Serviceguard filesets before installing SGeRAC. NOTE: If the version of Serviceguard in the MCOE, HAOE, or DCOE is not A.11.
Agile addressing is the default on new 11i v3 installations, but the I/O subsystem still recognizes pre-11i v3 device files, which as of 11i v3 are referred to as legacy device files. Device files using the new nomenclature are called persistent device files. When you upgrade to HP-UX 11i v3, a set of new, persistent device files is created, but the existing, legacy device files are left intact and by default will continue to be used by HP-UX and Serviceguard.
• • • the Logical Volume Management volume of the HP-UX System Administrator’s Guide (in the 11i v3 -> System Administration collection) the HP-UX 11i v3 Installation and Update Guide (in the 11i v3 -> Installing and Updating collection) the following white papers: — The Next Generation Mass Storage Stack (under Network and Systems Management -> Storage Area Management) — Migrating from HP-UX 11i v2 to HP-UX 11i v3 — HP-UX 11i v3 Native Multi-Pathing for Mass Storage — LVM Migration from Legacy to Agile Na
• • • • • • • • • • • • • GMS authorization Support for DRD; see “Upgrade Using DRD” (page 16). Support for multi-node online reconfiguration (MORE) of LVM volume groups; see “Support for Multi-Node Online Configuration (MORE) —LVM Version 2.1 Volume Groups Only” (page 18). Support for Logical Volume Manager Version 2.0 Support for Veritas CFS and CVM Versions 5.0 and 5.0.
NOTE: You are not required to move to LVM 2.0 volume groups and everything will work as before if you do nothing. If you do use LVM 2.0 volume groups, you can still manage them with the same commands as before, although you may have to make minor changes to any scripts you use that parse the output of lvdisplay, vgdisplay, pvdisplay or vgscan, as the output of these commands has changed slightly. In addition, new options are available for some commands. For more information, see the white paper LVM 2.
In addition, SGeRAC A.11.19 on HP-UX 11i v3 supports Veritas VxVM, CVM and CFS 5.0.1. For more information, see the HP-UX 11i v2 or 11i v3 version of the HP Serviceguard Storage Management Suite Version A.02.01 Release Notes (for Veritas version 5.0) and the HP Serviceguard Storage Management Suite Version A.03.00 Release Notes (for Veritas version 5.0.1) at http://docs.hp.com -> High Availability -> HP Serviceguard Storage Management Suite.
Support for the SGeRAC Toolkit The SGeRAC Toolkit provides documentation and scripts to simplify the integration of SGeRAC and the Oracle 10gR2/11gR1 RAC stack. It also manages the dependency between Oracle Clusterware and Oracle RAC instances with a full range of storage management options (CFS, SLVM, CVM, ASM over SLVM). You can download the SGeRAC Toolkit free from http://software.hp.com —> High availability.
NOTE: Starting with Oracle 10g, Oracle Clusterware processes register with cmgmsd while Oracle server processes register with Oracle Clusterware. The maximum number of Oracle server processes supported is determined by Oracle Clusterware. The maximum number of processes registered by Oracle Clusterware should not exceed the maximum supported by cmgmsd. Upgrade Using DRD DRD stands for Dynamic Root Disk.
If, after reading and understanding the restrictions, you decide to perform a non-rolling upgrade using DRD, follow the instructions under “Performing a Non-Rolling Upgrade Using DRD” (page 25). Restrictions for DRD Upgrades • • Upgrade using DRD is supported only on HP-UX 11i v3. As of the date of these release notes, the only paths that are supported for DRD upgrade are: — from Serviceguard/SGeRAC version A.11.18 with patch PHSS_37602 (or a later cumulative patch) to A.11.19 or an A.11.
IMPORTANT: If the install depot is on tape (or is a single file) you must copy it onto the clone disk or an upgrade server before running swinstall or update-ux to upgrade the clone.
NOTE: MORE is available only for LVM Version 2.1 volume groups. For earlier versions, you can still use the Single-Node Online Reconfiguration (SNOR) method. This method works on all LVM versions, but it requires the deactivation of the volume group on all but one node in a cluster; see the white paper SLVM Single-Node Online Volume Re-configuration, which you can find on docs.hp.com under HP-UX 11i v3 Operating Environments -> LVM Volume Manager -> White Papers.
Compatibility Information and Installation Read this entire document and any other Release Notes or READMEs you may have before you begin an installation. Serviceguard Extension for RAC Compatibility with HP-UX and Oracle Releases For the most up-to-date compatibility information, see the Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility and Feature Matrix at http://docs.hp.com -> High Availability -> Serviceguard -> Support Matrixes. Port Requirements Refer to the Serviceguard Version A.
NOTE: If you are adding Serviceguard Extension for RAC to an existing Serviceguard cluster, there are additional steps. See“Adding Serviceguard Extension for RAC to an Existing Cluster”.
Performing a Rolling Upgrade Using DRD CAUTION: All the limitations listed in Appendix A of Using Serviceguard Extension for RAC also apply to a rolling upgrade with DRD. In addition, there are special conditions that apply to upgrading a system to Serviceguard A.11.19. You should read the entire section on “Rolling Software Upgrades” in Appendix A of Using Serviceguard Extension for RAC, and the corresponding section of Appendix D in the latest version of Managing Serviceguard, before you proceed.
Before You Start IMPORTANT: If you need to upgrade Oracle software, a non-rolling upgrade may be required; consult the Oracle documentation. • • Make sure you plan sufficient system capacity to allow moving the packages from node to node during the process without an unacceptable loss of performance. Make sure you have read and understood the “Restrictions for DRD Upgrades” (page 17), and that your cluster meets the prerequisites. If you are upgrading from a qualifying A.11.
11. Move the packages back to the upgraded node. 12. Verify that the applications are functioning properly. • If the applications do not function properly and this is not the last node to be upgraded, you can revert to the previous release on this node. This is called hot recovery, and it will allow you to keep the node up and running in the cluster while you upgrade the other nodes, though you will still need to investigate and solve the problems on this node before the cluster upgrade can complete.
Performing a Non-Rolling Upgrade Using DRD Limitations of Non-Rolling Upgrades using DRD CAUTION: Stricter limitations apply to an upgrade to A.11.19; do not proceed with an upgrade to A.11.19 until you have read and understood the “Special Considerations for Upgrade to Serviceguard A.11.19” in Appendix D of the latest version of Managing Serviceguard.
8. If necessary, upgrade all the nodes in the cluster to the new Oracle (RAC, CRS, Clusterware, OPS) release. 9. Restart Oracle (RAC, CRS, Clusterware, OPS) on all nodes in the cluster and configure the Serviceguard/SGeRAC packages and Oracle as needed. 10. Verify that the cluster is healthy, the packages can run, and applications are functioning properly.
Removing Serviceguard Extension for RAC Without Removing Serviceguard If you want to remove SGeRAC and return the cluster to use as a Serviceguard cluster, use the following steps: 1. Halt the cluster. 2. Use swremove to remove SGeRAC from each node. 3. Reboot each node. 4. Edit the cluster configuration ASCII file to remove any OPS_VOLUME_GROUP entries, then run the cmapplyconf command. 5. Restart the cluster.
NOTE: Patches can be superseded or withdrawn at any time. Be sure to check the status of any patch before downloading it. Shared LVM Online Reconfiguration (SNOR) Patches Table 1-1 list patches that are required to support the Shared LVM Online Reconfiguration (SNOR) feature on HP-UX 11i v2. Table 1-1 HP-UX 11i v2 Patches for SNOR Patch Post Date Description PHCO_33309 20050927 s700_800 11.23 LVM Commands Patch PHKL_33312 20050927 s700_800 11.
Table 1-2 SGeRAC A.11.19 Fixes (continued) QXCR Number QXCR Title QXCR1000583780 The toolkit README indicates the need to modify the AUTO_START profile attribute during configuration to prevent the automatic start of RAC instance and Oracle Service as part of Oracle Clusterware startup. QXCR1000586962 The toolkit README does not describe how user defined Oracle Services are handled by the toolkit.
releases are supported for an extended period of time, determined by HP. Patches will be made available within the extended support time frame even though a newer version of the product is available. Feature Release A feature release contains new product features. Feature releases are for customers who desire to use the latest features of the product. In general, feature releases will be supported until a newer version becomes available.
