Before installing DB2 Universal Database(TM) (UDB) Version 8.2 FixPak 4 and later, read the appropriate sections of this readme that apply to your installation. Version 8.2 FixPak 4 and later is equivalent to Version 8.1 FixPak 11.
All FixPaks are cumulative in nature. For example, the current FixPak can be applied on top of Version 8.2 FixPak 1 without having to apply the FixPaks in between.
If you migrate from DB2 UDB Version 8.1 to DB2 UDB Version 8.2, and then need to move back to DB2 UDB Version 8.1, there are important considerations you need to know. For instructions on how to move back to DB2 UDB Version 8.1, see the "Migrating database directory files from Version 8.2 back to Version 8.1" section.
Starting with DB2(R) UDB Version 8 for Windows(R) FixPak 3, IBM(R) is providing product-specific FixPaks instead of one general FixPak. This change affects only DB2 Version 8 products on Windows platforms.
This new delivery mechanism provides the following advantages:
If you have only one DB2 Version 8 for Windows product installed, you need to download the corresponding product-specific FixPak.
If you have more than one DB2 Version 8 product installed on the same system, you must download and uncompress all of the corresponding product-specific FixPaks before starting the FixPak installation process.
For example, if you have DB2 Enterprise Server Edition and DB2 Warehouse Manager installed, you must download and uncompress both DB2 Enterprise Server Edition (ESE) and DB2 Warehouse Manager (WM) FixPaks. You can uncompress the DB2 products into the directory path of your choice, however, you need to consider how you plan to install DB2 Version 8.2 FixPak 4 and later:
See the "Installation of DB2 UDB Version 8.2 FixPak 4 and later" section for details.
If you do not already have a DB2 Version 8 for Windows product installed, the installation proceeds but the products go into Try & Buy mode, a complementary copy for a limited time.
The delivery mechanism supports all installation scenarios.
This section details the prerequisite information (including software, hardware, and operating system prerequisites) you need, points to where the product fix history is located, and lists the tasks that must be performed prior to installing DB2 UDB.
Consult the following Web sites for the latest software, hardware, operating system and product fix information:
If you have received special fixes from IBM support, you must contact IBM support before you install DB2 UDB Version 8.2 FixPak 4 and later to check if you need an updated version of the special fixes. This helps to ensure that your system is in a consistent state and that no special fixes are lost.
You must have a DB2 product Version 8 installed at a lower VRMF (version, release, modification/maintenance level, and fix) level than DB2 Version 8.2 FixPak 4 and later before you install Version 8.2 FixPak 4 and later.
If you have a DB2 Version 8 product already installed, it must be at a lower service level than DB2 Version 8.2 FixPak 4 and later. There are various methods to determine the version and level of the currently installed DB2 product. You can:
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\<product name>\CurrentVersion\Version HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\<product name>\CurrentVersion\Release HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\<product name>\CurrentVersion\ModificationThe following values should display:
The values for Version, Release, and Modification correspond to the first three numbers of the VRMF number. The value for Modification in the registry for the currently installed products must be less than the third number of the VRMF number for DB2 Version 8.2 FixPak 4 and later, which is 11.
For a list of all product fixes (APARs) and support news, see Web site
Read the Known problems and workarounds sections before installing DB2 Version 8.2 FixPak 4 and later.
Before starting the installation, you must also:
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 forceFor more information on stopping an instance, see http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/admin/t0008751.htm
The following table lists the DB2 services:
| Service | Service Name | Description |
|---|---|---|
| DB2 - <instance name> | <instance name> | Allows applications to create, update, control, and manage relational databases. This service is created for each instance on the server |
| DB2 Data Links File Manager | DlfmService | Manages linked files under the control of the Data Links Filesystem Filter (DLFF) in coordination with registered DB2 databases |
| DB2 Governor | DB2GOVERNOR | Collects statistics for applications connected to DB2 databases. For technical information on the Governor utility, search the Information Center |
| DB2 Information Center Server | DB2ICSERVER | Provides documentation for the DB2 Information Management family of products and features for Linux, UNIX, and Windows operating systems |
| JDBC Applet Server | DB2JDS | Provides JDBC server support for DB2 applications |
| DB2 License Server | DB2LICD | Monitors DB2 license compliance |
| DB2 Query Patroller | DB2QP | DB2 Query Patroller |
| DB2 Registry Reflector | DB2NTREGREFLECTOR | Allows DB2 64-bit servers to support DB2 32-bit local applications |
| DB2 Remote Command Server | DB2REMOTECMD | Supports remote DB2 command execution |
| DB2 Security Server | DB2NTSECSERVER | Authenticates DB2 database users when the authentication is performed at the client computer |
| DB2 Warehouse Agent | DB2DWAgent | Controls the starting and stopping of DB2 warehouse agents |
| DB2 Warehouse Logger | DB2DWLogger | Provides message logging for the DB2 Warehouse Manager |
| DB2 Warehouse Server | DB2DWServer | Controls the interaction of DB2 warehouse components, controls and monitors warehouse agents, and provides scheduling functions |
| DB2DAS - DB2DASXX | DB2DASXX (where XX is 00-99) | Supports local and remote database administrative requests |
DB2 UDB Version 8.2 FixPak 4 and later can be installed in the following ways:
Select the method appropriate for you.
DB2 UDB Version 8.2 FixPak 4 and later images can be downloaded from the DB2 Technical support Web site, directly from the IBM anonymous FTP server, or images are available on the FixPak CD.
To install the DB2 Version 8.2 FixPak 4 and later on a system with a single DB2 product installed:
You can also uncompress the fixpak 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 FP11_WR21365_ESE.exe -e
Online help is available to guide you through the Setup wizard GUI. To invoke the online help, click Help or press F1.
DB2 UDB Version 8.2 FixPak 4 and later images can be downloaded from the DB2 Technical support Web site, directly from the IBM anonymous FTP server, or images are available on the FixPak CD.
To install DB2 Version 8.2 FixPak 4 and later on a system with multiple DB2 products installed:
You can also uncompress the fixpak installation images using an unzip compatible utility. For example, to uncompress the DB2 Enterprise Server Edition product to a directory of your choice, enter: winzip32 FP11_WR21365_ESE.exe -e
All images must be uncompressed.
The Setup wizard GUI detects the other installed DB2 products.
DB2 UDB Version 8.2 FixPak 4 and later images can be downloaded from the DB2 Technical support Web site, directly from the IBM anonymous FTP server, or images are available on the FixPak CD.
To install DB2 Version 8.2 FixPak 4 and later using a response file:
Download the images for all the products you have installed.
You can also uncompress the fixpak installation images using an unzip compatible utility. For example, to uncompress the DB2 Enterprise Server Edition product to a directory of your choice, enter: winzip32 FP11_WR21365_ESE.exe -e
All images must be uncompressed to subdirectories under the same parent directory.
setup -u e:\db2fixpk.rsp -t c:\db2fixpk.trc -l c:\db2fixpk.log
If you have more than one DB2 Version 8 product installed, the Setup wizard GUI detects the other installed DB2 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, see the DB2 Version 8.2 FixPak 4 and later Command line parameters section.
Sample response files can be found in the <product-abbreviation>\db2\Windows\samples directory. For example, ESE\db2\windows\samples.
This topic describes how to install DB2 UDB Version 8.2 FixPak 4 and later on top of an existing Version 8 installation in a Microsoft(R) Cluster Server (MSCS) environment.
Assumptions: To illustrate how to install DB2 Version 8.2 FixPak 4 and later 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 partitions. In addition, there are two Cluster Groups:
This is the initial configuration.
To install DB2 UDB Version 8.2 FixPak 4 and later on top of an existing Version 8 installation in an MSCS environment:
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.
After installing DB2 Version 8.2 FixPak 4 and later, do the following:
This task is strongly recommended if you want to use capabilities specific to the latest FixPak. If you are not planning to use capabilities specific to the latest FixPak and might possibly decide to return to an earlier FixPak, you should not use db2updv8.
After installing DB2 Universal Database (UDB) Version 8.2 FixPak 4 and later, run the db2updv8 command to update the system catalogs to support the current level by enabling several built-in routines. Running the db2updv8 command is not required, but some functionality in DB2 UDB Version 8.2 will not work if this command is not run.
After you have run the db2updv8 command to update the system catalogs to the current Version 8 level, falling back to Version 8.1 is not supported.
For more information on the db2updv8 command, run this command with the -h option. For technical information, search the Information Center for Update Database to Version 8 Current Level Command.
If you installed a partitioned DB2 server on Windows 2000, Windows Server 2003, or Windows XP, you must enable the DB2 Remote Command Service security feature to protect your data and resources. To be fully secure, you need to 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:
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.
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.
To disable the DB2 Remote Command Service security feature, enter the following command:
db2set DB2RCMD_LEGACY_MODE=ON
You need to bind your DB2 utilities against all your databases after the installation. This step is necessary for the fixes to become effective. The binding procedure, needs to be performed only once per database.
After applying fixes, you must issue one of the following command sequences:
db2 terminate
db2 CONNECT TO <dbname>
db2 BIND $DB2DIR\BND\@db2ubind.lst GRANT PUBLIC ACTION ADD
db2 terminate
or
At the DB2 command line, enter:
TERMINATE
CONNECT TO <dbname>
BIND <path>/@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
TERMINATE
where <dbname> represents the name of a database to which the utilities should be bound and $DB2DIR represents the directory where you have installed DB2. db2ubind.lst and db2cli.lst contain lists of required bind files used by DB2 UDB Version 8. Packages that are already bound will return an SQL0719 error. This is expected.
If you are connecting to host databases, you need to 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 ===== =================================================================== MVS BIND $DB2DIR\BND\@ddcsmvs.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC ACTION ADD VM BIND $DB2DIR\BND\@ddcsvm.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC ACTION ADD VSE BIND $DB2DIR\BND\@ddcsvse.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC ACTION ADD OS400 BIND $DB2DIR\BND\@ddcs400.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC ACTION ADD
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 $DB2DIR\BND\<bind_file> BLOCKING ALL GRANT PUBLIC sqlerror continue
db2 terminate
where <bind_file> represents the name of the bind file, and <dbname> represents the name of your database.
For installations on the server, an additional bind file needs to be bound to existing databases. This requirement does not apply to clients.
To bind db2schema.bnd on the server, execute one of these commands sequences:
At a command prompt:
db2 terminate
db2 CONNECT TO <dbname>
db2 BIND $DB2DIR\BND\db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue
db2 terminate
or,
At the DB2 command line:
TERMINATE
CONNECT TO <dbname>
BIND $DB2DIR\BND\db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue
TERMINATE where <dbname> represents the name of a database to which the utilities should be bound and $DB2DIR represents the directory where you have installed DB2.
If you have existing spatial-enabled databases, you must bind the list file db2gse.lst after you install a DB2 FixPak or patch. 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, you must have one of the following authorities:
To bind the db2gse.lst file:
cd %DB2PATH%\bnd
db2 connect to dbname db2 bind /home/instance/sqllib/bnd/@db2gse.lst db2 terminate
For syntax and options for the BIND command, refer to the DB2 Command Reference.
In DB2 UDB Version 8.2, two new fields were added to the database entry structure, changing the database directory file structure. After installing Version 8.2 over Version 8.1, the first time the database directory files are used, they are migrated automatically. To demigrate the database directory files from Version 8.2 to Version 8.1, the db2demigdbd is provided to convert all migrated database directory files to the Version 8.1 format.
You can find documentation for the db2demigdb tool at http://publib.boulder.ibm.com/infocenter/db2help/topic/com.ibm.db2.udb.doc/core/r0011770.htm. For more information and how to download the db2demigdb tool, search the Technotes database at http://www.ibm.com/software/data/db2/udb/support.html using the keywords "db2demigdb tool".
The following sections detail problems and workarounds you must be aware of prior to installing DB2 UDB Version 8.2 FixPak 4 and later.
There are no know problems and workarounds for Version 8.2 FixPak 4 and later.
If you have more than one DB2 product installed on the same computer, you need to update all existing DB2 products to the same fixpak level. For details, see the "Compatibility issues" section of the Version 8.2 FixPak 3 (equivalent to Version 8.1 Fixpak 10) Release Notes.
Despite the previous ability to connect to host systems from DB2 Universal Database Workgroup Server Edition and DB2 Universal Database Express Edition, beginning with Version 8.2 (Version 8.1 FixPak 7), this connection is no longer permitted.
Prior to Version 8.2 (Version 8.1 FixPak 7), when DB2 Workgroup Server Edition or DB2 Express Edition was installed, the JCC Universal Driver file, db2jcc_license_cisuz.jar, was included in \sqllib\java. The JCC Universal Driver did not check user licenses before initiating a host connection.
Beginning with Version 8.2 (Version 8.1 FixPak 7), the ability to initiate a host connection is disabled. This change affects the following Version 8.2 products:
To contact DB2 Customer Service by phone:
The main Usenet newsgroup for DB2 product-related questions is comp.databases.ibm-db2.
For additional information about changes to the product, review the product Release Notes. You can view the latest product Release Notes without installing DB2 Version 8.2 FixPak 4 and later by going to the DB2 Support Web site:
You can review the Release Notes directly from the DB2 Version 8.2 FixPak 4 and later CD by going to /doc/%L/db2ir/index.htm, where %L represents the locale name.
The DB2 Information Integrator Version 8 Release Notes are located at http://www.ibm.com/software/data/integration/db2ii.
The DB2 Query Patroller Release Notes are located at http://www.ibm.com/software/data/db2/udb/support.html.
DB2 Version 8.2 FixPak 4 and later can be downloaded from:
The following reference information is available:
The following table details the PTF information:
| Operating system or product | PTF |
|---|---|
| Windows 32-bit | WR21365 |
| Windows 64-bit | WR21366 |
| Windows x86-64 | WR21367 |
The following product abbreviations should be used when searching directories or when identifying files to uncompress:
The following table details the supported languages for DB2 clients that are available from the FTP site:
| Operating System | DB2 Administration Client | DB2 Application Development Client | DB2 Run-Time Client |
|---|---|---|---|
| AIX(R) 4.3.3 (32-bit) |
|
|
All supported languages are in one tarred file |
| AIX 5L(TM) (32-bit and 64-bit) |
|
|
All supported languages are in one tarred file |
| HP-UX 11i (PA-RISC) and HP-UX 11i v2 (IA64) (32-bit and 64-bit) | All supported languages are in one tarred file | All supported languages are in one tarred file | All supported languages are in one tarred file |
| Linux(TM) | All supported languages are in one tarred file | All supported languages are in one tarred file | All supported languages are in one tarred file |
| Solaris Operating Environments | All supported languages are in one tarred file | All supported languages are in one tarred file | All supported languages are in one tarred file |
| Windows | All supported languages are in one self-extracting zip file | All supported languages are in one self-extracting zip file | All supported languages are in one self-extracting zip file |
DB2 products continue to be supported on Windows 98, Windows ME and Windows NT(R) until DB2 Version 8.1 goes out of service. For existing installations and new installations of DB2 products, upgrading to a more current operating system version of Windows (such as Windows 2003) is recommended.
The following lists show the supported products and components for each Windows operating system:
If you want to run a DB2 command in a language other than the default language on your computer, specify a language identifier. The language must be available on the platform on which you are running the installation.
| Language | Language identifier |
|---|---|
| Arabic | ar |
| Brazilian Portuguese | br |
| Bulgarian | bg |
| Chinese, Simplified | cn |
| Chinese, Traditional | tw |
| Croatian | hr |
| Czech | cz |
| Danish | dk |
| Dutch | nl |
| English | en |
| Finnish | fi |
| French | fr |
| German | de |
| Greek | el |
| Hebrew | iw |
| Hungarian | hu |
| Italian | it |
| Japanese | jp |
| Korean | kr |
| Norwegian | no |
| Polish | pl |
| Portuguese | pt |
| Romanian | ro |
| Russian | ru |
| Slovak | sk |
| Slovenian | sl |
| Spanish | es |
| Swedish | se |
| Turkish | tr |
The setup command is run after the FixPak installation image is uncompressed. The options are:
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, Universal Database, and S/390 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. ** *******************************************************************************