DB2 Version 8 FixPak 5 Readme Contents 1) Readme for IBM(R) DB2 Universal Database(TM) Version 8 FixPak 5 (Windows(R)) 1a) About this readme 1b) Who should read this readme file 1c) How to get help 1c.i) IBM FTP server 1d) PTF information 1e) Supported products and components by operating system 1f) Installation scenarios 1g) Prerequisites 1h) Prior to installing Version 8 FixPak 5 1i) Product abbreviations 1j) Installing DB2 Version 8 FixPak 5 1k) DB2 Version 8 FixPak 5 Command line parameters 1k.i) FP5_$PTF_ command options 1k.ii) Setup command options 1k.iii) Language identifiers 1l) Installing DB2 Version 8 FixPak 5 in an MSCS environment 1m) Applying a FixPak or a modification level for Data Links Manager (Windows) 1n) After installation 1n.i) Enable DB2 Remote Command Service 1n.ii) Re-binding bind files 1o) Known problems and workarounds (Version 8 FixPak 5) 1o.i) SQL limits 1p) Known problems and workarounds (prior to Version 8 FixPak 5) 1p.i) Recommended application server for deploying DB2 Web Tools 2) Notices 1) Readme for IBM(R) DB2 Universal Database(TM) Version 8 FixPak 5 (Windows(R)) 1a) About this readme DB2 Version 8 FixPak 5 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 5 is the fifth 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, and now Version 8 FixPak 5. 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 support, you must contact IBM support before you install DB2 Version 8 FixPak 5 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. 1b) 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 5. 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. 1c) 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 5 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 5 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. 1c.i) IBM FTP server DB2 Version 8 FixPak 5 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 (32-bit) go to ps/products/db2/fixes/english-us/db2winIA32v8/fixpak/FP5_WR21334 * For the FixPak or modification level images for Windows (64-bit) go to ps/products/db2/fixes/english-us/db2winIA64v8/fixpak/FP5_WR21335. 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. 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: +---------+----------------------+-------------------------+---------+ | Operati | DB2 Administration | DB2 Application | DB2 | | ng | Client | Development Client | Run-Tim | | System | | | 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 | | PA-RISC | languages are in one | are in one tarred file | support | | 11i | tarred file | | ed | | (32- | | | languag | | and | | | es are | | 64-bit) | | | in one | | and | | | tarred | | HP-UX | | | file | | on IA64 | | | | +---------+----------------------+-------------------------+---------+ | 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 | | Operati | languages are in one | are in one tarred file | support | | ng | tarred file | | ed | | Environ | | | languag | | ments | | | 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 | +---------+----------------------+-------------------------+---------+ 1d) PTF information The following table details the PTF and VRMF information: +------------------------------------------+--------------------------+ | Operating system or product | PTF | +------------------------------------------+--------------------------+ | Windows 32-bit | WR21334 | +------------------------------------------+--------------------------+ | Windows 64-bit | WR21335 | +------------------------------------------+--------------------------+ 1e) 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 Express, Version 8 * DB2 UDB Personal Edition, Version 8 1f) 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. 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, (for example, DB2 Enterprise Server Edition and DB2 Warehouse Center) you will need to download all of the corresponding product-specific FixPaks before starting the FixPak installation process. This new delivery mechanism provides the following advantages: * Less disk space is required on the operating system drive. * Overall amount of disk spaces 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. 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. 1g) 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 5. 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 5. 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 5. 1h) Prior to installing Version 8 FixPak 5 * 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 5. 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. 1i) 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 1j) Installing DB2 Version 8 FixPak 5 DB2 Version 8 FixPak 5 images are downloaded directly from the IBM anonymous FTP server. Also use this method for installing Version 8 FixPak 5 in silent mode. Restrictions Once you install DB2 Version 8 FixPak 5, you cannot roll back to a previous level. Procedure To install the DB2 Version 8 FixPak 5: 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. 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 FP5_$PTF_ -e -f command (where $PTF represents either: WR21334 on Windows 32-bit, or WR21335 on Windows 64-bit). For example, to uncompress the DB2 Enterprise Server Edition product to a directory called c:\db2_fixpak\images, enter FP5_WR21334_ESE -e -f c:\db2_fixpak\images (For a description of this command, see the DB2 Version 8 FixPak 5 Command line parameters section.) * If you have more than one DB2 Version 8 product installed, you must uncompress the image for each product under a common parent directory. All images must be uncompressed for the GUI install or silent install to proceed. The installation will fail if the image for each product is 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. For a description of setup command, see the DB2 Version 8 FixPak 5 Command line parameters section. The DB2 Launchpad opens. Once you have initiated the installation, proceed by following the setup program's prompts. Online help is available to guide you through the remaining steps. To invoke the online help, click Help or press F1. 7. If you are installing DB2 Version 8 FixPak 5 in silent mode, you need to run the installation with a response file. In this case, enter setup -u db2fixpk.rsp The setup command is located under the directory with the product abbreviation. For a description of the setup command, see the DB2 Version 8 FixPak 5 Command line parameters section. To see sample response files, go to the \db2\windows\samples directory. For example, CONEE\db2\windows\samples. For a list of abbreviations, see the Product abbreviations section. Sample response files for Version 8 FixPak 5 can be found in the \db2\windows\samples directory. 1k) DB2 Version 8 FixPak 5 Command line parameters 1k.i) FP5_$PTF_ command options To launch the installation process, use the FP5_$PTF_ command where $PTF represents: * WR21334 on Windows 32-bit * WR21335 on Windows 64-bit For a list of abbreviations, see the Product abbreviations section. If only a single DB2 product is installed, the FP5_$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 FP5_WR21334_ESE. If multiple DB2 products or a silent installation are being installed, the FP5_$PTF_ command requires parameters. The following options are available: FP5_$PTF_ -s -e -f x:\ -a -u e:\fixpak.rsp -t c:\fixpak.trc -l c:\fixpak.log where: -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. 1k.ii) Setup command options The setup command is run after the FixPak is uncompressed. The options are: setup -f -i language -l log_file -t trace file -u response file -w -? -h where: -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. 1k.iii) 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 | +----------------------------------+----------------------------------+ 1l) Installing DB2 Version 8 FixPak 5 in an MSCS environment This topic describes how to install DB2 Version 8 FixPak 5 in a Microsoft Cluster Server (MSCS) environment. Assumptions: To illustrate how to install DB2 Version 8 FixPak 5 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 5 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 5 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 5. 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 5 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 5. 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. 1m) 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. 1n) After installation 1n.i) 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. 1n.ii) 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. 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. 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 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. 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. 1o) Known problems and workarounds (Version 8 FixPak 5) 1o.i) SQL limits The Maximum NPAGES in a buffer pool for 32-bit releases is 1 048 576. Table 2. Database Manager Limits Description | Limit ----------------------------------------------+---------------------- Maximum NPAGES in a buffer pool for 32-bit | 1 048 576 releases | ----------------------------------------------+---------------------- Maximum NPAGES in a buffer pool for 64-bit | 2 147 483 647 releases | ----------------------------------------------+---------------------- Maximum total size of all buffer pool slots | 2 147 483 646 (4K) | ----------------------------------------------+---------------------- Maximum number of nested levels for stored | 16 procedures | ----------------------------------------------+---------------------- Maximum number of table spaces in a database | 32 768 ----------------------------------------------+---------------------- Maximum number of attributes in a structured | 4082 type | ----------------------------------------------+---------------------- Maximum number of simultaneously opened LOB | 32 100 locators in a transaction | 1p) Known problems and workarounds (prior to Version 8 FixPak 5) 1p.i) 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. Installing the application server -- additional prerequisite The application server for DB2 requires DB2 ESE Version 8.1.2 or higher. 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 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) 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. ** *******************************************************************************