Recommended Software Levels and APAR fixes for the DB2 PureScale V9.8 product on AIX

Preventive Service Planning


Abstract

This document describes recommended software levels and APARs related to the DB2 Version 9.8 product.

Content

Recommendations for running DB2® Version 9.8 on AIX®

AIX version Recommended minimum AIX technology levels
7.1 TL01 SP1
6.1 TL06 SP6


Recommended AIX Infiniband and uDAPL APAR fixes
  • IV37441 IB INTERFACE FAILURES. INTERFACE STOP PINGING. PENDING BIT ISSUE
  • IV47374 CREATION UNCLOSED DESCRIPTORS MAY LEAD TO FAILED SOCKET
  • IV35894 UDAPL CONSUMER DOING DAT_EVD_WAIT COULD GET STUCK IN A TIMEOUT


Related Flashes
  • Upgrading SDDPCM to 2.6.3.x from earlier versions will fail device configurations if the algorithm attribute of the device is set to 'fail_over'
    Please review the following flash if you are using the Subsystem Device Path Control Module (SDDPCM) for your tiebreaker disk in a DB2 PureScale environment and you are upgrading to SDDPCM 2.6.3.x from an earlier version.

    http://www.ibm.com/support/docview.wss?&uid=ssg1S1004072

Recommended Fix Pack

Use the DB2 Version 9.8 Fix Pack 5 product. It includes:
  • fixes for APARs found in the DB2 Version 9.8 Fix Pack 4 product
  • fixes for SECURITY/HIPER/Special Attention APARs from earlier releases
  • GPFS™ 3.4.0.13
  • TSA MP 3.2.2.1

You can download a copy of DB2 Version 9.8 Fix Pack 5 from the following link:

http://www.ibm.com/support/docview.wss?uid=swg24032798


Recommended GPFS and TSA MP Levels with the DB2 Version 9.8 Fix Pack 4 product

If you use the DB2 Version 9.8 Fix Pack 4 product, use the following software levels:
  • GPFS 3.3.0.14 efix 11
    You can obtain GPFS 3.3.0.14 efix 11 from the following location:

    ftp testcase.boulder.ibm.com
    userid = anonymous
    password = email address
    cd fromibm/im
    bin
    get g330p14e11.power.tar

  • TSA MP 3.2.1.2 efix 4
    You can obtain TSA MP 3.2.1.2 efix 4 from the following location:

    ftp testcase.boulder.ibm.com
    userid = anonymous
    password = email address
    cd fromibm/im
    bin
    get SAM3212_GA_efix_4.tar.gz


Installing GPFS 3.3.0.14 efix 11 and TSA MP 3.2.1.2 efix 4 on an instance of the DB2 Version 9.8 Fix Pack 4 product

