3.7.0 HP StorageWorks HP Scalable NAS File Serving Software upgrade guide HP Scalable NAS for Linux (AG513-96005, October 2009)

Also save the following MxDB-Oracle-HiAv information:
• Record the primary and backup nodes for the Virtual Oracle Service associated
with each database. Run the following command for each database:
mxdb -d <database> –Q
• Preserve any custom MxDB-Oracle-HiAv files. For example, MxDB-Oracle-HiAv
supports the optional configuration file mxdbha_<DBNAME>.conf, where <DB-
NAME> is the name of the service monitor associated with the Virtual Oracle
Service. If used, the file is located in $ORACLE_HOME/dbs.
• Save custom startup scripts in /opt/hpcfs/mxdb_oracle_ha/.
You should have access to the old $ORACLE_HOME from an upgraded node;
however, you will lose anything local, such as oraIventory files (if local), the
Oracle UNIX account directory, /etc/oratab, and so forth, unless you take steps
to preserve what you need.
Uninstall MxODM
The PolyServe MxODM product has been discontinued in the 3.7.0 release. Recent
Linux changes have made this product unnecessary. This product should be uninstalled
from the cluster before upgrading to HP Scalable NAS version 3.7.0. You should be
aware of the following before uninstalling MxODM:
• Be sure that there are no Oracle Instances running on any nodes in the cluster.
• The package must be uninstalled from the node where you installed it.
• Ensure that the PSFS filesystems used by Oracle are mounted.
To uninstall MxODM, run the following command as user root:
# rpm -e odm-3.5.3
This command removes all files associated with MxODM and restores Oracle to its
configuration before MxODM was installed. Be sure to consider the resulting changes
to the performance characteristics during your upgrade testing.
Considerations for Oracle
• The Oracle database must be running version 10.2.0.4.
• A shared Oracle home must be in place on a PSFS filesystem, beginning at least
at the Oracle base path location (for example, /u01/app/oracle).
• The 3.7.0 upgrade also requires an upgrade of the operating system. You will
likely want to relink the Oracle binaries after upgrading the operating system;
however, the timing for relinking has important ramifications for cluster high
Upgrade Matrix Server and MxDB-Oracle-HiAv34