DB2 Version 8 FixPak 6 Readme

Contents

1.0 Readme for IBM DB2 Universal Database(TM) Version 8 FixPak 6 for
AIX, Solaris Operating Environments, HP-UX, and Linux
1.1 About this readme
1.2 Who should read this readme file
1.3 How to get help
1.3.1 IBM FTP server
1.4 PTF information
1.5 Supported products and components by operating system
1.6 Prerequisites
1.7 Updated patch levels -- servers
1.8 Updated patch levels -- clients
1.9 Prior to installing DB2 Version 8 FixPak 6
1.9.1 Setting up Version 8 FixPak 6 (Solaris Operating Environments,
AIX 4.3.3, and AIX 5L)
1.9.2 Data Warehouse functionality (Linux, AIX, and Solaris
Operating Environments)
1.10 Installing DB2 Version 8 FixPak 6
1.10.1 After installation
1.11 Installation of a FixPak or a modification level from a directory
path
1.12 Applying a FixPak or a modification level for Data Links Manager
(AIX)
1.13 Applying a FixPak or a modification level for Data Links Manager
(Solaris Operating Environments)
1.14 Uninstalling FixPaks or modification levels on Linux or UNIX
1.15 Installing DB2 Version 8 Alternate FixPak
1.16 Uninstalling DB2 Version 8 Alternate FixPak
1.17 Known problems and workarounds (Version 8 FixPak 6)
1.17.1 New parameter -- db2sqljcustomize - DB2 SQLJ Profile
Customizer Command
1.17.2 New parameter -- sqlj - DB2 SQLJ Translator Command
1.17.3 Installing Query Patroller at FixPak 3 level or later
1.17.4 Replication for Informix sources
1.18 Known problems and workarounds (prior to Version 8 FixPak 6)
1.18.1 Recommended application server for deploying DB2 Web Tools
1.18.2 DB2 Setup Wizard appears not to run using Exceed (Linux)
1.18.3 DB2 Data Links Manager installation when DB2 Enterprise
Server Edition already installed
1.18.4 Loss of Control Center functionality
2.0 Notices

1.0 Readme for IBM DB2 Universal Database(TM) Version 8 FixPak 6 for
AIX, Solaris Operating Environments, HP-UX, and Linux

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 upgrade their earlier level of DB2(R) Version
8 to Version 8 FixPak 6. This readme file contains operating system
specific information about the latest changes and known problems and
workarounds for DB2 UDB.

This readme file contains DB2 Version 8 FixPak 6 information for all
Linux and UNIX(R) operating systems supported by DB2 Version 8. Specific
information for each supported operating system is described in separate
sections of this readme. Unless otherwise specified, the instructions
are applicable to all supported operating systems.

Users of DB2 Information Integrator can access the latest information at
http://www.ibm.com/software/data/integration/db2ii, including product
documentation and product Release Notes.

1.3 How to get help

Web-based support for DB2 products, including documentation, and APAR
information is provided at
* http://www.ibm.com/software/data/db2/udb/winos2unix/support

The main Usenet newsgroup for DB2 product-related questions is
comp.databases.ibm-db2.

To contact DB2 Customer Service by phone:
* In Canada and the United States, call 1-800-IBM-SERV (426-7378).
* Worldwide, see the Directory of worldwide contacts for information on
IBM offices in your country or region, at
http://www.ibm.com/planetwide

For additional information about changes to the product, review the
product Release Notes after you have installed DB2 Version 8 FixPak 6:

AIX(R) | /usr/opt/db2_08_01/Readme/%L/Release.Notes
-----------------------+---------------------------------------------
HP-UX, Linux, and | /opt/IBM/db2/V8.1/Readme/%L/Release.Notes
Solaris Operating |
Environment |

where %L represents the locale name.

You can also view the latest product Release Notes without installing
DB2 Version 8 FixPak 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 can be downloaded from the IBM anonymous FTP
server at ftp.software.ibm.com. Go to ps/products/db2/fixes/%L/%P/
where:
* %L represents the appropriate locale; for example, english-us,
spanish, german.
* %P represents the supported operating system name and version.

The DB2 Version 8 FixPak 6 installation image can be found in the fixpak
directory. The mfp directory contains the DB2 Version 8 Alternate FixPak
image. The client directory holds client refresh images on the related
level.

The directory names for each specific Linux and UNIX operating system
are:

AIX 4.3.3 (32-bit) | db2aix433v8
----------------------------------+----------------------------------
AIX 5L(TM) (32-bit & 64-bit) | db2aix5v8
----------------------------------+----------------------------------
HP-UX 11i (32-bit & 64-bit) | db2hpv8
----------------------------------+----------------------------------
HP-UX 11i v2 (IA64) | db2hpIA64v8
----------------------------------+----------------------------------
Linux (x86, 32-bit) | db2linuxIA32v8
----------------------------------+----------------------------------
Linux (IA64, 64-bit) | db2linuxIA64v8
----------------------------------+----------------------------------
Linux (iSeries(TM) and | db2linuxPPCv8
pSeries(TM), 32-bit) |
----------------------------------+----------------------------------
Linux (S/390(R) and zSeries(TM), | db2linux390v8
31-bit) |
----------------------------------+----------------------------------
Linux (S/390 and zSeries, | db2linux39064v8
64-bit) |
----------------------------------+----------------------------------
Linux (AMD64, 32-bit & 64-bit) | db2linuxAMD64v8
----------------------------------+----------------------------------
Solaris Operating Environment | db2sunv8
(32-bit & 64-bit) |

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.

1.4 PTF information

The following table details the PTF and VRMF information.

+----------------------------------+----------------------------------+
| Operating system | PTF |
+----------------------------------+----------------------------------+
| AIX 4.3.3 | U497634 |
+----------------------------------+----------------------------------+
| AIX 5 | U497635 |
+----------------------------------+----------------------------------+
| Solaris Operating Environment | U497645 |
+----------------------------------+----------------------------------+
| HP-UX 11i | U497646 |
+----------------------------------+----------------------------------+
| HP-UX 11i v2 (IA64) | U497647 |
+----------------------------------+----------------------------------+
| LINUX (x86, 32-bit) | MI00080 |
+----------------------------------+----------------------------------+
| LINUX (IA64, 64-bit) | MI00081 |
+----------------------------------+----------------------------------+
| LINUX (iSeries and pSeries) | MI00082 |
+----------------------------------+----------------------------------+
| LINUX (AMD64, 64-bit) | MI00083 |
+----------------------------------+----------------------------------+
| LINUX (S/390, zSeries 31-bit) | MI00084 |
+----------------------------------+----------------------------------+
| LINUX (S/390, zSeries 64-bit) | MI00085 |
+----------------------------------+----------------------------------+

1.5 Supported products and components by operating system