The following instructions are for a two member, two CF cluster. Adjust the instructions according to your cluster topology.

    1) As instance owner, issue the db2stop command on each host to stop the DB2 instance.

      db2 terminate
      db2 deactivate db <dbname>
      db2stop
      db2 terminate
      db2instance -list

      db2stop instance on <host-db01>
      db2stop instance on <host-db02>
      db2stop instance on <host-CF01>
      db2stop instance on <host-CF02>


    2) On one of the hosts as root, put the cluster in TSA maintenance mode.

    <pathInstalled>/bin/db2cluster -cm -enter -maintenance -all

    The following is an example of putting the cluster in TSA maintenance mode:

    root@host-db01:/opt/IBM/db2/v9.8/bin>db2cluster -cm -enter -maintenance -all
    Domain '<domain_name>' has entered maintenance mode.


    3) Enter the tar -xvf g330p14e11.power.tar command.

    Follow the install instructions in the README file provided with g330p14e11.power.tar. You can also use the topic "Updating GPFS on AIX to meet DB2 pureScale requirements" in the DB2 Version 9.8 Information Center found at the following link:
    http://pic.dhe.ibm.com/infocenter/db2luw/v9r8/topic/com.ibm.db2.luw.sd.doc/doc/t0058716.html

      IMPORTANT: The instructions in the GPFS README are missing a step. It is necessary to first delete the current GPFS efix before installing the new efix. Proceed with this step between steps 4 and 5. You can delete the current GPFS efix by using the following steps:

      Delete the currently installed GPFS efix

      1) Determine the currently installed GPFS efix.

      cd DB2DIR/install/gpfs directory
      Where DB2DIR represents the location where the DB2R copy is installed.

      db2ckgpfs -s install
      This lists the currently installed efix name.

      2) Delete currently installed efix.

      usr/sbin/emgr -r -L efixName

    4) Unzip and untar the SAM3212_GA_efix_4.tar.gz file. Go into the SAM3212_GA_efix_4 directory and run the installSAM --noliccheck command to install the new driver.

    The driver must be installed on all hosts that are part of the cluster. Run the following commands on each host to install the driver:

      root@host-db01:/> gunzip SAM3212_GA_efix_4.tar.gz
      SAM3212_GA_efix_4.tar

      root@host-db01:/> tar -xvf SAM3212_GA_efix_4.tar
      SAM3212_GA_efix_4

      root@host1:/>~/SAM3212_GA_efix_4> ls -rlt
      total 520
      drwxr-xr-x    2 root     system       256 Dec 02 2011  README
      drwxr-xr-x    6 root     system     4096 Dec 02 2011  AIX
      -rwxr-xr-x    1  root     system   45573 Dec 02 2011  uninstallSAM
      -rwxr-xr-x    1  root     system   75605 Dec 02 2011  prereqSAM
      drwxr-xr-x    2 root     system       256 Dec 02 2011  license
      drwxr-xr-x    2 root     system       256 Dec 02 2011  integration
      -rwxr-xr-x    1 root      system 129795 Dec 02 2011  installSAM
      drwxr-xr-x    2 root     system     4096 Dec 02 2011  docs
      drwxr-xr-x    6 root     system       256 Dec 02 2011  Linux


      root@host-db01:/~/SAM3212_GA_efix_4> installSAM --noliccheck
      prereqSAM: All prerequisites for the ITSAMP installation are met on operating system:  AIX 6100-06
      installSAM: No installation was performed.
      installSAM: The package version supplied for installation is already installed:  sam.core.rte 3.2.6.2 COMMITTED SA CHARM Runtime Commands
      installSAM: Applying efixes: ./AIX/AIX6/efix/packages/sam.core
      ...OK
      installSAM: The following license is installed:
      Product: IBM Tivoli System Automation for Multiplatforms 3.2
      Creation date: Wed Aug 19 00:00:01 2009
      Expiration date: Thu Dec 31 00:00:01 2037
      root@host-db01:/~/SAM3212_GA_efix_4>


      List the TSA & RSCT versions to ensure the update is successful.  Check the efix directory to ensure that there are four efixes.

      root@host-db01:/> /usr/sbin/rsct/bin/samversion
      rsa326s003a 3.2.1.2 Jun 23 2011 21:17:22 Nightly Build

      root@host-db01:/> /usr/sbin/rsct/install/bin/ctversion -b
      rhols005a 3.1.0.5 11172.17:58:03

      root@host-db01:/> cd /opt/IBM/tsamp/sam/efix;ls -rlt
      total 32
      -rwxr-xr-x    1 root     system          377 Nov  9 11:24 0004.efix
      -rwxr-xr-x    1 root     system          330 Nov  9 11:24 0003.efix
      -rwxr-xr-x    1 root     system          505 Nov  9 11:24 0002.efix
      -rwxr-xr-x    1 root     system          254 Nov  9 11:24 0001.efix


    5) Exit TSA maintenance by issuing the db2cluster -cm -exit -maintenance -all command.

    6) Start the instance on each host:
      db2start instance on <host-CF01>
      db2start instance on <host-CF02>
      db2start instance on <host-db01>
      db2start instance on <host-db02>

    7) Start the cluster by issuing the db2start command.

    8) Run the db2instance -list command to ensure that all members and CFs have started.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows
pureScale

Software version:

9.8

Operating system(s):

AIX

Software edition:

Enterprise Server

Reference #:

1605129

Modified date:

2013-09-03

Translate my page

Machine Translation

Content navigation