Perform the preparatory steps in this section if you are performing a full upgrade of the cluster. Before you upgrade, make sure that your systems meet the hardware and software requirements for this release.
To prepare to upgrade SF Oracle RAC
main.cf, types.cf, CVMTypes.cf, CFSTypes.cf, OracleTypes.cf, OracleASMTypes.cf, PrivNIC.cf, MultiPrivNIC.cf, CRSResource.cf, /etc/llttab, /etc/llthosts, /etc/gabtab, /etc/vxfentab, /etc/vxfendg, /etc/vxfenmode
For example:
# cp /etc/VRTSvcs/conf/config/main.cf \ /etc/VRTSvcs/conf/config/main.cf.save
/etc/vx/cbr/bk
.If not, a warning message is displayed.
If the applications are under VCS control:
# hagrp -offline grp_name -any
If the applications are not under VCS control:
Use native application commands to stop the application.
If the Oracle database is managed by VCS, set the AutoStart value to 0 to prevent the database service group from starting automatically when VCS starts:
# haconf -makerw # hagrp -modify oracle_group AutoStart 0 # haconf -dump -makero
If the Oracle database is not managed by VCS, change the management policy for the database to manual:
$ srvctl modify database -d db-name -y manual
# hastop -all
One way to check whether or not the configuration is valid is to check the main.cf file as follows:
# hacf -verify /etc/VRTSvcs/conf/config
However, this method can not verify whether all configurations are vaild. If SF Oracle RAC was running properly before the upgrade, the configurations are valid.
# mount |grep vxfs
# fuser -m /mount_point
# umount /mount_point
Make sure that no processes are running which make use of mounted shared file system or shared volumes.
# fuser -cu /mount_point
See Pre-upgrade tasks for migrating the SFDB repository database.
If you are running version 5.1 and later, stop the ports using the installer:
# ./installsfrac -stop