SAP Basis Tech Supports

Symptom

To install FixPakslower than FixPak 9, see
Note 940551
You want to install one of the following FixPaks for DB2 UDB for UNIX and Windows Version 8.2 (which we will refer to as DB6):
FixPak 9FixPak 10FixPak 11FixPak 12FixPak 13SAP (*)FixPak 14SAP (*)FixPak 15FixPak 16FixPak 17

(*) “Special Builds” for SAP are called FixPak xSAP.
Other terms

DB2 UDB for Unix and Windows
FixPak9, FixPak10, FixPak11, FixPak12, FixPak13SAP, FixPak14SAP, FixPak15, FixPak16, FixPak17
Solaris SUN, AIX AIX 5L, Linux HP-UX, HPIA64, RS6000,
db2udb,
SQL0443N,
CREATE INDEX,
SORT,
REORG
Reason and Prerequisites

NOTE:
==============
FixPak 13SAP and FixPak 14SAP are “Special Builds” of the relevant IBM DB2 FixPak for SAP.
If a Special Build of a FixPak version exists (see above), SAPONLYsupports this Special Build.
For more information about FixPaks supported by SAP, seeNote 101809.You must shut down all instances created on the server and all DB2 services before you install a new FixPak.Only one FixPak status can be retained, therefore all DB2 instances will have the latest status after you install the FixPak. You must carry out all the post-processing activities described below on all instances.If you operate a partitioned system with database nodes on several servers, you must import the same FixPak on all servers concerned.To migrate from V7 to V8, you should use FixPak 5b or higher. For more information, seeNote 638230.Before you install the FixPak, you must have carried out the following actions on the database server and all application servers:Shut down the SAP SystemInstall the database softwareAfter installing the software, you must update the DB2 instances. Different FixPak statuses on the DB servers involved can cause problems.Use the following commands to receive an overview of the DB components that have already been installed: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. Shutting down the SAP System and Database
II. Installing the software
III. Updating the instances
IV. -
V. Special post-processing for FixPak 9 and higher

I. Shutting down the SAP System and Database
=============================================
1. Stop the 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:a) As a DAS user, enter the following command: /das/bin/db2admin stop
–> see Section II: “Installing the software”
On HP-UX,leaving outthis step may cause the db2asrrm process to start, and can cause problems with the memory. It is possible that this problem can also occur on other platforms.3. Stop the remaining DB2 processes as follows:a) Terminate the license daemon as user ‘db2‘ with the following command:
db2licd endb) To check that all DB2 processes have been completed, enter the following command:
ps -ef | grep db2

II. Installing the software
============================
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 (AIX)
SOLARIS (Solaris)
LINUX_32 (Linux 32-bit)
LINUX26_32 (Linux 32- bit, Kernel 2.6)
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)
Only Linux:
As of FixPak 9, a distinction is made for the Linux 32-bit version as to whether kernel version 2.4 or 2.6 is used. The database software for the 2.4 kernel is on the DVD in the LINUX_32 subdirectory, the software for 2.6 kernel is in the LINUX26_32 subdirectory.
The FixPak Software for Linux IA 64 Bit does not distinguish between Kernel Versions 2.4 and 2.6. In both cases, the FixPak software is located in the LINUXIA64_64 subdirectory.
In the case of Linux for Power PC 64 Bit and Linux for AMD 64 Bit, SAP only supports Kernel Version 2.6.
Linux for Power PC 64 Bit:
Before you install FixPak9 or higher, you must install the IBM XL C/C++ runtime environment. The installation is described inNote 1092448.
All:
is used when unpacking the respective software. The directory, into which the software is installed, is divided as follows:
AIX:/usr/opt/db2_08_01
Linux, Solaris, HP: /opt/IBM/db2/V8.1
Note that the directory has changed compared to Version 7.
======================================================================
HP-UX (HPIA 64) Only – Important
If you want to install FixPak 8SAP or higher on HPIA 64 Bit, read the section “Additional remarks for V8.2 FixPak 8SAP on HPIA 64 Bit” at the end of this SAP Note.
======================================================================

1. Unpacking/making the software availablea) Log on as user ‘root’.b) Mount the CD/DVD under .c) Generate an empty temporary directory for retrieving/unpacking the software. You require approximately 200 MB (200 MB on Solaris, 110 MB on AIX and Linux) of temporary space in . You need about 30 MB in the file directory, in which the directory is located, in order to install the software there.

d) Execute the following commands for unpacking:
cd
//SAPCAR -xvf //V8FP.SAR
whereby is the FixPak number (9, 10, 11, 12,
13SAP, 14SAP, 15, 16, 17)
This unpacks the software to /FIXPAK (= ).2. Installation of the software
If, when you installFixPak 9, terminations occur during a SORT, REORG or CREATE INDEX Operation,see the instructions inNote 864555.
To carry out the installation, change to the temporary directory specified above and start the installation using the following commands:
cd (= /FIXPAK)
./installFixPak

For AIX only:
installFixPak confirms all updated filesets. If you do not want this confirmation, execute the installFixPak command with the “-a” option as follows:
./installFixPak -a
“-a” stands for “apply” instead of “commit”

III. Updating the instances
==================================
1. To update and restart the Adminserver process, enter the following command on the DB server as user ‘root’:
/instance/daslist
This provides the Administration Server User , with which
you can execute the following command:
/instance/dasupdt 2. To update all DB2 instances, enter the following command for each instance as user ‘root’:
/instance/db2iupdt db2

IV.-
=======================================================================

V. Special Post-Processingas ofFixPak9
====================================================
As of FixPak 9, you must parameterize registry variables and other parameters by running a db6_update_db.sh script.

FixPak9 only:

Do not use the script delivered in the DVD, as the contents of this have since changed. Instead of this, download the db6_update_db.SAR attachment to this note, and unpack it using the SAPCAR program or alternatively, download the db6_update_db.ZIP attachment and unpack it using the “unzip” command.

As of FixPak9:
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.

Start the script as user db2 from the directory where you unpacked it, using the following command:

./db6_update_db.sh -d
This writes the parameter settings into a db6_update_db_out.sh output script. Check the settings in this script and adjust it if necessary. Use the following command to start the script.

./db6_update_db_out.sh > db6_update_db_out.sh.log
FixPak10 only:
To avoid the error SQL0443N occurring when you execute SAP programs, see the instructions inNote 879582.

Procedure on application servers:
On application servers, execute the following command as user db2:
“db2 list db directory”
to trigger a DB directory migration.

The installation is now complete and you can restart your SAP System.

HPIA 64-bit: Additional remarks for V8.2 FixPak 9 and higher
====================================================================

FixPak 9 cannot be installed directly on FixPak 7b and lower. To migrate to FixPak 9 and so on in spite of this, proceed as follows:

Uninstall the DB2 software.InstallFixPak 9 Full Install(to do this, seeNote 863620).Install the FixPak you want (above 9) as described in this note.

Repairs in the Code

Attention: Do not enter source code here! Enter source code under
“Corrections” -> “Correction instructions”.
Lines entered here are deleted automatically when saving!