The following lists show the supported products and components for each
Linux and UNIX operating system:

AIX(R) 4.3.3 (32-bit)
Product and components list:
* DB2 Administration Client, Version 8
* DB2 Application Development Client, Version 8
* DB2 Connect(TM) Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Unlimited Edition, Version 8
* DB2 Cube Views, Version 8
* DB2 Data Links Manager, Version 8
* DB2 HTML Documentation, Version 8
* DB2 PDF Documentation, Version 8
* DB2 Query Patroller, Version 8
* DB2 Run-Time Client, Version 8
* DB2 Spatial Extender, Version 8
* DB2 UDB Enterprise Server Edition, Version 8
* DB2 UDB Workgroup Server Edition, Version 8
* DB2 UDB Workgroup Server Unlimited Edition, Version 8
* DB2 Warehouse Manager, Version 8
* DB2 Warehouse Manager Connectors, Version 8

AIX(R) 5L (32-bit and 64-bit)
Product list:
* DB2 Administration Client, Version 8
* DB2 Application Development Client, Version 8
* DB2 Connect Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Enterprise Unlimited Edition, Version 8
* DB2 Cube Views, Version 8
* DB2 Data Links Manager, Version 8
* DB2 HTML Documentation, Version 8
* DB2 PDF Documentation, Version 8
* DB2 Query Patroller, Version 8
* DB2 Run-Time Client, Version 8
* DB2 Spatial Extender, Version 8
* DB2 UDB Enterprise Server Edition, Version 8
* DB2 UDB Workgroup Server Edition, Version 8
* DB2 UDB Workgroup Server Unlimited Edition, Version 8
* DB2 Warehouse Manager, Version 8
* DB2 Warehouse Manager Connectors, Version 8

HP-UX(TM) 11i (PA-RISC, 32-bit and 64-bit)
Product list:
* DB2 Administration Client, Version 8
* DB2 Connect Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Unlimited Edition, Version 8
* DB2 HTML Documentation, Version 8
* DB2 PDF Documentation, Version 8
* DB2 Query Patroller, Version 8
* DB2 Run-Time Client, Version 8
* DB2 Spatial Extender, Version 8
* DB2 UDB Enterprise Server Edition, Version 8
* DB2 UDB Workgroup Server Edition, Version 8
* DB2 UDB Workgroup Server Unlimited Edition, Version 8

HP-UX(TM) 11i v2 (IA64)
Product list:
* DB2 Administration Client, Version 8
* DB2 Application Development Client, Version 8
* DB2 Connect Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Unlimited Edition, Version 8
* DB2 Run-Time Client, Version 8
* DB2 UDB Enterprise Server Edition, Version 8

Linux(TM) (x86, 32-bit)
Product list:
* DB2 Administration Client, Version 8
* DB2 Application Development Client, Version 8
* DB2 Connect Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Personal Edition, Version 8
* DB2 Connect Unlimited Edition, Version 8
* DB2 Cube Views, Version 8
* DB2 HTML Documentation, Version 8
* DB2 PDF Documentation, Version 8
* DB2 Query Patroller, Version 8
* DB2 Run-Time Client, Version 8
* DB2 Spatial Extender, Version 8
* DB2 UDB Enterprise Server Edition, Version 8
* DB2 UDB Express, Version 8
* DB2 UDB Personal Edition, Version 8
* DB2 UDB Workgroup Server Edition, Version 8
* DB2 UDB Workgroup Server Unlimited Edition, Version 8
* DB2 Warehouse Manager, Version 8

Linux(TM) (IA64, 64-bit)
Product list:
* DB2 Administration Client, Version 8
* DB2 Application Development Client, Version 8
* DB2 Connect Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Personal Edition, Version 8
* DB2 Connect Unlimited Edition, Version 8
* DB2 HTML Documentation, Version 8
* DB2 PDF Documentation, Version 8
* DB2 Run-Time Client, Version 8
* DB2 Spatial Extender, Version 8
* DB2 UDB Enterprise Server Edition, Version 8
* DB2 UDB Personal Edition, Version 8

Linux(TM) (iSeries and pSeries)
Product list:
* DB2 Administration Client, Version 8
* DB2 Connect Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Unlimited Edition, Version 8
* DB2 HTML Documentation, Version 8
* DB2 PDF Documentation, Version 8
* DB2 Run-Time Client, Version 8
* DB2 UDB Enterprise Server Edition, Version 8
* DB2 UDB Workgroup Server Edition, Version 8
* DB2 UDB Workgroup Server Unlimited Edition, Version 8

Linux(TM) (S/390(R) and zSeries(R) 31-bit)
Product list:
* DB2 Administration Client, Version 8
* DB2 Connect Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Unlimited Edition, Version 8
* DB2 HTML Documentation, Version 8
* DB2 PDF Documentation, Version 8
* DB2 Run-Time Client, Version 8
* DB2 Spatial Extender, Version 8
* DB2 UDB Enterprise Server Edition, Version 8

Linux(TM) (S/390(R) and zSeries(R) 64-bit)
Product list:
* DB2 Connect Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Unlimited Edition, Version 8

Linux(TM) (AMD64)
Product list:
* DB2 Administration Client, Version 8
* DB2 Application Development Client, Version 8
* DB2 Connect Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Personal Edition, Version 8
* DB2 Connect Unlimited Edition, Version 8
* DB2 HTML Documentation, Version 8
* DB2 PDF Documentation, Version 8
* DB2 Run-Time Client, Version 8
* DB2 UDB Enterprise Server Edition, Version 8
* DB2 UDB Personal Edition, Version 8

Solaris(R) Operating Environments (32-bit and 64-bit)
Product list:
* DB2 Administration Client, Version 8
* DB2 Application Development Client, Version 8
* DB2 Connect Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Unlimited Edition, Version 8
* DB2 Cube Views, Version 8
* DB2 Data Links Manager, Version 8
* DB2 HTML Documentation, Version 8
* DB2 PDF Documentation, Version 8
* DB2 Query Patroller, Version 8
* DB2 Run-Time Client, Version 8
* DB2 Spatial Extender, Version 8
* DB2 UDB Enterprise Server Edition, Version 8
* DB2 UDB Workgroup Server Edition, Version 8
* DB2 UDB Workgroup Server Unlimited Edition, Version 8
* DB2 Warehouse Manager, Version 8
* DB2 Warehouse Manager Connectors, Version 8

If you add new components after you install DB2 Version 8 FixPak 6, you
need to reinstall DB2 Version 8 FixPak 6 to ensure that the newly added
components are updated.

1.6 Prerequisites

Ensure you have reviewed the software, hardware, and operating system
requirements. See the Updated patch levels section and the Release Notes
for the latest information.
* You must have a DB2 product Version 8 installed at a lower VRMF level
than DB2 Version 8 FixPak 6 before installation.
* Ensure that you have read the entire contents of this readme.

