IBM DB2 Version 9.1 Fix Pack 1 Readme Contents 1.0 Installing IBM DB2 Version 9.1 Fix Pack 1 (Windows) 1.1 Installation delivery 1.2 Pre-installation 1.2.1 Prerequisites 1.2.2 Prior to installing DB2 Version 9.1 Fix Pack 1 1.3 Installing DB2 Version 9.1 Fix Pack 1 1.3.1 Installing DB2 Version 9.1 Fix Pack 1 for a single DB2 database product 1.3.2 Installing DB2 Version 9.1 Fix Pack 1 for multiple DB2 database products 1.3.3 Installing DB2 Version 9.1 Fix Pack 1 using a response file 1.3.4 Installing DB2 Version 9.1 Fix Pack 1 in an MSCS environment 1.4 Post-installation 1.4.1 Enabling the DB2 Remote Command Service security feature 1.4.2 Binding bind files 1.4.3 Restrictions to adding additional DB2 database products 2.0 Uninstalling Version 9.1 Fix Pack 1 3.0 How to get help 3.1 Where to download the fix pack installation images 4.0 Reference 4.1 PTF information 4.2 Supported languages for DB2 Clients available from the FTP site 5.0 Notices 1.0 Installing IBM DB2 Version 9.1 Fix Pack 1 (Windows) Before installing DB2(R) Version 9.1 Fix Pack 1, read the appropriate sections of this readme that apply to your installation. 1.1 Installation delivery There is one type of fix pack image for DB2 Version 9.1 Fix Pack 1 on Windows(R): * Product-specific fix packs for each individual DB2 database product. Notes: 1. Since the DB2 Client fix pack is contained within the DB2 server fix packs (namely the fix packs for Enterprise Server Edition (ESE), Workgroup Server Edition (WSE), Express Edition (EXP), Personal Edition (PE) and Connect Enterprise Edition (ConEE)), you can use a DB2 server fix pack to upgrade DB2 Clients. 2. The DB2 Connect(TM) Personal Edition product does not have its own product-specific fix pack. To upgrade DB2 Connect Personal Edition products, you can either use the DB2 Client fix pack or a DB2 server fix pack. If you have multiple DB2 copies on the same system, those copies can be at different version and fix pack levels. If you want to apply this fix pack to one or more DB2 copies, you must install the fix pack on those DB2 copies one by one. If you have more than one DB2 Version 9.1 product installed in a single DB2 copy, you must download and uncompress all of the corresponding product-specific fix packs before starting the fix pack installation process. Note: If you have already downloaded a DB2 server fix pack, you do not need to download the DB2 Client fix pack, since it is contained within the DB2 server fix pack. 1.2 Pre-installation This section details the prerequisite information (including software, hardware, and operating system prerequisites) and lists the tasks that must be performed prior to installing DB2 database products. 1.2.1 Prerequisites Before downloading DB2 Version 9.1 Fix Pack 1, perform the following steps: 1. Ensure that your system meets all of the system requirements: http://www.ibm.com/software/data/db2/9/sysreqs.html This action prevents technical problems that might occur after the installation and configuration of the fix pack. 2. Review the Flashes and open Authorized Problem Analysis Reports (APARs) on the DB2 for Linux(R), UNIX(R) and Windows product support Web site: http://www.ibm.com/software/data/db2/udb/support.html Open APARs describe defects that are not yet addressed in a fix pack, and they might contain workarounds that will impact your use of DB2 Version 9.1 Fix Pack 1. For a list of open DB2 Version 9.1 APARs, refer to: http://www.ibm.com/software/data/db2/udb/support/apars.html 3. Read the Fix Pack 1 Release Notes and the "Known problems and workarounds" section of this readme. 4. Ensure that you have sufficient free space to download and extract the fix pack. 5. Ensure that you have sufficient free space to install the fix pack. The space required to install the fix pack is equal to the space required for the DB2 Version 9.1 for Linux, UNIX and Windows general availability (GA) installation. Ensure the space required is available in the location of the DB2 copy that you are updating or in the location where you plan to create a new installation of DB2. Refer to the following topic: "Disk and memory requirements" http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.uprun.doc/doc/r0008877.htm 6. If you already have a DB2 database product installed and have obtained special fixes, contact IBM(R) support to determine whether you need an updated version of the fixes before you install DB2 Version 9.1 Fix Pack 1. This helps to ensure that your system is in a consistent state and that no special fixes are lost. 1.2.2 Prior to installing DB2 Version 9.1 Fix Pack 1 Before installing DB2 Version 9.1 Fix Pack 1, perform the following steps: 1. Uncompress the fix pack 2. Review the license terms and conditions 3. Stop all DB2 instances, services and applications 1.2.2.1 Uncompressing fix pack installation images Fix pack installation images on the FTP site are in compressed format. Before you can apply the fix pack, uncompress the fix pack installation image in a temporary directory. You can uncompress the fix packs into the directory path of your choice, however, you should consider how you plan to install DB2 Version 9.1 Fix Pack 1: * If you plan to install DB2 Version 9.1 Fix Pack 1 using the DB2 Setup wizard GUI, the setup command detects the other installed DB2 database products. If all of the fix pack images for your DB2 database products are uncompressed into subdirectories under the same parent directory, the setup command automatically starts installing the fix pack for all DB2 database products without prompting you. If the fix pack product images are uncompressed into different directories, the setup command detects the other installed DB2 database products and prompts you for each directory path. * If you plan to install DB2 Version 9.1 Fix Pack 1 in silent mode, all the product images must be uncompressed into subdirectories under the same parent directory. To uncompress the fix pack installation images, perform the following steps: 1. Change to the directory where you have downloaded the fix pack installation image. 2. To uncompress the self-extracting image, double click the self-extracting .exe file. For example, if you have the DB2 Enterprise Server Edition product on Windows 32-bit, double click on v9fp1_win_ese.exe. The WinZip Self Extractor window opens. You can also uncompress the fix pack installation image using an unzip compatible utility. For example, to uncompress the DB2 Enterprise Server Edition product to a directory of your choice, enter: winzip32 v9fp1_win_ese.exe -e 3. Select the folder to contain the unzipped files. 4. Click Unzip. All files are unzipped to the specified folder. Repeat these steps to uncompress the self-extracting images for all of the DB2 database products you have installed. If you want to perform a silent installation using a response file, all of the images must be uncompressed to subdirectories under the same parent directory. 1.2.2.2 Reviewing license terms and conditions The license terms and conditions are located in the "db2\license" directory of the uncompressed fix pack installation image. If you install DB2 products using a response file, you must change the keyword LIC_AGREEMENT to ACCEPT within your response file to indicate your acceptance of the license agreement. If you do not already have a DB2 Version 9.1 for Windows product installed, the installation proceeds but the products go into Try & Buy mode, a complimentary copy for a limited time. 1.2.2.3 Stopping all DB2 instances, services and applications If you have DB2 Version 9.1 products already installed, ensure all DB2 instances, all DB2 services, and all applications are stopped. To stop all instances and DB2 services, use the services control panel applet (Control Panel ->Administrative Tools -> Services). If you have active database clients, you might have to force these clients off while stopping the instance. To force clients, issue the following command: db2stop force For more information on stopping an instance, see http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/t0008751.htm Refer to http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.uprun.doc/doc/r0023249.htm for a list of DB2 services that run on your system. 1.3 Installing DB2 Version 9.1 Fix Pack 1 DB2 Version 9.1 Fix Pack 1 can be installed in the following ways: * install the fix pack for a single DB2 database product * install the fix pack for multiple DB2 database products * install the fix pack using a response file (single product or multiple products) * install the fix pack in an MSCS environment. Select the method appropriate for you. 1.3.1 Installing DB2 Version 9.1 Fix Pack 1 for a single DB2 database product To install DB2 Version 9.1 Fix Pack 1 on a system with a single DB2 database product installed: 1. Ensure that you have the appropriate installation user accounts: * If you are installing a DB2 database product, you require an installation user account to perform the installation. Normally, the user account must belong to the Administrators group on the machine where you will perform the installation. Refer to "Required user accounts for installation of DB2 server products (Windows): http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.uprun.doc/doc/r0007134.htm * If you are installing a DB2 Connect product and want a non-Administrator to perform the installation, refer to "Non-Administrator installation of DB2 Connect (Windows)": http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.uprun.doc/doc/c0008462.htm * If you are installing a DB2 Client or DB2 Runtime Client, refer to "Notes on installing using a user account that is not a member of the Administrators group" at the end of this topic: http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.uprun.doc/doc/t0007315.htm 2. Change to the folder where the unzipped files are located. The setup command is located under the folder with the product abbreviation. For example, DB2 Enterprise Server Edition would be under ESE. 3. To start the DB2 Setup wizard, double click the setup.exe file. The DB2 Setup wizard GUI Launchpad opens. Online help is available to guide you through the Setup wizard GUI. To invoke the online help, click Help or press F1. 1.3.2 Installing DB2 Version 9.1 Fix Pack 1 for multiple DB2 database products To install DB2 Version 9.1 Fix Pack 1 on a system with multiple DB2 database products installed: 1. Change to the folder where the unzipped files are located. The setup command is located under the folder with the product abbreviation. For example, DB2 Enterprise Server Edition would be under ESE. 2. To start the DB2 Setup wizard, double click the setup.exe file. The DB2 Setup wizard GUI Launchpad opens. The Setup wizard GUI detects the other installed DB2 database products. * If all the product images are uncompressed into subdirectories under the same parent directory, the DB2 Setup wizard GUI automatically starts the installation of all DB2 database products without prompting you. * If the product images are uncompressed into different directories, the Setup wizard GUI detects the other installed DB2 database products and prompts you for the directory path. 1.3.3 Installing DB2 Version 9.1 Fix Pack 1 using a response file To install DB2 Version 9.1 Fix Pack 1 using a response file: 1. Change to the folder where the unzipped files are located. Ensure that all of the images were uncompressed to subdirectories under the same parent directory. The setup command is located under the folder with the product abbreviation. For example, DB2 Enterprise Server Edition would be under ESE. 2. To install DB2 Version 9.1 Fix Pack 1 in silent mode, run the installation with a response file. For example, enter: setup -u c:\db2fixpk.rsp -t c:\db2fixpk.trc -l c:\db2fixpk.log Note: The parameters -t and -l are optional. They specify a trace file and a log file. If you have more than one DB2 Version 9.1 product installed, the Setup wizard GUI detects the other installed DB2 database products. The installation fails if all uncompressed product images are not in subdirectories under the same parent directory. For a description of the setup command, refer to http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/r0011768.htm Sample response files can be found in the product-abbreviation\db2\Windows\samples directory. For example, ESE\db2\windows\samples. 1.3.4 Installing DB2 Version 9.1 Fix Pack 1 in an MSCS environment This topic describes how to install DB2 Version 9.1 Fix Pack 1 on top of an existing Version 9.1 installation in a Microsoft(R) Cluster Server (MSCS) environment. To illustrate how to install DB2 Version 9.1 Fix Pack 1 in an MSCS environment, a simple example configuration must be understood. In this example, the initial configuration is a DB2 instance that is comprised of two database partitions. In addition, there are two Cluster Groups: * DB2 Group 0: contains Partition 0 active on Machine A. The Administration Server (DAS) is also located here. * DB2 Group 1: contains Partition 1 active on Machine B. This is the initial configuration. To install DB2 Version 9.1 Fix Pack 1 on top of an existing Version 9.1 installation in an MSCS environment: 1. Set automatic failback to off. During the installation process you might have to restart your machine. When this happens the cluster service restarts automatically. Therefore the automatic failback must be set off so none of the groups automatically failback. a. In DB2 Group 0, to disable automatic failback: 1) From the Cluster Administrator window, right-click DB2 Group 0. 2) Select Properties. The DB2 Group 0 Properties window displays. 3) On the Failback tab, select the Prevent failback radio button. 4) Click OK. b. In DB2 Group 1, to disable automatic failback: 1) From the Cluster Administrator window, right-click DB2 Group 1. 2) Select Properties. The DB2 Group 1 Properties window displays. 3) On the Failback tab, select the Prevent failback radio button. 4) Click OK. 2. Move DB2 Group 1 to Machine A. a. From the Cluster Administrator GUI, click on DB2 Group 1. b. Right-click, select Move Group. The Owner column changes to Machine A. 3. Stop the cluster service on Machine B. a. From the Component Services window, right-click Cluster Service. b. Click Stop. 4. Install DB2 Version 9.1 Fix Pack 1 on Machine B. Note: * DB2 is still running and available on Machine A. * As part of the installation process, you might have to restart your computer. * The Silent Mode installation process can also be used to install DB2 Version 9.1 Fix Pack 1. 5. Take the DB2 resources on Machine A offline. a. Partition 0, Partition 1, and the DAS are on Machine A. These must be taken offline one at a time. To take Machine A resources offline: 1) From the Cluster Administrator window, in the left window panel, select Groups. 2) Select DB2 Group 0. The resources for the group display in the right window panel. * For DB2 Group 0 the DB2 resources include Partition 0 and the DAS. 3) In the right window panel, right-click one of the resources, select Take Offline. * Repeat this step for each of the DB2 resources in DB2 Group 0. 4) Select DB2 Group 1. The resources for the group display in the right window panel. * For DB2 Group 1 the DB2 resources include Partition 1. 5) In the right window panel, right-click the resource (Partition 1), select Take Offline. 6. Start the cluster service on Machine B. (If the installation required a restart of your computer, and, if the Restart Type for the cluster service is set to automatic, skip this step because the cluster service is already started.) To start the cluster service: a. From the Component Services window, right-click Cluster Service. b. Click Start. 7. Move DB2 Group 0 and DB2 Group 1 to Machine B. a. From the Cluster Administrator window, click DB2 Group 0. b. Right-click, select Move Group. The Owner column changes to Machine B. c. Click on DB2 Group 1. d. Right-click, select Move Group. The Owner column changes to Machine B. 8. Bring the DB2 resources on Machine B online. a. Partition 0, Partition 1, and the DAS are on Machine B. These must be brought back online one at a time. To bring these resources online: 1) From the Cluster Administrator window, in the left window panel, select Groups. 2) Select DB2 Group 0. The resources for the group display in the right window panel. * For DB2 Group 0 the DB2 resources include Partition 0 and the DAS. 3) In the right window panel, right-click one of the resources, select Bring Online. * Repeat this step for each of the DB2 resources in DB2 Group 0. 4) Select DB2 Group 1. The resources for the group display in the right window panel. * For DB2 Group 1 the DB2 resources include Partition 1. 5) In the right window panel, right-click the resource (Partition 1), select Bring Online. 9. Stop the cluster service on Machine A. a. From the Component Services window, right-click Cluster Service. b. Click Stop. 10. Install DB2 Version 9.1 Fix Pack 1 on Machine A. Note: * DB2 is still running and available on Machine B. * As part of the installation process, you might have to restart your computer. * The Silent Mode installation process can also be used to install DB2 Version 9.1 Fix Pack 1. 11. Start the cluster service on Machine A. (If the installation required a restart of your computer, and, if the Restart Type is set to automatic, skip this step because the cluster service is already started.) To start the cluster service: a. From the Component Services window, right-click Cluster Service. b. Click Start. 12. Move DB2 Group 0 to Machine A. a. From the Cluster Administrator window, click DB2 Group 0. b. Right-click, select Move Group. The Owner column changes to Machine A. This brings the MSCS environment back to the initial configuration. 13. If automatic failback was turned off in Step 1, you must turn it on. a. In DB2 Group 0, to enable automatic failback: 1) From the Cluster Administrator GUI, right-click DB2 Group 0. 2) Select Properties. The DB2 Group 0 Properties window displays. 3) On the Failback tab, select the Allow failback radio button. 4) Click OK. b. In DB2 Group 1, to enable automatic failback: 1) From the Cluster Administrator window, right-click DB2 Group 1. 2) Select Properties. The DB2 Group 1 Properties window displays. 3) On the Failback tab, select the Allow failback radio button. 4) Click OK. 1.4 Post-installation After installing DB2 Version 9.1 Fix Pack 1, perform the following steps: 1. Enable the DB2 Remote Command Service security feature. 2. Bind the bind files. After applying a fix pack, it is not mandatory to recompile applications. However, to take advantage of any changes to the files linked to in the application, recompiling applications is recommended. 1.4.1 Enabling the DB2 Remote Command Service security feature If you installed a partitioned DB2 server on Windows 2000, Windows Server 2003, or Windows XP, enable the DB2 Remote Command Service security feature to protect your data and resources. To be fully secure, enable either the computer (if the service is running under the context of the LocalSystem account) or a user for delegation (if the service is being run under the logon context of a user). To enable the DB2 Remote Command Service security feature: 1. Open the Active Directory Users and Computers window on the domain controller, click Start and select Programs --> Administrative tools --> Active Directory Users and Computers. 2. In the right window panel, right-click on the computer or user to enable, select Properties. 3. Click the General tab and select the Trust computer for delegation check box. For user setting, click the Account tab and select the Account is trusted for delegation check box in the Account option group. Ensure that the Account is sensitive and cannot be delegated box has not been checked. 4. Click OK to enable the computer or user for delegation. Repeat these steps for each computer or user that needs to be enabled. You must restart your computer for the security change to take effect. 1.4.1.1 Disabling the DB2 Remote Command Service security feature You can disable the DB2 Remote Command Service security feature and return the environment to its previous state using the DB2RCMD_LEGACY_MODE registry variable. Disable the DB2 Remote Command Service security feature by entering the following command: db2set DB2RCMD_LEGACY_MODE=ON Note: This registry variable requires Boolean values as arguments, the values YES, 1, TRUE, and ON are all equivalent and the values NO, 0, FALSE, and OFF are also equivalent. You can specify any of the appropriate equivalent values. 1.4.2 Binding bind files This section describes how and where to bind the database utilities (import, export, reorg, the Command Line Processor) and DB2 CLI bind files. 1.4.2.1 Binding to DB2 databases From the database server Perform the following actions once for each database in the DB2 database products that you upgraded: db2 terminate db2 CONNECT TO dbname db2 BIND path\db2schema.bnd BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE db2 BIND path\@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD db2 BIND path\@db2cli.lst BLOCKING ALL GRANT PUBLIC ACTION ADD db2 terminate where dbname represents the name of a database to which the files should be bound, and where path is the full path name of the directory where the bind files are located, such as $HOME\sqllib\bnd where $HOME represents the home directory of the instance for the database server. db2ubind.lst and db2cli.lst contain lists of required bind files used by DB2 database products. Packages that are already bound will return an SQL0719 error. This is expected. From the clients A "client" here refers to the initiator of a connection to a database in another DB2 copy or on another database server. This role can be filled by any of the following DB2 database products: DB2 Client, DB2 Runtime Client, DB2 Connect products, or a DB2 server product. Note: The Runtime Client cannot be used to bind the database utilities and DB2 CLI bind files. You must use the DB2 Client instead. For additional details on the differences between these two types of clients, refer to "Types of clients - DB2 Runtime Client and DB2 Client": http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.uprun.doc/doc/c0022612.htm If you install DB2 Version 9.1 Fix Pack 1 and you intend to connect to a database that is running on a different operating system or at a different DB2 version or service level, then you must bind the database utilities and DB2 CLI bind files against the database. Perform the following actions once from each unique combination of operating system and DB2 version or service level: db2 terminate db2 CONNECT TO dbname db2 BIND path\@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD db2 BIND path\@db2cli.lst BLOCKING ALL GRANT PUBLIC ACTION ADD db2 terminate where dbname represents the name of a database to which the utilities should be bound, and where path is the full path name of the directory where the bind files are located, such as $HOME\sqllib\bnd where $HOME represents the home directory of the instance on the "client". db2ubind.lst and db2cli.lst contain lists of required bind files used by DB2 database products. Packages that are already bound will return an SQL0719 error. This is expected. 1.4.2.2 Binding host databases If you are connecting to host databases, bind the new bind files to the host. Use the DB2 Command Line Processor to connect to the host database and bind the utilities as follows: HOST COMMAND ===== =================================================================== OS/390 or z/OS BIND path\BND\@ddcsmvs.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC ACTION ADD VM BIND path\BND\@ddcsvm.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC ACTION ADD VSE BIND path\BND\@ddcsvse.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC ACTION ADD OS/400 BIND path\BND\@ddcs400.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC ACTION ADD where path is the full path name of the directory where the bind files are located, such as $HOME\sqllib\bnd where $HOME represents the home directory of the instance 1.4.2.3 Binding specific bind files If you want to bind only the specific .bnd files to the database, issue the following commands for each database: db2 terminate db2 CONNECT TO dbname db2 BIND path\BND\bind_file BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE db2 terminate where dbname represents the name of your database, path is the full path name of the directory where the bind file is located, and bind_file represents the name of the bind file. 1.4.2.4 Binding spatial-enabled databases If you have existing spatial-enabled databases, you must bind the list file db2gse.lst after you install a DB2 fix pack. The db2gse.lst file contains the names of the bind files for the stored procedures that DB2 Spatial Extender provides. To bind the db2gse.lst file: 1. Ensure that you have one of the following authorities: * SYSADM or DBADM authority * ALTERIN privilege on the schema * BIND privilege on the package 2. Connect to the database and execute the BIND command. For example, enter: db2 connect to dbname db2 bind path\bnd\@db2gse.lst db2 terminate where dbname represents the name of the database and path is the full path name of the directory where the bind files are located. For syntax and options for the BIND command, refer to http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/r0001935.htm 1.4.3 Restrictions to adding additional DB2 database products Once a DB2 database product has been installed, additional DB2 database products can be added. The following recommendations and restrictions apply: If you have more than one DB2 database product installed in a single DB2 copy, update all of the DB2 database products in that DB2 copy to the same fix pack level. For more information on DB2 copies, refer to "Multiple DB2 copies roadmap": http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/r0024057.htm If you want to install additional DB2 database products in an existing DB2 copy, they must be at the same fix pack level as the existing DB2 database products in that DB2 copy. For example, DB2 Version 9.1 Enterprise Edition is already installed and Fix Pack 1 has been applied. If you want to add the DB2 Query Patroller product to the same DB2 copy, you must install DB2 Query Patroller using the appropriate Fix Pack 1 installation image. If the fix pack image that you are using to add new products is not at the same level as the installed DB2 database products, the installation attempt will not succeed. 2.0 Uninstalling Version 9.1 Fix Pack 1 After Version 9.1 Fix Pack 1 has been installed, it cannot be removed. The DB2 database products would need to be uninstalled. Refer to "Uninstalling your DB2 product (Windows)": http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.uprun.doc/doc/t0007436.htm 3.0 How to get help To contact DB2 Customer Service by phone: * In Canada and the United States, call 1-800-IBM-SERV (426-7378). * Worldwide, see the Directory of worldwide contacts for information on IBM offices in your country or region, at http://www.ibm.com/planetwide The main Usenet newsgroup for DB2 database product-related questions is comp.databases.ibm-db2. For additional information about changes to the product, review the Fix Pack 1 Release Notes. You can view the latest product Release Notes without installing DB2 Version 9.1 Fix Pack 1 by going to the DB2 Support Web site: * http://www.ibm.com/software/data/db2/udb/support.html 3.1 Where to download the fix pack installation images DB2 Version 9.1 Fix Pack 1 can be downloaded from: * the DB2 for Linux, UNIX and Windows product support Web site: http://www.ibm.com/software/data/db2/udb/support.html * the IBM anonymous FTP server: * ftp.software.ibm.com/ps/products/db2/fixes2/english-us/%P/fixpack/ where: * %P represents * db2winIA32v9 * db2winIA64v9 * db2winX64v9 Note: All other supported language directories (ftp.software.ibm.com/ps/products/db2/fixes2/%L, where %L represents the locale, for example, Spanish, German) link to the english-us directory. Go to the previously mentioned directories to get the fix pack or modification level images with all the supported languages. 4.0 Reference The following reference information is available: * PTF information * Supported languages for DB2 clients 4.1 PTF information The following list details the unique PTF labels for DB2 Version 9.1 Fix Pack 1: * WR21374: Windows (32-bit) * WR21375: Windows (64-bit) * WR21376: Windows (x64, for AMD64 and Intel(R) EM64T processors) 4.2 Supported languages for DB2 Clients available from the FTP site All of the supported languages for DB2 Client products are available in the products' self-extracting zip files on the FTP site. 5.0 Notices IBM may not offer the products, services, or features discussed in this document in all countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country/region or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country/region where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product, and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information that has been exchanged, should contact: IBM Canada Limited Office of the Lab Director 8200 Warden Avenue Markham, Ontario L6G 1C7 CANADA Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems, and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements, or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information may contain examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious, and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information may contain sample application programs, in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows: (C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. _enter the year or years_. All rights reserved. IBM, DB2 and S/390(R) are trademarks of International Business Machines Corporation in the United States, other countries, or both. Windows is a registered trademark of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others. ------------------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. ------------------------------------------------------------------------------- ******************************************************************************* ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1999, 2006. ** ALL RIGHTS RESERVED. ** *******************************************************************************