SAP Basis Tech Supports

Symptom

This note relates to installing FixPaks for DB2 V9.1 (UNIX and Linux).

Other terms

DB2 V9.1 for Linux, UNIX and Windows
Fix Pack, FixPak, FixPack, DB6, UDB, LUW
Solaris SUN, AIX AIX 5L, Linux HP-UX, HPIA64, RS6000
Reason and Prerequisites

For more information about FixPaks supported by SAP, seeNote 101809.

Before the installation of a new fix pack, shut down all instances that were created on the copy of the DB2 software and all relevant DB2 services.You are use a partitioned system with database nodes on several servers.If they are locally installed software copies, install the same fix pack on all affected servers.If all servers access a single centrally installed DB2 software instance, then you only need to update the DB2 software once.
Newer SAP installation tools install the DB2 software in a subdirectory of the instance directory, so that it is available to all servers centrally.DB2 V9.1 is always a full install for Windows and UNIX. You can use the images toInstall a new copy of the DB2 softwareUpdate an existing DB2 V9.1 instanceYou can display an overview of all installed DB2 V9.1 copies using the DB2 command “/usr/local/bin/db2ls”. You can display older DB2 installations using the following commands:AIX:lslpp -L all | grep -i db2Solaris:pkginfo | grep -i db2Linux:rpm -q -a | grep -i db2HP-UX:swlist | grep -i db2

Solution

Procedure:
===============

I. Downloading the software from SAP Service Marketplace (SMP) (optional)
II. Stopping the SAP System and the database
III. Updating the instances
IV. Postprocessing (parameterization, package rebind)
V. Updating the global directory

I. Downloading the software from SMP (optional)
=============================================
In addition, two directories are used that differ from one another in terms of their individual UNIX variants. Replace the directory with one of the following:
AIX_64 (AIX)
SUNOS_64 (Solaris)
LINUX_32 (Linux 32-bit)
LINUXIA64_64 (Linux IA 64-bit)
LINUXPPC64_64 (Linux Power PC 64-bit)
LINUXX86_64 (Linux AMD 64-bit)
HP11_64 (HP-UX)
HPIA64 (HP IA 64-bit)
is used for the path name of the respective software. represents the directory in which the software is installed.
You can install the software directly from the DB2 software DVD delivered by SAP, or download it from SAP Service Marketplace, unpack it, and then install it from a local directory.
If you download the software from SAP Service Marketplace, you must perform the following steps before the installation:

1. In SAP Service Marketplace (SMP), go to “Software Download”.2. Choose “Download”.3. Choose “Database Patches (from other vendors)”.4. Choose “DB2 for Unix and Windows”.5. Choose “DB2 Version V9.1 software download”.6. Choose “Installation”.7. Choose “DB2 UDB”.8. Download the software relevant to your operating system into one of the following paths labeled with .9. Unpack the file xxxxxxxx_y.zip (xxxxxxxx is the material number) into the directory using the command:
unzip xxxxxxxx_y.zip

When you load the images for UNIX or Linux operating systems from SAP Service Marketplace, the execute permissions for the respective files disappear when you execute the “unzip” command. You can then no longer execute scripts.
As a preliminary workaround we recommend that you set the execute permissions’ manually for all files. To do this, go to the directory
and execute the following command as user ‘root’
chmod -R 755 .

II. Stopping the SAP System and the database
=====================================
A single DB2 copy can drive many DB2 instances. Therefore, you must stop all SAP Systems and DB2 instances that are affected before you update a DB2 copy. To display a list of all DB2 instances that belong to a DB2 copy, execute the command “db2ilist” as user db2.
You can defer stopping your SAP System until you have switched your existing DB2 instance to the new DB2 software copy, if you install a new copy of the DB2 software.

1. Shut down SAP system and the SAP database instance as follows:a) As user ‘adm’, enter the following command:
stopsapb) Stop the SAP OS Collector with the following command:
saposcol -k2. Stop the admin instance (if it exists) as follows: As a DAS user, enter the following command:
/das/bin/db2admin stop
On HP-UX,leaving outthis step may cause the db2asrrm process to start and storage space problems to occur. It is possible that this problem can also occur on other platforms.

III. Updating the instances
================================
You can import a FixPak by installing a new DB2 copy or by updating the installed software. Both are permitted for all SAP Releases.
Update using a new installation:
Install the new software copy using db2setup or db2_install as user “root”. We recommend that you install the copy in a subdirectory of the home directory db2 using “db2setup”, for example, ~db2/db2_v9_fp1.
Then execute program “db2iupdt” to switch your existing DB2 instance from the current software copy to the new DB2 software copy. If you have not yet stopped your SAP System and DB2 instances, you must do so before executing “db2iupdt”.
In our example, “db2iupdt” is called as follows:
~db2/db2_v9_fp1/instance/db2iupdt db2
Caution: The new copy does not have a DB2 license. Therefore, you must install the DB2 license as user db2 using the command “db2licm -a”, as described in Note 816773 (the license is available on SAP Service Marketplace at http://service.sap.com/swcenter-3pmain).
After a successful test, you can uninstall the old, unused DB2 copy at any time using the following command:

/install/db2_deinstall
Updating an existing software installation:
Call installFixPack from the DVD as user “root”. You can either specify the desired installation path directly (./installFixPack -b ), or call installFixPack without specifying a path. In this case, installFixPack asks you for the path.
Then call the program “db2iupdt” to update the instance. Therefore, in our example:
/instance/db2iupdt db2
Customers who use a DAS instance, must update this as well.
The relevant command is:
/instance/dasupdt

IV. Postprocessing (parameterization, package rebind)
======================================================
You must start the database before postprocessing.
Finally, use the script db6_update_db.sh to perform the parameterization of registry variables and other parameters, and to perform a package rebind. This script is available in the file db6_update_db.SAR that is attached to this note.
Important: If you use an HADR database, you must ensure that the script is run on the PRIMARY HADR NODE only. See Note 1289413 for further information.

To do this, proceed as follows:

1. Download the attachment db6_update_db.SAR to a temporary directory and unpack it using the program SAPCAR.2. Start the script from this directory with the following command:
./db6_update_db.sh -d
This writes the parameter settings into an output script db6_update_db_out.sh.3. Check the settings in this script and adjust it if necessary.4. Use the following command to start the script.

./db6_update_db_out.sh > db6_update_db_out.log

5. Check the entries in the file “db6_update_db_out.log” for any error messages, and correct any errors that you may find.

If the following error occurs the next time you execute the script or a connect to the database:
SQL1013N The database alias name or database name “” could not be found,
execute adb2_killcommand to clean out any shared memory segments that may remain.

V. Updating the global directory
======================================================
You must perform the update only for for SAP versions that have a CLI driver installed. SAP Basis Release 7.10 always contains a CLI driver. In Basis Release 7.00, a CLI driver is used only if the following directory exists:
/usr/sap//SYS/global/db6//db6_clidriver/

The database software is updated automatically during the installation of a FixPak. You must execute the script ‘db6_update_client.sh’ so the DB2 driver or JDBC driver is also updated in the global directory. This script is available in the file db6_update_client.SAR that is attached to this note. Proceed as follows:
1. Log on to the database host as user adm.2. Mount the DB2 9 LUW CLI/JDBC driver DVD.3. Copy the entire content of the DVD to a temporary directory .4. Download the attachment db6_update_client.SAR that is included in this note to the subdirectory /CLIENT and unpack it there using the program SAPCAR.5. Go to the subdirectory /CLIENT.6. Start the script db6_update_client.sh from this directory using the following command:

./db6_update_client.sh -u
The script ‘db6_update_client.sh’ updates the DB2 CLI driver and the JDBC driver for Java in the directory global/db6 for all available operating systems.
The installation is now complete and you can now restart your SAP systems.