Symantec logo

< Previous  | TOC | Index | Next  >  

Upgrading from 4.0 MP3 to SF 5.0 Oracle RAC

The procedure in the following sections assumes that you have a working SF Oracle RAC cluster at 4.0MP3.

Upgrading consists of:

Upgrading AIX to 5300-04-04

SF Oracle RAC for 5.0 requires that the AIX operating system be at level 5300-04-04. If you are using an earlier version of AIX, upgrade now.

Pre-Upgrade tasks: stopping Oracle and cluster resources
  1. Log in as root user to one of the nodes in the cluster and make a backup of the VCS configuration file, main.cf.

    # cp /etc/VRTSvcs/conf/config/main.cf \ /etc/VRTSvcs/conf/config/main.cf.40mp3

  2. For Oracle9i:
    1. Stop gsd. On each node, log in as oracle user and enter:

      $ $ORACLE_HOME/bin/gsdctl stop

    2. Offline all VCS service groups that contain resources for managing Oracle listener process or the database instances. As root user, enter:

      # hagrp -offline <group_name> -any

  3. For Oracle 10g:
    1. Stop all resources configured under CRS control. As oracle user, enter:

      $ srvctl stop nodeapps -n <sys>

      Repeat the above command for each node in the cluster. Note that if the Oracle listener or database instances are managed by CRS, they are taken offline by the "srvctl" command shown above.

    2. If the Oracle listener or database instances are under VCS control, you must take the corresponding VCS service groups offline. As root user, enter:

      # hagrp -offline <group_name> -any

    3. Stop CRS.
      • If CRS is not controlled by VCS, log in as root user on each system in the cluster and enter:

        # /etc/init.crs stop

      • If CRS is controlled by VCS, log in as root user on any system in the cluster and enter:

        # hares -offline <cssd_res> -sys <sys>

        Repeat this command for each system in the cluster.

  4. Take offline all other VCS groups that depend on VxFS file systems or VxVM disk groups, whether local or CFS.
  5. Stop all applications that use VxFS or VxVM but that are not under VCS control. Unmount the corresponding file systems and deport the corresponding disk groups.
  6. Make sure VCS is running on all systems in the cluster.
  7. Set the VCS resource attribute, AutoStart, to 0 for all VCS resources that manage CRS or Oracle database instances. From any system in the cluster, enter:

    # haconf -makerw

    # hares -modify <cssd_res> AutoStart 0

    # hares -modify <oracle_res> AutoStart 0

    # haconf -dump -makero

  8. Comment out the CRS-specific lines in the /etc/inittab file to prevent the system from starting the CRS daemons during system startup. On each system, prefix the CRS lines with a colon (":") to comment them out. For example:

    :h1:2:respawn:/etc/init/evmd run >/dev/null 2>&1 </dev/null

    :h2:2:respawn:/etc/init/cssd fatal >/dev/null 2>&1 </dev/null

    :h3:2:respawn:/etc/init.crsd run >/dev/null 2>&1 </dev/null

  9. On each system, invoke "slibclean" to unload all unused modules:

    # /usr/sbin/slibclean

Invoking installsfrac to upgrade to SF Oracle 5.0
  1. Mount the software disc:

    # mkdir /cdrom

    # mount -V cdrfs -o ro /dev/cd0 /cdrom

  2. Start the SF Oracle RAC installer utility. Include the -rsh option if you have not set up SSH:

    # cd /cdrom/dvd1/sfrac

    # ./installsfrac

  3. The installer displays information about the cluster, the systems, and the service groups, and prompts you about upgrading:

    ...

    Do you want to upgrade to version 5.0 on these systems using the current configuration? [y,n,q,?] (y)

    Press Enter.

  4. The installer verifies rsh accessibility and the existing licenses.

    ...

    Do you want to enter another license key for galaxy? [y,n,q](n)

  5. If necessary, answer "y" and enter the license keys at the prompt.
  6. The installer checks existing AIX operating system filesets and reports any missing recommended filesets, prompting you to add them before continuing.
  7. Install any required or recommended filesets for SF 5.0 Oracle RAC and answer "y" at the prompt to continue.
  8. The installer displays the list of all filesets included with SF 5.0 Oracle RAC and proceeds to stop SF Oracle RAC processes on each system in the cluster. The installer prompts you to confirm whether to proceed with the upgrade.

    All SFRAC processes that are currently running must be stopped.