To determine if the required prerequisites are installed, issue the
appropriate command for your operating system to display information
about the currently installed version of DB2.

1.7 Updated patch levels -- servers

For the most up-to-date operating system information, see
http://www.ibm.com/software/data/db2/udb/sysreqs.html

The following lists the updated patch level for DB2 Version 8 FixPak 6
servers:

AIX
* Version 4.3.3 (32-bit)
* With maintenance level 9 and APARs IY22308 and IY32690;
or
* With maintenance level 10 or later and APAR IY32690

* Version 5.1.0 (32-bit)
* With maintenance level 2 or later and APARs IY31254,
IY32217, IY32905, IY29345, and IY31080; or
* With maintenance level 3 or later and APAR IY48735 and
IY49254 if using JFS2 filesystems

* Version 5.1.0 (64-bit)
* With maintenance level 2 or later and APARs IY31254,
IY32217, IY32905, IY33023, IY29345, IY32466, IY31080, and
IY45135; or
* With maintenance level 3 or later and APAR IY48735 and
IY49254 if using JFS2 filesystem

* Version 5.2.0 (32-bit or 64-bit)
* APAR IY45135; or
* APAR IY45707 if using Concurrent I/O (CIO) mounted
volume; or
* APARs IY48339 and IY49304 if using JFS2 filesystem; or
* APAR IY49129 if using JFS2 filesystem and Concurrent I/O
(CIO) mounted volume

HP-UX HP-UX 11i (11.11) for systems with PA-RISC 2.x (PA-8x00)
processors with:
* June 2003 GOLDBASE11i bundle
* June 2003 GOLDAPPS11i bundle
* Patches PHSS_26560, PHKL_28489 and PHCO_27434
* Patches for Java SDK 1.3.1. See
http://www.hp.com/products1/unix/java/patches/index.html for
required patches.

HP-UX on IA64
HP-UX 11i v2 (B.11.23) for Itanium(R)-based systems requires
patch PHKL_30065.

Solaris Operating Environment

DB2 Workgroup Server Edition (single-partition database
environment only) is supported on the following Solaris
Operating Environment versions:
* Solaris 7 (32-bit) "Recommended & Security Patches" +
107226-17 + 107153-01 + 106327-10
* Solaris 8 (32-bit) "Recommended & Security Patches" +
108921-12 + 108940-24 + 108434-03 and 108528-12
* Solaris 9 (32-bit)

DB2 Enterprise Server Edition, on both single-partition and
partitioned database environment, is supported on the following
Solaris Operating Environment versions:
* Solaris 7 (32-bit) "Recommended & Security Patches" +
107226-17 + 107153-01 + 106327-10
* Solaris 7 (64-bit) "Recommended & Security Patches" +
107226-17 + 107153-01 + 106300-11 + 106327-10
* Solaris 8 (32-bit) "Recommended & Security Patches" +
108921-12 + 108940-24 + 108434-03 and 108528-12
* Solaris 8 (64-bit) "Recommended & Security Patches" +
108921-12 + 108940-24 + 108435-03 + 108434-03 and 108528-12
* Solaris 9 (32-bit)
* Solaris 9 (64-bit)

"Recommended & Security Patches" can be obtained from the
http://sunsolve.sun.com Web site. From the SunSolve Online Web
site, click on the "Patches" menu item in the left panel.

The J2SE Solaris Operating Environment Patch Clusters and the
SUNWlibC software are also required and can be obtained from
the http://sunsolve.sun.com Web site.

For DB2 on 64-bit Fujitsu PRIMEPOWER systems, you require the
following:
* Solaris 8 Kernel Update Patch 108528-16 or later to get the
fix for patch 912040-01.
* Solaris 9 Kernel Update Patch 112233-01 or later to get the
fix for patch 912041-01.

The Fujitsu PRIMEPOWER patches for the Solaris Operating
Environment can be downloaded from FTSI at:
http://download.ftsi.fujitsu.com/.

Linux To check for the latest technical information on the supported
levels of Linux, point your browser to
http://www.ibm.com/db2/linux/validate

1.8 Updated patch levels -- clients

The following lists the updated patch level for DB2 Version 8 FixPak 6
clients:

AIX
* Version 4.3.3 (32-bit)
* With maintenance level 9 and APARs IY22308 and IY32690;
or
* With maintenance level 10 or later and APAR IY32690

HP-UX HP-UX 11i (11.11) for systems with PA-RISC 2.x (PA-8x00)
processors with:
* June 2003 GOLDBASE11i bundle
* June 2003 GOLDAPPS11i bundle
* Patches PHSS_26560, PHCO_27434, and PHKL_28489
* Patches for Java SDK 1.3.1. See
http://www.hp.com/products1/unix/java/patches/index.html for
required patches.

HP-UX on IA64
HP-UX 11i v2 (B.11.23) for Itanium(R)-based systems requires
patch PHKL_30065.

Solaris Operating Environment

For the most up-to-date operating system information, see
http://www.ibm.com/software/data/db2/udb/sysreqs.html.

* Solaris Version 7 or later
* The following patches are required for the Solaris Operating
Environment Version 7:
* Solaris 7 (32-bit) "Recommended & Security Patches" +
107226-17 + 107153-01 + 106327-10
* Solaris 7 (64-bit) "Recommended & Security Patches" +
107226-17 + 107153-01 + 106300-11 + 106327-10
* Solaris 8 (32-bit) "Recommended & Security Patches" +
108921-12 + 108940-24 + 108434-03 and 108528-12
* Solaris 8 (64-bit) "Recommended & Security Patches" +
108921-12 + 108940-24 + 108435-03 + 108434-03 and
108528-12
* Solaris 9 (32-bit)
* Solaris 9 (64-bit)

"Recommended & Security Patches" can be obtained from the
http://sunsolve.sun.com Web site. From the SunSolve Online
Web site, click on the "Patches" menu item in the left
panel.

The J2SE Solaris Operating Environment Patch Clusters are
also required.

The following software is required to install a DB2 client on
Solaris Operating Environment:
* SUNWlibC

Linux To check for the latest technical information on the supported
levels of Linux, point your browser to
http://www.ibm.com/db2/linux/validate

1.9 Prior to installing DB2 Version 8 FixPak 6

Please read the Known problems and workarounds sections before
installing DB2 Version 8 FixPak 6.

Before starting the installation, ensure all DB2 processes are stopped.

1. Switch to root authority by running the su - root command.
2. Run the following commands for each instance:
su - iname
. $HOME/sqllib/db2profile
db2 force applications all
db2 terminate
db2stop
db2licd -end # run at each physical node
exit

where iname represents the instance owner name.

