Before installing DB2(R) Version 9.1 Fix Pack 1, read the sections of this readme that apply to your installation.
There are two ways that you can use the fix pack:
This readme provides instructions for both of these scenarios.
There are two types of fix pack images:
Use this type of fix pack if you only have a single DB2 database product installed and you want to upgrade it to a new fix pack level, or if you want to install a DB2 database product at a particular fix pack level.
A universal fix pack services installations where more than one DB2 database product has been installed.
If national languages have been installed, you also require a separate national language fix pack.
If the type of fix pack that you are using affects the installation steps, this is noted in the following instructions.
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.
Before downloading DB2 Version 9.1 Fix Pack 1, perform the following steps:
This action prevents technical problems that might occur after the installation and configuration of the fix pack.
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
You need to have a file system with one gigabyte of free space to contain the .tar.gz file and the uncompressed installation image. If you also plan to install a national language fix pack, you need up to two gigabytes of free space.
The free space must be 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.
To determine the space used by the existing DB2 database products, perform the command:
du -k -s DB2DIR
where DB2DIR represents the location where the DB2 database product is installed.
Before installing DB2 Version 9.1 Fix Pack 1, perform the following steps:
There must not be any spaces in the directory path where you plan to download and uncompress the fix pack. If there are spaces in the directory path, the installation will fail. For example, make sure your directory path resembles the following:
/home/DB2FixPack/FP1/ ...
It should not resemble the following:
/home/DB2 FixPack/FP1/ ...
All fix pack installation images on the FTP site are compressed using gzip. Before you can apply the fix pack from this format, copy the image to a temporary directory and use gunzip and tar to extract the fix pack installation image.
To uncompress the fix pack installation images, perform the following steps:
gunzip -c filename.tar.gz | tar -xvf -where filename is the fix pack you are applying.
Before installing DB2 Version 9.1 Fix Pack 1, you must review and accept the license terms and conditions located in the db2/license directory of the uncompressed fix pack installation image.
If you use the fix pack image to install a licensed DB2 database product, a Try and Buy License will be installed. If you have a permanent license for the new DB2 database products, you can either:
The following tasks are required only if you already have DB2 database products installed in the selected installation path. You must ensure that all DB2 processes are stopped. If you have multiple DB2 copies, you need to stop only the DB2 processes that are associated with the copy that you are updating. For more information on the use of multiple copies of DB2, refer to http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/r0024057.htm
To stop all DB2 processes, perform the following steps:
DB2DIR/instance/db2ilistwhere DB2DIR represents the location where the DB2 copy is installed.
su - iname
. $HOME/sqllib/db2profile
db2 force applications all
db2 terminate
db2stop
db2licd -end # run at each physical node
exit
where iname represents the instance owner name.
If you are an HACMP(TM) user, you must use the ha_db2stop command to stop DB2 instead of the db2stop command. If you use the db2stop command instead of the ha_db2stop command, you will trigger a failure event.
su - aname
. $HOME/das/dasprofile
db2admin stop
exit
where aname represents the DAS owner name.
/usr/sbin/slibclean
ps -efFor example, on AIX the db2fmcu command is run from DB2DIR/bin directory, where DB2DIR is the location where the DB2 copy is installed.
db2fmcu -d
db2fm -i iname -Dwhere iname represents the instance owner name. The command must be performed once for each instance.
$HOME/sqllib/bin/ipclean
This section describes how to install DB2 Version 9.1 Fix Pack 1.
Use this method if a DB2 database product is already installed in the selected installation path and you want to apply a new fix pack level.
If there is more than one DB2 database product installed in the selected path, you must use the universal fix pack image.
The following restrictions apply to installing DB2 Version 9.1 Fix Pack 1:
For example, if a DB2 product with non-English support is installed at GA level, you would update it to Fix Pack 1 level by downloading the DB2 product's Fix Pack 1 image (or the universal Fix Pack 1 image) and the national language Fix Pack 1. Then run installFixPack from the DB2 product's Fix Pack 1 (or the universal Fix Pack 1) image.
To install DB2 Version 9.1 Fix Pack 1:
./installFixPack -b DB2DIRwhere DB2DIR is the location of the DB2 products that you want to update.
For additional information about this command, refer to http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/r0023700.htm
Use this method if either:
The following restrictions apply to installing DB2 Version 9.1 Fix Pack 1:
For example, if you want to install a DB2 product with non-English support, you would download the DB2 product's Fix Pack 1 image and the national language Fix Pack 1. Then run db2setup from the DB2 product's Fix Pack 1 image.
To install DB2 Version 9.1 Fix Pack 1:
./db2setup
For additional information about this command, refer to http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/r0008889.htm
After installing DB2 Version 9.1 Fix Pack 1, perform the following steps:
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.
If you have WebSphere Federation Server installed, you must run the djxlink command after installing DB2 Version 9.1 Fix Pack 1 and before running db2iupdt. Perform the following steps:
djxlink
This task is mandatory if you installed DB2 Version 9.1 Fix Pack 1 to update an existing installation. If you installed the fix pack to create a new installation, this task is not required.
If you have multiple DB2 copies, update the instances in the DB2 copy where you installed the fix pack. All instances in the DB2 copy must be updated after a fix pack is installed.
Perform the following steps:
DB2DIR/instance/db2ilistwhere DB2DIR represents the location where the DB2 copy is installed.
DB2DIR/instance/db2iupdt inamewhere iname represents the instance name and DB2DIR represents the location where the DB2 copy is installed.
DB2DIR/instance/dasupdtwhere DB2DIR is the location where the DB2 copy is installed. If this DB2 copy is now running at a more recent fix pack level than all of the other DB2 copies, consider updating the DAS to belong to this DB2 copy.
For more information on the db2iupdt or dasupdt commands, run these commands with the -h option.
This task is required if you installed DB2 Version 9.1 Fix Pack 1 to update an existing installation. If you installed the fix pack to create a new installation, this task is not required.
To restart an instance:
To restart the administration server, log in as the DAS owner and run the db2admin start command.
This section describes how and where to bind the database utilities (import, export, reorg, the Command Line Processor) and DB2 CLI bind files.
If you installed DB2 Version 9.1 Fix Pack 1 to update an existing DB2 copy, bind the database utilities and DB2 CLI bind files against all of the databases in the DB2 copy. If you installed the fix pack to create a new installation, this task is not required.
Issue the following commands once for each database in the DB2 copy 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.
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(TM) products, or a DB2 server product.
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.
If you are connecting to host databases, you also 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 ======= =================================================== OS/390 or z/OS BIND path/@ddcsmvs.lst BLOCKING ALL GRANT PUBLIC ACTION ADD SQLERROR CONTINUE VM BIND path/@ddcsvm.lst BLOCKING ALL GRANT PUBLIC ACTION ADD SQLERROR CONTINUE VSE BIND path/@ddcsvse.lst BLOCKING ALL GRANT PUBLIC ACTION ADD SQLERROR CONTINUE OS/400 BIND path/@ddcs400.lst BLOCKING ALL GRANT PUBLIC ACTION ADD SQLERROR CONTINUE
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 a list of bind files that are used for your specific client operating system, refer to: http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.doc/doc/c0005595.htm. If a bind file changes and your clients do not use that bind file, you do not need to bind it.
If you want to bind only a specific .bnd file to the database, issue the following commands for each database:
db2 terminate
db2 CONNECT TO dbname
db2 BIND path/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 files are located, andbind_file represents the name of the bind file.
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:
db2 connect to dbname db2 bind path/bnd/@db2gse.lst db2 terminatewhere 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.
Once a DB2 database product has been installed, additional DB2 database products can be added. If you use the db2setup command to add products, both the installed products and the new products being added should be at the same code level for a particular location (installation path).
If the new products are WebSphere Information Integration products, you will receive a warning message if you issue db2setup from a fix pack image that is at a lower level than the existing DB2 database products. You must apply the appropriate fix pack after the product installation is complete.
For all other DB2 database products, 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 in a particular DB2 copy, the installation attempt will not succeed.
After applying DB2 Version 9.1 Fix Pack 1, you can go back to an earlier fix pack level by reinstalling an earlier fix pack. Use the installFixPack command with the force option (-f) to bypass the level check. For example, to uninstall DB2 Version 9.1 Fix Pack 1, run the installFixPack command from within the DB2 Version 9.1 GA installation image, as follows:
./installFixPack -f -b DB2DIR
where DB2DIR is the location of the DB2 products that you want to force to a lower level fix pack image. For additional information about this command, refer to http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/r0023700.htm
The following sections detail problems and workarounds you must be aware of prior to installing DB2 Version 9.1 Fix Pack 1.
After installing a fix pack in an existing copy of DB2, you must update instances to use the new level of DB2. However, running the db2iupdt command overwrites the following scripts: db2profile and db2cshrc. If you previously changed either of these scripts, your changes will be lost after running the db2iupdt command. You can avoid the problem by making changes to userprofile and usercshrc instead of db2profile and db2cshrc, respectively.
The following requirements must be met before installing 64-bit DB2 for Linux on iSeries(TM) and pSeries(R):
On AIX, if you have the Trusted Computing Base (TCB) enabled on the system, before installing or uninstalling DB2 Version 9.1 Fix Pack 1 ensure that the TCB is in a consistent state for any file or directory related to a DB2 instance, DAS, and installed DB2 files. The TCB can be in an inconsistent state if, for example, DB2 instances were removed without using the db2idrop command.
You can check the TCB state by entering the following command as root:
tcbck -n ALL
See the AIX Security Guide for details regarding the Trusted Computing Base.
To contact IBM Support by phone:
The main Usenet newsgroup for DB2 database product-related questions is comp.databases.ibm-db2.
For information about changes to the product, read the product Release Notes and the What's New section of the product documentation. 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 at http://www.ibm.com/software/data/db2/udb/support.html.
DB2 Version 9.1 Fix Pack 1 can be downloaded from:
The following reference information is available:
The following list details the unique PTF labels for DB2 Version 9.1 Fix Pack 1:
The DB2 Client and DB2 Runtime Client are available on the FTP site. They only provide support for the English language. You must install both the client and the national fix pack in order to install the client with national language support. For example, to install a DB2 Client with national language support, download the Fix Pack 1 DB2 Client image and the national language Fix Pack 1. Then run db2setup from the Fix Pack 1 DB2 Client image.
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 are trademarks of International Business Machines Corporation in the United States, other countries, or both.
Windows is a registered trademark of Microsoft(R) 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. ** *******************************************************************************