Practical tips for Installing the DB2 UDB Revision pack on Unix

Brief introduction

This article will help you download and install the DB2®UDB Revision Pack and understand the steps involved in the process. Each DB2 revision pack has a Readme.txt file, which is often referenced when we read this article.

Similar to other software products, frequent revisions to DB2 are made in the form of revised packages. A given DB2 version may end up with up to 15 or more revision packs, each containing a number of patches for the problems found. Aparlist. The TXT file contains a brief description of each of these patches. Sometimes the revision package contains new features that provide more powerful functionality for DB2 products. These are described in the ReleaseNotes.txt file. The revision pack comes with aparlist. TXT and ReleaseNotes.txt files.

First, please check the necessary requirements:

1. DB2 UDB version 6.1 or version 7.2 is installed on the current system.

2. The operating system is UNIX.

The 3.DB2 version is a personal, workgroup, or Enterprise Edition (EE).

4. After the download of the revised package is decompressed and unpacked, there is sufficient file system space to hold the files (depending on the revision package to be downloaded, the file system requires 140 to 900 megabytes of space).

5. You can obtain root and instance owner permissions on the system.

Download the revision pack from the DB2 FTP site

Before downloading a specific DB2 revision pack, you can determine the current revision package setting by entering Db2level on the DB2 command window. The results are similar to the following:

db21085i Instance "DB2V71" uses DB2 code release "SQL07020" with level identifier "3010105" and Informational tokens "DB2" v7.1.0.41 "," s010426 "and" U475377 ".

In bold, "B2V71" represents the DB2 version, and "U475377" indicates the revision package level. The latter is an encrypted code that can be decoded by going to IBM's DB2 UDB Download Revision Pack and the client Web page.

Click the link that is associated with your DB2 version (that is, version 6 or version 7), which is located at the top left of the Web page. This will take you to another Web page where you will select the operating system (at the top of it). Click the link that applies to the operating system and compare the code with its revision package release number. When the Db2level command is executed, if the output is displayed as "" instead of "U475377", it means that you do not have any revision packs installed.

Note: DB2 revision pack do not ask you to install each revision package in turn. For example, you can install Revision Pack 8 for version 6.1 even if you are currently using Revision Pack 1.

To download the revision package, you can go to the revision package site mentioned above, or select one of the following options:

FTP to anonymous server ftp.software.ibm.com. Go to ps/products/db2/fixes/%l/%p/, where%l is the appropriate locale (such as American English, Spanish, German, etc.),%P is the product name/version (for example, DB2NTV71, etc.).

Use a Web browser to connect to the DB2 UDB and DB2 Connect online support Web pages.

On the CompuServe, execute go IBMDB2. Then, go to the appropriate library to find the revision pack.

On the IBM PCC BBS (in the United States), call 919-517-0001 (in North Carolina State Raleigh), and then enter "DB2" on the main menu to find the revision pack.

If you will download the revision pack via UNIX command-line FTP, make sure to enter ' bin ' to enter the binary mode after connecting to the FTP site. This is the correct transport of the revision pack tar. Required for the Z file. If you download to a Windows NT machine and then FTP to a UNIX machine, you also need to enter ' bin ' to transfer the file correctly. After you copy the file, check to make sure that both the original file and the FTP file have the same file size (in bytes) on both the Windows NT machine and the UNIX machine. Before the transfer completes, a common condition during an FTP session is terminated because of interruption. If there are several byte differences between the original file and the copy, the problem will occur.

The most common error caused by an incorrect file size occurs during the file unpack (Untar). The error at the end of the tar operation would be "tar:directory checksum error," which means that the file size does not match the desired file size. Even if this error occurs, the installation files are generated, causing some people to believe that they can install the revision pack.

You should prepare to install the revision pack in the following order. In the following example, we will revise package 3 for DB2 version 7.1 on Sun Solaris: