(UNIX + Linux)
Note Language: English Version: 15 Validity: Valid Since 26.09.2011
Summary
SymptomThis note concerns the installation of fix packs for DB2 V9.7 (UNIX and Linux).
Other terms
DB2 V9.7 for Linux, UNIX and Windows Fix pack, FixPak, DB6, UDB, LUW
Solaris, SUN, AIX 5L, Linux, HPIA64, RS6000 Upgrade SYSTOOLS.HMON_ATM_INFO
Reason and Prerequisites
For more information about fix packs supported by SAP, see
Note 101809.
o Before installing a new fix pack, you must shut down all instances that were created on the copy of the DB2 software and all relevant DB2 services.
o You are using 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 centrally-installed DB2 software copy, you need to update the DB2 software once only.
Newer SAP installation tools install the DB2 software in a subdirectory of the instance directory, so that it is available to all servers centrally.
o DB2 V9.7 is always a full install in the case of Windows and UNIX. You can use the images to
- Install a new copy of the DB2 software - Update an existing DB2 V9.7 instance
o You can display an overview of all installed DB2 V9.7 copies using the DB2 command "/usr/local/bin/db2ls".
Solution
Procedure:
===============
I. Downloading the software from SAP Service Marketplace (optional) II. Stopping the SAP system and database
(UNIX + Linux)
IV. Postprocessing (parametrizations) V. Updating the global directory
VI. Special postprocessing steps and comments 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 <OS> directory with one of the following:
o AIX_64 (AIX) o SUNOS_64 (Solaris)
o LINUXPPC64_64 (Linux Power PC 64-bit) o LINUXX86_64 (Linux AMD 64-bit) o HPIA64 (HP IA 64-bit)
<OS> is used for the path name of the respective software. <dbsw> 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.7 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 <Inst-Drive>.
9. Unpack the file xxxxxxxx_y.zip (xxxxxxxx is the material number) into the <Inst-Drive> 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.
(UNIX + Linux)
for all files. To do so, go into the directory <OS> and enter the following command as user "root":
chmod -R 755 .
II. Stop SAP system and database =====================================
If you want to install a new copy, you can defer stopping the instances until you must execute the command db2iupdt. For more information, see section III. - "
Update using a new installation
".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<dbsid>.
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 "<sapsid>adm", enter the following command:
stopsap
b) Stop the SAP OS Collector with the following command: saposcol -k
2. Stop the admin instance (if it exists). As a DAS user, enter the following command:
<dbsw>/das/bin/db2admin stop
III. Updating the instances ================================
You can import a fix pack 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<dbsid> using "db2setup", for example, ~db2<besid>/db2_v9_fp1. Note: In the case of Fix Pack 4, "DB2 Advanced Enterprise Server Edition" (AESE) is in the first place. In this case, always choose "DB2 Enterprise Server
Edition" (ESE).
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".
(UNIX + Linux)
In the following example, "db2iupdt" is called as follows: ~db2<dbsid>/db2_97_fp1/instance/db2iupdt db2<dbsid>
When you install Fix Pack 1, you can ignore the following error message when you execute db2iupdt:
"line 6163: chgowngrp: command not found"
Caution:
The new copy does not have a DB2 license. Therefore, you must reinstall the DB2 license as user "db2<dbsid>" using the command "db2licm -a" in
accordance with Note 816773.
The license is available for SAP DB2 OEM customers on SAP Service Marketplace (SMP) 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:
<path to old software>/install/db2_deinstall
Updating an existing software installation:
1. You must first stop your SAP system and all existing DB2 instances. 2. Call "installFixPack" from the DVD as user "root". You can either
specify the desired installation path directly (./installFixPack -b <path>) or call "installFixPack" without specifying a path. In this case, "installFixPack" asks you for the path.
IV. Postprocessing (parameterizations) - Execution on the database server only
====================================================== You must start the database instance before postprocessing.
You must then perform a parameterization and a package rebind using the script 'db6_update_db.sh'.
To do this, follow the instructions provided in Note 1365982. This note also contains the latest version of the script in the file
'db6_update_db.SAR'.
Note:
If you use HADR, you must consider the information in Note 1289413. The next time you execute the script or a connect to the
database, the following error may occur:
SQL1013N The database alias name or database name "" could not be found, In this case, you must execute a
db2_kill
command torelease any shared memory segments that still exist. V. Updating the global directory
(UNIX + Linux)
You must perform the update only 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/<SID>/SYS/global/db6/<OS>/db6_clidriver/
The database software is updated automatically during the installation of a fix pack. You must execute the script db6_update_client.sh so the DB2
driver or JDBC driver is also updated in the global directory. The script is available in the file db6_update_client.SAR that is attached to Note 1365982.
Procedure:
1. Log on to the database host as user "<sapsid>adm". 2. Mount the DB2 V9.7 LUW CLI/JDBC driver DVD.
3. Copy the entire content of the DVD to a temporary directory <temp>. 4. Download the attachment db6_update_client.SAR to the subdirectory
<temp>/CLIENT, and unpack it there using the program SAPCAR. 5. Go to the subdirectory <temp>/CLIENT.
6. Start the script "db6_update_client.sh" from this directory using the following command:
./db6_update_client.sh -u
or db6_update_client.sh -j for Java-only systems (take this into account)
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 restart your SAP system. V. Special postprocessing steps and comments
======================================================
o DB2 V9.7 FP2SAP
During the graphical installation of FP2SAP via db2setup, the following warning may be displayed in the GUI:
DEVELOPMENT MESSAGE: The C code and Java code in this install image are image are at mixed levels. This is caused by build problems and may prevent this install image from working correctly. Please
inform the build team and install team of this immediately. You can continue using this install image if does not crash on startup, but if you find any problems with this image then please include
information about the mixed code levels in the problem report. Since no problem occurs, you can ignore the warning.
(UNIX + Linux)
Header Data
Release Status: Released for Customer Released on: 26.09.2011 12:00:07 Master Language: German
Priority: Correction with medium priority Category: Installation information
Primary Component: BC-DB-DB6 DB2 Universal Database for Unix / NT
The Note is release-independent
Related Notes
Number Short Text
1598376 DB6: BACK GROUND SYSTEM APPS GET SQL1226N 1517012 DB6: High physical write times on DB2 9.7 FP1
1365982 DB6: Current db6_update_db/db6_update_client script (V35) 101809 DB6: Supported Fix Packs DB2 for Linux, UNIX and Windows