If you are a hacmp user, you must use the ha_db2stop command to stop
DB2 instead of the db2stop command. Otherwise, the db2stop command
triggers a failure event.

3. Run the following commands:
su - aname
. $HOME/das/dasprofile
db2admin stop
exit

where aname represents the DAS owner name.
4. On AIX, you should also run slibclean to unload unused shared
libraries from memory before installation:
/usr/sbin/slibclean

5. Stop all instances that are using DB2 Version 8, including the Fault
Monitor if it exists and is using DB2 Version 8.

1.9.1 Setting up Version 8 FixPak 6 (Solaris Operating Environments, AIX
4.3.3, and AIX 5L)

For Solaris Operating Environments, AIX 4.3.3 and AIX 5L, you need to
have a filesystem with 2 GB of free space to contain the tar.Z file and
the uncompressed installation image, in addition to the disk
requirements of Version 8 FixPak 6 in the installation path.

Downloading the Version 8 Alternate FixPak from the IBM anonymous FTP
server

If you are downloading the Version 8 Alternate FixPak from the IBM
anonymous FTP server at ftp.software.ibm.com, follow this procedure:
1. Untar and uncompress the following compressed .tar files:
* FP6_$PTF_ESE_MFP.tar.Z for AIX 4.3.3 and Solaris Operating
Environments
* FP6_$PTF_ESE_MFP_SBCS.tar.Z or FP6_$PTF_ESE_MFP_DBCS.tar.Z for AIX
5

where $PTF represents:
* U497634 on AIX 4.3.3
* U497635 on AIX 5
* U497645 on Solaris Operating Environments

Note: FP6_$PTF_ESE_MFP_SBCS.tar.Z (ese.mfp.sbcs.tar.Z inside)
supports the following languages: English, Brazilian,
Portuguese, Danish, Finnish, French, German, Italian,
Norwegian, Spanish, and Swedish. FP6_$PTF_ESE_MFP_DBCS.tar.Z
(ese.mfp.dbcs.tar.Z inside) supports the following languages:
English, Japanese, Korean, Simplified Chinese, and Traditional
Chinese.

2. Copy the ese.mfp.tar.Z file (for AIX 4.3.3 and Solaris Operating
Environments), or either ese.mfp.sbcs.tar.Z or ese.mfp.dbcs.tar.Z
(for AIX 5) to the tempspace that you set aside for this
installation.
3. Untar and uncompress the ese.mfp.tar(.Z) file.
4. See the FixpakReadme.txt for information on installing DB2 Version 8
Alternate FixPak from the tempspace directory where you untarred the
installation image.

Installing DB2 Version 8 Alternate FixPak from the CD-ROM

If you have the DB2 Version 8 Alternate FixPak from CD-ROM, follow this
procedure:
1. Copy the ese.mfp.tar(.Z) file to the tempspace that you set aside for
this installation. For AIX 5L, the file that you copy is
ese.mfp.sbcs.tar.Z or ese.mfp.dbcs.tar.Z. See the preceding section
for the supported languages in each file.
2. Untar and uncompress the ese.mfp.tar(.Z) file (for AIX 5L, untar
ese.mfp.sbcs.tar.Z or ese.mfp.dbcs.tar.Z).
3. See the FixpakReadme.txt for information on installing DB2 Version 8
Alternate FixPak from the tempspace directory where you untarred the
installation image.

Installing DB2 Version 8 FixPak 6 from the CD-ROM (AIX 4.3.3, and
Solaris Operating Environment)

If you have the DB2 Version 8 FixPak 6 CD-ROM for AIX 4.3.3, or for the
Solaris Operating Environment:
1. Copy the compressed tar file (FP6_$PTF.tar.Z), located on the CD-ROM,
into a temporary directory on your system. This directory must have 2
GB of free space.
2. Uncompress and untar the file (FP6_$PTF.tar.Z).
3. Follow the instructions in the Version 8 FixPak 6 readme to install
Version 8 FixPak 6 for AIX 4.3.3, or the Solaris Operating
Environment.

Note:
1. In steps 1 and 2 $PTF represents:
* U497634 for AIX 4.3.3
* U497635 for Solaris Operating Environment

2. These steps also apply if you download the .tar.Z file from the
IBM anonymous FTP server. Download the file and follow steps
1-3.

Installing DB2 Version 8 FixPak 6 from the CD-ROM (AIX 5L)

To install IBM DB2 Version 8 FixPak 6 from the CD-ROMs on AIX 5L, you
are required to manually copy the file sets from two CD-ROMs: REGULAR
FIXPAK 6 (Volume 1 of 4) and REGULAR FIXPAK 6 (Volume 2 of 4).

1. Copy the compressed tar file (FP6_U497635.tar.Z), located on REGULAR
FIXPAK 6 (Volume 1 of 4), into a temporary directory on your system.
This directory must have 2 GB of free space.
2. Copy the compressed tar file (extra.tar.Z), located on REGULAR FIXPAK
6 (Volume 2 of 4), into the same temporary directory on your system
that you used in Step 1.
3. Uncompress and untar the file (FP6_U497635.tar.Z).
4. Uncompress and untar the extra.tar.Z file.
5. Follow the instructions in the Installing DB2 Version 8 FixPak 6
section.

Note: These steps (except Step 2 and Step 4) also apply if you download
the .tar.Z file from the IBM anonymous FTP server.

1.9.2 Data Warehouse functionality (Linux, AIX, and Solaris Operating
Environments)

If you are running Data Warehouse functionality on Linux, for example
the Data Warehouse Agent that comes with some server products, you will
need to back up your /opt/IBM/db2/V8.1/bin/IWH.environment. If you have
this file, back it up before applying DB2 Version 8 FixPak 6.

On AIX and Solaris, you should back up the same file (for AIX, this file
is found in /usr/opt/db2_08_01/bin/IWH.environment).

1.10 Installing DB2 Version 8 FixPak 6

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.

Please read the Known problems and workarounds sections before
installing DB2 Version 8 FixPak 6.

Restrictions

The following restrictions apply when installing DB2 Version 8 FixPak 6:
* DB2 Version 8 FixPak 6 for AIX 4.3.3 can only be applied on AIX 4.3.3
and DB2 Version 8 FixPak 6 for AIX 5 can only be applied on AIX 5.
* On AIX, the installFixPak script provides installation prerequisite
checking that is not provided when you install DB2 Version 8 FixPak 6
using SMIT or installp. Using SMIT is still supported, but
installFixPak is the only method documented in this readme. For
instructions on using SMIT, see your AIX manuals. It is strongly
recommended that you use the installFixPak script to install DB2
Version 8 FixPak 6.
* For DB2 Version 8 for HP-UX on IA64, do not use the SAM utility to
install the FixPak. The only supported method to apply the FixPak is
to run the installFixPak command delivered with the current FixPak
image.
* On Linux, once you have installed DB2 Version 8 FixPak 6, you cannot
uninstall it and return to the previous DB2 level.

