DB2 Version 8 FixPak 6 Readme Contents 1.0 Readme for IBM DB2 Universal Database(TM) Version 8 FixPak 6 (Windows) 1.1 About this readme 1.2 Who should read this readme file 1.3 How to get help 1.3.1 IBM FTP server 1.4 PTF information 1.5 Supported products and components by operating system 1.6 Installation scenarios 1.7 Prerequisites 1.8 Prior to installing Version 8 FixPak 6 1.9 Product abbreviations 1.10 Installing DB2 Version 8 FixPak 6 1.11 DB2 Version 8 FixPak 6 Command line parameters 1.11.1 FP6_$PTF_ command options 1.11.2 Setup command options 1.11.3 Language identifiers 1.12 Installing DB2 Version 8 FixPak 6 in an MSCS environment 1.13 Applying a FixPak or a modification level for Data Links Manager (Windows) 1.14 After installation 1.14.1 Enable DB2 Remote Command Service 1.14.2 Re-binding bind files 1.14.3 Restrictions to adding products using the db2setup command 1.15 Known problems and workarounds (Version 8 FixPak 6) 1.15.1 New parameter -- db2sqljcustomize - DB2 SQLJ Profile Customizer Command 1.15.2 New parameter -- sqlj - DB2 SQLJ Translator Command 1.15.3 Replication for Informix sources 1.16 Known problems and workarounds (prior to Version 8 FixPak 6) 1.16.1 Recommended application server for deploying DB2 Web Tools 2.0 Notices 1.0 Readme for IBM DB2 Universal Database(TM) Version 8 FixPak 6 (Windows) 1.1 About this readme DB2 Version 8 FixPak 6 is a FixPak, not a modification level. APAR fixes are included in FixPaks. APARs and new functionality are included in modification levels. DB2 Version 8 FixPak 6 is the sixth 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, and now Version 8 FixPak 6. 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 6 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 install or upgrade their present version of DB2(R) UDB with DB2 Version 8 FixPak 6. This readme file contains operating system specific information about the latest changes and known problems and workarounds for DB2 products. Users of DB2 Information Integrator can access the latest information at http://www.ibm.com/software/data/integration/db2ii, includes 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. You can view the latest product Release Notes without installing DB2 Version 8 FixPak 6 by going to the DB2 Support Web site: * http://www.ibm.com/software/data/db2/udb/winos2unix/support Note: 1. You can review the Release Notes directly from the DB2 Version 8 FixPak 6 CD-ROM without either installing them or going to the IBM Web site. The Release Notes can be found at /doc/%L/db2ir/index.htm, where %L represents the locale name. 2. The DB2 Information Integrator Version 8 Release Notes are located at http://www.ibm.com/software/data/integration/db2ii. 3. The DB2 Query Patroller Release Notes are located at http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/v8pubs_trans.d2w/report. 1.3.1 IBM FTP server DB2 Version 8 FixPak 6 for Windows can be downloaded from the DB2 Technical Support site at http://www.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/download.d2w/report or directly from the IBM anonymous FTP server at ftp.software.ibm.com. * For the FixPak or modification level images for Windows(R) (32-bit) go to ps/products/db2/fixes/english-us/db2winIA32v8/fixpak/FP6_WR21340 * For the FixPak or modification level images for Windows (64-bit) go to ps/products/db2/fixes/english-us/db2winIA64v8/fixpak/FP6_WR21341. Note: All other supported language directories (ps/products/db2/fixes/%L, where %L represents the appropriate locale, for example, spanish, german) link to the english-us directory. Go to the previously mentioned directories to get the FixPak or modification level images with all the supported languages. 1.3.1.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: +----------+----------------------+-------------------------+---------+ | Operatin | DB2 Administration | DB2 Application | DB2 | | g System | Client | Development Client | Run-Tim | | | | | e | | | | | Client | +----------+----------------------+-------------------------+---------+ | AIX(R) | * SBCS1 (English, | * SBCS1 (English, | All | | 4.3.3 | French, German, and | French, German, and | support | | (32-bit) | Italian) | Italian) | ed | | | * SBCS2 (English, | * SBCS2 (English, | languag | | | Brazilian | Brazilian Portuguese, | es are | | | Portuguese, and | and Spanish) | in one | | | Spanish) | * NORDIC (English, | tarred | | | * NORDIC (English, | Danish, Finnish, | file | | | Danish, Finnish, | Norwegian, and Swedish) | | | | Norwegian, and | * DBCS (English, | | | | Swedish) | Japanese, Korean, | | | | * DBCS (English, | Simplified Chinese, and | | | | Japanese, Korean, | Traditional Chinese) | | | | Simplified Chinese, | | | | | and Traditional | | | | | Chinese) | | | +----------+----------------------+-------------------------+---------+ | AIX | * SBCS (English, | * SBCS (English, | All | | 5L(TM) | Brazilian | Brazilian Portuguese, | support | | (32-bit | Portuguese, Danish, | Danish, Finnish, | ed | | and | Finnish, French, | French, German, | languag | | 64-bit) | German, Italian, | Italian, Norwegian, | es are | | | Norwegian, Spanish, | Spanish, and Swedish) | in one | | | and Swedish) | * DBCS (English, | tarred | | | * DBCS (English, | Japanese, Korean, | file | | | Japanese, Korean, | Simplified Chinese, and | | | | Simplified Chinese, | Traditional Chinese) | | | | and Traditional | | | | | Chinese) | | | +----------+----------------------+-------------------------+---------+ | HP-UX | All supported | All supported languages | All | | 11i | languages are in one | are in one tarred file | support | | (PA-RISC | tarred file | | ed | | ) and | | | languag | | HP-UX | | | es are | | 11i v2 | | | in one | | (IA64) | | | tarred | | (32-bit | | | file | | and | | | | | 64-bit) | | | | +----------+----------------------+-------------------------+---------+ | Linux | All supported | All supported languages | All | | | languages are in one | are in one tarred file | support | | | tarred file | | ed | | | | | languag | | | | | es are | | | | | in one | | | | | tarred | | | | | file | +----------+----------------------+-------------------------+---------+ | Solaris | All supported | All supported languages | All | | Operatin | languages are in one | are in one tarred file | support | | g | tarred file | | ed | | Environm | | | languag | | ents | | | es are | | | | | in one | | | | | tarred | | | | | file | +----------+----------------------+-------------------------+---------+ | Windows | All supported | All supported languages | All | | | languages are in one | are in one | support | | | self-extracting zip | self-extracting zip | ed | | | file | file | languag | | | | | es are | | | | | in one | | | | | self-ex | | | | | tractin | | | | | g zip | | | | | file | +----------+----------------------+-------------------------+---------+ 1.4 PTF information The following table details the PTF and VRMF information: +------------------------------------------+--------------------------+ | Operating system or product | PTF | +------------------------------------------+--------------------------+ | Windows 32-bit | WR21340 | +------------------------------------------+--------------------------+ | Windows 64-bit | WR21341 | +------------------------------------------+--------------------------+ 1.5 Supported products and components by operating system The following lists show the supported products and components for each Windows operating system: Windows 98 * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect(TM) Personal Edition, Version 8 * DB2 HTML Documentation, Version 8 * DB2 PDF Documentation, Version 8 * DB2 Run-Time Client, Version 8 Windows ME * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Personal 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 Personal Edition, Version 8 Windows XP 32-bit * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Personal 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 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 * DB2 Warehouse Manager Connectors, Version 8 Windows XP 64-bit * DB2 Administration Client, Version 8 * DB2 Application Development Client, Version 8 * DB2 Connect Personal 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 Personal Edition, Version 8 Windows NT(R) 4.0 and Windows 2000 * 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 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 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 * DB2 Warehouse Manager Connectors, Version 8 Windows Server 2003 32-bit * 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 * DB2 Warehouse Manager Connectors, Version 8 Windows Server 2003 64-bit * 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 1.6 Installation scenarios Starting with DB2 Version 8 for Windows FixPak 3, IBM is providing product-specific FixPaks instead of one general FixPak. This change only affects DB2 Version 8 products on Windows platforms. This new delivery mechanism provides the following advantages: * Less disk space is required on the operating system drive. * Overall amount of disk space required for the installation is reduced. * Easier installation for rollout scenarios at a FixPak or modification level later than Version 8 General Availability (GA) level. If you only have one DB2 Version 8 for Windows product installed, all you need to do is download the corresponding product-specific FixPak. If you have more than one DB2 Version 8 for Windows product installed on the same system, you must download and uncompress all of the corresponding product-specific FixPaks before starting the FixPak installation process. For example, if you have DB2 Enterprise Server Edition and DB2 Warehouse Manager installed, you must download and uncompress both DB2 Enterprise Server Edition (ESE) and DB2 Warehouse Manager (WM). You can uncompress the DB2 products into the directory path of your choice, however, you need to consider how you plan to install DB2 Version 8 FixPak 6: * If you plan to install DB2 Version 8 FixPak 6 using the DB2 Setup wizard GUI, the setup command detects the other installed DB2 products. If all product images are uncompressed into subdirectories under the same parent directory, the setup command automatically launches the installation of all DB2 products without prompting you. If product images are uncompressed into different directories, the setup command detects the other installed DB2 products and prompts you for each directory path. * If you plan to install DB2 Version 8 FixPak 6 in silent mode, all the product images must be uncompressed into subdirectories under the same parent directory. See the "Installing DB2 Version 8 FixPak 6" section for details. The delivery mechanism supports all installation scenarios. Note: You must have the product license installed before installing a refresh image of either the DB2 Information Integrator Relational Wrapper product or the DB2 Information Integrator Nonrelational Wrapper product. Otherwise you receive an error message. 1.7 Prerequisites * Ensure that you have read the entire contents of this readme. * If you have a DB2 Version 8 product already installed, it must be at a lower service level than DB2 Version 8 FixPak 6. To determine the version and level of the currently installed DB2 product, enter the regedit command from a command prompt and check the following values under the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\\CurrentVersion\Version HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\\CurrentVersion\Release HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\\CurrentVersion\Modification The following values should display: * Version "8" * Release "1" * Modification "x" where x should be lower than the level of the DB2 Version 8 FixPak 6. The values for Version, Release, and Modification correspond to the first three numbers of the VRMF number. The value for Modification in the registry for the currently installed product should be less than the third number of the VRMF number for DB2 Version 8 FixPak 6. 1.8 Prior to installing Version 8 FixPak 6 * If you have DB2 Version 8 products already installed, stop all instances and applications that are using DB2 Version 8 on the system. * When upgrading or uninstalling DB2 products it is recommended that you manually shut down all DB2 services and processes on your computer. * Verify that you have enough space to install the FixPak or the modification level. You need enough space to uncompress the self-extracting zip file. * Ensure that your system has met all of the installation prerequisites including operating system patches prior to the installation of DB2 Version 8 FixPak 6. 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. 1.9 Product abbreviations The following product abbreviations should be used when searching directories or when identifying files to uncompress: ADMCL DB2 Administration Client ADCL DB2 Application Development Client CONEE DB2 Connect Enterprise Edition, DB2 Connect Unlimited Edition, or DB2 Connect Application Server Edition CONPE DB2 Connect Personal Edition CUBE DB2 Cube Views DLM DB2 Data Links Manager ESE DB2 Enterprise Server Edition EXP DB2 Express Edition, or DB2 Express Edition processor option IINW DB2 Information Integrator Nonrelational Wrappers IIRW DB2 Information Integrator Relational Wrappers PE DB2 Personal Edition QP DB2 Query Patroller RTCL DB2 Run-Time Client GSE DB2 Spatial Extender WM DB2 Warehouse Manager WMC DB2 Warehouse Manager Connectors WSE DB2 Workgroup Server Edition or DB2 Workgroup Server Unlimited Edition 1.10 Installing DB2 Version 8 FixPak 6 DB2 Version 8 FixPak 6 images are downloaded directly from the IBM anonymous FTP server. Also use this method for installing Version 8 FixPak 6 in silent mode. Restrictions Once you install DB2 Version 8 FixPak 6, you cannot roll back to a previous level. Procedure To install the DB2 Version 8 FixPak 6: 1. Download the images for the products that you have installed. The FixPak images are downloaded directly from the IBM anonymous FTP server at ftp.software.ibm.com. If you have more than one DB2 Version 8 for Windows product installed on the same system, download the images for all the products you have installed. 2. Ensure that all DB2 processes are stopped. To stop all database activity, issue the following commands: db2stop db2admin stop 3. Ensure that all DB2 services are stopped. Use the services control panel applet to stop these services. 4. Uncompress the self-extracting images. Uncompress the images using a zip utility, such as WinZip, or using the FP6_$PTF_.exe command (where $PTF represents either: WR21340 on Windows 32-bit, or WR21341 on Windows 64-bit). When you uncompress the self-extracting images, you must consider whether you are uncompressing a single DB2 Version 8 product or multiple DB2 Version 8 products: * Single product If you have only one DB2 Version 8 for Windows product installed, you can uncompress the product and automatically launch the DB2 Setup wizard GUI to install DB2 Version 8 FixPak 6 with one command. The command parameters required depend on whether you want to install the product in silent mode using a response file: * Setup wizard GUI installation To uncompress a single product and automatically launch the installation Setup wizard, enter the following command: FP6_$PTF_.exe For example, to uncompress the DB2 Enterprise Server Edition product on Windows 32-bit enter FP6_WR21340_ESE.exe. * Silent mode installation using a response file To uncompress a single product and automatically launch a silent installation, enter the following command: FP6_$PTF_.exe -s -a -u e:\db2fixpk.rsp -t c:\db2fixpk.trc -l c:\db2fixpk.log Sample response files can be found in the \db2\windows\samples directory. For a list of product abbreviations, see the Product abbreviations section. For a description of the FP6_$PTF_.exe command and the setup command, see the DB2 Version 8 FixPak 6 Command line parameters section. * Multiple products If you have more than one DB2 Version 8 for Windows product installed on the same system, the directory you uncompress the products to depends on whether you plan to install DB2 Version 8 FixPak 6 using the DB2 Setup wizard or install in silent mode using a response file. When you uncompress the self-extracting images, you have the following options: * If you plan to install DB2 Version 8 FixPak 6 using the DB2 Setup wizard GUI and you have more than one DB2 Version 8 product installed, the setup command detects the other installed DB2 products. If all the product images are uncompressed into subdirectories under the same parent directory, the setup command automatically launches the installation of all DB2 products without prompting you. If the product images are uncompressed into different directories, the setup command detects the other installed DB2 products and prompts you for the directory path. * If you plan to install DB2 Version 8 FixPak 6 in silent mode, all the product images must be uncompressed into subdirectories under the same parent directory. Uncompress the images using a zip utility, such as WinZip, or using the FP6_$PTF_ -e -f command (where $PTF represents either: WR21340 on Windows 32-bit, or WR21341 on Windows 64-bit). For example, to uncompress the DB2 Enterprise Server Edition product and the DB2 Warehouse Manager product into subdirectories under the parent directory called c:\db2_fixpak\images, enter FP6_WR21340_ESE.exe -e -f c:\db2_fixpak\images FP6_WR21340_WM.exe -e -f c:\db2_fixpak\images For a description of this command, see the DB2 Version 8 FixPak 6 Command line parameters section. For a list of product abbreviations, see the Product abbreviations section. All images must be uncompressed for the DB2 Setup wizard GUI install or silent install to proceed. The installation fails if the images for all products are not uncompressed. 5. Change to the directory where the setup command is located. This is under the directory with the product abbreviation. For example, DB2 Enterprise Server Edition would be under the directory ESE. 6. Run the setup command to launch the DB2 Setup wizard. The command parameters required depend on whether you want to install the product in silent mode using a response file. * Setup wizard GUI installation To install DB2 Version 8 FixPak 6, enter: setup The DB2 Launchpad opens. Once you have initiated the installation, proceed by following the setup program's prompts. If you have more than one DB2 Version 8 product installed, the setup command detects the other installed DB2 products. If all the product images are uncompressed into subdirectories under the same parent directory, the setup command automatically launches the installation of all DB2 products without prompting you. If all the product images are uncompressed into different directories, the setup command detects the other installed DB2 products and prompts you for each directory path. Online help is available to guide you through the remaining steps. To invoke the online help, click Help or press F1. * Silent mode installation using a response file To install DB2 Version 8 FixPak 6 in silent mode, you need to run the installation with a response file. If you have more than one DB2 Version 8 product installed, all uncompressed product images must be in subdirectories under the same parent directory. For example, to install DB2 Version 8 FixPak 6 in silent mode enter: setup -u e:\db2fixpk.rsp -t c:\db2fixpk.trc -l c:\db2fixpk.log Sample response files can be found in the \db2\windows\samples directory. For example, ESE\db2\windows\samples. For a list of product abbreviations, see the Product abbreviations section. For a description of the setup command, see the DB2 Version 8 FixPak 6 Command line parameters section. 1.11 DB2 Version 8 FixPak 6 Command line parameters 1.11.1 FP6_$PTF_ command options To launch the installation process, use the FP6_$PTF_ command where $PTF represents: * WR21340 on Windows 32-bit * WR21341 on Windows 64-bit For a list of abbreviations, see the Product abbreviations section. If only a single DB2 product is installed, the FP6_$PTF_ command can be issued, without parameters, to launch the installation process. For example, to uncompress DB2 Enterprise Server Edition in a 32-bit environment, enter FP6_WR21340_ESE. If you have more than one DB2 Version 8 for Windows product installed on the same system, the directory you uncompress the products to depends on whether you plan to install DB2 Version 8 FixPak 6 using the DB2 Setup wizard or you plan to install in silent mode. When you uncompress the self-extracting images, you have the following options: * If you plan to install DB2 Version 8 FixPak 6 using the DB2 Setup wizard GUI, the setup command detects the other installed DB2 products. If all the product images are uncompressed into the same parent directory, the setup command automatically launches the installation of all DB2 products without prompting you. If the product images are uncompressed into different directories, the setup command detects the other installed DB2 products and prompts you for the directory path. * If you plan to install DB2 Version 8 FixPak 6 in silent mode, all the product images must be uncompressed into the same parent directory. The installation fails if the image for each product is not uncompressed. The FP6_$PTF_ command requires parameters. The following options are available: -s This parameter makes the extraction of the image silent. -e This parameter is used to stop the installation from launching automatically after the FixPak or modification level is uncompressed. This parameter is useful if you have multiple products installed and you just want to prepare for the installation by uncompressing the images. Without this parameter, the installation launches immediately after the FixPak or modification level is uncompressed. -f x:\ Uncompresses DB2 to a directory other than c:\temp where x:\ is a drive with enough space and is the directory to be used. -a If specified, this must be the last parameter specified. This is required to pass further parameters to the Setup command. Any of the Setup command parameters can be used. For a list of these parameters, see the Setup command options section. 1.11.2 Setup command options The setup command is run after the FixPak is uncompressed. The options are: -f This parameter forces any DB2 process to stop before installation begins. -i language Represents the two-letter language code of the language in which to perform the installation. For a list of languages, see the Language identifiers section. -l log_file This parameter shows the log for the installation. Default is My Documents\DB2LOG\db2wi.log -t trace_file The location of the trace file used when capturing detailed diagnostic information. -u response_file The location of the path and file name of the response file to use. -w This parameter keeps the parent process alive until the installation finishes. -?, -h This parameter generates usage information. 1.11.3 Language identifiers If you want to run a DB2 command in a language different from the default language on your computer, specify a language identifier. The language must be available on the platform where you are running the installation. Table 1. Language identifiers +----------------------------------+----------------------------------+ | Language | Language identifier | +----------------------------------+----------------------------------+ | Arabic | ar | +----------------------------------+----------------------------------+ | Brazilian Portuguese | br | +----------------------------------+----------------------------------+ | Bulgarian | bg | +----------------------------------+----------------------------------+ | Chinese, Simplified | cn | +----------------------------------+----------------------------------+ | Chinese, Traditional | tw | +----------------------------------+----------------------------------+ | Croatian | hr | +----------------------------------+----------------------------------+ | Czech | cz | +----------------------------------+----------------------------------+ | Danish | dk | +----------------------------------+----------------------------------+ | Dutch | nl | +----------------------------------+----------------------------------+ | English | en | +----------------------------------+----------------------------------+ | Finnish | fi | +----------------------------------+----------------------------------+ | French | fr | +----------------------------------+----------------------------------+ | German | de | +----------------------------------+----------------------------------+ | Greek | el | +----------------------------------+----------------------------------+ | Hebrew | iw | +----------------------------------+----------------------------------+ | Hungarian | hu | +----------------------------------+----------------------------------+ | Italian | it | +----------------------------------+----------------------------------+ | Japanese | jp | +----------------------------------+----------------------------------+ | Korean | kr | +----------------------------------+----------------------------------+ | Norwegian | no | +----------------------------------+----------------------------------+ | Polish | pl | +----------------------------------+----------------------------------+ | Portuguese | pt | +----------------------------------+----------------------------------+ | Romanian | ro | +----------------------------------+----------------------------------+ | Russian | ru | +----------------------------------+----------------------------------+ | Slovak | sk | +----------------------------------+----------------------------------+ | Slovenian | sl | +----------------------------------+----------------------------------+ | Spanish | es | +----------------------------------+----------------------------------+ | Swedish | se | +----------------------------------+----------------------------------+ | Turkish | tr | +----------------------------------+----------------------------------+ 1.12 Installing DB2 Version 8 FixPak 6 in an MSCS environment This topic describes how to install DB2 Version 8 FixPak 6 in a Microsoft Cluster Server (MSCS) environment. Assumptions: To illustrate how to install DB2 Version 8 FixPak 6 in an MSCS environment, a simple example configuration must be understood. In this example, the initial configuration is a DB2 instance that is comprised of two partitions. In addition, there are two Cluster Groups: * DB2 Group 0: contains Partition 0 active on Machine A. The Administration Server (DAS) is also located here. * DB2 Group 1: contains Partition 1 active on Machine B. This is the initial configuration. Procedure To install DB2 Version 8 FixPak 6 in an MSCS environment: 1. Ensure automatic failback is set to off. a. During the installation process you might have to restart your machine. When this happens the cluster service restarts automatically. Therefore the automatic failback must be set off so none of the groups automatically failback. b. In DB2 Group 0, to disable automatic failback: 1) From the Cluster Administrator window, right click DB2 Group 0. 2) Select Properties. The DB2 Group 0 Properties window displays. 3) On the Failback tab, select the Prevent failback radio button. 4) Click OK. c. In DB2 Group 1, to disable automatic failback: 1) From the Cluster Administrator window, right click DB2 Group 1. 2) Select Properties. The DB2 Group 1 Properties window displays. 3) On the Failback tab, select the Prevent failback radio button. 4) Click OK. 2. Move DB2 Group 1 to Machine A. a. From the Cluster Administrator GUI, click on DB2 Group 1. b. Right click, select Move Group. The Owner column changes to Machine A. 3. Stop the cluster service on Machine B. a. From the Component Services window, right click Cluster Service. b. Click Stop. 4. Download and install DB2 Version 8 FixPak 6 on Machine B. Note: * DB2 is still running and available on Machine A. * As part of the installation process, you might have to restart your computer. * The Silent Mode installation process can also be used to install DB2 Version 8 FixPak 6. 5. Take the DB2 resources on Machine A offline. a. Partition 0, Partition 1, and the DAS are all resources on Machine A. These must be taken offline one at a time. To take Machine A resources offline: 1) From the Cluster Administrator window, in the left window panel, select Groups. 2) Select DB2 Group 0. The resources for the group display in the right window panel. * For DB2 Group 0 the DB2 resources include Partition 0 and the DAS. 3) In the right window panel, right click one of the resources, select Take Offline. * Repeat this step for each of the DB2 resources in DB2 Group 0. 4) Select DB2 Group 1. The resources for the group display in the right window panel. * For DB2 Group 1 the DB2 resources include Partition 1. 5) In the right window panel, right click the resource (Partition 1), select Take Offline. 6. Start the cluster service on Machine B. (If the installation required a restart of your computer, and, if the Restart Type for the cluster service is set to automatic, skip this step because the cluster service is already started.) To start the cluster service: a. From the Component Services window, right click Cluster Service. b. Click Start. 7. Move DB2 Group 0 and DB2 Group 1 to Machine B. a. From the Cluster Administrator window, click DB2 Group 0. b. Right click, select Move Group. The Owner column changes to Machine B. c. Click on DB2 Group 1. d. Right click, select Move Group. The Owner column changes to Machine B. 8. Bring the DB2 resources on Machine B online. a. Partition 0, Partition 1, and the DAS are now resources on Machine B. These must be brought back online one at a time. To bring these resources online: 1) From the Cluster Administrator window, in the left window panel, select Groups. 2) Select DB2 Group 0. The resources for the group display in the right window panel. * For DB2 Group 0 the DB2 resources include Partition 0 and the DAS. 3) In the right window panel, right click one of the resources, select Bring Online. * Repeat this step for each of the DB2 resources in DB2 Group 0. 4) Select DB2 Group 1. The resources for the group display in the right window panel. * For DB2 Group 1 the DB2 resources include Partition 1. 5) In the right window panel, right click the resource (Partition 1), select Bring Online. 9. Stop the cluster service on Machine A. a. From the Component Services window, right click Cluster Service. b. Click Stop. 10. Download and install DB2 Version 8 FixPak 6 on Machine A. Note: * DB2 is still running and available on Machine A. * As part of the installation process, you might have to restart your computer. * The Silent Mode installation process can also be used to install DB2 Version 8 FixPak 6. 11. Start the cluster service on Machine A. (If the installation required a restart of your computer, and, if the Restart Type is set to automatic, skip this step because the cluster service is already started.) To start the cluster service: a. From the Component Services window, right click Cluster Service. b. Click Start. 12. Move DB2 Group 0 to Machine A. a. From the Cluster Administrator window, click DB2 Group 0. b. Right click, select Move Group. The Owner column changes to Machine A. This brings the MSCS environment back to the initial configuration. 13. If automatic failback was turned off in Step 1, you must turn it on. a. In DB2 Group 0, to enable automatic failback: 1) From the Cluster Administrator GUI, right click DB2 Group 0. 2) Select Properties. The DB2 Group 0 Properties window displays. 3) On the Failback tab, select the Allow failback radio button. 4) Click OK. b. In DB2 Group 1, to enable automatic failback: 1) From the Cluster Administrator window, right click DB2 Group 1. 2) Select Properties. The DB2 Group 1 Properties window displays. 3) On the Failback tab, select the Allow failback radio button. 4) Click OK. 1.13 Applying a FixPak or a modification level for Data Links Manager (Windows) To apply a FixPak or a modification level for Data Links Manager on Windows: 1. As the DB2 Data Links Manager Administrator (dlmadmin), bring down the DB2 Data Links Manager by stopping the DB2 Data Links Manager service: a. Select Start and select Settings->Control Panel->Services. b. Right click on the DB2 Data Links Manager service and select Stop. Ensure that there are no other DB2 processes remaining, by issuing a db2stop command for each instance. 2. Ensure that all DB2 services have been stopped. Use the services control panel applet to stop these services. 3. Install the FixPak or the modification level. 4. As the DB2 Data Links Manager Administrator, run the following commands to bring up the DB2 Data Links Manager: dlfm bind dlfm start Alternatively, the dlfm start command can be performed through the Windows Services GUI. 1.14 After installation 1.14.1 Enable DB2 Remote Command Service If you installed a partitioned DB2 server on Windows 2000, Windows Server 2003, or Windows XP, you must enable the DB2 Remote Command Service to protect your data and resources. To be fully secured, you will need to enable either the computer, if the service is running under the context of the LocalSystem account, or a user for delegation, if the services is being run under the logon context of a user. To enable the DB2 Remote Command Service: 1. Open the Active Directory Users and Computers window, click Start and select Programs --> Administrative tools --> Active Directory Users and Computers. 2. In the right window panel, right click on the computer or user to enable, select Properties. 3. Click the General tab and select the Trust computer for delegation check box. For user setting, click the Account tab and check the Account is trusted for delegation check box in the Account option group. Ensure that the Account is sensitive and cannot be delegated box has not been checked. 4. Click OK to enable the computer or user for delegation. Repeat these steps for each computer or user that needs to be enabled. You must restart your computer for the security change to take effect. You can disable the DB2 Remote Command Service security features and return the environment to its previous state using the DB2RCMD_LEGACY_MODE registry variable. To disable the DB2 Remote Command Service security features, enter the following command: db2set DB2RCMD_LEGACY_MODE=ON Note: This registry variable requires Boolean values as arguments, the values YES, 1, TRUE, and ON are all equivalent and the values NO, 0, FALSE, and OFF are also equivalent. You can specify any of the appropriate equivalent values. 1.14.2 Re-binding bind files You need to bind your DB2 utilities against all your databases after the installation. This step is necessary for the fixes to become effective. The binding procedure, which follows, needs to be performed only once per database. 1.14.2.1 Re-binding to DB2 UDB databases After applying fixes, execute the following commands: db2 terminate db2 CONNECT TO db2 BIND $DB2DIR\BND\@db2ubind.lst GRANT PUBLIC db2 BIND $DB2DIR\BND\@db2cli.lst GRANT PUBLIC db2 terminate where represents the name of a database to which the utilities should be bound and $DB2DIR represents the directory where you have installed DB2. db2ubind.lst and db2cli.lst contain lists of required bind files used by DB2 UDB Version 8. 1.14.2.2 Re-binding host databases If you are connecting to host databases, you need to bind the new bind files to the host. Use the DB2 Command Line Processor to connect to the host database and bind the utilities as follows: HOST COMMAND ===== =================================================================== MVS BIND $DB2DIR\BND\@ddcsmvs.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VM BIND $DB2DIR\BND\@ddcsvm.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VSE BIND $DB2DIR\BND\@ddcsvse.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC OS400 BIND $DB2DIR\BND\@ddcs400.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC 1.14.2.3 Re-binding specific packages If you want to bind only the specific .bnd files to the database, issue the following commands for each database. db2 terminate db2 CONNECT TO db2 BIND $DB2DIR\BND\ BLOCKING ALL GRANT PUBLIC sqlerror continue db2 terminate where represents the name of the bind file, and represents the name of your database. 1.14.2.4 Bind db2schema.bnd to existing databases For installations 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 commands sequences: At a command prompt: db2 terminate db2 CONNECT TO db2 BIND $DB2DIR\BND\db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue db2 terminate or, At the DB2 command line: TERMINATE CONNECT TO BIND $DB2DIR\BND\db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue TERMINATE where represents the name of a database to which the utilities should be bound and $DB2DIR represents the directory where you have installed DB2. 1.14.2.5 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.14.3 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 2. 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.15 Known problems and workarounds (Version 8 FixPak 6) 1.15.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.15.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.15.3 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.16 Known problems and workarounds (prior to Version 8 FixPak 6) 1.16.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 at Web site http://publib.boulder.ibm.com/infocenter/db2help/topic/com.ibm.db2.udb.doc/start/c0009827.htm. These additions to the following sections must also be noted. 1.16.1.1 Installing the application server -- additional prerequisite The application server for DB2 requires DB2 ESE Version 8.1.2 or higher. 1.16.1.2 Installing the application server -- additional restriction The default 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.16.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.bat -db2path C:\IBM\SQLLIB -instance DB2 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. 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. ** *******************************************************************************