Are you sure you want to upgade SFRAC [y,n,q](y)

Answer "y" to continue with the upgrade.

  1. As the installer proceeds, it:
    1. Takes the cvm group and other dependent groups offline.
    2. Updates GAB and VCS configurations as needed for SF 5.0 Oracle RAC.
  2. When the installer is ready to stop the cluster to make updates to the configuration, it prompts for your OK. At the prompt, press Enter.

    ...

    Are you ready to begin the Veritas Storage Foundation for Oracle RAC upgrade at this time? [y,n,q](y)

  3. The installer backs up the configuration files, freezes VCS service groups, and uninstalls the 4.0 SF Oracle RAC filesets.

    Backing up types.cf and main.cf .................Done

    Freezing group cvm ..............................Done

    ...

    Stopping SFRAC: 100%

    Shutdown completed successfully on all systems

    Uninstalling SFRAC: 100%

    Uninstall completed successfully on all systems

    Installing SFRAC: 100%

    Installation completed successfully on all systems

  4. The installer displays where logs for the upgrade can be found. It then indicates you must reboot each system.
  5. Reboot each system in the cluster.

    # /usr/sbin/shutdown -r

Post-upgrade tasks for SF 5.0 Oracle RAC

When the systems come back up after the rebooting, GAB ports, a, b, d, h, and o are configured. The VCS service groups are frozen.

  1. Invoke installsfrac once again, this time to enter configuration information. Include the -rsh option if you have not set up SSH:

    # cd /opt/VRTS/install

    # ./installsfrac -configure

  2. Enter the system names when prompted:

    Enter the system names separated by spaces on which to configure SFRAC: galaxy nebula

  3. The installer now verifies rsh accessibility between the systems and prompts you whether to use the same VCS/GAB/LLT configuration. Answer "y."

    Are you sure you want to reuse configuration of SFRAC 4.0.3.0? [y,n,q] (y)

  4. The installer now stops all SF Oracle RAC processes.

    Stopping SFRAC processes. Please wait...

    SFRAC processes are stopped

    Press [Return] to continue:

  5. The installer next prompts you to change permissions to allow the current oracle user and group to access Veritas Storage Foundation for Oracle RAC tools. The questions are asked for each system in the cluster.

    ...

    The Veritas Storage Foundation for Oracle RAC utility for database administration requires permission changes to allow database administrators (DBAs) access to the tools. The default settings at installation time for the /opt/VRTSdbed directory allows only the root user access to the

    directory. You need to change permissions to allow a DBA or a group of DBAs access to the Veritas Storage Foundation for Oracle RAC tools

    Do you want to add single user access on galaxy [y,n,q,?] (Y)

    Answer "y"

    Enter login account name for DBA user: oracle

    Enter group name for DBA users: dba

  6. For each system, the installer prompts you to verify the fully qualified hostnames. Answer "y" to confirm. For example:

    ...

    Is the fully qualified hostname of system "galaxy" =

    "galaxy.example.com"? [y,n,q,b,?] (y) y

    Querying fully qualified domain name of host "galaxy" .. ok

    Is the fully qualified hostname of system "nebula" =

    "nebula.example.com"? [y,n,q,b] (y) y

  7. When you are prompted about enabling Storage Foundation Management Sever, answer "n".

    ...

    Enable Storage Foundation Management Server Management? [y,n,q,b] (y) n

  8. The installer now configures VEA, gridnode, actionagent, and Storageagent for all nodes in the cluster.

    Configuring VEA in STANDALONE mode on "galaxy" ..... ok

    Configuring gridnode on "galaxy" ................... ok

    Registering gridnode on "galaxy" ................... ok

    Configuring actionagent on "galaxy" ................ ok

    Registering actionagent on "galaxy" ................ ok

    Stopping StorageAgent on "galaxy" .................. ok

    Registering StorageAgent on "galaxy" ............... ok

    ....

  9. When you are prompted to start SF Oracle RAC processes, accept the default "y" by pressing Enter.

    Do you want to start Veritas Storage Foundation for Oracle RAC processes now? [y,n,q,b] (y)

  10. After starting the SF Oracle RAC processes, the installer exits.