Procedure

To install DB2 Version 8 FixPak 6:
1. Change to the directory in which the installation image is located.
2. Enter the ./installFixPak command to launch the installation.

Note: By default, the installFixPak command will commit all of the
updated file sets on AIX.

On AIX, if you do not wish to commit the updates, you should issue the
installFixPak command with the -a option (for "apply" as opposed to
"commit") as follows:

./installFixPak -a

1.10.1 After installation

After installing DB2 Version 8 FixPak 6, you must:
* If you have DB2 Relational Connect installed, run the djxlink
command.
* Update instances to use the new level of DB2
* Restart the instances, and
* Re-bind the bind files

1.10.1.1 Relational Connect and the djxlink command

If you have DB2 Relational Connect installed, you must run the djxlink
command after installing DB2 Version 8 FixPak 6 and before running
db2iupdt. Perform the following steps:
1. Log on as root.
2. Remove or rename the file djxlink.out, which is located in the
$install_dir/lib/ directory, where $install_dir is the DB2
installation directory.
3. If you are using Relational Connect to connect to an Oracle data
source, set the environment variable ORACLE_HOME to the oracle home
directory.
4. Run the command: djxlink

1.10.1.2 Updating instances to use the new level of DB2

This is mandatory. All instances must be updated after a new level of
DB2 is installed.

You need to be logged on as root to update the instances. For each
instance, issue the command:

INSTHOME/instance/db2iupdt iname

where iname represents the instance name and INSTHOME represents the
installation directory appropriate to your operating system.

Run the dasupdt command if the database administration server (DAS)
instance exists and is a DB2 Version 8 DAS instance. To update the DAS
instance, issue the command:

INSTHOME/instance/dasupdt dasname

where dasname represents the DAS owner name and INSTHOME represents the
installation directory appropriate to your operating system.

For more information on the db2iupdt or dasupdt commands, run these
commands with the -h option.

1.10.1.3 Restarting the instances

To restart an instance:
1. Log in as the instance owner and enter the db2start command.
2. Repeat for each instance.

To restart the administration server, log in as the DAS owner and run
the db2admin start command.

1.10.1.4 Re-binding bind files

You need to bind your DB2 utilities against all your databases after
installation. This step is necessary for the fixes to complete the
installation and ensure that the right code level is used. The
procedure of binding, which follows, needs to be performed only once per
database.

1.10.1.4.1 Re-binding to DB2 UDB databases

After applying fixes, you must do one of the following command
sequences:

At a command prompt, enter:
db2 terminate
db2 CONNECT TO <dbname>
db2 BIND <path>/@db2ubind.lst BLOCKING ALL GRANT PUBLIC
db2 BIND <path>/@db2cli.lst BLOCKING ALL GRANT PUBLIC
db2 terminate
or,

At the DB2 command line, enter:
TERMINATE
CONNECT TO <dbname>
BIND <path>/@db2ubind.lst BLOCKING ALL GRANT PUBLIC
BIND <path>/@db2cli.lst BLOCKING ALL GRANT PUBLIC
TERMINATE

Where <dbname> represents the name of a database to which the utilities
should be bound, and where <path> represents the full path name of the
directory where the bind files are located, such as $HOME/sqllib/bnd
where $HOME represents the home directory of the instance for the
database server. db2ubind.lst and db2cli.lst contain lists of required
bind files used by DB2 UDB.

1.10.1.4.2 Re-binding host databases

If you are connecting to host databases, you also need to bind the new
bind files to the host. Use the DB2 Command Line Processor to connect
to the host database and bind the utilities as follows:

HOST COMMAND
======= ===================================================
MVS BIND <path>/@ddcsmvs.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE
VM BIND <path>/@ddcsvm.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE
VSE BIND <path>/@ddcsvse.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE
OS400 BIND <path>/@ddcs400.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE

See "Binding Applications and Utilities" in the DB2 Connect User's Guide
for a list of bind files that are used for your specific client
operating system. If a bind file changes and your clients do not use
that bind file, you do not need to bind it.

1.10.1.4.3 Re-binding specific packages

If you want to bind only a specific .bnd file to the database, issue one
of the following command sequences for each database.

At a command prompt, enter:
db2 terminate
db2 CONNECT TO <dbname>
db2 BIND <path>/<bind_file> BLOCKING ALL GRANT PUBLIC sqlerror continue
db2 terminate
or,

At the DB2 command line, enter:
TERMINATE
CONNECT TO <dbname>
BIND <path>/<bind_file> BLOCKING ALL GRANT PUBLIC sqlerror continue
TERMINATE

where <bind_file> represents the name of the bind file, and <dbname>
represents the name of your database.

1.10.1.4.4 Binding database utilities using the Run-Time Client

The Run-Time Client cannot be used to bind the database utilities
(import, export, reorg, the Command Line Processor) and DB2 CLI bind
files. You must use the DB2 Administration Client or the DB2 Application
Development Client instead.

You must bind the database utilities (import, export, reorg, the Command
Line Processor) and DB2 CLI bind files to each database before they can
be used with that database. In a network environment, if you are using
multiple clients that run on different operating systems or that are at
different DB2 version or service levels, you must bind the utilities
once for each operating system and DB2 client-version combination.

1.10.1.4.5 Bind db2schema.bnd to existing databases

After installation on the server, an additional bind file needs to be
bound to existing databases. This requirement does not apply to clients.

Procedure

To bind db2schema.bnd on the server, execute one of these command
sequences:

At a command prompt:
db2 terminate
db2 CONNECT TO <dbname>
db2 BIND <path>/db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue
db2 terminate
or,
At the DB2 command line:
TERMINATE
CONNECT TO <dbname>
BIND <path>/db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue
TERMINATE

where <dbname> represents the name of a database to which the utilities
should be bound, and where <path> is the full path name of the directory
where the bind files are located.

1.10.1.4.6 Rebinding after FixPak or patch installation

If you have existing spatial-enabled databases, you must rebind the list
file db2gse.lst after you install a DB2 FixPak or patch. The db2gse.lst
file contains the names of the bind files for the stored procedures that
DB2 Spatial Extender provides.

Prerequisites

To bind the db2gse.lst file, you must have one of the following
authorities:
* sysadm or dbadm authority
* ALTERIN privilege on the schema
* BIND privilege on the package

Procedure

To rebind the db2gse.lst file:
1. Change to the instance directory where the bind files are located.
a. On Windows, open a DB2 command window and enter the following
command:
cd %DB2PATH%\bnd

b. On UNIX, enter the following command:
cd $HOME/sqllib/bnd

where $HOME is the instance owner's home directory.

