IBM DB2 Universal Database Version 8.2 FixPak 4 and later (equivalent to Version 8.1 FixPak 11 and later) Readme Contents 1.0 Installing IBM DB2 Universal Database Version 8.2 FixPak 4 and later for AIX, HP-UX, Linux and Solaris Operating Environments 1.1 Pre-installation 1.1.1 Prerequisites 1.1.2 Product fix history 1.1.3 Prior to installing DB2 Version 8.2 FixPak 4 and later 1.2 Installation of Version 8.2 FixPak 4 and later 1.2.1 Installing DB2 Version 8.2 FixPak 4 and later 1.2.2 Installing DB2 Version 8 Alternate FixPak 1.3 Post-installation 1.3.1 Federated servers and the djxlink command 1.3.2 Updating instances to use the new level of DB2 1.3.3 Updating the system catalogs 1.3.4 Restarting the instances and administration server 1.3.5 Binding bind files 1.3.6 Restrictions to adding products using the db2setup command 2.0 Uninstallation of Version 8.2 FixPak 4 and later 2.1 Migrating database directory files from Version 8.2 back to Version 8.1 2.2 Uninstalling FixPaks or modification levels on Linux or UNIX 2.3 Uninstalling DB2 Version 8 Alternate FixPak 3.0 Known problems and workarounds 3.1 Known problems and workarounds (Version 8.2 FixPak 4 and later) 3.1.1 Instance update overwrites scripts db2profile and db2cshrc 3.2 Known problems and workarounds (prior to Version 8.2 FixPak 4) 3.2.1 FixPak level and installation of new products 3.2.2 IBM XL C/C++ Compiler run time must be installed (Linux iSeries and pSeries, 64-bit) 3.2.3 Connecting to host systems from DB2 Workgroup Server Edition and DB2 Express Edition is not permitted 3.2.4 Ensure Trusted Computing Base is in consistent state (AIX) 3.2.5 DB2 interprocess communications (IPCs) must be cleaned for instance update 3.2.6 Installing Query Patroller at FixPak 3 level or later 3.2.7 DB2 Data Links Manager installation when DB2 UDB Enterprise Server Edition already installed 4.0 How to get help 4.1 Where to download the FixPak installation images 5.0 Reference 5.1 Supported languages for DB2 clients available from the FTP site 5.2 Supported products and components by operating system 6.0 Notices 1.0 Installing IBM DB2 Universal Database Version 8.2 FixPak 4 and later for AIX, HP-UX, Linux and Solaris Operating Environments Before installing DB2 Universal Database(TM) (DB2(R) 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 and later. 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. 1.1 Pre-installation 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. 1.1.1 Prerequisites Consult the following Web sites for the latest software, hardware, operating system and product fix information: 1. For operating system requirements, see * http://www.ibm.com/software/data/db2/udb/sysreqs.html 2. For a list of all fixed bugs (called APARs) and support news, see * http://www.ibm.com/software/data/db2/support/db2_9/ If you are applying the FixPak on AIX(R), HP-UX, or Solaris Operating Environments, ensure you have the space required before applying the FixPak. The space required to install the FixPak is equal to the space required for the DB2 UDB, Version 8 general availability (GA) installation. (On AIX, this only applies if you use the -a option, for "apply" as opposed to "commit".) Linux(R) does not require additional space to apply a FixPak. To see the space used by the DB2 UDB, Version 8 GA installation, enter the following command: du -k -s where represents the installation directory: * On AIX: /usr/opt/db2_08_01 * On HP-UX and Solaris Operating Environments: /opt/IBM/db2/V8.1 Before applying the FixPak, ensure the space required (provided by the previous command) is available in the following directory: * On AIX: /usr/opt/db2_08_01 * On HP-UX: /var/adm/sw * On Solaris Operating Environments: /var/sadm If you have received special fixes from IBM(R) support, you must contact IBM support before you install DB2 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 Version 8 product installed at a lower VRMF (version, release, modification/maintenance level, and fix) level than this FixPak before you install Version 8.2 FixPak 4 and later. To determine if the required prerequisites are installed, issue the appropriate command for your operating system to display information about the currently installed version of DB2. The following table shows the command for each Linux and UNIX(R) operating system: +----------+------------------------+---------------------------------+ | Operatin | Command | Output to look for | | g System | | | +----------+------------------------+---------------------------------+ | AIX | lslpp -al | db2_08_01.client 8.1.0.0 or | | | "db2_08_01.client*" | later (for AIX 4.3.3) | | | | | | | | db2_08_01.client 8.1.1.0 or | | | | later (for AIX 5) | | | | | | | | Sample outputs for DB2 for AIX | | | | 4.3.3: | | | | db2_08_01.client 8.1.0.0 | | | | COMMITTED ... | | | | 8.1.0.3 COMMITTED ... | | | | 8.1.0.8 COMMITTED ... | | | | | | | | Check the largest installation | | | | signature that is | | | | returned (8.1.0.x) to make sure | | | | it is smaller | | | | than the VRMF of the current | | | | DB2 level. | | | | For AIX 5, the signature looks | | | | like 8.1.1.y. | +----------+------------------------+---------------------------------+ | HP-UX | swlist -l product | DB2V8CAE 8.1.0.x [product name] | | | "*DB2*" | | | | | or, | | | | | | | | PDB2... 8.1.0.x Product Patch | | | | | | | | where x must be smaller than | | | | the current | | | | level (the 4th digit in VRMF). | +----------+------------------------+---------------------------------+ | Linux | rpm -qa | grep db2 | db2cliv81-8.1.0-x | | | | | | | | db2cliv81-8.1.1-x on | | | | Linux/AMD64. | | | | where x must be smaller than | | | | the current | | | | level (the 4th digit in VRMF). | +----------+------------------------+---------------------------------+ | Solaris | pkginfo -l db2cliv81 | | VERSION: 8.1.0.x | | Operatin | grep VERSION | | | g | | where x must be smaller than | | Environm | | the current | | ent | | level (the 4th digit in VRMF). | +----------+------------------------+---------------------------------+ 1.1.2 Product fix history For a list of all product fixes (APARs) and support news, see Web site * http://www.ibm.com/software/data/db2/support/db2_9/ 1.1.3 Prior to installing DB2 Version 8.2 FixPak 4 and later Read the Known problems and workarounds sections before installing DB2 Version 8.2 FixPak 4 and later. 1.1.3.1 License terms and conditions Before installing DB2 Version 8.2 FixPak 4 and later, you must confirm you have reviewed and accept the license terms and conditions located in the "db2/license" directory. A new option on the installation command indicates your agreement to the license terms and conditions. The option must be specified for installation to continue. 1.1.3.2 Stopping all DB2 processes Before installing a FixPak, you must stop all of the DB2 processes. Note: You only need to stop the DB2 processes that are associated with the specific DB2 installation path that you are updating. For example, processes and instances running from an Alternate FixPak or from a different version of DB2 do not need to be stopped. 1. Switch to root authority by running the su - root command. 2. Run the following commands for each instance: su - . $HOME/sqllib/db2profile db2 force applications all db2 terminate db2stop db2licd -end # run at each physical node exit where 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. Otherwise, the db2stop command triggers a failure event. For more information on stopping an instance, see http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/admin/t0004897.htm 3. Run the following commands: su - . $HOME/das/dasprofile db2admin stop exit where represents the DAS owner name. 4. On AIX, you should also run slibclean to unload unused shared libraries from memory before installation: /usr/sbin/slibclean 5. Disable the Fault Monitor if it exists and is using DB2 Version 8. To disable the Fault Monitor Coordinator: a. Log on as root b. To locate where the db2fmcu command is to run from, issue the command: ps -ef For example, on AIX thedb2fmcu command is run from /usr/opt/db2_08_01/bin. c. Switch to the directory indicated by the ps command d. To disable the Fault Monitor Coordinator, issue the command: db2fmcu -d e. To stop the Fault Monitor Daemon, issue the command: db2fm -D 6. Ensure all DB2 interprocess communications (IPCs) are cleaned for the instance to be updated. As the instance owner, run the following command at each physical node: $HOME/sqllib/bin/ipclean 1.1.3.3 Directory path cannot contain spaces When you download and untar a FixPak or a modification level, make sure that there are no spaces in the directory path where the file was located. If there are spaces in the directory path, the installation will fail. For example, make sure your directory path resembles the following: /home/DB2FixPak/FP16/ ... It should not resemble the following: /home/DB2 FixPak/FP16/ ... 1.1.3.4 Ensure sufficient file system free space (AIX 4.3.3, AIX 5L, Linux, and Solaris Operating Environments) In addition to the software disk requirements, you need to have a file system with 2 gigabytes of free space to contain the tar.Z file or tar.gz file, and the uncompressed installation image. 1.1.3.5 Uncompressing FixPak installation images Some FixPak installation images on the FTP site or the FixPak CD are in compressed or gzipped format. Before you can apply the DB2 FixPak from these formats, you need to copy the image to a temporary directory and uncompress or gunzip the FixPak installation image. The compressed or gzipped images might have the file name FP16_$PTF.tar.Z or FP16_$PTF.tar.gz, where FP16_$PTF represents the latest FixPak operating system name and version. In addition to the software disk requirements, you must have a filesystem with 2 gigabytes of free space to contain the tar.Z or tar.gz file and the uncompressed image. Procedure To uncompress the FixPak installation images, perform the following steps: 1. Copy the compressed or gzipped image to a temporary file system containing at least 2 gigabytes of free space. 2. Change to the directory where you copied the image by entering cd /TMP, where /TMP represents the directory where you copied the compressed image. 3. If the product has the *.tar.Z extension, enter the following command: zcat filename.tar.Z | tar -xvf - where filename is the DB2 FixPak you are applying. 4. If the product has the *.tar.gz extension, enter the following command to uncompress: gunzip -c filename.tar.gz | tar -xvf - where filename is the DB2 FixPak you are applying. Note: gunzip is part of the AIX 5L(TM) default installation setup. If you do not have gunzip, install the rpm.rte fileset from the AIX 5L installation media. The rpm.rte fileset contains gunzip. You can also download gzip for AIX 5L from the Web site: http://www.ibm.com/systems/p/os/aix/linux/rpmgroups.html 5. If the compressed FixPak installation images are on a FixPak CD, there might be additional CDs with the file name extra.tar.Z or extra.tar.gz. Repeat these steps for each CD. 1.1.3.6 Uncompressing Version 8 Alternate FixPak installation images Some Alternate FixPak installation images on the FTP site or the FixPak CD are in compressed or gzipped format. Before you can apply the DB2 Alternate FixPak from these formats, you need to copy the image to a temporary directory and uncompress or gunzip the Alternate FixPak installation image. The compressed or gzipped images might have the file extension .tar.Z or .tar.gz. Alternate FixPak installation images have the following filenames: * FP#_PTF#_ESE_MFP for AIX 4.3.3 and Solaris Operating Environments * FP#_PTF#_ESE_MFP_SBCS for single-byte character set (SBCS) code pages on AIX 5 * FP#_PTF#_ESE_MFP_DBCS for double-byte character set (DBCS) code pages on AIX 5 where FP# is the FixPak number (for example, "FP15") and $PTF represents a PTF identifier (for example, "U810952"). Notes: 1. The Alternate FixPaks labelled FP#_PTF#_ESE_MFP_SBCS support the following languages: English, Brazilian, Danish, Finnish, French, German, Italian, Norwegian, Portuguese, Spanish, and Swedish. 2. The Alternate FixPaks labelled FP#_PTF#_ESE_MFP_DBCS supports the following languages: English, Japanese, Korean, Simplified Chinese, and Traditional Chinese. In addition to the software disk requirements, you must have a filesystem with 2 gigabytes of free space to contain the tar.Z or tar.gz file and the uncompressed image. Procedure To uncompress the FixPak installation images, perform the following steps: 1. Copy the compressed or gzipped image to a temporary file system containing at least 2 gigabytes of free space. 2. Change to the directory where you copied the image by entering cd /TMP, where /TMP represents the directory where you copied the compressed image. 3. If the product has the *.tar.Z extension, enter the following command: zcat filename.tar.Z | tar -xvf - where filename is the DB2 Alternate FixPak you are applying. 4. If the product has the *.tar.gz extension, enter the following command to uncompress: gunzip -c filename.tar.gz | tar -xvf - where filename is the DB2 Alternate FixPak you are applying. Note: gunzip is part of the AIX 5L default installation setup. If you do not have gunzip, install the rpm.rte fileset from the AIX 5L installation media. The rpm.rte fileset contains gunzip. You can also download gzip for AIX 5L from the Web site: http://www.ibm.com/systems/p/os/aix/linux/rpmgroups.html 5. If the compressed Alternate FixPak installation images are on a FixPak CD, there might be additional CDs with the file name extra.tar.Z or extra.tar.gz. Repeat these steps for each CD. 1.1.3.7 Data Warehouse functionality backup (AIX, Linux, and Solaris Operating Environments) If you are running Data Warehouse functionality on Linux, for example the Data Warehouse Agent that comes with some server products, you need to back up your /opt/IBM/db2/V8.1/bin/IWH.environment. If you have this file, back it up before applying DB2 Version 8.2 FixPak 4 and later. On AIX and Solaris, you should back up the same file (for AIX, this file is found in /usr/opt/db2_08_01/bin/IWH.environment). 1.2 Installation of Version 8.2 FixPak 4 and later This section details Installing DB2 Version 8.2 FixPak 4 and later and installing an Alternate FixPak. 1.2.1 Installing DB2 Version 8.2 FixPak 4 and later Ensure that your system has met all of the installation prerequisites including operating system patches prior to the installation of DB2 Version 8.2 FixPak 4 and later as detailed in the Prerequisites section. This action prevents technical problems that might occur after the installation and configuration of DB2 UDB. Read the Known problems and workarounds sections before installing DB2 Version 8.2 FixPak 4 and later. Restrictions The following restrictions apply to installing DB2 Version 8.2 FixPak 4 and later: * On AIX, the installFixPak script provides installation prerequisite checking that is not provided when you install DB2 Version 8.2 FixPak 4 and later using SMIT or installp. Using SMIT is still supported, but installFixPak is the only method documented in this readme. For instructions on using SMIT, see your AIX manuals. It is strongly recommended that you use the installFixPak script to install DB2 Version 8.2 FixPak 4 and later. * For DB2 Version 8 for HP-UX on IA64, do not use the SAM utility to install the FixPak. The only supported method to apply the FixPak is to run the installFixPak command delivered with the current FixPak image. * On Linux, when you have installed DB2 Version 8.2 FixPak 4 and later, you cannot back it out and return to the previous DB2 level. You must uninstall and reinstall the desired product level, FixPak level, or both. Procedure To install DB2 Version 8.2 FixPak 4 and later: 1. You must be logged on as root. 2. Change to the directory in which the installation image is located. 3. To launch the installation, enter: ./installFixPak -y where the -y option indicates your agreement to the license terms and conditions. The -y option must be specified for installation to continue. Note: By default, the installFixPak command will commits all of the updated file sets on AIX. On AIX, if you do not want to commit the updates, you should issue the installFixPak command with the -a option (for "apply" as opposed to "commit") as follows: ./installFixPak -y -a 1.2.2 Installing DB2 Version 8 Alternate FixPak DB2 UDB Enterprise Server Edition (ESE) operating on Linux or UNIX operating systems supports the coexistence of multiple levels of code for the same release on your system. This support is referred to as Multiple FixPak (MFP) support. MFP support is accomplished through the use of Alternate FixPaks (AFP). AFPs allow FixPaks or modification levels to be installed to an alternate path. That is, a different installation path with a different file set or package name. In this case, the operating system treats the DB2 code installed to an alternate path as different software. Restrictions: * Each AFP has its own unique installation path. That path is fixed and cannot be changed. You cannot install an AFP to an arbitrary location of your choice. * If you install DB2 Version 8 Alternate FixPaks without an installed and licensed copy of DB2 Version 8, you need to obtain the license key from the Version 8 release level media. You can then install the license by using the db2licm command. * DB2 UDB Version 8 FixPak 9 Alternate FixPak and DB2 UDB Version 8 FixPak 9a Alternate FixPak cannot coexist. If you want to install the DB2 UDB Version 8 FixPak 9a Alternate FixPak on a system that already has the DB2 UDB Version 8 FixPak 9 Alternate FixPak installed, you must uninstall DB2 UDB Version 8 FixPak 9 before installing the DB2 UDB Version 8 FixPak 9a Alternate FixPak. * Response file installations for Alternate FixPaks are not supported. Prerequisites: * You need root authority. * You need a copy of the DB2 Version 8 Alternate FixPak image. Refer to the section called "Where to download the FixPak installation images" in this readme. To install this DB2 Version 8 Alternate FixPak for Enterprise Server Edition (ESE) on a Linux or UNIX operating system: 1. Run the installAltFixPak -y utility from the directory where you untarred the image for DB2 Version 8 Alternate FixPak. The -y option indicates your agreement to the license terms and conditions and must be specified for installation to continue. 2. The install program checks to see if DB2 Version 8 is installed in the GA path. If it detects an existing DB2 Version 8 installation in the GA path, it prompts you to install the same file sets or packages from the DB2 Version 8 Alternate FixPak. * If the answer is yes, then the installation program proceeds to install the same set of file sets or packages as are already installed. * If the answer is no, or if DB2 Version 8 was not detected in either /usr/opt/db2_08_01 (on AIX), or /opt/IBM/db2/V8.1 (on other platforms), then it starts db2_install. Note: No licenses are shipped with the DB2 Version 8 Alternate FixPak; licenses must be installed from the Version 8 release level media. 1.3 Post-installation After installing DB2 Version 8.2 FixPak 4 and later, do the following: * For federated servers that access relational data sources, run the djxlink command for each data source. * Update instances to use the new level of DB2 * Update the system catalogs * Restart the instances, and * Bind the bind files After applying a FixPak, 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.3.1 Federated servers and the djxlink command If you have federated servers that access relational data sources, you must run the djxlink command for each data source. You must run the command after installing DB2 Version 8.2 FixPak 4 and later and before running db2iupdt. Perform the following steps: 1. Log on as root. 2. Remove or rename the file djxlink.out, which is located in the $install_dir/lib/ directory, where $install_dir is the DB2 installation directory. 3. If you are using Relational Connect to connect to an Oracle data source, set the environment variable ORACLE_HOME to the Oracle home directory. 4. Run the command: djxlink 1.3.2 Updating instances to use the new level of DB2 This task is mandatory if you installed a FixPak to update an existing installation. If you installed the FixPak to create a new installation with new instances, this task is not required. You must update all of the existing instances that are associated with the installation path (or copy of DB2 UDB) where you installed the FixPak. In addition, you can choose to update existing instances that are associated with another installation path to use the new level of DB2 UDB. Prerequisite: * You need to be logged on as root to update the instances. * Ensure that the instance you are updating and all of its DB2 processes are stopped. Refer to "Stopping all DB2 processes". 1. For each instance, issue the command: /instance/db2iupdt where represents the instance name and represents the installation path where you installed the FixPak. 2. Run the dasupdt command if the DB2 administration server (DAS) is a DB2 UDB Version 8 DAS and exists in the installation path where you installed the FixPak. To update the DAS, issue the command: /instance/dasupdt where represents the DAS owner name and represents the installation path where you installed the FixPak. Notes: 1. If an instance is being downgraded from a higher FixPak level to a lower level and it is being moved to a new copy of DB2 (in a new installation path), you must specify the option '-D' command parameter with the db2iupdt command. 2. If you are updating a DB2 instance or DAS from an existing code level (the original installation path) to a new code level (a new installation path), never remove the "original" installation path before you run the db2iupdt and dasupdt commands. When db2iupdt and dasupdt have completed successfully and if no other instance is using the code level, you can then uninstall the copy of DB2 UDB that the instance was originally linked to. 3. The Fault Monitor Coordinator is automatically added to /etc/inittab when you install a FixPak. If you want to disable the Fault Monitor Coordinator, you will need to remove the db2fmcd entry from /etc/inittab after you install a FixPak. For example, issue the following command while logged in as a root or superuser: db2fmcu -d The following is an example of two options for updating an existing instance to a new level of DB2: An instance db2inst1 is currently running against Alternate FixPak 1. If you want to update the instance to run at the code level delivered in this FixPak, you can perform one of the following: 1. Install the DB2 Version 8 Alternate FixPak delivered in this FixPak, then update your instance. For example: a. Install this Version 8 Alternate FixPak. b. Stop db2inst1. c. Run /instance/db2iupdt db2inst1, where refers to the installation path for this Version 8 Alternate FixPak: * On AIX, the is: /usr/opt/db2_08_FP16 * On Linux and other UNIX operating systems, the is: /opt/IBM/db2/V8.FP16 2. Install the regular DB2 Version 8.2 FixPak 4 and later FixPak delivered in this FixPak, then update your instance. For example: a. Install the regular DB2 Version 8.2 FixPak 4 and later FixPak on top of the Version 8.1 GA (General Availability) code or any previous Version 8.1 level code. b. Stop db2inst1. c. Run /instance/db2iupdt db2inst1 where refers to the installation path for Version 8.1 GA. Note that in this example, the instance is moved from a lower code level to a higher code level. The same procedure can be used if you want to move to a lower code level. In that case, you must use the -D flag when running the db2iupdt command. For more information on the db2iupdt or dasupdt commands, run these commands with the -h option. 1.3.3 Updating the system catalogs 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. 1.3.4 Restarting the instances and administration server To restart an instance: 1. Log in as the instance owner and enter the db2start command. 2. Repeat for each instance. To restart the administration server, log in as the DAS owner and run the db2admin start command. 1.3.5 Binding bind files You need to bind your DB2 utilities against all your databases after installation. This step is necessary for the fixes to complete the installation and ensure that the right code level is used. The procedure of binding, which follows, needs to be performed only once per database. 1.3.5.1 Binding to DB2 UDB databases After applying fixes, you must issue one of the following command sequences: At a command prompt, enter: db2 terminate db2 CONNECT TO db2 BIND /@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD db2 terminate or at the DB2 command line, enter: TERMINATE CONNECT TO BIND /@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD TERMINATE Where represents the name of a database to which the utilities should be bound, and where represents 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 UDB. Packages that are already bound will return an SQL0719 error. This is expected. 1.3.5.2 Binding db2schema.bnd to existing databases After installation on the server, an additional bind file needs to be bound to existing databases. This requirement does not apply to clients. Procedure To bind db2schema.bnd on the server, execute one of these command sequences: At a command prompt: db2 terminate db2 CONNECT TO db2 BIND /db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue db2 terminate or at the DB2 command line: TERMINATE CONNECT TO BIND /db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue TERMINATE where represents the name of a database to which the utilities should be bound, and where is the full path name of the directory where the bind files are located. 1.3.5.3 Binding federated databases If you have existing federated databases, you must bind the bind files db2dsproc.bnd and db2stats.bnd after you install a DB2 FixPak or patch. Prerequisites To bind the bind files, you must have one of the following authorities: * SYSADM or DBADM authority * ALTERIN privilege on the schema * BIND privilege on the package Procedure To bind the bind files db2dsproc.bnd and db2stats.bnd, connect to the database and execute the BIND command. For example: db2 connect to db2 bind /db2dsproc.bnd blocking all grant public db2 bind /db2stats.bnd blocking all grant public db2 terminate where represents the name of the federated database, and where represents the full path name of the directory where the bind files are located, such as $HOME/sqllib/bnd where $HOME represents the DB2 instance home directory. For syntax and options for the BIND command, refer to the DB2 Command Reference. 1.3.5.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 FixPak or patch. The db2gse.lst file contains the names of the bind files for the stored procedures that DB2 Spatial Extender provides. Prerequisites To bind the db2gse.lst file, you must have one of the following authorities: * SYSADM or DBADM authority * ALTERIN privilege on the schema * BIND privilege on the package Procedure To bind the db2gse.lst file: 1. Change to the instance directory where the bind files are located. Enter the following command: cd $HOME/sqllib/bnd where $HOME is the instance owner's home directory. 2. Connect to the database and execute the BIND command. For example, enter: db2 connect to db2 bind /home/instance/sqllib/bnd/@db2gse.lst db2 terminate where represents the name of the spatial-enabled database. For syntax and options for the BIND command, refer to the DB2 Command Reference. 1.3.5.5 Binding host databases 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 ======= =================================================== MVS BIND /@ddcsmvs.lst BLOCKING ALL GRANT PUBLIC ACTION ADD SQLERROR CONTINUE VM BIND /@ddcsvm.lst BLOCKING ALL GRANT PUBLIC ACTION ADD SQLERROR CONTINUE VSE BIND /@ddcsvse.lst BLOCKING ALL GRANT PUBLIC ACTION ADD SQLERROR CONTINUE OS400 BIND /@ddcs400.lst BLOCKING ALL GRANT PUBLIC ACTION ADD SQLERROR CONTINUE where represents the full path name of the directory where the bind files are located, such as $HOME/sqllib/bnd where $HOME represents the DB2 instance home directory. See "Binding Applications and Utilities" in the DB2 Connect(TM) User's Guide for a list of bind files that are used for your specific client operating system. If a bind file changes and your clients do not use that bind file, you do not need to bind it. 1.3.5.6 Binding specific bind files If you want to bind only a specific bind file to the database, issue one of the following command sequences for each database. At a command prompt, enter: db2 terminate db2 CONNECT TO db2 BIND / BLOCKING ALL GRANT PUBLIC sqlerror continue db2 terminate or at the DB2 command line, enter: TERMINATE CONNECT TO BIND / BLOCKING ALL GRANT PUBLIC sqlerror continue TERMINATE where represents the name of the bind file, is the full path name of the directory where the bind files are located, and represents the name of your database. 1.3.5.7 Binding database utilities using the Run-Time Client The Run-Time Client cannot be used to bind the database utilities (IMPORT, EXPORT, REORG, the Command Line Processor) and DB2 CLI bind files. You must use the DB2 Administration Client or the DB2 Application Development Client instead. You must bind the database utilities (IMPORT, EXPORT, REORG, the Command Line Processor) and DB2 CLI bind files to each database before they can be used with that database. In a network environment, if you are using multiple clients that run on different operating systems or that are at different DB2 version or service levels, you must bind the utilities once for each operating system and DB2 client-version combination. 1.3.6 Restrictions to adding products using the db2setup command Once a DB2 product has been installed, additional DB2 products can be added. If you use the db2setup command to add products the following recommendations and restrictions apply. Recommendations Both the installed product and the product being added should be at the same code level. For example, DB2 ESE Server Version 8 FixPak 15 is already installed and you want to add a WebSphere(R) Information Integration solution. In this case, the WebSphere Information Integration solution should also be at the Version 8 FixPak 15 level. Restrictions * If the DB2 FixPak level is higher than the FixPak level of the product being added, the combination is allowed. However, since the FixPak level of the product being added is lower than the DB2 FixPak level, the DB2 FixPak level must be reapplied after installing the additional product. See the appropriate FixPak Readme for instructions to reapply the FixPak. * If the DB2 FixPak level is lower than the FixPak level of the product being added, an error is generated. The product being added cannot be at a higher FixPak level than DB2. In this case, you must first bring DB2 to the appropriate level, then install the additional product. See the appropriate FixPak Readme for instructions. The following table summarizes the db2setup combinations: Table 1. db2setup combinations +------------+-------------+------------------------------------------+ | DB2 FixPak | Additional | Is this combination permitted? | | level | product | | | | FixPak | | | | level | | +------------+-------------+------------------------------------------+ | Version 8 | Version 8 | Yes. This is recommended. | | FixPak 3 | FixPak 3 | | +------------+-------------+------------------------------------------+ | Version 8 | Version 8 | Yes, but Version 8 FixPak 3 must be | | FixPak 3 | GA | reapplied. See the appropriate FixPak | | | | Readme for instructions to reapply the | | | | FixPak by going to the DB2 Support Web | | | | site. | +------------+-------------+------------------------------------------+ | Version 8 | Version 8 | No. DB2 must first be brought to the | | FixPak 3 | FixPak 5 | higher fix pack level (in this example, | | | | Version 8 FixPak 5) before installing | | | | the additional product. See the | | | | appropriate FixPak Readme for | | | | instructions to install the required | | | | Version 8 FixPak by going to the DB2 | | | | Support Web site. | +------------+-------------+------------------------------------------+ The DB2 Support Web site address is http://www.ibm.com/software/data/db2/support/db2_9/ 2.0 Uninstallation of Version 8.2 FixPak 4 and later 2.1 Migrating database directory files from Version 8.2 back to Version 8.1 In DB2 UDB Version 8.2. two new fields were added to the database entry structure, therefore the database directory file structure has changed. When migrating from Version 8.1 to Version 8.2 the database directory files will be migrated automatically. However, to demigrate the database directory files from Version 8.2 to Version 8.1, db2demigdbd is required to convert the current database directory files to the Version 8.1 format. The db2demigdbd tool is available as part of the Linux and UNIX FixPak install. It can also be located directly on the Linux and UNIX FixPak CD, without installing the FixPak. On Windows(R), Linux, and UNIX, the db2demigdbd tool is downloadable from the IBM anonymous FTP server at ftp.software.ibm.com/ps/products/db2/tools. You can find documentation for the db2demigdbd 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 db2demigdbd tool, search the Technotes database at http://www.ibm.com/software/data/db2/support/db2_9/ using the keywords "db2demigdb tool". 2.2 Uninstalling FixPaks or modification levels on Linux or UNIX Note: If you have received special fixes from IBM Support that you have applied to the DB2 UDB Version 8.2 FixPak 4 and later level, you will lose all of the special fixes when you uninstall DB2 UDB Version 8.2 FixPak 4 and later. The special fixes you received from IBM Support are only applicable to your current version. You should not apply the same special fixes on top of a backlevel version. If this applies to you, contact IBM Support before uninstalling DB2 UDB Version 8.2 FixPak 4 and later. Before uninstalling DB2 UDB Version 8.2 FixPak 4 and later, ensure that you: * Stop all instances and DAS * Backup your data AIX If DB2 UDB Version 8.2 FixPak 4 and later was installed and the file sets were applied but not committed, DB2 UDB Version 8.2 FixPak 4 and later can be rejected using SMIT. See the SMIT documentation for more details. If the file sets were committed when DB2 UDB Version 8.2 FixPak 4 and later was installed, which is the default, DB2 UDB Version 8.2 FixPak 4 and later cannot be rejected. The only course of action available is to uninstall DB2 UDB from your system, reinstall DB2 UDB Version 8, and bring DB2 UDB up to the desired level by applying the corresponding level of DB2 UDB. If you have the Trusted Computing Base (TCB) enabled on the system, before uninstalling DB2 UDB Version 8.2 FixPak 4 and later you need to ensure that the TCB is in a consistent state. See the Known problems and workarounds section in this readme for details. HP-UX DB2 UDB Version 8.2 FixPak 4 and later file sets can be uninstalled using the sam utility. If you use swlist or sam, you can list all file sets for DB2 UDB Version 8.2 FixPak 4 and later and receive output similar to the following: PDB2_810100010 8.1.0.8 PDB2_810100011 8.1.0.8 PDB2_810300011 8.1.0.24 PDB2_810300010 8.1.0.24 The installation signature is combined with the name of the file set. You should uninstall the group of PDB2_* file sets with the same signature starting with the largest number. You can remove DB2 UDB Version 8.2 FixPak 4 and later, or the latest version plus the second last, and so on. You can also select them all. Linux You cannot uninstall DB2 UDB Version 8.2 FixPak 4 and later on Linux. The only course of action available is to uninstall DB2 UDB from your system, reinstall DB2 UDB Version 8, and bring DB2 UDB up to the desired level by applying the corresponding level of DB2 UDB. A db2_deinstall script is provided with DB2 UDB Version 8.2 FixPak 4 and later which will uninstall DB2 UDB from your system. Solaris Operating Environment The backoutallpatch script is provided with all version images. Run this script to uninstall DB2 UDBVersion 8.2 FixPak 4 and later and leave the system in the state that it was before installing DB2 UDB Version 8.2 FixPak 4 and later. You can find this script in /var/sadm/patch. The script will be named backoutallpatch.8.1.x.y where 8.1.x.y corresponds to the VRMF of DB2 UDB Version 8.2 FixPak 4 and later. The files required to uninstall a FixPak or modification level are stored in /var/sadm. Disk space requirements for each FixPak or modification level in /var/sadm can reach almost the same amount of disk space required by DB2 in /opt/IBM/db2/V8.1. You must uninstall from the highest to the lowest level until you have uninstalled the version that you want to remove. For example if you are at FixPak 3 and installed FixPak 1 and modification level 2 before FixPak 3 was installed, you would not be able to uninstall FixPak 1 unless you have uninstalled modification level 2 and FixPak 3. Update all instances and the DAS. 2.3 Uninstalling DB2 Version 8 Alternate FixPak This task provides steps for removing DB2 Version 8 products using the db2_deinstall command. The db2_deinstall command removes all DB2 products from your system in the corresponding installation path. If you want to remove a subset of DB2 products, use your operating system's native tools to remove DB2 components, packages, or file sets. Prerequisites Before you remove DB2 products from your Linux or UNIX system: * You must have root authority to remove DB2 products. * The db2_deinstall command is found in the root directory on all DB2 installable images (regular or Alternate FixPak). Procedure To remove an Alternate FixPak from your system: 1. Log in as user with root authority. 2. Locate the copy of db2_deinstall that came with the Alternate FixPak you want to remove. For example, you cannot use the db2_deinstall script that came with Alternate FixPak x to remove Alternate FixPak y. 3. Run the db2_deinstall -n command. There are alternative methods for removing DB2 products from your operating system. You may employ one of these methods if you only want to remove a subset of DB2 products from your system. For example on HP-UX, alternative methods for removing DB2 products include using the swremove command. 3.0 Known problems and workarounds The following sections detail problems and workarounds you must be aware of prior to installing DB2 UDB Version 8.2 FixPak 4 and later. 3.1 Known problems and workarounds (Version 8.2 FixPak 4 and later) Limitations and known problems for DB2 database products are documented in technotes and APARs on the DB2 for Linux, UNIX and Windows product support Web site: http://www.ibm.com/software/data/db2/support/db2_9/ As problems are discovered and resolved, those resources are updated. By searching the knowledge base, you can quickly find workarounds or solutions to problems. The following links launch customized queries of the technotes and APARs: * View all technotes for DB2 UDB Version 8: http://www.ibm.com/support/search.wss?rs=71+56&dc=DB520+D600&dtm&atrn1=SWVersion&atrv1=8&tc=SSEPGG+SSEPDU * View all APARs for DB2 UDB Version 8: http://www.ibm.com/support/search.wss?rs=71+56&apar=only&tc=SSEPGG&atrn=SWVersion&atrv=8*&atrn1=&atrv1=&atrwcs=on&lang=all&dr=all&r=10&cc=us To create your own query, go to the Advanced search page on the IBM Software Support Web site: http://www.ibm.com/support/advsrch.wss 3.1.1 Instance update overwrites scripts db2profile and db2cshrc After installing a FixPak, to use the new level of DB2, you must update instances. However, running the db2iupdt command overwrites the following scripts: db2profile and db2cshrc. If you previously edited either of these scripts, your changes will be lost after running the db2iupdt command. 3.2 Known problems and workarounds (prior to Version 8.2 FixPak 4) 3.2.1 FixPak level and installation of new products 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. If you have installed Alternate FixPaks (AFPs), this restriction also applies. Since each AFP has its own unique installation path, all products installed in that installation path must be at 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. 3.2.2 IBM XL C/C++ Compiler run time must be installed (Linux iSeries and pSeries, 64-bit) The following requirements must be met before installing 64-bit DB2 for Linux on iSeries(TM) and pSeries(R): 1. Running on iSeries or pSeries hardware supported by the Linux distribution. 2. Running a Linux distribution supported by DB2. See http://www.ibm.com/software/data/db2/linux/validate/ 3. Download and install the IBM XL C/C++ Advanced Edition V7.0 for Linux Run-Time Environment Component. For more information, see www.ibm.com/support/docview.wss?uid=swg24007906 or follow these steps: a. Visit the XL C/C++ support page at: www.ibm.com/software/awdtools/xlcpp/support/ b. Under the "Download" heading, select "Fixes by version". c. Under the "Linux" heading, find "XL C/C++ Advanced Edition V7.0 for Linux Runtime Environment" and select "Latest updates". 3.2.3 Connecting to host systems from DB2 Workgroup Server Edition and DB2 Express Edition is not permitted 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 initiating a host connection is disabled by removing file db2jcc_license_cisuz.jar. This change affects the following Version 8.2 products: * DB2 UDB Express Edition * DB2 UDB Express Edition CPU Option * DB2 UDB Workgroup Server Edition * DB2 UDB Workgroup Server Unlimited Edition. 3.2.4 Ensure Trusted Computing Base is in consistent state (AIX) On AIX, if you have the Trusted Computing Base (TCB) enabled on the system, before installing or uninstalling DB2 UDB Version 8.2 FixPak 4 and later you need to 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 If the TCB is not in a consistent state, installing, uninstalling, or rejecting DB2 UDB Version 8.2 FixPak 4 and later can fail and leave some DB2 filesets in a broken state. See the AIX Security Guide for details regarding the Trusted Computing Base. 3.2.5 DB2 interprocess communications (IPCs) must be cleaned for instance update You must clean up all DB2 interprocess communications (IPCs) for the instance to be updated. Otherwise, the instance update might have errors or the db2start command might fail after the instance is updated. All DB2 IPCs must be cleaned on all nodes for the instance. See the "Stopping all DB2 processes" section for details. 3.2.6 Installing Query Patroller at FixPak 3 level or later Query Patroller is a query management system used to control the flow of queries against your DB2 database. In DB2 UDB Version 8.1.2, DB2 Query Patroller became a stand-alone product. It was no longer a component of the DB2 Warehouse Manager. If you have DB2 UDB Version 8 FixPak 3 or later installed and you install the DB2 Query Patroller base or GA version, you must reapply the DB2 FixPak level. Otherwise, the Query Patroller changes are not applied at the DB2 FixPak level. If you are installing the Query Patroller server, you must also update the DB2 instances after reapplying the DB2 FixPak level. This is mandatory. See the Updating instances to use the new level of DB2 section in this readme for details. After the instances are updated they must be restarted. See the Restarting the instances section of this readme for details. Updating instances to use the new level of DB2, and, Restarting the instances are subsections of the After installation section. 3.2.7 DB2 Data Links Manager installation when DB2 UDB Enterprise Server Edition already installed The DB2 Data Links Manager installation will fail when creating the dlfm instance if DB2 UDB ESE is already installed on the machine. The workaround is to modify the response file and continue or to perform a response file installation to install the DB2 Data Links Manager. For more information on response files, see the Installation and Configuration Supplement or search for "response file" in the Information Center. 4.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 product-related questions is comp.databases.ibm-db2. For information about changes to the product, read 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 at http://www.ibm.com/software/data/db2/support/db2_9/. You can also 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. You can also review the Release Notes after installing DB2 Version 8.2 FixPak 4 and later: AIX | /usr/opt/db2_08_01/Readme/%L/Release.Notes -----------------------+--------------------------------------------- HP-UX, Linux, and | /opt/IBM/db2/V8.1/Readme/%L/Release.Notes Solaris Operating | Environment | where %L represents the locale name, for example, english-us, spanish, german. The Websphere Federation Server Release Notes are found at: http://www.ibm.com/support/docview.wss?rs=3170&context=SS2K5T&uid=swg27007246 4.1 Where to download the FixPak installation images DB2 UDB Version 8.2 FixPak 4 and later and Alternate FixPaks can be downloaded from the DB2 product support Web site: http://www.ibm.com/software/data/db2/support/db2_9/ In particular, refer to the "Fixes by version" document in the Download section of the Web site. Ensure that you choose the appropriate fix pack for your operating system. In most cases, you can either choose to access the FTP folder directly or you can use a Java(TM) applet called Download Director to download the files. 5.0 Reference The following reference information is available: * Supported languages for DB2 clients * Supported products and components by operating system. 5.1 Supported languages for DB2 clients available from the FTP site The following table details the supported languages for DB2 clients that are available from the FTP site. +------------+--------------------+----------------------+------------+ | Operating | DB2 Administration | DB2 Application | DB2 | | System | Client | Development Client | Run-Time | | | | | Client | +------------+--------------------+----------------------+------------+ | AIX 4.3.3 | * SBCS1 (English, | * SBCS1 (English, | All | | (32-bit) | French, German, | French, German, and | supported | | | and Italian) | Italian) | languages | | | * SBCS2 (English, | * SBCS2 (English, | are in one | | | Brazilian | Brazilian | tarred | | | Portuguese, and | Portuguese, and | file | | | Spanish) | Spanish) | | | | * NORDIC | * NORDIC (English, | | | | (English, Danish, | Danish, Finnish, | | | | Finnish, | Norwegian, and | | | | Norwegian, and | Swedish) | | | | Swedish) | * DBCS (English, | | | | * DBCS (English, | Japanese, Korean, | | | | Japanese, Korean, | Simplified Chinese, | | | | Simplified | and Traditional | | | | Chinese, and | Chinese) | | | | Traditional | | | | | Chinese) | | | +------------+--------------------+----------------------+------------+ | AIX 5L | * SBCS (English, | * SBCS (English, | All | | (32-bit | Brazilian | Brazilian | supported | | and | Portuguese, | Portuguese, Danish, | languages | | 64-bit) | Danish, Finnish, | Finnish, French, | are in one | | | French, German, | German, Italian, | tarred | | | Italian, | Norwegian, Spanish, | file | | | Norwegian, | and Swedish) | | | | Spanish, and | * DBCS (English, | | | | Swedish) | Japanese, Korean, | | | | * DBCS (English, | Simplified Chinese, | | | | Japanese, Korean, | and Traditional | | | | Simplified | Chinese) | | | | Chinese, and | | | | | Traditional | | | | | Chinese) | | | +------------+--------------------+----------------------+------------+ | HP-UX 11i | All supported | All supported | All | | (PA-RISC) | languages are in | languages are in one | supported | | and HP-UX | one tarred file | tarred file | languages | | 11i v2 | | | are in one | | (IA64) | | | tarred | | (32-bit | | | file | | and | | | | | 64-bit) | | | | +------------+--------------------+----------------------+------------+ | Linux | All supported | All supported | All | | | languages are in | languages are in one | supported | | | one tarred file | tarred file | languages | | | | | are in one | | | | | tarred | | | | | file | +------------+--------------------+----------------------+------------+ | Solaris | All supported | All supported | All | | Operating | languages are in | languages are in one | supported | | Environmen | one tarred file | tarred file | languages | | ts | | | are in one | | | | | tarred | | | | | file | +------------+--------------------+----------------------+------------+ | Windows | All supported | All supported | All | | | languages are in | languages are in one | supported | | | one | self-extracting zip | languages | | | self-extracting | file | are in one | | | zip file | | self-extra | | | | | cting zip | | | | | file | +------------+--------------------+----------------------+------------+ 5.2 Supported products and components by operating system DB2 products continue to be supported on AIX 4.3.3 and Solaris 7 until DB2 Version 8.1 goes out of service. Existing installs of DB2 as well as new installs of DB2 products are recommended to upgrade to a more current version of AIX, such as AIX 5.3, because AIX 4.3.3 is now out of service, and to a more current version of Solaris, such as Solaris 9. The following lists show the supported products and components for each Linux and UNIX operating system: AIX 5L (32-bit and 64-bit) Product list: * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 Connect for iSeries, Version 8 * DB2 Cube Views(TM), Version 8 * DB2 Data Links Manager, Version 8 * DB2 Information Center, Version 8 * DB2 PDF Documentation, Version 8 * DB2 Query Patroller, Version 8 * DB2 Run-Time Client, Version 8 * DB2 Spatial Extender, Version 8 * DB2 UDB Enterprise Server Edition, Version 8 * DB2 UDB Workgroup Server Edition, Version 8 * DB2 UDB Workgroup Server Unlimited Edition, Version 8 * DB2 Warehouse Manager, Version 8 HP-UX 11i (PA-RISC, 32-bit and 64-bit) Product list: * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 Connect for iSeries, Version 8 * DB2 Data Links Manager, Version 8 * DB2 Information Center, Version 8 * DB2 PDF Documentation, Version 8 * DB2 Query Patroller, Version 8 * DB2 Run-Time Client, Version 8 * DB2 Spatial Extender, Version 8 * DB2 UDB Enterprise Server Edition, Version 8 * DB2 UDB Workgroup Server Edition, Version 8 * DB2 UDB Workgroup Server Unlimited Edition, Version 8 HP-UX 11i v2 (IA64) Product list: * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 Connect for iSeries, Version 8 * DB2 Run-Time Client, Version 8 * DB2 UDB Enterprise Server Edition, Version 8 * DB2 UDB Workgroup Server Edition, Version 8 * DB2 UDB Workgroup Server Unlimited Edition, Version 8 Linux (x86, 32-bit) Product list: * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Personal Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 Connect for iSeries, Version 8 * DB2 Cube Views, Version 8 * DB2 Data Links Manager, Version 8 * DB2 Information Center, Version 8 * DB2 PDF Documentation, Version 8 * DB2 Query Patroller, Version 8 * DB2 Run-Time Client, Version 8 * DB2 Spatial Extender, Version 8 * DB2 UDB Enterprise Server Edition, Version 8 * DB2 UDB Express, Version 8 * DB2 UDB Personal Edition, Version 8 * DB2 UDB Workgroup Server Edition, Version 8 * DB2 UDB Workgroup Server Unlimited Edition, Version 8 * DB2 Warehouse Manager, Version 8 Linux (IA64, 64-bit) Product list: * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Personal Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 Connect for iSeries, Version 8 * DB2 Information Center, Version 8 * DB2 PDF Documentation, Version 8 * DB2 Query Patroller, Version 8 * DB2 Run-Time Client, Version 8 * DB2 Spatial Extender, Version 8 * DB2 UDB Enterprise Server Edition, Version 8 * DB2 UDB Express Edition, Version 8 * DB2 UDB Personal Edition, Version 8 * DB2 UDB Workgroup Server Edition, Version 8 * DB2 UDB Workgroup Server Unlimited Edition, Version 8 Linux (iSeries and pSeries, 32-bit and 64-bit) Product list: * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 Connect for iSeries, Version 8 * DB2 Information Center, Version 8 * DB2 Query Patroller, Version 8 * DB2 PDF Documentation, Version 8 * DB2 Run-Time Client, Version 8 * DB2 UDB Enterprise Server Edition, Version 8 * DB2 UDB Express Edition, Version 8 * DB2 UDB Workgroup Server Edition, Version 8 * DB2 UDB Workgroup Server Unlimited Edition, Version 8 Linux (S/390(R) and zSeries(R) 31-bit) Product list: * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 Information Center, Version 8 * DB2 PDF Documentation, Version 8 * DB2 Run-Time Client, Version 8 * DB2 Spatial Extender, Version 8 * DB2 UDB Enterprise Server Edition, Version 8 Linux (S/390 and zSeries 64-bit) Product list: * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 Connect for iSeries, Version 8 * DB2 Run-Time Client, Version 8 * DB2 UDB Enterprise Server Edition, Version 8 Linux (AMD64) Product list: * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Personal Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 Connect for iSeries, Version 8 * DB2 Information Center, Version 8 * DB2 Query Patroller, Version 8 * DB2 PDF Documentation, Version 8 * DB2 Run-Time Client, Version 8 * DB2 UDB Enterprise Server Edition, Version 8 * DB2 UDB Express Edition, Version 8 * DB2 UDB Personal Edition, Version 8 * DB2 UDB Workgroup Server Edition, Version 8 * DB2 UDB Workgroup Server Unlimited Edition, Version 8 Solaris Operating Environments (32-bit and 64-bit) Product list: * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 Connect for iSeries, Version 8 * DB2 Cube Views, Version 8 * DB2 Data Links Manager, Version 8 * DB2 Information Center, Version 8 * DB2 PDF Documentation, Version 8 * DB2 Query Patroller, Version 8 * DB2 Run-Time Client, Version 8 * DB2 Spatial Extender, Version 8 * DB2 UDB Enterprise Server Edition, Version 8 * DB2 UDB Workgroup Server Edition, Version 8 * DB2 UDB Workgroup Server Unlimited Edition, Version 8 * DB2 Warehouse Manager, Version 8 If you add new components after you install DB2 Version 8.2 FixPak 4 and later, you need to reinstall DB2 Version 8.2 FixPak 4 and later to ensure that the newly added components are updated. 6.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, 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, 2007. ** ALL RIGHTS RESERVED. ** *******************************************************************************