DB2 Version 8 FixPak 1+ Readme Contents 1) FixPak readme for IBM(R) DB2 Universal Database(TM) Version 8 FixPak 1+ for AIX(R) and Solaris Operating Environments 1a) About this FixPak readme 1b) Who should read this readme file 1c) How to get help 1d) PTF and VRMF information 1e) Supported products and components by platform 1f) Prerequisites 1g) Before installation 1g.i) Data Warehouse functionality on Linux, AIX, and Solaris Operating Environments 1h) Installing the DB2 FixPak 1i) After installation 1i.i) Updating instances to use the new fix level 1i.ii) Restart the instances 1i.iii) Re-binding bind files 1j) Known problems and workarounds 1j.i) DB2 Data Links Manager install 1j.ii) Loss of Control Center functionality 1j.iii) Installation of a FixPak or a modification level from a directory path 1j.iv) Applying a FixPak or a modification level for Data Links Manager on AIX 1j.v) Applying a FixPak or a modification level for Data Links Manager on Solaris Operating Environments 1j.vi) Controlling login restrictions of a connecting user on an AIX server 1j.vii) Updates to RESTORE DATABASE Command 2) Notices 1) FixPak readme for IBM(R) DB2 Universal Database(TM) Version 8 FixPak 1+ for AIX(R) and Solaris Operating Environments. 1a) About this FixPak readme Set the font to monospace to better view this file. Note: If you have received special fixes from IBM support since 03/30/2003, then you must contact IBM support to request an updated version of the special fixes instead of installing this FixPak. By doing this, you are assured that your system is in a consistent state and no special fixes are lost. 1b) Who should read this readme file The information in this readme file should be read by database administrators who plan to upgrade their present version of DB2(R) with the latest FixPak. This readme file contains platform specific information about the latest changes and known problems and workarounds for DB2. This readme file contains DB2 Version 8 FixPak information for all UNIX(R) operating systems supported by DB2 Version 8. Specific information for each supported UNIX operating system is described in separate sections of this readme. However, unless otherwise specified, the instructions are applicable to all supported UNIX operating systems. 1c) How to get help Web-based support for DB2 products, including documentation, FixPaks, and APAR information is provided at * http://www.ibm.com/software/data/db2/udb/winos2unix/support NOTE: This specific DB2 Version 8 FixPak 1+ is not available on the above support web site. The main Usenet newsgroup for DB2-related questions is comp.databases.ibm-db2. To contact DB2 Customer Service by phone: * In the United States, call 1-800-237-5511. * In Canada, call 1-800-IBM-SERV (426-7378). * Worldwide, call 1-404-238-1234 (charges may apply). For information on IBM offices in your country or region, consult the IBM Directory of Worldwide Contacts at http://www.ibm.com/planetwide. For additional information on changes to the product, review the product Release Notes after you've installed the fixpak: +-----------------------+---------------------------------------------+ | AIX | /usr/opt/db2_08_01/Readme/%L/Release.Notes | +-----------------------+---------------------------------------------+ | Solaris Operating | /opt/IBM/db2/V8.1/Readme/%L/Release.Notes | | Environment | | +-----------------------+---------------------------------------------+ where %L represents the locale name. You can also view the latest product Release Notes without installing the fixpak by going to the DB2 Support Web site: * http://www.ibm.com/software/data/db2/udb/winos2unix/support 1d) PTF and VRMF information +-----------------------+----------------------+----------------------+ | Operating system | PTF | VRMF | +-----------------------+----------------------+----------------------+ | AIX 4.3.3 | U486245CM | 8.1.0.11 | +-----------------------+----------------------+----------------------+ | AIX 5 | U486246CM | 8.1.1.11 | +-----------------------+----------------------+----------------------+ | Solaris Operating | U486247CM | 8.1.0.11 | | Environment | | | +-----------------------+----------------------+----------------------+ 1e) Supported products and components by platform This readme file contains information for the following products and components for each UNIX operating system: AIX(R) 4.3.3 (32-bit) Product and components list: * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect(TM) Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 Data Links Manager, Version 8 * DB2 HTML Documentation, 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 * DB2 UDB Workgroup Server Edition, Version 8 * DB2 UDB Workgroup Server Unlimited Edition, Version 8 * DB2 Warehouse Manager, Version 8 * DB2 Warehouse Manager Connectors, Version 8 AIX(R) 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 Enterprise Unlimited Edition, Version 8 * DB2 HTML Documentation, 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 Solaris(R) 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 Data Links Manager, Version 8 * DB2 HTML Documentation, 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 * DB2 UDB Workgroup Server Edition, Version 8 * DB2 UDB Workgroup Server Unlimited Edition, Version 8 * DB2 Warehouse Manager, Version 8 * DB2 Warehouse Manager Connectors, Version 8 If you add new components after you have installed the current FixPak, you need to reapply the FixPak to ensure that the newly added components are also updated. 1f) Prerequisites * You must have DB2 Version 8 installed at the level lower than this FixPak before installing this FixPak. * Ensure that you have read the entire contents of this FixPak readme. 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: +---------+-----------------------------+-----------------------------+ | Operati | Command | Output to look for | | ng | | | | 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.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. | +---------+-----------------------------+-----------------------------+ | Solaris | pkginfo -l db2cliv81 | grep | VERSION: 8.1.0.x | | Operati | VERSION | | | ng | | where x must be 0 or later. | | Environ | | | | ment | | | +---------+-----------------------------+-----------------------------+ 1g) Before installation 1. Switch to root authority by running su - root command. 2. Run the following commands for each instance: 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. 3. Run the following commands: su - aname . $HOME/sqllib/db2profile db2admin stop exit where aname represents the administration server instance name. 4. On AIX, you should also run, as root, slibclean to unload unused shared libraries from memory before installing this FixPak: /usr/sbin/slibclean 5. Stop all instances that are using DB2 Version 8, including the Fault Monitor if it exists and is using DB2 Version 8. 1g.i) Data Warehouse functionality on Linux, AIX, 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 will need to back up your /opt/IBM/db2/V8.1/bin/IWH.environment. Basically, if you have this file, back it up before applying any Version 8 FixPak. On AIX and Sun, you should back up the same file (for AIX, this file is found in /usr/opt/db2_08_01/bin/IWH.environment). 1h) Installing the DB2 FixPak Restrictions The following restrictions apply when installing the DB2 FixPak: * The DB2 Version 8 FixPak for AIX 4.3.3 can only be applied on AIX 4.3.3 and the DB2 Version 8 FixPak for AIX 5 can only be applied on AIX 5. * On AIX, the installFixPak script provides installation prerequisite checking that is not provided when you install the FixPak using SMIT or installp. Using SMIT is still supported, but installFixPak is the only method documented in this readme. For instructions on using SMIT, please see your AIX manuals. It is strongly recommended that you use the installFixPak script to install this FixPak. * On Linux (Intel or S/390), once you have installed the FixPak, you cannot uninstall it. Prerequisites * Ensure that you've reviewed your software, hardware, and operating system requirements. See the Release Notes for the latest information. Procedure To install the DB2 Version 8 FixPak: 1. Change to the directory in which the FixPak image is located. 2. Type the ./installFixPak command to launch the installation. By default, installFixPak will commit all of the updated filesets. However, on AIX, if you do not wish to commit the updates, you should issue the installFixPak command with the -a option (for "apply" as versus "commit") as follows: ./installFixPak -a 1i) After installation 1i.i) Updating instances to use the new fix level You need to be logged on as root to update the instances. For each instance, issue the command: INSTHOME/instance/db2iupdt iname where iname represents the instance name and INSTHOME represents the install directory appropriate to your operating system. Run the dasupdt command if the database administration server (DAS) instance exists and is a DB2 Version 8 DAS instance. To update the DAS instance, issue the command: INSTHOME/instance/dasupdt dasname where dasname represents the DAS and INSTHOME represents the install directory appropriate to your operating system. For more information on the db2iupdt or dasupdt commands, run these commands with the "-h" option. 1i.ii) Restart the instances To restart an instance: 1. Type su . 2. Type the db2start command. Repeat for each instance. To restart the administration server, login the DAS owner ID and run the db2admin start command. 1i.iii) Re-binding bind files Due to the new bind (.bnd) files that have been shipped with this FixPak, you will need to bind your DB2 utilities against all your databases after the FixPak installation. This step is necessary for the fixes in this FixPak to become effective. The procedure of binding, which follows, only needs to be performed once per database. Re-binding to DB2 UDB databases After applying fixes, you must do the following: At a command prompt: db2 terminate db2 CONNECT TO db2 BIND /@db2ubind.lst BLOCKING ALL GRANT PUBLIC db2 BIND /@db2cli.lst BLOCKING ALL GRANT PUBLIC db2 terminate or, At the DB2 command line: TERMINATE CONNECT TO BIND /@db2ubind.lst BLOCKING ALL GRANT PUBLIC BIND /@db2cli.lst BLOCKING ALL GRANT PUBLIC 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. Re-binding host databases If you are connecting to host databases, you will also need to bind the new bind files to the host. As above, use the DB2 Command Line Processor to connect to the host database, and then bind the utilities as follows: HOST COMMAND ======= =================================================== MVS BIND /@ddcsmvs.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE VM BIND /@ddcsvm.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE VSE BIND /@ddcsvse.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE OS400 BIND /@ddcs400.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE See "Binding Applications and Utilities" in the DB2 Connect 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. Re-binding specific packages If you want to bind only a specific .bnd file to the database, issue the following commands for each database. At a command prompt: db2 terminate db2 CONNECT TO db2 BIND / BLOCKING ALL GRANT PUBLIC sqlerror continue db2 terminate or, At the DB2 command line: TERMINATE CONNECT TO BIND / BLOCKING ALL GRANT PUBLIC sqlerror continue TERMINATE where represents the name of the bind file, and represents the name of your database. 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 are at different versions or service levels of DB2, you must bind the utilities once for each operating system and DB2 client-version combination. Bind db2schem.bnd to existing databases For FixPak installations on the server, an additional bind file needs to be bound to existing databases after applying the FixPak. This requirement does not apply to clients. Procedure To bind db2schem.bnd on the server, execute these commands: At a command prompt: db2 terminate db2 CONNECT TO db2 BIND /db2schem.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue db2 terminate or, At the DB2 command line: TERMINATE CONNECT TO BIND /db2schem.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. 1j) Known problems and workarounds 1j.i) DB2 Data Links Manager install The DB2 Data Links Manager install will fail when creating the dlfm instance if DB2 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. 1j.ii) Loss of Control Center functionality Consult the Client/Server Compatibility and Migration Considerations whitepaper which is available at: * http://www-3.ibm.com/software/data/pubs/papers/ 1j.iii) Installation of FixPak from a directory path When you download and untar or unzip a FixPak, make sure that there are no spaces in your directory path where the file was located. If there are spaces in your directory path the installation will fail. For example, make sure your directory path resembles the following: /home/DB2FixPak/FP1/ ... It should not resemble the following: /home/DB2 FixPak/FP1/ ... 1j.iv) Applying a FixPak for Data Links Manager on AIX To apply a fixpak for Data Links Manager on AIX: 1. As the DB2 Data Links Manager Administrator, bring down the DB2 Data Links Manager by running the following commands: dlfm stop dlfm stopdbm Ensure that there are no DB2 or DLFM processes remaining. 2. As root, unmount each dlfs filesystem (filesystems controlled by the DB2 Data Links Manager) by running the following command: umount /filesystem_name where /filesystem_name represents the name of the dlfs filesystem which you want to unmount. 3. As root, unload the DLFS device driver by running the following command: strload -uf /usr/opt/db2_08_01/cfg/dlfs_cfg 4. Install the fixpak. 5. After successful installation of the fixpak, as root, update the Data Links Manager instance by running the following command: /usr/opt/db2_08_01/instance/dlfmupdt dlm_instance_name where dlm_instance_name represents the name of the DB2 Data Links Manager Administrator. 6. As root, load the DLFS device driver by running the following command: strload -f /usr/opt/db2_08_01/cfg/dlfs_cfg 7. As root, mount each of the DLFS filesystems by running the following command: mount -v dlfs /filesystem_name 8. As the DB2 Data Links Manager Administrator, run the following commands to bring up the DB2 Data Links Manager: dlfm bind dlfm start 1j.v) Applying a FixPak for Data Links Manager on Solaris Operating Environments To apply a fixpak for Data Links Manager on Solaris Operating Environments: 1. As the DB2 Data Links Manager Administrator, bring down the DB2 Data Links Manager by running the following commands: dlfm stop dlfm stopdbm Ensure that there are no DB2 or DLFM processes remaining. 2. As root, unmount each dlfs filesystem (filesystems controlled by the DB2 Data Links Manager) by running the following command: umount /filesystem_name where /filesystem_name represents the name of the dlfs filesystem which you want to unmount. 3. As root, unload the DLFS device driver by running the following command: rem_drv dlfsdrv 4. Install the fixpak. 5. After successful installation of the fixpak or the modification level, as root, update the Data Links Manager instance by running the following command: /opt/IBMdb2/V8.1/instance/dlfmupdt dlm_instance_name where dlm_instance_name represents the name of the DB2 Data Links Manager Administrator. 6. As root, load the DLFS device driver by running the following command: add_drv -m '* 0777 dlfm dlfmgrp' dlfsdrv 7. As root, mount each of the DLFS filesystems by running the following command: mount -v dlfs /filesystem_name 8. As the DB2 Data Links Manager Administrator, run the following commands to bring up the DB2 Data Links Manager: dlfm bind dlfm start 1j.vi) Controlling login restrictions of a connecting user on an AIX server By default, when an user is authenticated on an AIX server, DB2 will check the connecting user's local login restrictions before allowing the connection to proceed. The DB2LOGINRESTRICTIONS registry variable will permit DB2 to enforce alternative modes of login restrictions. If DB2LOGINRESTRICTIONS is not set, the default value is LOCAL. The variable may be set to the following values: REMOTE DB2 will only enforce remote login restrictions SU DB2 will only enforce su restrictions NONE DB2 will not enforce any particular mode of login restrictions LOCAL DB2 will only enforce local login restrictions In all cases, DB2 will still check for the following error conditions: * expired account * locked account * invalid user 1j.vii) Updates to RESTORE DATABASE Command The following is an update to the RESTORE DATABASE command topic. You can restore database backups created in DB2 Version 8 32-bit Windows system to a DB2 Version 8 64-bit Windows system, or the reverse. Database backups created on AIX, HP, and Solaris Operating Environments, each in either DB2 Version 8 32-bit or 64-bit, may be restored on AIX, HP, and Solaris Operating Environments, each in either DB2 Version 8 32-bit or 64-bit. You can restore database backups created in DB2 Version 8 32-bit Linux (Intel) to a DB2 Version 8 64-bit Linux (Intel) platform, or the reverse. 2) 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. ******************************************************************************* ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2003. ** ALL RIGHTS RESERVED. ** *******************************************************************************