2. Connect to the database and execute the BIND command. For example,
enter:
db2 connect to dbname
db2 bind /home/instance/sqllib/bnd/@db2gse.lst
db2 terminate

You can use the DB2RBIND command with the ALL option instead of the BIND
command. For syntax and options for the BIND and DB2RBIND commands,
refer to the DB2 Command Reference.

1.10.1.5 Restrictions to adding products using the db2setup command

Once a DB2 product has been installed, additional DB2 products can be
added. If you use the db2setup command to add products the following
recommendations and restrictions apply.

Recommendations

Both the installed product and the product being added should be at the
same code level. For example, DB2 ESE Server Version 8 FixPak 5 is
already installed and you want to add the DB2 Information Integrator
product. In this case, DB2 Information Integrator should also be at the
Version 8 FixPak 5 level.

Restrictions

* If the DB2 fixpak level is higher than the fixpak level of the
product being added, the combination is allowed. However, since the
fixpak level of the product being added is lower than the DB2 fixpak
level, the DB2 fixpak level must be reapplied after installing the
additional product. See the appropriate FixPak Readme for
instructions to reapply the fixpak.
* If the DB2 fixpak level is lower than the fixpak level of the product
being added, an error is generated. The product being added cannot be
at a higher fixpak level than DB2. In this case, you must first bring
DB2 to the appropriate level, then install the additional product.
See the appropriate FixPak Readme for instructions.

The following table summarizes the db2setup combinations:

The DB2 Support Web site address is
http://www.ibm.com/software/data/db2/udb/winos2unix/support

1.11 Installation of a FixPak or a modification level from a directory
path

When you download and untar a FixPak or a modification level, make sure
that there are no spaces in your directory path where the file was
located. If there are spaces in your directory path the installation
will fail. For example, make sure your directory path resembles the
following:

/home/DB2FixPak/FP6/ ...

It should not resemble the following:

/home/DB2 FixPak/FP6/ ...

1.12 Applying a FixPak or a modification level for Data Links Manager
(AIX)

To apply a fixpak or a modification level for Data Links Manager on AIX:
1. As the DB2 Data Links Manager Administrator, bring down the DB2 Data
Links Manager by running the following commands:
dlfm stop
dlfm stopdbm

Ensure that there are no DB2 or DLFM processes remaining.
2. As root, unmount each dlfs filesystem (filesystems controlled by the
DB2 Data Links Manager) by running the following command:
umount /filesystem_name

where /filesystem_name represents the name of the dlfs filesystem
which you want to unmount.
3. As root, unload the DLFS device driver by running the following
command:
strload -uf /usr/opt/db2_08_01/cfg/dlfs_cfg

4. Install the fixpak or the modification level.
5. After successful installation of the fixpak or the modification
level, as root, update the Data Links Manager instance by running the
following command:
/usr/opt/db2_08_01/instance/dlfmupdt dlm_instance_name

where dlm_instance_name represents the name of the DB2 Data Links
Manager Administrator.
6. As root, load the DLFS device driver by running the following
command:
strload -f /usr/opt/db2_08_01/cfg/dlfs_cfg

7. As root, mount each of the DLFS filesystems by running the following
command:
mount -v dlfs /filesystem_name

8. As the DB2 Data Links Manager Administrator, run the following
commands to bring up the DB2 Data Links Manager:
dlfm bind
dlfm start

1.13 Applying a FixPak or a modification level for Data Links Manager
(Solaris Operating Environments)

To apply a fixpak or a modification level for Data Links Manager on
Solaris Operating Environments:
1. As the DB2 Data Links Manager Administrator, bring down the DB2 Data
Links Manager by running the following commands:
dlfm stop
dlfm stopdbm

where /filesystem_name represents the name of the dlfs filesystem
which you want to unmount.
3. As root, unload the DLFS device driver by running the following
command:
rem_drv dlfsdrv

4. Install the fixpak or the modification level.
5. After successful installation of the fixpak or the modification
level, as root, update the Data Links Manager instance by running the
following command:
/opt/IBMdb2/V8.1/instance/dlfmupdt dlm_instance_name

where dlm_instance_name represents the name of the DB2 Data Links
Manager Administrator.
6. As root, load the DLFS device driver by running the following
command:
add_drv -m '* 0777 dlfm dlfmgrp' dlfsdrv

7. As root, mount each of the DLFS filesystems by running the following
command:
mount -v dlfs /filesystem_name

8. As the DB2 Data Links Manager Administrator, run the following
commands to bring up the DB2 Data Links Manager:
dlfm bind
dlfm start

1.14 Uninstalling FixPaks or modification levels on Linux or UNIX

Note: If you have received special fixes from IBM Support that you have
applied to the DB2 Version 8 FixPak 6 level, you will lose all of
the special fixes when you uninstall DB2 Version 8 FixPak 6. The
special fixes you received from IBM Support are only applicable to
your current version. You should not apply the same special fixes
on top of any backlevel version. If this applies to you, contact
IBM Support before uninstalling DB2 Version 8 FixPak 6.

Before uninstalling DB2 Version 8 FixPak 6, ensure that you:
* Stop all instances and DAS
* Backup your data

AIX If DB2 Version 8 FixPak 6 was installed and the file sets were
applied but not committed, DB2 Version 8 FixPak 6 can be
rejected using SMIT. See the SMIT documentation for more
details.

If the file sets were committed when DB2 Version 8 FixPak 6 was
installed, which is the default, then DB2 Version 8 FixPak 6
cannot be rejected. The only course of action available is to
uninstall DB2 from your system, reinstall DB2 Version 8, and
bring DB2 up to the desired level by applying the corresponding
level of DB2.

HP-UX DB2 Version 8 FixPak 6 file sets can be uninstalled using the
sam utility. If you use swlist or sam, you can list all file
sets for DB2 Version 8 FixPak 6 and receive output similar to
the following:
PDB2_810100010 8.1.0.8
PDB2_810100011 8.1.0.8
PDB2_810300011 8.1.0.24
PDB2_810300010 8.1.0.24

The installation signature is combined with the name of the
file set. You should uninstall the group of PDB2_* file sets
with the same signature starting with the largest number. You
can remove DB2 Version 8 FixPak 6, or the latest version plus
the second last, and so on. You can also select them all.

Linux You cannot uninstall DB2 Version 8 FixPak 6 on Linux. The only
course of action available is to uninstall DB2 from your
system, reinstall DB2 Version 8, and bring DB2 up to the
desired level by applying the corresponding level of DB2. A
db2_deinstall script is provided with DB2 Version 8 FixPak 6
which will uninstall DB2 from your system.