Setting default disk group to on galaxy ........... Done

Unfreezing cvm ..................................... Done

Unfreezing oradb1_grp .............................. Done

Onlining ClusterService Group on galaxy ............ Done

Onlining cvm Group on galaxy ....................... Done

Onlining cvm Group on nebula ....................... Done

Setting default disk group to on nebula ........... Done

  1. Check the output of the gabconfig -a command to ensure that ports a, b, d, f, h, o, v, and w are configured.
  2. All VCS resources, except the ones for which AutoStart is set to 0, should now be online.

    See Pre-Upgrade tasks: stopping Oracle and cluster resources for setting the AutoStart attribute for resources to 0.

  3. Import any VxVM disk groups not under VCS control. Also mount any VxFS file systems not under VCS control.
  4. If your systems run Oracle 10g, ensure that the file system containing CRS binaries is online on all systems in the cluster. Also, the OCR and Vote disks must be accessible from all nodes in the cluster.
  5. Verify the file system containing Oracle binaries is mounted and accessible on all systems in the cluster. Also ensure that the file system containing the Oracle databases is mounted.
  6. Ensure that CRS (for Oracle 10g) and the Oracle database instances are not running.
  7. If your systems run Oracle9i, skip to step 20. If your systems run Oracle 10g, perform the following setup steps on each system in the cluster before bringing up CRS:
    1. Unload any unused modules:

      # /usr/sbin/slibclean

    2. Create the 32-bit SKGXN archive library under /opt/VRTSvcs/rac/lib:

      # cd /opt/VRTSvcs/rac/lib

      # rm libskgxn2.a

      # cp libvcsmm.so shr_skgxn2.o

      # ar -X32 -qv libskgxn2.a shr_skgxn2.o

      # rm shr_skgnx2.o

    3. Create the 64-bit SKGXN archive library under /opt/VRTSvcs/rac/lib64

      # cd /opt/VRTSvcs/rac/lib64

      # rm libskgxn2.a

      # cp libvcsmm.so shr_skgxn2.o

      # ar -X64 -qv libskgxn2.a shr_skgxn2.o

      # rm shr_skgxn2.o

  8. If you are running 10gR1, copy these 5.0 SKGXN libraries to $CRS_HOME

    # cp /opt/VRTSvcs/rac/lib/libskgxn2.a \ $CRS_HOME/lib32/libskgxn2.a

    # cp /opt/VRTSvcs/rac/lib/libskgxn2.a \ $CRS_HOME/lib32/libskgxnr.a

    # cp /opt/VRTSvcs/rac/lib64/libskgxn2.a \

    $CRS_HOME/lib/libskgxn2.a

    # cp /opt/VRTSvcs/rac/lib64/libskgxn2.a \ $CRS_HOME/lib/libskgxnr.a

    Run the commands on each system in the cluster.

  9. If you're running 10gR2, perform the following commands on each system in the cluster.
    1. Remove the following files from under /opt/ORCLcluster:

      # rm /opt/ORCLcluster/lib/libskgxn2.a

      # rm /opt/ORCLcluster/lib/libskgxn2.so

      # rm /opt/ORCLcluster/lib32/libskgxn2.a

      # rm /opt/ORCLcluster/lib32/libskgxn2.so

    2. Copy these SF 5.0 Oracle RAC SKGXN libraries to /opt/ORCLcluster.

      # cp /opt/VRTSvcs/rac/lib/libskgxn2.a \

      /opt/ORCLcluster/lib32/libskgxn2.a

      # cp /opt/VRTSvcs/rac/lib/libvcsmm.so \

      /opt/ORCLcluster/lib32/libskgxn2.so

      # cp /opt/VRTSvcs/rac/lib64/libskgxn2.a \

      opt/ORCLcluster/lib/libskgxn2.a

      # cp /opt/VRTSvcs/rac/lib64/libvcsmm.so \

      /opt/ORCLcluster/lib/libskgxn2.so

      Run the commands on each system in the cluster.

    3. Copy the SF Oracle RAC SKGXP library to /opt/ORCLcluster:

      # cd /opt/ORCLcluster/lib32

      # cp /opt/VRTSvcs/rac/lib/libskgxp10_ver25_32.so .

      # cp /opt/VRTSvcs/rac/lib/libskgxp10_ver25_32.a .

      # cd /opt/ORCLcluster/lib

      # cp /opt/VRTSvcs/rac/lib/libskgxp10_ver25_64.so .

      # cp /opt/VRTSvcs/rac/lib/libskgxp10_ver25_64.a .

    4. Copy the clsinfo script to /opt/ORCLcluster.

      # cd /opt/ORCLcluster

      # mkdir bin

      # cd bin

      # cp /opt/VRTSvcs/rac/bin/scripts/clsinfo .

  10. Next, relink Oracle. Invoke installsfrac, enter the system names, navigate to the "Install and Relink Oracle" menu, and select the appropriate Oracle version:

    1) Oracle 9iR2

    2) Oracle 10gR1

    3) Oracle 10gR2\

    Select an option [1-3,2] 3

  11. On the subsequent screens, enter the DISPLAY, Oracle User, Oracle Group, location of ORACLE_BASE, location of CRS_HOME, location of ORACLE_HOME, and the Oracle Patch level currently installed on the systems:

    Enter Oracle UNIX user name: [b] (oracle) oracle

    Enter Oracle UNIX group name: [b] (oinstall) oinstall

    Enter Oracle base directory: [b] /app/oracle

    Enter absolute path of CRS home directory: [b] /app/crshome

    Enter absolute path of Database Home directory: [b]

    /app/loracle/orahome

    Enter Oracle Patch level for 10.2: [b] (0.1)

  12. Confirm your responses in the verification screen. The Installer now copies the 5.0 SF Oracle RAC libraries to ORACLE_HOME and relinks Oracle.

    Oracle environment information verification

    Oracle Unix User: oracle

    Oracle Unix Group: oinstall

    Oracle Clusterware (CRS) Home: /app/oracle/orahome

    Oracle Release: 10.2

    Oracle Patch Level: 0.1

    Oracle Base: /app/oracle

    Oracle Home: /app/oracle/orahome

    Is this informatin correct: [y,n,q] (y)

    Verifying binaries in /app/oracle/orahome on galaxy ...ok

    Verifying binaries in /app/oracle/orahome on nebula ...ok

    Copying SFRAC libskgxn on galaxy ......................ok

    Copying SFRAC libskgxn on nebula ......................ok

    Copying SFRAC ODM library on galaxy ...................ok

    Copying SFRAC ODM library on nebula ...................ok

    Copying SFRAC libskgxp on galaxy ......................ok

    Copying SFRAC libskgxp on nebula ......................ok

    Relinking Oracle on galaxy ............................ok

    Relinking Oracle on nebula ............................ok

    Oracle Relinking is now complete.

    After relinking is complete, enter "q" to quit the installer.

  13. As root user, removing the prefix ":" to uncomment the CRS-specific lines in the /etc/inittab file.
  14. Start the CRS daemons.
    1. If CRS is not configured under VCS control, log in as root user on each system in the cluster and enter:

      # /etc/init.crs start

    2. If Oracle instances are configured under VCS control, log in as root user and enter the following command for each system in the cluster:

      # hares -online <ora_res> -sys <sys>

  15. Verify that the Oracle instances are up and running.
  16. Reset the VCS resource attribute AutoStart to 1 for all resources that manage Oracle CRS and database instances. As root user on any system in the cluster, enter:

    # haconf -makerw

    # hares -modify <cssd_res. AutoStart 1

    # hares -modify <oracle_res> AutoStart 1

    # haconf -dump -makero


 ^ Return to Top

< Previous  | TOC | Index | Next  >