DB2 Version 8 FixPak 6p Readme Contents 1.0 Readme for IBM DB2 Universal Database(TM) Version 8 FixPak 6p for AIX, Solaris Operating Environments, HP-UX, and Linux 1.1 About this readme 1.2 Who should read this readme file 1.3 How to get help 1.4 PTF information 1.5 Supported products and components by operating system 1.6 Prerequisites 1.7 Updated patch levels -- servers 1.8 Updated patch levels -- clients 1.9 Prior to installing DB2 Version 8 FixPak 6p 1.9.1 Setting up Version 8 FixPak 6p (Solaris Operating Environments, AIX 4.3.3, and AIX 5L) 1.9.2 Data Warehouse functionality (Linux, AIX, and Solaris Operating Environments) 1.10 Installing DB2 Version 8 FixPak 6p 1.10.1 After installation 1.11 Installation of a FixPak or a modification level from a directory path 1.12 Uninstalling FixPaks or modification levels on Linux or UNIX 1.13 Known problems and workarounds (Version 8 FixPak 6p) 1.13.1 New parameter -- db2sqljcustomize - DB2 SQLJ Profile Customizer Command 1.13.2 New parameter -- sqlj - DB2 SQLJ Translator Command 1.13.3 Installing Query Patroller at FixPak 3 level or later 1.13.4 Replication for Informix sources 1.14 Known problems and workarounds (prior to Version 8 FixPak 6p) 1.14.1 Recommended application server for deploying DB2 Web Tools 1.14.2 DB2 Setup Wizard appears not to run using Exceed (Linux) 1.14.3 DB2 Data Links Manager installation when DB2 Enterprise Server Edition already installed 1.14.4 Loss of Control Center functionality 2.0 Notices 1.0 Readme for IBM DB2 Universal Database(TM) Version 8 FixPak 6p for AIX, Solaris Operating Environments, HP-UX, and Linux 1.1 About this readme DB2 Version 8 FixPak 6p is a ship vehicle for DB2 Version 8. Previous ship vehicles include: Version 8 FixPak 1, Version 8.1.2, Version 8 FixPak 3, Version 8.1.4, Version 8 FixPak 5, Version 8 FixPak 6, and now Version 8 FixPak 6p. All ship vehicles are cumulative in nature. Set the font to monospace to better view this file. Note: If you have received special fixes from IBM(R) support, you must contact IBM support before you install DB2 Version 8 FixPak 6p to check if you need an updated version of the special fixes. This helps ensure that your system is in a consistent state and that no special fixes are lost. 1.2 Who should read this readme file The information in this readme file should be read by database administrators who plan to upgrade their earlier level of DB2(R) Version 8 to Version 8 FixPak 6p. This readme file contains operating system specific information about the latest changes and known problems and workarounds for DB2 UDB. This readme file contains DB2 Version 8 FixPak 6p information for all Linux and UNIX(R) operating systems supported by DB2 Version 8. Specific information for each supported operating system is described in separate sections of this readme. Unless otherwise specified, the instructions are applicable to all supported operating systems. Users of DB2 Information Integrator can access the latest information at http://www.ibm.com/software/data/integration/db2ii, including product documentation and product Release Notes. 1.3 How to get help Web-based support for DB2 products, including documentation, and APAR information is provided at * http://www.ibm.com/software/data/db2/udb/winos2unix/support The main Usenet newsgroup for DB2 product-related questions is comp.databases.ibm-db2. 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 For additional information about changes to the product, review the product Release Notes after you have installed DB2 Version 8 FixPak 6p: AIX(R) | /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. You can also view the latest product Release Notes without installing DB2 Version 8 FixPak 6p by going to the DB2 Support Web site: * http://www.ibm.com/software/data/db2/udb/winos2unix/support 1.4 PTF information The following table details the PTF and VRMF information. +----------------------------------+----------------------------------+ | Operating system | PTF | +----------------------------------+----------------------------------+ | AIX 5 | U497635_11555 | +----------------------------------+----------------------------------+ | Solaris Operating Environment | U497645_11557 | +----------------------------------+----------------------------------+ | HP-UX 11i | U497646_11558 | +----------------------------------+----------------------------------+ | HP-UX 11i v2 (IA64) | U497647_11559 | +----------------------------------+----------------------------------+ | LINUX (x86, 32-bit) | MI00080_11560 | +----------------------------------+----------------------------------+ | LINUX (IA64, 64-bit) | MI00081_11561 | +----------------------------------+----------------------------------+ 1.5 Supported products and components by operating system The following lists show the supported products and components for each Linux and UNIX operating system: 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 Cube Views, Version 8 * DB2 Data Links Manager, Version 8 * DB2 HTML Documentation, 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 * DB2 Warehouse Manager Connectors, Version 8 HP-UX(TM) 11i (PA-RISC, 32-bit and 64-bit) Product list: * DB2 Administration Client, Version 8 * DB2 Connect Application Server Edition, Version 8 * DB2 Connect Enterprise Edition, Version 8 * DB2 Connect Unlimited Edition, Version 8 * DB2 HTML Documentation, 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(TM) 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 Run-Time Client, Version 8 * DB2 UDB Enterprise Server Edition, Version 8 Linux(TM) (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 Cube Views, Version 8 * DB2 HTML Documentation, 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(TM) (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 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 Personal 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 Cube Views, Version 8 * DB2 Data Links Manager, Version 8 * DB2 HTML Documentation, 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 * DB2 Warehouse Manager Connectors, Version 8 If you add new components after you install DB2 Version 8 FixPak 6p, you need to reinstall DB2 Version 8 FixPak 6p to ensure that the newly added components are updated. 1.6 Prerequisites Ensure you have reviewed the software, hardware, and operating system requirements. See the Updated patch levels section and the Release Notes for the latest information. * You must have a DB2 product Version 8 installed at a lower VRMF level than DB2 Version 8 FixPak 6p before installation. * Ensure that you have read the entire contents of this 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. +--------+-------------------------+----------------------------------+ | Operat | Command | Output to look for | | ing | | | | 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). | +--------+-------------------------+----------------------------------+ | Solari | pkginfo -l db2cliv81 | | VERSION: 8.1.0.x | | s | grep VERSION | | | Operat | | where x must be smaller than the | | ing | | current | | Enviro | | level (the 4th digit in VRMF). | | nment | | | +--------+-------------------------+----------------------------------+ 1.7 Updated patch levels -- servers For the most up-to-date operating system information, see http://www.ibm.com/software/data/db2/udb/sysreqs.html The following lists the updated patch level for DB2 Version 8 FixPak 6p servers: AIX * Version 5.1.0 (32-bit) * With maintenance level 2 or later and APARs IY31254, IY32217, IY32905, IY29345, and IY31080; or * With maintenance level 3 or later and APAR IY48735 and IY49254 if using JFS2 filesystems * Version 5.1.0 (64-bit) * With maintenance level 2 or later and APARs IY31254, IY32217, IY32905, IY33023, IY29345, IY32466, IY31080, and IY45135; or * With maintenance level 3 or later and APAR IY48735 and IY49254 if using JFS2 filesystem * Version 5.2.0 (32-bit or 64-bit) * APAR IY45135; or * APAR IY45707 if using Concurrent I/O (CIO) mounted volume; or * APARs IY48339 and IY49304 if using JFS2 filesystem; or * APAR IY49129 if using JFS2 filesystem and Concurrent I/O (CIO) mounted volume HP-UX HP-UX 11i (11.11) for systems with PA-RISC 2.x (PA-8x00) processors with: * June 2003 GOLDBASE11i bundle * June 2003 GOLDAPPS11i bundle * Patches PHSS_26560, PHKL_28489 and PHCO_27434 * Patches for Java SDK 1.3.1. See http://www.hp.com/products1/unix/java/patches/index.html for required patches. HP-UX on IA64 HP-UX 11i v2 (B.11.23) for Itanium(R)-based systems requires patch PHKL_30065. Solaris Operating Environment DB2 Workgroup Server Edition (single-partition database environment only) is supported on the following Solaris Operating Environment versions: * Solaris 7 (32-bit) "Recommended & Security Patches" + 107226-17 + 107153-01 + 106327-10 * Solaris 8 (32-bit) "Recommended & Security Patches" + 108921-12 + 108940-24 + 108434-03 and 108528-12 * Solaris 9 (32-bit) DB2 Enterprise Server Edition, on both single-partition and partitioned database environment, is supported on the following Solaris Operating Environment versions: * Solaris 7 (32-bit) "Recommended & Security Patches" + 107226-17 + 107153-01 + 106327-10 * Solaris 7 (64-bit) "Recommended & Security Patches" + 107226-17 + 107153-01 + 106300-11 + 106327-10 * Solaris 8 (32-bit) "Recommended & Security Patches" + 108921-12 + 108940-24 + 108434-03 and 108528-12 * Solaris 8 (64-bit) "Recommended & Security Patches" + 108921-12 + 108940-24 + 108435-03 + 108434-03 and 108528-12 * Solaris 9 (32-bit) * Solaris 9 (64-bit) "Recommended & Security Patches" can be obtained from the http://sunsolve.sun.com Web site. From the SunSolve Online Web site, click on the "Patches" menu item in the left panel. The J2SE Solaris Operating Environment Patch Clusters and the SUNWlibC software are also required and can be obtained from the http://sunsolve.sun.com Web site. For DB2 on 64-bit Fujitsu PRIMEPOWER systems, you require the following: * Solaris 8 Kernel Update Patch 108528-16 or later to get the fix for patch 912040-01. * Solaris 9 Kernel Update Patch 112233-01 or later to get the fix for patch 912041-01. The Fujitsu PRIMEPOWER patches for the Solaris Operating Environment can be downloaded from FTSI at: http://download.ftsi.fujitsu.com/. Linux To check for the latest technical information on the supported levels of Linux, point your browser to http://www.ibm.com/db2/linux/validate 1.8 Updated patch levels -- clients The following lists the updated patch level for DB2 Version 8 FixPak 6p clients: AIX * Version 5.1.0 (32-bit) * With maintenance level 2 or later and APARs IY31254, IY32217, IY32905, IY29345, and IY31080; or * With maintenance level 3 or later and APAR IY48735 and IY49254 if using JFS2 filesystems * Version 5.1.0 (64-bit) * With maintenance level 2 or later and APARs IY31254, IY32217, IY32905, IY33023, IY29345, IY32466, IY31080, and IY45135; or * With maintenance level 3 or later and APAR IY48735 and IY49254 if using JFS2 filesystem * Version 5.2.0 (32-bit or 64-bit) * APAR IY45135; or * APAR IY45707 if using Concurrent I/O (CIO) mounted volume; or * APARs IY48339 and IY49304 if using JFS2 filesystem; or * APAR IY49129 if using JFS2 filesystem and Concurrent I/O (CIO) mounted volume HP-UX HP-UX 11i (11.11) for systems with PA-RISC 2.x (PA-8x00) processors with: * June 2003 GOLDBASE11i bundle * June 2003 GOLDAPPS11i bundle * Patches PHSS_26560, PHCO_27434, and PHKL_28489 * Patches for Java SDK 1.3.1. See http://www.hp.com/products1/unix/java/patches/index.html for required patches. HP-UX on IA64 HP-UX 11i v2 (B.11.23) for Itanium(R)-based systems requires patch PHKL_30065. Solaris Operating Environment For the most up-to-date operating system information, see http://www.ibm.com/software/data/db2/udb/sysreqs.html. * Solaris Version 7 or later * The following patches are required for the Solaris Operating Environment Version 7: * Solaris 7 (32-bit) "Recommended & Security Patches" + 107226-17 + 107153-01 + 106327-10 * Solaris 7 (64-bit) "Recommended & Security Patches" + 107226-17 + 107153-01 + 106300-11 + 106327-10 * Solaris 8 (32-bit) "Recommended & Security Patches" + 108921-12 + 108940-24 + 108434-03 and 108528-12 * Solaris 8 (64-bit) "Recommended & Security Patches" + 108921-12 + 108940-24 + 108435-03 + 108434-03 and 108528-12 * Solaris 9 (32-bit) * Solaris 9 (64-bit) "Recommended & Security Patches" can be obtained from the http://sunsolve.sun.com Web site. From the SunSolve Online Web site, click on the "Patches" menu item in the left panel. The J2SE Solaris Operating Environment Patch Clusters are also required. The following software is required to install a DB2 client on Solaris Operating Environment: * SUNWlibC Linux To check for the latest technical information on the supported levels of Linux, point your browser to http://www.ibm.com/db2/linux/validate 1.9 Prior to installing DB2 Version 8 FixPak 6p Please read the Known problems and workarounds sections before installing DB2 Version 8 FixPak 6p. Before starting the installation, ensure all DB2 processes are stopped. 1. Switch to root authority by running the 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. If you are a hacmp user, you must use the ha_db2stop command to stop DB2 instead of the db2stop command. Otherwise, the db2stop command triggers a failure event. 3. Run the following commands: su - aname . $HOME/das/dasprofile db2admin stop exit where aname 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. Stop all instances that are using DB2 Version 8, including the Fault Monitor if it exists and is using DB2 Version 8. 1.9.1 Setting up Version 8 FixPak 6p (Solaris Operating Environments, AIX 4.3.3, and AIX 5L) For Solaris Operating Environments and AIX 5L, you need to have a filesystem with 2 GB of free space to contain the tar.Z file and the uncompressed installation image, in addition to the disk requirements of Version 8 FixPak 6p in the installation path. 1.9.2 Data Warehouse functionality (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. If you have this file, back it up before applying DB2 Version 8 FixPak 6p. 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.10 Installing DB2 Version 8 FixPak 6p Ensure that your system has met all of the installation prerequisites including operating system patches prior to the installation of DB2 Version 8 FixPak 6p. This action will prevent technical problems that might occur after the installation and configuration of DB2. Installation prerequisites are found in either the Installation Notes or the Information Center. Please read the Known problems and workarounds sections before installing DB2 Version 8 FixPak 6p. Restrictions The following restrictions apply when installing DB2 Version 8 FixPak 6p: * DB2 Version 8 FixPak 6p 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 DB2 Version 8 FixPak 6p 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 FixPak 6p. * 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, once you have installed DB2 Version 8 FixPak 6p, you cannot uninstall it and return to the previous DB2 level. Procedure To install DB2 Version 8 FixPak 6p: 1. Change to the directory in which the installation image is located. 2. Enter the ./installFixPak command to launch the installation. Note: By default, the installFixPak command will commit all of the updated file sets on AIX. On AIX, if you do not wish to commit the updates, you should issue the installFixPak command with the -a option (for "apply" as opposed to "commit") as follows: ./installFixPak -a 1.10.1 After installation After installing DB2 Version 8 FixPak 6p, you must: * If you have DB2 Relational Connect installed, run the djxlink command. * Update instances to use the new level of DB2 * Restart the instances, and * Re-bind the bind files 1.10.1.1 Relational Connect and the djxlink command If you have DB2 Relational Connect installed, you must run the djxlink command after installing DB2 Version 8 FixPak 6p 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.10.1.2 Updating instances to use the new level of DB2 This is mandatory. All instances must be updated after a new level of DB2 is installed. 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 installation 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 owner name and INSTHOME represents the installation directory appropriate to your operating system. For more information on the db2iupdt or dasupdt commands, run these commands with the -h option. 1.10.1.3 Restarting the instances 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.10.1.4 Re-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.10.1.4.1 Re-binding to DB2 UDB databases After applying fixes, you must do one of the following command sequences: At a command prompt, enter: 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, enter: 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. 1.10.1.4.2 Re-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 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. 1.10.1.4.3 Re-binding specific packages If you want to bind only a specific .bnd 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, and represents the name of your database. 1.10.1.4.4 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.10.1.4.5 Bind 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.10.1.4.6 Rebinding after FixPak or patch installation If you have existing spatial-enabled databases, you must rebind 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 rebind the db2gse.lst file: 1. Change to the instance directory where the bind files are located. a. On Windows, open a DB2 command window and enter the following command: cd %DB2PATH%\bnd b. On UNIX, 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 dbname db2 bind /home/instance/sqllib/bnd/@db2gse.lst db2 terminate You can use the DB2RBIND command with the ALL option instead of the BIND command. For syntax and options for the BIND and DB2RBIND commands, refer to the DB2 Command Reference. 1.10.1.5 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 5 is already installed and you want to add the DB2 Information Integrator product. In this case, DB2 Information Integrator should also be at the Version 8 FixPak 5 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 | Additional | Is this combination permitted? | | fixpak | product | | | level | fixpak level | | +----------+--------------+-------------------------------------------+ | Version | Version 8 | Yes. This is recommended. | | 8 FixPak | FixPak 3 | | | 3 | | | +----------+--------------+-------------------------------------------+ | Version | Version 8 GA | Yes, but Version 8 FixPak 3 must be | | 8 FixPak | | reapplied. See the appropriate FixPak | | 3 | | Readme for instructions to reapply the | | | | fixpak by going to the DB2 Support Web | | | | site. | +----------+--------------+-------------------------------------------+ | Version | Version 8 | No. DB2 must first be brought to the | | 8 FixPak | FixPak 5 | higher fix pack level (in this example, | | 3 | | 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/udb/winos2unix/support 1.11 Installation of a FixPak or a modification level from a directory path When you download and untar a FixPak or a modification level, 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/FP6p/ ... It should not resemble the following: /home/DB2 FixPak/FP6p/ ... 1.12 Applying a FixPak or a modification level for Data Links Manager (AIX) To apply a fixpak or a modification level 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 or the modification level. 5. After successful installation of the fixpak or the modification level, 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 1.13 Applying a FixPak or a modification level for Data Links Manager (Solaris Operating Environments) To apply a fixpak or a modification level 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 or the modification level. 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 1.12 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 Version 8 FixPak 6p level, you will lose all of the special fixes when you uninstall DB2 Version 8 FixPak 6p. 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 any backlevel version. If this applies to you, contact IBM Support before uninstalling DB2 Version 8 FixPak 6p. Before uninstalling DB2 Version 8 FixPak 6p, ensure that you: * Stop all instances and DAS * Backup your data AIX If DB2 Version 8 FixPak 6p was installed and the file sets were applied but not committed, DB2 Version 8 FixPak 6p can be rejected using SMIT. See the SMIT documentation for more details. If the file sets were committed when DB2 Version 8 FixPak 6p was installed, which is the default, then DB2 Version 8 FixPak 6p cannot be rejected. The only course of action available is to uninstall DB2 from your system, reinstall DB2 Version 8, and bring DB2 up to the desired level by applying the corresponding level of DB2. HP-UX DB2 Version 8 FixPak 6p file sets can be uninstalled using the sam utility. If you use swlist or sam, you can list all file sets for DB2 Version 8 FixPak 6p 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 Version 8 FixPak 6p, or the latest version plus the second last, and so on. You can also select them all. Linux You cannot uninstall DB2 Version 8 FixPak 6p on Linux. The only course of action available is to uninstall DB2 from your system, reinstall DB2 Version 8, and bring DB2 up to the desired level by applying the corresponding level of DB2. A db2_deinstall script is provided with DB2 Version 8 FixPak 6p which will uninstall DB2 from your system. Solaris Operating Environment The backoutallpatch script is provided with all version images. Run this script to uninstall DB2 Version 8 FixPak 6p and leave the system in the state that it was before installing DB2 Version 8 FixPak 6p. 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 Version 8 FixPak 6p. 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, including the DAS instance. 1.13 Known problems and workarounds (Version 8 FixPak 6p) 1.13.1 New parameter -- db2sqljcustomize - DB2 SQLJ Profile Customizer Command -storebindoptions Stores the value of the -bindoptions and -staticpositioned values in the serialized profile. If these values are not specified when invoking the dbsqljbind tool, the values stored in the serialized profile is used. When the Customizer is invoked with .grp file, the values are stored in each individual .ser file. The stored values can be viewed using db2sqljprint tool. 1.13.2 New parameter -- sqlj - DB2 SQLJ Translator Command -db2optimize Specifies that the SQLJ translator generates code for a connection context class that is optimized for DB2. This option optimizes the code for the user-defined context but not for the default context. When you run the SQLJ translator with this option, the DB2 Universal JDBC Driver file db2jcc.jar must be in the CLASSPATH for compiling the generated Java application. 1.13.3 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 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 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. 1.13.4 Replication for Informix sources Replication for Informix sources is no longer dependent on timestamp values. This enhancement eliminates issues that would arise during a backward time change, such as daylight savings in October. To take advantage of this enhancement, you must migrate any existing registrations and subscriptions for Informix sources as described in IBM Support Technote 1165347, "Migrating Informix source triggers in DB2 DataPropagator 8.1 FP 5". To access the Technote, perform the following steps. 1. Open a Web browser 2. Go to the DB2 DataPropagator Support Web page at http://www.ibm.com/software/data/dpropr/support.html 3. Enter 1165347 in the Search support for this product area of the page, then click Submit. 1.14 Known problems and workarounds (prior to Version 8 FixPak 6p) 1.14.1 Recommended application server for deploying DB2 Web Tools The recommended application server for deploying DB2 Web Tools is the embedded application server for DB2. The recommended method is to use the automated script that is provided. To deploy DB2 Web Tools on the embedded application server for DB2, the following order is recommended: 1. Installing the application server for DB2 2. Starting the application server for DB2 3. Deploying automatically on the application server for DB2 For detailed instructions for each step, see the DB2 Information Center. These additions to the following sections must also be noted. 1.14.1.1 Installing the application server -- additional prerequisite The application server for DB2 requires DB2 ESE Version 8.1.2 or higher. 1.14.1.2 Installing the application server -- additional restriction The default Red Hat installation creates an association between the hostname of the machine and the loopback address, 127.0.0.1. In addition, the /etc/nsswitch.conf file is set up to use /etc/hosts before trying to look up the server using a name server (DNS). This loopback processing can hang utilities that start and stop a server, such as startServer.sh, even though the server might successfully start or stop. Ensure that the host name is defined properly. The default configuration has localhost defined in the /etc/hosts file. The default /etc/nsswitch.conf looks only at the host file and not the DNS server. To correct this problem, remove the 127.0.0.1 mapping to localhost in the /etc/hosts file, or, edit the name service configuration file /etc/nsswitch.conf to resolve the proper host name by using the name server. For example, remove the 127.0.0.1 mapping from the /etc/hosts file, which might look like this example: # IP Address name of machine n.n.n.n hostname.domain.com 127.0.0.1 localhost Otherwise, change the etc/nsswitch.conf file to search DNS before searching the hosts file. For example, hosts : dns files 1.14.1.3 Deploying automatically on the application server for DB2 -- additional prerequisite The application server for DB2 requires DB2 ESE Version 8.1.2 or higher. The command to automatically deploy DB2 Web Tools requires the DB2 instance name be specified: 1. Change to the /bin directory and run the deploy_db2wa script: /bin/db2wa_deploy -db2path db2path -instance instanceName where: * is the installation path for the application server for DB2. * db2path is the installation path for DB2. * instanceName is the DB2 instance name. For example: db2wa_deploy.sh -db2path /home/db2v8/sqlib -instance db2v8 2. Invoke the DB2 Web Tools enterprise application from a browser by entering the following: http://hostname:/db2wa where: * hostname is the name of the DB2 server. * port_number is 20000 by default, unless modified after the installation of the application server. 1.14.2 DB2 Setup Wizard appears not to run using Exceed (Linux) When using Hummingbird(R) Exceed PC X Server software to connect to a Linux computer from a computer running Microsoft(R) Windows, the DB2 Setup wizard may not appear to run. This problem arises when Exceed is configured to use multiple window mode, with the Window Manager set to "Default to Native" and with the communications mode set to "Passive". The symptoms you may observe include: 1. The DB2 Setup Launchpad appears quite small, as small as 5 pixels x 5 pixels, and will need to be resized before it can be used. 2. Even after resizing, the DB2 Setup Launchpad sometimes will not paint properly and instead appears as a blank grey panel. To run the DB2 Setup Wizard on a Linux computer using Exceed, change either of the following Exceed configuration settings: * Change the Window Manager setting to "Native" and ensure the "Use Native WM for Embedded Clients" check box is checked, or, * Change the Window Mode to "Single" and the communication mode from "Passive" to "XDCMP-query". 1.14.3 DB2 Data Links Manager installation when DB2 Enterprise Server Edition already installed The DB2 Data Links Manager installation 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. 1.14.4 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/ 2.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-2004. ** ALL RIGHTS RESERVED. ** *******************************************************************************