Solaris Operating Environment
The backoutallpatch script is provided with all version images.
Run this script to uninstall DB2 Version 8 FixPak 6 and leave
the system in the state that it was before installing DB2
Version 8 FixPak 6. You can find this script in
/var/sadm/patch. The script will be named
backoutallpatch.8.1.x.y where 8.1.x.y corresponds to the VRMF
of DB2 Version 8 FixPak 6. The files required to uninstall a
FixPak or modification level are stored in /var/sadm. Disk
space requirements for each FixPak or modification level in
/var/sadm can reach almost the same amount of disk space
required by DB2 in /opt/IBM/db2/V8.1.

You must uninstall from the highest to the lowest level until
you have uninstalled the version that you want to remove. For
example if you are at FixPak 3 and installed FixPak 1 and
modification level 2 before FixPak 3 was installed, you would
not be able to uninstall FixPak 1 unless you have uninstalled
modification level 2 and FixPak 3.

Update all instances, including the DAS instance.

1.15 Installing DB2 Version 8 Alternate FixPak

DB2 UDB Enterprise Server Edition (ESE) operating on Linux or UNIX-based
operating systems supports the coexistence of multiple levels of code
for the same release on your system. This support is referred to as
Multiple FixPak (MFP) support.

MFP support is accomplished through the use of Alternate FixPak (AFP)
support. AFP support allows FixPaks or modification levels to be
installed to an alternate path. That is, a different installation path
with a different file set/package name. In this case, the operating
system treats the DB2 code installed to an alternate path as different
software.

Restrictions:
* Each AFP has its own unique installation path. That path is fixed and
cannot be changed. That is, you cannot install an AFP to an arbitrary
location of your choice.
* If you install DB2 Version 8 Alternate FixPaks without an installed
and licensed copy of DB2 Version 8, you will need to obtain the
license key from the Version 8 release level media. You can then
install the license by using the db2licm command.
* Response file installations for Alternate FixPaks are not supported
at this time.

To install DB2 Version 8 Alternate FixPak, ensure that:
* You have root authority.
* You have a copy of the DB2 Version 8 Alternate FixPak image. This can
be downloaded from the IBM anonymous FTP server at
ftp.software.ibm.com. Go to ps/products/db2/fixes/%L/%P/mfp where %L
represents the appropriate locale (for example, english-us, spanish,
german), and %P represents the product name/version.

Note: If you plan to uninstall an alternate FixPak, make sure there are
no DB2 instances or DAS running against the alternate FixPak. To
verify there are no DB2 instances of DAS running against the
alternate FixPak, use the db2ilist -a command for instances and
the daslist command for DAS. To update a DB2 instance or DAS from
an existing code level (for example, Version 8 FixPak 1) to a
different code level (for example, Version 8.1.2) you must have
the new code level (Version 8.1.2) installed and keep the original
code level (Version 8 FixPak 1) before you can successfully run
the db2iupdt command or dasupdt command from the new code level
installation path. Never remove the "original" alternate FixPak
installation path prior to running the db2iupdt command. Once
db2iupdt has completed successfully and if no other instance is
using the code, you can then remove the code that the instance
was originally linked to (for example, Version 8 FixPak 1).

If you want to update an instance running against an Alternate FixPak or
modification level that has been installed to an alternate path to a
different code level, you can do so in one of two ways.

For example, an instance db2inst1 is currently running against Alternate
FixPak 1. If you wish to update the instance to run at the Version 8
FixPak 6 code level, you can perform one of the following:
1. Install DB2 Version 8 Alternate FixPak, then update your instance.
For example:
a. Install Version 8 Alternate FixPak.
b. Stop db2inst1.
c. Run V8.1.6_alternate_installation_path/instance/db2iupdt db2inst1
where V8.1.6_alternate_installation_path refers to the
installation path for Version 8 Alternate FixPak 6.

2. Install DB2 Version 8 FixPak 6, then update your instance. For
example:
a. Install DB2 Version 8 FixPak 6 on top of the Version 8.1 GA
(General Availability) code or any previous Version 8.1 level
code.
b. Stop db2inst1.
c. Run Version_8.1_GA_installation_path/instance/db2iupdt db2inst1
where Version_8.1_GA_installation_path refers to the installation
path for Version 8.1 GA.

Note that in this example, the instance is moved from a lower code level
to a higher code level. The same procedure can be used if you wish to
move to a lower code level. In that case, you will be required to use
the -D flag when running the db2iupdt command.

To install the DB2 Version 8 Alternate FixPak 6 for Enterprise Server
Edition (ESE) on a Linux or UNIX operating system:
1. Run the installAltFixPak utility from the directory where you
untarred the image for DB2 Version 8 Alternate FixPak.
2. The install program checks to see if DB2 Version 8 is installed in
the GA path. If it detects an existing DB2 Version 8 installation in
the GA path, it will prompt you to install the same file
sets/packages from the DB2 Version 8 Alternate FixPak.
* If the answer is yes, then the installation program proceeds to
install the same set of file sets/packages as are already
installed.
* If the answer is no, or if DB2 Version 8 was not detected in
either /usr/opt/db2_08_01 or /opt/IBM/db2/V8.1, then it starts
db2_install.

Note: No licenses are shipped with the DB2 Version 8 Alternate FixPak -
licenses must be installed from the Version 8 release level media.

1.16 Uninstalling DB2 Version 8 Alternate FixPak

This task provides steps for removing DB2 Version 8 products using the
db2_deinstall command. The db2_deinstall command removes all DB2
products from your system in the corresponding installation path. If you
want to remove a subset of DB2 products, use your operating system's
native tools to remove DB2 components, packages, or file sets.

Prerequisites

Before you remove DB2 products from your Linux or UNIX system:

* You must have root authority to remove DB2 products.
* The db2_deinstall command is found in the root directory on all DB2
installable images (regular or Alternate FixPak).

Procedure

To remove an Alternate FixPak from your system:
1. Log in as user with root authority.
2. Locate the copy of db2_deinstall that came with the Alternate FixPak
you want to remove. For example, you cannot use the db2_deinstall
script that came with Alternate FixPak x to remove Alternate FixPak
y.
3. Run the db2_deinstall -n command.

There are alternative methods for removing DB2 products from your
operating system. You may employ one of these methods if you only want
to remove a subset of DB2 products from your system. For example on
HP-UX, alternative methods for removing DB2 products include using the
swremove command.

1.17 Known problems and workarounds (Version 8 FixPak 6)

1.17.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.17.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.17.3 Installing Query Patroller at FixPak 3 level or later

Query Patroller is a query management system used to control the flow of
queries against your DB2 database. In DB2 Version 8.1.2, DB2 Query
Patroller became a stand-alone product. It was no longer a component of
the DB2 Warehouse Manager.

If you have DB2 Version 8 FixPak 3 or later installed and you install
the DB2 Query Patroller base or GA version, you must reapply the DB2
FixPak level. Otherwise, the Query Patroller changes are not applied at
the DB2 FixPak level.

