DB6: Installation of FixPaks for DB2 V9.5 (Windows)

[] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []

Related:

  1. DB6: Installation of FixPaks for DB2 V9.5 (UNIX+Linux)Symptom This note relates to installing FixPaks for DB2 V9.5...
  2. DB6: Installing FixPaks for DB2 V9.1 on WindowsSymptom This note relates to installing FixPaks for DB2 V9.1...
  3. DB6: Installing FixPaks for DB2 V9.1 (UNIX+Linux)Symptom This note relates to installing FixPaks for DB2 V9.1...
  4. DB6: SAP NetWeaver Inst. based on Kernel 7.11 – WindowsSymptom SAP NetWeaver Installation based on Kernel 7.11 – Windows...
  5. DB6: Installing V8.2 FixPaks (as of FP9) on Win NT/Win 2000Symptom To install FixPakslower than FixPak 9, see Note 940550....
  6. DB6: Installing V8.2 FixPaks (as of FixPak 9) on UNIXSymptom To install FixPakslower than FixPak 9, see Note 940551...
  7. DB6:Inst.NW 7.0 EHP2 – WindowsSymptom SAP NetWeaver 7.0 incl.EHP 2 on Windows with DB2...
  8. DB6: SAP System Inst. with DB2 V9 only – UNIXSymptom SAP System Installation based on SAP Kernel 7.0 with...

Symptom

This note relates to installing FixPaks for DB2 V9.5 (for Windows).

Other terms

DB2 9.5 for Linux, UNIX, and Windows
Fix pack, FixPack, FixPak
Windows 2003
Upgrade SYSTOOLS.HMON_ATM_INFO

Reason and Prerequisites

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

Ensure that you shut down all instances created on the copy of the DB2 software as well as all related DB2 services before you install a new FixPak.If you operate a partitioned system with database nodes on several servers, you must import the same FixPak on all servers concerned.DB2 V9.5 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.5 software installationIf you install a new DB2 copy, you can switch an existing DB2 V9.5 instance from the old copy to the newly installed copy using the command db2iupdt.
The SAP kernel of Releases 3.1I – 7. 0 can currently work with a default copy only. Therefore, you must update the existing default copy to install a FixPak. A 7.10 system can be operated with its own DB2 copy.

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 (parametrizations)
V. Updating the global directory

I. Downloading the software from SMP (optional)
==================================================
You can install the software directly from the DVD, or download it from SAP Service Marketplace, unpack it, and then install it from a local directory. If you want to install the software directly from the DVD, proceed with step II.
If you download the software from SAP Service Marketplace, you must perform the following steps before the installation:

1. In SAP Service Marketplace, 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 9.5 software download”.6. Choose “Installation”.7. Choose “DB2 UDB”.8. Download the software relevant to your Windows operating system into one of the following paths labeled with .9. Unpack the file xxxxxxxx_y.zip (where xxxxxxxx is the material number) into the directory by double-clicking the file name.

II. Stopping the SAP System and the database
======================================
The following steps must be carried out by a user with administrator rights.
First, stop:
all SAP systems that are currently runningthe SAPOSCOL processall DB2 instances and DB2 services of the DB2 copy that you want to update (this also applies to the Admin instance, if one exists –> as user DAS with the command: db2admin stop)

III. Updating the instances
================================
SAP Releases 3.1I – 7.0 can operate with the “default copy” only. Therefore, only an update of the default copy is permitted. You have the option of updating the existing copy or of changing your DB2 instance to a new copy only as of SAP Release 7.10.
This note describes theUpgrade of an existing copy.
indicates the path to the FixPak software. With a direct installation from the DVD, the path is:
:\. Here, represents the relevant Windows operating system.

1. Switch to the path \ESE\image and call the program “setup.exe” from there.2. Choose “Install a Product”.3. Choose “Work with Existing”. The system displays a list of all copies that are installed.4. Select the copy to be updated.5. Choose “Launch the DB2 Setup Wizard”.6. Follow the instructions in the setup wizard.

After you install the DB2 software, you must start the database again. All DB2 services are then started again.
IV. Postprocessing (parametrizations)
=======================================================================
You must start the database before postprocessing.
Finally, you must perform the parameterization of registry variables and other parameters using the script db6_update_db.bat.
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 as the user db2 using the following command:

db6_update_db.bat -d
This writes the parameter settings into an output script db6_update_db_out.bat.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.bat > db6_update_db_out.bat.log

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

CAUTION:
If you performed a database release upgrade from DB2 V9 GA to
DB2 V9.5 FP1SAP or DB2 V9.5 FP2, execute
the following command:
db2 drop table SYSTOOLS.HMON_ATM_INFO
You can use this to prevent the known problems that are described in more detail in
Note 1263266.

V. Updating the global directory
=======================================================================
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\\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.bat’ 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.5 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.bat’ from this directory using the following command:

db6_update_client.bat -u
The script ‘db6_update_client.bat’ 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.
Additional points with regard to installation on multipartition systems
=======================================================================
Windows XP as a domain controller: All hosts configured on a multipartition system must have the property “Trust Computer for delegation” activated.
The user in whose context the “DB2 Remote Command Service” is running, must fulfill the following criteria.

1. The user must be a domain administrator.2. The user must have the “Logon as a service” Windows authorization.3. Windows XP as a domain controller: The user account must have the “Trusted for delegation” property.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment