©2003 International Business Machines Corporation. All rights reserved.

Introduction

Recently, DB2® Universal Database^TM (DB2 UDB) Fix Pack 3 became generally available. You can download this Fix Pack from the IBM DB2 UDB and DB2 Connect^TM Support Web site.

There are some features that are delivered in Fix Pack 3, but as its name would suggest, its contents are mainly fixed-based. The more interesting features that are part of Fix Pack 3 include support for Microsoft® Visual Studio 2003 and its associated .NET Framework Version 1.1, and support for 64-bit Linux on the AMD Opteron processor family.

Instructions on how to install Fix Pack 3 are in the README file that is shipped with it; however, there is some missing information that could be helpful. There was an update to Fix Pack 3 to make it easier to install on Tuesday, August 12, 2003. However, if you invested the time to download the fix pack before this date, use this article as an aid to the instructions provided in the fix pack README to quickly apply Fix Pack 3 maintenance to your DB2 UDB server.

Back to top

A couple of words about fix packs and updates in the Version 8 release

In order to help identify feature-oriented ship vehicles from fix-oriented vehicles in the DB2 UDB V8 release, those that deliver mainly fixes to a DB2 UDB installation are called fix packs; those that mainly deliver new features are called updates.

So far, there have been three delivery vehicles for the DB2 UDB V8 release: Fix Pack 1, followed by the DB2 UDB V8.1.2 update, followed by Fix Pack 3.

All ship vehicles are cumulative in nature as shown in the figure below. Therefore, applying Fix Pack 3 will also include everything delivered by the v8.1.2 Update and Fix Pack 1.

Back to top

The skinny on installing Fix Pack 3 on a DB2 UDB Windows server

To install Fix Pack 3 on your DB2 UDB server, perform the following steps:

1. Determine what DB2 UDB products that require maintenance are installed on your system.
   

   Determining what DB2 UDB products you have installed on your system is something new that you have to consider for Fix Pack 3. If you have applied a Fix Pack or an Update before, you likely downloaded one file and installed it in one step for all the DB2 UDB products on your workstation. Things are a little different for Fix Pack 3. You have to download a Fix Pack for each and every DB2 UDB product installed on your system.

   I use Start -> Settings -> Control Panel -> Add or Remove Programs to determine what DB2 UDB programs that could require maintenance are installed on my system, as shown in Figure 2 below:

   
   Figure 2. The Add/Remove Programs that shows the DB2 UDB products on my system
   
   

   You should install a Fix Pack for each and every DB2 UDB product that is installed on your system.

2. Create a parent directory to house the fix packs that you need to download.
   

   For my system, I created a parent directory called FP3 on my D:\ drive using the md FP3 command.

3. Create a subdirectory under the parent directory that you created in Step 2 for each and every product for which you are going to download a Fix Pack.
   

   For my system, since I have two DB2 UDB products installed (as shown in Figure 2), I created two subdirectories in the FP3 parent directory using the md ESE and the md CUBE commands. The result of these commands is shown in Figure 3:

   
   Figure 3. Directories created on my computer
   
   
4. Download the appropriate fix packs for all the DB2 UDB products you have installed on your system from the DB2 UDB and DB2 Connect Support Site. Ensure that each Fix Pack goes into the appropriate subdirectory that you created for each DB2 UDB product.
   

   You need to download a Fix Pack for each and every DB2 UDB product that you have installed on your workstation.

   Each of the Fix Packs are prefixed with FIX PACK3_WR21324_, and the suffix identifies the product for which the Fix Pack has been created.

   For example, FIX PACK3_WR21324_CUBE.exe is the Fix Pack that you would download if you have DB2 UDB Cube Views installed on your system.

   For my system, since I have DB2 UDB Enterprise Server Edition and DB2 UDB Cube Views installed (shown in Figure 3), I need to download the FIX PACK3_WR21324_CUBE.exe and the FIX PACK3_WR21324_ESE.exe files as shown below:

   
   Figure 4. Downloading the fix packs from the FTP site
   
   

   In my example, after I downloaded all the Fix Packs and put them in their appropriate directories, an .exe file will be in each subdirectory. The following figure shows the contents of the D:\FP3\ESE directory on my system:

   
   Figure 5. The fix pack package downloaded on disk
   
   
5. Decompress each .exe file in each directory by entering the name of the .exe file you downloaded, along with the –e –f options (where –f represents the filepath where the Fix Pack is located).

   The installation instructions that come with Fix Pack 3 do not mention the required –e option in the interactive instructions. As well, it is not shown in the syntax of the command you use to unpack the fix pack to your disk.

   So, for my system, I would enter the following commands to unpack the Fix Pack files that I downloaded from the Internet:

   D:\FP3\CUBE\FIX PACK3_WR21324_CUBE.exe –e –f d:\FIX PACK3\CUBE D:\FP3\ESE\FIX PACK3_WR21324_ESE.exe –e –f d:\FIX PACK3\ESE

   
   
   Figure 6. A tip to keep in mind
   
   

   When you enter either of these commands, the corresponding fix pack’s files are unpacked to the specified directory as shown in Figure 7 below:

   
   Figure 7. The fix pack package unpacking on disk
   
   

   You can verify this by checking the contents of the directory when it has finished. It should be similar to the following:

   
   Figure 8. The fix pack unpacked to your disk
   
   
6. Install your Fix Packs by going to one of the Fix Pack directories that you created and entering the setup.exe command.
   

   You can enter the setup.exe command from any subdirectory that you have set up for the fix pack files. I used the Cube Views directory when I installed Fix Pack 3 on my machine. The setup.exe command will start the installation process (assuming that you are logged on to your machine with the correct authorities etc.; see the README file for more information) for the Fix Pack for which it was invoked.

   
   Figure 9. Fix pack for Cube Views installing on your system
   
   

   Regardless of the Fix Pack directory where you first entered the setup.exe command, when that particular fix pack has finished installing, the DB2 UDB installation program will go on to all the Fix Packs that you created in the parent directory (in my example, this was the d:\FP3 directory) and install them as well.

   So, provided you followed the steps I outlined in this article, the DB2 UDB installation program will install all of the Fix Packs that you downloaded and unpackaged in their respective directories. The installation program should automatically locate all the Fix Packs you downloaded. If for some reason cannot find one of them, it will prompt you for its location.

   Since I downloaded two Fix Packs and created directories for them, when the DB2 UDB Cube Views Fix Pack has finished installing, it will move on to the DB2 UDB ESE Fix Pack as shown below.

   
   Figure 10. Fix Pack 3 for DB2 ESE installing automatically
   
   
   
   Figure 11. Fix Pack for DB2 ESE installing automatically
   
   
7. When you have completed the installation and followed any post installation steps that the DB2 UDB installation may have asked you to do, enter the db2level command to verify the Fix Pack level of your DB2 UDB server.
   

   Entering the db2level command will show you the Fix Pack level of your DB2 UDB server as shown in Figure 12:

   
   Figure 12. Output from db2level command
   
   

   If you followed my instructions, and used the information in the README, you should have no problems delivering maintenance to your DB2 UDB installation. Allow yourself some time if you have multiple DB2 UDB products installed on your workstation. They can take a while to download (even over a high speed connection) and the unpacking takes a while too.

Back to top

Resources

• DB2® Universal Database™ (DB2 UDB) Fix Pack 3
  
  

About the author

Paul C. Zikopoulos, BA, MBA, is an IDUG keynote and award-winning speaker with the IBM Global Sales Support team. He has more than seven years of experience with DB2 and has written numerous magazine articles and books about it. Paul has written articles on DB2 for many magazines and has co-authored the books: DB2 - The Complete Reference, DB2 Fundamentals Certification for Dummies, DB2 For Dummies, A DBA's Guide to Databases on Linux, and the soon to be released DB2 Version 8: The Official Guide. Paul is a DB2 Certified Advanced Technical Expert (DRDA and Cluster/EEE) and a DB2 Certified Solutions Expert (Business Intelligence and Database Administration). You can reach him at paulz_ibm@msn.com.

Comments (Undergoing maintenance)

Back to top

Trademarks  |  My developerWorks terms and conditions

Table of contents

• Introduction
• A couple of words about fix packs and updates in the Version 8 release
• The skinny on installing Fix Pack 3 on a DB2 UDB Windows server
• Resources
• About the author
• Comments

Next steps from IBM

• Try: DB2 Enterprise
• Demo: DB2 serving ATOM feed
• Webcast: A smarter way to successful SOA - Information as a trusted strategic asset
• Briefing: Information on Demand
• Buy: DB2 Enterprise

My developerWorks community

Dig deeper into Information Management on developerWorks

DB2 pureScale

See how true transparent scaling architecture can be achieved on distributed platforms

Special offers