If you are installing the Query Patroller server, you must also update
the DB2 instances after reapplying the DB2 FixPak level. This is
mandatory. See the Updating instances to use the new level of DB2
section in this readme for details. After the instances are updated they
must be restarted. See the Restarting the instances section of this
readme for details. Updating instances to use the new level of DB2, and,
Restarting the instances are subsections of the After installation
section.

1.17.4 Replication for Informix sources

Replication for Informix sources is no longer dependent on timestamp
values. This enhancement eliminates issues that would arise during a
backward time change, such as daylight savings in October.

To take advantage of this enhancement, you must migrate any existing
registrations and subscriptions for Informix sources as described in IBM
Support Technote 1165347, "Migrating Informix source triggers in DB2
DataPropagator 8.1 FP 5". To access the Technote, perform the following
steps.
1. Open a Web browser
2. Go to the DB2 DataPropagator Support Web page at
http://www.ibm.com/software/data/dpropr/support.html
3. Enter 1165347 in the Search support for this product area of the
page, then click Submit.

1.18 Known problems and workarounds (prior to Version 8 FixPak 6)

1.18.1 Recommended application server for deploying DB2 Web Tools

The recommended application server for deploying DB2 Web Tools is the
embedded application server for DB2. The recommended method is to use
the automated script that is provided.

To deploy DB2 Web Tools on the embedded application server for DB2, the
following order is recommended:
1. Installing the application server for DB2
2. Starting the application server for DB2
3. Deploying automatically on the application server for DB2

For detailed instructions for each step, see the DB2 Information Center.
These additions to the following sections must also be noted.

1.18.1.1 Installing the application server -- additional prerequisite

The application server for DB2 requires DB2 ESE Version 8.1.2 or higher.

1.18.1.2 Installing the application server -- additional restriction

The default Red Hat installation creates an association between the
hostname of the machine and the loopback address, 127.0.0.1. In
addition, the /etc/nsswitch.conf file is set up to use /etc/hosts before
trying to look up the server using a name server (DNS). This loopback
processing can hang utilities that start and stop a server, such as
startServer.sh, even though the server might successfully start or stop.

Ensure that the host name is defined properly. The default configuration
has localhost defined in the /etc/hosts file. The default
/etc/nsswitch.conf looks only at the host file and not the DNS server.

To correct this problem, remove the 127.0.0.1 mapping to localhost in
the /etc/hosts file, or, edit the name service configuration file
/etc/nsswitch.conf to resolve the proper host name by using the name
server. For example, remove the 127.0.0.1 mapping from the /etc/hosts
file, which might look like this example:

# IP Address name of machine
n.n.n.n hostname.domain.com
127.0.0.1 localhost

Otherwise, change the etc/nsswitch.conf file to search DNS before
searching the hosts file. For example, hosts : dns files

1.18.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 <AS_root>/bin directory and run the deploy_db2wa
script:
<AS_root>/bin/db2wa_deploy -db2path db2path -instance instanceName

where:
* <AS_root> is the installation path for the application server for
DB2.
* db2path is the installation path for DB2.
* instanceName is the DB2 instance name.

For example:

db2wa_deploy.sh -db2path /home/db2v8/sqlib -instance db2v8

2. Invoke the DB2 Web Tools enterprise application from a browser by
entering the following:
http://hostname:<port_number>/db2wa

where:
* hostname is the name of the DB2 server.
* port_number is 20000 by default, unless modified after the
installation of the application server.

1.18.2 DB2 Setup Wizard appears not to run using Exceed (Linux)

When using Hummingbird(R) Exceed PC X Server software to connect to a
Linux computer from a computer running Microsoft(R) Windows, the DB2
Setup wizard may not appear to run. This problem arises when Exceed is
configured to use multiple window mode, with the Window Manager set to
"Default to Native" and with the communications mode set to "Passive".

The symptoms you may observe include:
1. The DB2 Setup Launchpad appears quite small, as small as 5 pixels x 5
pixels, and will need to be resized before it can be used.
2. Even after resizing, the DB2 Setup Launchpad sometimes will not paint
properly and instead appears as a blank grey panel.

To run the DB2 Setup Wizard on a Linux computer using Exceed, change
either of the following Exceed configuration settings:
* Change the Window Manager setting to "Native" and ensure the "Use
Native WM for Embedded Clients" check box is checked, or,
* Change the Window Mode to "Single" and the communication mode from
"Passive" to "XDCMP-query".

1.18.3 DB2 Data Links Manager installation when DB2 Enterprise Server
Edition already installed

The DB2 Data Links Manager installation will fail when creating the dlfm
instance if DB2 ESE is already installed on the machine. The workaround
is to modify the response file and continue or to perform a response
file installation to install the DB2 Data Links Manager. For more
information on response files, see the Installation and Configuration
Supplement or search for "response file" in the Information Center.

1.18.4 Loss of Control Center functionality

Consult the Client/Server Compatibility and Migration Considerations
whitepaper, which is available at:
* http://www-3.ibm.com/software/data/pubs/papers/

2.0 Notices

IBM may not offer the products, services, or features discussed in this
document in all countries. Consult your local IBM representative for
information on the products and services currently available in your
area. Any reference to an IBM product, program, or service is not
intended to state or imply that only that IBM product, program, or
service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate
and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document does
not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact
the IBM Intellectual Property Department in your country/region or send
inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any
other country/region where such provisions are inconsistent with local
law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in
certain transactions; therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of
those Web sites. The materials at those Web sites are not part of the
materials for this IBM product, and use of those Web sites is at your
own risk.

IBM may use or distribute any of the information you supply in any way
it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one)
and (ii) the mutual use of the information that has been exchanged,
should contact:
IBM Canada Limited
Office of the Lab Director
8200 Warden Avenue
Markham, Ontario
L6G 1C7
CANADA

Such information may be available, subject to appropriate terms and
conditions, including in some cases payment of a fee.

The licensed program described in this document and all licensed
material available for it are provided by IBM under terms of the IBM
Customer Agreement, IBM International Program License Agreement, or any
equivalent agreement between us.

Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating
environments may vary significantly. Some measurements may have been
made on development-level systems, and there is no guarantee that these
measurements will be the same on generally available systems.
Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should
verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers
of those products, their published announcements, or other publicly
available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility, or any other claims related
to non-IBM products. Questions on the capabilities of non-IBM products
should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to
change or withdrawal without notice, and represent goals and objectives
only.

This information may contain examples of data and reports used in daily
business operations. To illustrate them as completely as possible, the
examples include the names of individuals, companies, brands, and
products. All of these names are fictitious, and any similarity to the
names and addresses used by an actual business enterprise is entirely
coincidental.

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:

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.
**
*******************************************************************************