IBM DB2 Universal Database Version 8.2 (Version 8.1 FixPak 7) Readme
Contents
1.0 Installing IBM DB2 Universal Database(TM) Version 8.2 (Version 8.1
FixPak 7) for AIX, HP-UX, Linux and Solaris Operating Environments
1.1 Pre-installation
1.1.1 Prerequisites
1.1.2 Product fix history
1.1.3 Prior to installing DB2 Version 8.2
1.2 Installation of Version 8.2
1.2.1 Installing DB2 Version 8.2
1.2.2 Installing DB2 Version 8 Alternate FixPak
1.3 Post-installation
1.3.1 Relational Connect and the djxlink command
1.3.2 Updating instances to use the new level of DB2
1.3.3 Restarting the instances and administration server
1.3.4 Re-binding bind files
1.3.5 Restrictions to adding products using the db2setup command
2.0 Uninstallation of Version 8.2
2.1 Migrating database directory files from Version 8.2 back to
Version 8.1
2.2 Uninstalling FixPaks or modification levels on Linux or UNIX
2.3 Uninstalling DB2 Version 8 Alternate FixPak
3.0 Known problems and workarounds
3.1 Known problems and workarounds (Version 8.2)
3.1.1 Distributed transaction support
3.1.2 db2ln command modified to create DB2 64-bit library links
3.1.3 New reason code for SQL5099N
3.1.4 Automatic setting of default prefetch size and update defaults
3.2 Known problems and workarounds (prior to Version 8.2)
3.2.1 Installing Query Patroller at FixPak 3 level or later
3.2.2 DB2 Data Links Manager installation when DB2 Enterprise Server
Edition already installed
3.2.3 Loss of Control Center functionality
4.0 How to get help
4.1 Where to download the FixPak installation images
5.0 Reference
5.1 PTF information
5.2 Supported languages for DB2 clients available from the FTP site
5.3 Supported products and components by operating system
6.0 Notices
1.0 Installing IBM DB2 Universal Database(TM) Version 8.2 (Version 8.1
FixPak 7) for AIX, HP-UX, Linux and Solaris Operating Environments
Before installing DB2 Universal Database (UDB) Version 8.2 (Version 8.1
FixPak 7), read the appropriate sections of this readme that apply to
your installation.
1.1 Pre-installation
This section details the prerequisite information (including software,
hardware, and operating system prerequisites) you need, points to where
the product fix history is located, and lists the tasks that must be
performed prior to installing DB2 UDB.
1.1.1 Prerequisites
Consult the following Web sites for the latest software, hardware,
operating system and product fix information:
1. For operating system requirements, see
* http://www.ibm.com/software/data/db2/udb/sysreqs.html
2. For a list of all fixed bugs (called APARs) and support news, see
* http://www.ibm.com/software/data/db2/udb/support.html
If you have received special fixes from IBM support, you must contact
IBM support before you install DB2 Version 8.2 to check if you need an
updated version of the special fixes. This helps to ensure that your
system is in a consistent state and that no special fixes are lost.
You must have a DB2(R) product Version 8 installed at a lower level than
DB2 Version 8.2 before you install Version 8.2.
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. The following table shows
the command for each Linux and UNIX operating system:
+----------+------------------------+---------------------------------+
| Operatin | Command | Output to look for |
| g System | | |
+----------+------------------------+---------------------------------+
| AIX(R) | lslpp -al | db2_08_01.client 8.1.0.0 or |
| | "db2_08_01.client*" | later (for AIX 4.3.3) |
| | | |
| | | db2_08_01.client 8.1.1.0 or |
| | | later (for AIX 5) |
| | | |
| | | Sample outputs for DB2 for AIX |
| | | 4.3.3: |
| | | db2_08_01.client 8.1.0.0 |
| | | COMMITTED ... |
| | | 8.1.0.3 COMMITTED ... |
| | | 8.1.0.8 COMMITTED ... |
| | | |
| | | Check the largest installation |
| | | signature that is |
| | | returned (8.1.0.x) to make sure |
| | | it is smaller |
| | | than the VRMF of the current |
| | | DB2 level. |
| | | For AIX 5, the signature looks |
| | | like 8.1.1.y. |
+----------+------------------------+---------------------------------+
| HP-UX | swlist -l product | DB2V8CAE 8.1.0.x [product name] |
| | "*DB2*" | |
| | | or, |
| | | |
| | | PDB2... 8.1.0.x Product Patch |
| | | |
| | | where x must be smaller than |
| | | the current |
| | | level (the 4th digit in VRMF). |
+----------+------------------------+---------------------------------+
| Linux | rpm -qa | grep db2 | db2cliv81-8.1.0-x |
| | | |
| | | db2cliv81-8.1.1-x on |
| | | Linux/AMD64. |
| | | where x must be smaller than |
| | | the current |
| | | level (the 4th digit in VRMF). |
+----------+------------------------+---------------------------------+
| Solaris | pkginfo -l db2cliv81 | | VERSION: 8.1.0.x |
| Operatin | grep VERSION | |
| g | | where x must be smaller than |
| Environm | | the current |
| ent | | level (the 4th digit in VRMF). |
+----------+------------------------+---------------------------------+
1.1.2 Product fix history
For a list of all product fixes (APARs) and support news, see Web site
* http://www.ibm.com/software/data/db2/udb/support.html.
1.1.3 Prior to installing DB2 Version 8.2
Read the Known problems and workarounds sections before installing DB2
Version 8.2.
1.1.3.1 License terms and conditions
Before installing DB2 Version 8.2, you must confirm you have reviewed
and accept the license terms and conditions located in the "db2/license"
directory.
A new option on the installation command indicates your agreement to the
license terms and conditions. The option must be specified for
installation to continue.
1.1.3.2 Stop all DB2 processes
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 an 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. To disable the Fault
Monitor Coordinator, you must be logged on as root and enter the
following:
db2fmcu -d
To stop the Fault Monitor, enter the following:
db2fm -d
1.1.3.3 Directory path cannot contain spaces
When you download and untar a FixPak or a modification level, make sure
that there are no spaces in the directory path where the file was
located. If there are spaces in the directory path, the installation
will fail. For example, make sure your directory path resembles the
following:
/home/DB2FixPak/FP7/ ...
It should not resemble the following:
/home/DB2 FixPak/FP7/ ...
1.1.3.4 Ensure sufficient file system free space (AIX 4.3.3, AIX 5L,
Linux, and Solaris Operating Environments)
In addition to the software disk requirements, you need to have a file
system with 2 gigabytes of free space to contain the tar.Z file or
tar.gz file, and the uncompressed installation image.
1.1.3.5 Uncompressing FixPak installation images
Some FixPak installation images on the FTP site or the FixPak CD are in
compressed or gzipped format. Before you can apply the DB2 FixPak from
these formats, you need to copy the image to a temporary directory and
uncompress or gunzip the FixPak installation image.
The compressed or gzipped images might have the file name FP7_$PTF.tar.Z
or FP7_$PTF.tar.gz, where FP7_$PTF represents the latest fixpak
operating system name and version.
In addition to the software disk requirements, you must have a
filesystem with 2 gigabytes of free space to contain the tar.Z or tar.gz
file and the uncompressed image.
Procedure
To uncompress the FixPak installation images, perform the following
steps:
1. Copy the compressed or gzipped image to a temporary file system
containing at least 2 gigabytes of free space.
2. Change to the directory where you copied the image by entering cd
/TMP, where /TMP represents the directory where you copied the
compressed image.
3. If the product has the *.tar.Z extension, enter the following
command:
zcat <filename>.tar.Z | tar -xvf -
where <filename> is the DB2 FixPak you are applying.
4. If the product has the *.tar.gz extension, enter the following
command to uncompress:
gunzip -c <filename>.tar.gz | tar -xvf -
where <filename> is the DB2 FixPak you are applying.
Note: gunzip is part of the AIX 5L default installation setup. If you
do not have gunzip, install the rpm.rte fileset from the AIX 5L
installation media. The rpm.rte fileset contains gunzip. You
can also download gzip for AIX5L from Web site:
http://www.ibm.com/servers/aix/products/aixos/linux/rpmgroups.html
5. If the compressed FixPak installation images are on a FixPak CD,
there might be additional CDs with the file name extra.tar.Z or
extra.tar.gz. Repeat these steps for each CD.
1.1.3.6 Uncompressing Version 8 Alternate FixPak installation images
Some Alternate FixPak installation images on the FTP site or the FixPak
CD are in compressed or gzipped format. Before you can apply the DB2
Alternate FixPak from these formats, you need to copy the image to a
temporary directory and uncompress or gunzip the Alternate FixPak
installation image.
The compressed or gzipped images might have the file extension .tar.Z or
.tar.gz.
Alternate FixPak installation images have the following filenames:
* FP7_$PTF_ESE_MFP for AIX 4.3.3 and Solaris Operating Environments
* FP7_$PTF_ESE_MFP_SBCS for AIX 5
* FP7_$PTF_ESE_MFP_DBCS for AIX 5
where $PTF represents:
* U498349 on AIX 4.3.3
* U498351 on Solaris Operating Environments
* U498350 on AIX 5
Notes:
1. FP7_$PTF_ESE_MFP_SBCS (ese.mfp.sbcs inside) supports the following
languages: English, Brazilian, Danish, Finnish, French, German,
Italian, Norwegian, Portuguese, Spanish, and Swedish.
2. FP7_$PTF_ESE_MFP_DBCS (ese.mfp.dbcs inside) supports the following
languages: English, Japanese, Korean, Simplified Chinese, and
Traditional Chinese.
In addition to the software disk requirements, you must have a
filesystem with 2 gigabytes of free space to contain the tar.Z or tar.gz
file and the uncompressed image.
Procedure
To uncompress the FixPak installation images, perform the following
steps:
1. Copy the compressed or gzipped image to a temporary file system
containing at least 2 gigabytes of free space.
2. Change to the directory where you copied the image by entering cd
/TMP, where /TMP represents the directory where you copied the
compressed image.
3. If the product has the *.tar.Z extension, enter the following
command:
zcat <filename>.tar.Z | tar -xvf -
where <filename> is the DB2 Alternate FixPak you are applying.
4. If the product has the *.tar.gz extension, enter the following
command to uncompress:
gunzip -c <filename>.tar.gz | tar -xvf -
where <filename> is the DB2 Alternate FixPak you are applying.
Note: gunzip is part of the AIX 5L default installation setup. If you
do not have gunzip, install the rpm.rte fileset from the AIX 5L
installation media. The rpm.rte fileset contains gunzip. You
can also download gzip for AIX5L from Web site:
http://www.ibm.com/servers/aix/products/aixos/linux/rpmgroups.html
5. If the compressed Alternate FixPak installation images are on a
FixPak CD, there might be additional CDs with the file name
extra.tar.Z or extra.tar.gz. Repeat these steps for each CD.
1.1.3.7 Data Warehouse functionality backup (AIX, Linux, 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 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.2.
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.2 Installation of Version 8.2
This section details Installing DB2 Version 8.2 and installing an
Alternate FixPak.
1.2.1 Installing DB2 Version 8.2
Ensure that your system has met all of the installation prerequisites
including operating system patches prior to the installation of DB2
Version 8.2 as detailed in the Prerequisites section. This action
prevents technical problems that might occur after the installation and
configuration of DB2 UDB.
Read the Known problems and workarounds sections before installing DB2
Version 8.2.
Restrictions
The following restrictions apply to installing DB2 Version 8.2:
* DB2 Version 8.2 for AIX 4.3.3 can be applied only on AIX 4.3.3 and
DB2 Version 8.2 for AIX 5 can be applied only on AIX 5.
* On AIX, the installFixPak script provides installation prerequisite
checking that is not provided when you install DB2 Version 8.2 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.2.
* 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, when you have installed DB2 Version 8.2, you cannot
uninstall it and return to the previous DB2 level.
Procedure
To install DB2 Version 8.2:
1. You must be logged on as root.
2. Change to the directory in which the installation image is located.
3. To launch the installation, enter:
./installFixPak -y
where the -y option indicates your agreement to the license terms
and conditions. The -y option must be specified for installation to
continue.
Note: By default, the installFixPak command will commits all of the
updated file sets on AIX.
On AIX, if you do not want to commit the updates, you should issue the
installFixPak command with the -a option (for "apply" as opposed to
"commit") as follows:
./installFixPak -y -a
1.2.2 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. 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 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.
Prerequisites:
* You need root authority.
* You need 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. When
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.2
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.7_alternate_installation_path/instance/db2iupdt db2inst1
where V8.1.7_alternate_installation_path refers to the
installation path for Version 8.2 Alternate FixPak.
2. Install DB2 Version 8.2, then update your instance. For example:
a. Install DB2 Version 8.2 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 want to
move to a lower code level. In that case, you must use the -D flag when
running the db2iupdt command.
To install the DB2 Version 8.2 Alternate FixPak for Enterprise Server
Edition (ESE) on a Linux or UNIX(R) operating system:
1. Run the installAltFixPak -y utility from the directory where you
untarred the image for DB2 Version 8 Alternate FixPak. The -y option
indicates your agreement to the license terms and conditions and must
be specified for installation to continue.
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 prompts 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.3 Post-installation
After installing DB2 Version 8.2, you must do the following:
* 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.3.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.2 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.3.2 Updating instances to use the new level of DB2
This task is mandatory. All instances must be updated after a new level
of DB2 is installed.
Prerequisite: You need to be logged on as root to update the instances.
1. 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.
2. 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.3.3 Restarting the instances and administration server
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.3.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.3.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.3.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(TM) 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.3.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.3.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.3.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.3.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.
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.3.5 Restrictions to adding products using the db2setup command
Once a DB2 product has been installed, additional DB2 products can be
added. If you use the db2setup command to add products the following
recommendations and restrictions apply.
Recommendations
Both the installed product and the product being added should be at the
same code level. For example, DB2 ESE Server Version 8 FixPak 5 is
already installed and you want to add the DB2 Information Integrator
product. In this case, DB2 Information Integrator should also be at the
Version 8 FixPak 5 level.
Restrictions
* If the DB2 fixpak level is higher than the fixpak level of the
product being added, the combination is allowed. However, since the
fixpak level of the product being added is lower than the DB2 fixpak
level, the DB2 fixpak level must be reapplied after installing the
additional product. See the appropriate FixPak Readme for
instructions to reapply the fixpak.
* If the DB2 fixpak level is lower than the fixpak level of the product
being added, an error is generated. The product being added cannot be
at a higher fixpak level than DB2. In this case, you must first bring
DB2 to the appropriate level, then install the additional product.
See the appropriate FixPak Readme for instructions.
The following table summarizes the db2setup combinations:
Table 1. db2setup combinations
+------------+-------------+------------------------------------------+
| DB2 fixpak | Additional | Is this combination permitted? |
| level | product | |
| | fixpak | |
| | level | |
+------------+-------------+------------------------------------------+
| Version 8 | Version 8 | Yes. This is recommended. |
| FixPak 3 | FixPak 3 | |
+------------+-------------+------------------------------------------+
| Version 8 | Version 8 | Yes, but Version 8 FixPak 3 must be |
| FixPak 3 | GA | reapplied. See the appropriate FixPak |
| | | Readme for instructions to reapply the |
| | | fixpak by going to the DB2 Support Web |
| | | site. |
+------------+-------------+------------------------------------------+
| Version 8 | Version 8 | No. DB2 must first be brought to the |
| FixPak 3 | FixPak 5 | higher fix pack level (in this example, |
| | | Version 8 FixPak 5) before installing |
| | | the additional product. See the |
| | | appropriate FixPak Readme for |
| | | instructions to install the required |
| | | Version 8 FixPak by going to the DB2 |
| | | Support Web site. |
+------------+-------------+------------------------------------------+
The DB2 Support Web site address is
http://www.ibm.com/software/data/db2/udb/support.html
2.0 Uninstallation of Version 8.2
2.1 Migrating database directory files from Version 8.2 back to Version
8.1
The db2demigdbd tool converts the format of the database directory
files. Use this tool when moving from the DB2 UDB Version 8.2 back to
Version 8.1.
The db2demigdb tool is available as part of the FixPak install. It can
also be located directly on the FixPak CD, without installing the
FixPak. It is also downloadable from the IBM anonymous FTP server at
ftp.software.ibm.com/ps/products/db2/tools/db2demigdbd.
2.2 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.2 level, you will lose all of the
special fixes when you uninstall DB2 Version 8.2. 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.2.
Before uninstalling DB2 Version 8.2, ensure that you:
* Stop all instances and DAS
* Backup your data
AIX If DB2 Version 8.2 was installed and the file sets were applied
but not committed, DB2 Version 8.2 can be rejected using SMIT.
See the SMIT documentation for more details.
If the file sets were committed when DB2 Version 8.2 was
installed, which is the default, DB2 Version 8.2 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.2 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.2 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.2, or the latest version plus the
second last, and so on. You can also select them all.
Linux You cannot uninstall DB2 Version 8.2 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.2 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.2 and leave the
system in the state that it was before installing DB2 Version
8.2. 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.2. 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.
2.3 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.
3.0 Known problems and workarounds
The following sections detail problems and workarounds you must be aware
of prior to installing DB2 UDB Version 8.2.
3.1 Known problems and workarounds (Version 8.2)
3.1.1 Distributed transaction support
In the documentation for the Version 8.2 What's new, the Distributed
transaction support information of the DB2 Universal JDBC Driver
improvements section has incorrect information. The last sentence of
this section is incorrect. The correct information is:
Support for distributed transaction processing that conforms to the XA
specification. This support implements the Java(TM) 2 Platform,
Enterprise Edition (J2EE) Java Transaction Service (JTS) and Java
Transaction API (JTA) specifications.
3.1.2 db2ln command modified to create DB2 64-bit library links
In previous levels of DB2 Version 8, the db2ln command created certain
DB2 links under /usr/lib and /usr/include. On platforms where both
32-bit and 64-bit DB2 instances are supported, these links point to
library or include files under DB2DIR/lib64 or DB2DIR/include64 by
default, where DB2DIR is the directory where DB2 Version 8 is installed.
If the default is not desired, you can specify the bit width by running
the db2ln command with the -w flag:
db2ln -w 32|64
This prevents DB2 32-bit instances from coexisting with 64-bit instances
on some platforms.
Starting with DB2 UDB Version 8.2, the db2ln command creates DB2 64-bit
library links on those platforms in appropriate directories. In this
case the -w flag is only used for populating /usr/include. When the
db2ln command creates the links for DB2 library files, both 32-bit and
64-bit links are created on supported platforms. This allows both 32-bit
instances and 64-bit instances to exist and run at the same time.
On some Linux distributions, the libc RPM command comes with the
/usr/lib/libdb2.so or /usr/lib64/libdb2.so library. This library is used
for Sleepycat Software's Berkeley DB implementation and is not
associated with IBM's DB2 UDB. However, this file prevents the db2ln
command and the db2rmln command from functioning. The db2ln command does
not overwrite the file and the db2rmln command does not remove the file.
In this case, to compile applications using DB2 UDB, compiling and
linking processes need to provide a full path to DB2's headers and
libraries, respectively. This is the recommended method because it
allows compiling and linking against multiple releases of DB2 UDB on the
same machine.
See the DB2 Version 8.2 Installation and Configuration manual for
details about restrictions using the db2ln command.
3.1.3 New reason code for SQL5099N
17 - Cannot disable log archiving when database is rollforward pending.
3.1.4 Automatic setting of default prefetch size and update defaults
Starting with DB2 UDB Version 8.2. you can use AUTOMATIC prefetch size
for a table space. DB2 UDB automatically updates the prefetch size when
the number of containers changes for the table space.
The syntax of DB2_PARALLEL_IO registry variable is expanded to recognize
containers with different I/O parallelism characteristics. Through the
expanded syntax, containers for different table spaces can have
different I/O parallelism characteristics. The I/O parallelism
characteristic of each table space is used when a prefetch size of
AUTOMATIC is specified for the table space. If the DB2_PARALLEL_IO
registry variable is enabled but the expanded syntax identifying
specific I/O parallelism characteristics for table spaces is not used, a
default level of parallelism is assumed. The default level is RAID 5
(6+1).
The prefetch size information used by the optimizer is refreshed only
when an ALTER TABLESPACE statement is issued that changes the prefetch
size of a table space or changes the number of containers (using
ADD/DROP/BEGIN NEW STRIPE SET/ADD TO NEW STRIPE SET). If the number of
physical disks per container registry settings changes, an ALTER
TABLESPACE <table space name> PREFETCHSIZE AUTOMATIC statement should be
issued to refresh the optimizer information (unless an ALTER TABLESPACE
statement that refreshes the optimizer information is already issued).
If a table space is redirected or restored to use a different number of
containers, refresh the optimizer information by issuing an ALTER
TABLESPACE <table space name> PREFETCHSIZE AUTOMATIC statement. If there
are multiple stripe sets within a table space, the maximum number of
containers among the stripe sets is used to calculated the prefetch
size. If the calculated prefetch size exceeds the maximum size (32767
pages), the largest multiple of the number of containers that is smaller
than the maximum is used as the prefetch size.
In an Enterprise Server Edition environment, if a table space uses an
AUTOMATIC prefetch size, the prefetch size might be different on
different database partitions. This is because different database
partitions can have different number of containers used for calculating
the prefetch size. To generate the query access plan, the optimizer
uses the prefetch size from the first partition in a database partition
group.
3.2 Known problems and workarounds (prior to Version 8.2)
3.2.1 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.
3.2.2 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.
3.2.3 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/
4.0 How to get help
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(R) offices in your country or region, at
http://www.ibm.com/planetwide
The main Usenet newsgroup for DB2 product-related questions is
comp.databases.ibm-db2.
For information about changes to the product, read the product Release
Notes. You can view the latest product Release Notes without installing
DB2 Version 8.2 by going to the DB2 Support Web site at
http://www.ibm.com/software/data/db2/udb/support.html.
You can also review the Release Notes directly from the DB2 Version 8.2
CD by going to /doc/%L/db2ir/index.htm, where %L represents the locale
name. You can also review the Release Notes after installing DB2 Version
8.2:
AIX | /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, for example, english-us, spanish,
german.
The DB2 Information Integrator Version 8 Release Notes are located at
http://www.ibm.com/software/data/integration/db2ii.
The DB2 Query Patroller Release Notes are located at
http://www.ibm.com/software/data/db2/udb/support.html.
4.1 Where to download the FixPak installation images
DB2 Version 8.2 can be downloaded from:
* the DB2 Technical Support Web site directly at:
http://www.ibm.com/software/data/db2/udb/support.html
* the IBM anonymous FTP server at
ftp.software.ibm.com/ps/products/db2/fixes/%L/%P/%D/ where:
* %L represents the appropriate locale directory; for example,
english-us, spanish, german.
* %P represents the supported operating system name and version
directory:
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) |
* %D represents the directory containing the required installation
image:
* the fixpak directory contains the DB2 Version 8.2 installation
image
* the mfp directory contains the DB2 Version 8 Alternate FixPak
image
* the client directory contains the Client refresh images
* the FixPak CD. A FixPak CD can be ordered separately by contacting
DB2 Customer Service. See the How to get help section for details.
5.0 Reference
The following reference information is available:
* PTF information
* Supported languages for DB2 clients
* Supported products and components by operating system.
5.1 PTF information
The following table details the PTF information.
+----------------------------------+----------------------------------+
| Operating system | PTF |
+----------------------------------+----------------------------------+
| AIX 4.3.3 | U498349 |
+----------------------------------+----------------------------------+
| AIX 5 | U498350 |
+----------------------------------+----------------------------------+
| Solaris Operating Environment | U498351 |
+----------------------------------+----------------------------------+
| HP-UX 11i | U498352 |
+----------------------------------+----------------------------------+
| HP-UX 11i v2 (IA64) | U498353 |
+----------------------------------+----------------------------------+
| LINUX (x86, 32-bit) | MI00086 |
+----------------------------------+----------------------------------+
| LINUX (IA64, 64-bit) | MI00087 |
+----------------------------------+----------------------------------+
| LINUX (iSeries and pSeries) | MI00088 |
+----------------------------------+----------------------------------+
| LINUX (AMD64, 64-bit) | MI00089 |
+----------------------------------+----------------------------------+
| LINUX (S/390, zSeries 31-bit) | MI00090 |
+----------------------------------+----------------------------------+
| LINUX (S/390, zSeries 64-bit) | MI00091 |
+----------------------------------+----------------------------------+
5.2 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.
+------------+--------------------+----------------------+------------+
| Operating | DB2 Administration | DB2 Application | DB2 |
| System | Client | Development Client | Run-Time |
| | | | Client |
+------------+--------------------+----------------------+------------+
| AIX 4.3.3 | * SBCS1 (English, | * SBCS1 (English, | All |
| (32-bit) | French, German, | French, German, and | supported |
| | and Italian) | Italian) | languages |
| | * SBCS2 (English, | * SBCS2 (English, | are in one |
| | Brazilian | Brazilian | tarred |
| | Portuguese, and | Portuguese, and | file |
| | Spanish) | Spanish) | |
| | * NORDIC | * NORDIC (English, | |
| | (English, Danish, | Danish, Finnish, | |
| | Finnish, | Norwegian, and | |
| | Norwegian, and | Swedish) | |
| | Swedish) | * DBCS (English, | |
| | * DBCS (English, | Japanese, Korean, | |
| | Japanese, Korean, | Simplified Chinese, | |
| | Simplified | and Traditional | |
| | Chinese, and | Chinese) | |
| | Traditional | | |
| | Chinese) | | |
+------------+--------------------+----------------------+------------+
| AIX 5L | * SBCS (English, | * SBCS (English, | All |
| (32-bit | Brazilian | Brazilian | supported |
| and | Portuguese, | Portuguese, Danish, | languages |
| 64-bit) | Danish, Finnish, | Finnish, French, | are in one |
| | French, German, | German, Italian, | tarred |
| | Italian, | Norwegian, Spanish, | file |
| | Norwegian, | and Swedish) | |
| | Spanish, and | * DBCS (English, | |
| | Swedish) | Japanese, Korean, | |
| | * DBCS (English, | Simplified Chinese, | |
| | Japanese, Korean, | and Traditional | |
| | Simplified | Chinese) | |
| | Chinese, and | | |
| | Traditional | | |
| | Chinese) | | |
+------------+--------------------+----------------------+------------+
| HP-UX 11i | All supported | All supported | All |
| (PA-RISC) | languages are in | languages are in one | supported |
| and HP-UX | one tarred file | tarred file | languages |
| 11i v2 | | | are in one |
| (IA64) | | | tarred |
| (32-bit | | | file |
| and | | | |
| 64-bit) | | | |
+------------+--------------------+----------------------+------------+
| Linux | All supported | All supported | All |
| | languages are in | languages are in one | supported |
| | one tarred file | tarred file | languages |
| | | | are in one |
| | | | tarred |
| | | | file |
+------------+--------------------+----------------------+------------+
| Solaris | All supported | All supported | All |
| Operating | languages are in | languages are in one | supported |
| Environmen | one tarred file | tarred file | languages |
| ts | | | are in one |
| | | | tarred |
| | | | file |
+------------+--------------------+----------------------+------------+
| Windows(R) | All supported | All supported | All |
| | languages are in | languages are in one | supported |
| | one | self-extracting zip | languages |
| | self-extracting | file | are in one |
| | zip file | | self-extra |
| | | | cting zip |
| | | | file |
+------------+--------------------+----------------------+------------+
5.3 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 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 Information Center, 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
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 Unlimited Edition, Version 8
* DB2 Cube Views, Version 8
* DB2 Data Links Manager, Version 8
* DB2 Information Center, 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
HP-UX(TM) 11i (PA-RISC, 32-bit and 64-bit)
Product list:
* DB2 Administration Client, Version 8
* DB2 Application Development Client, Version 8
* DB2 Connect Application Server Edition, Version 8
* DB2 Connect Enterprise Edition, Version 8
* DB2 Connect Unlimited Edition, Version 8
* DB2 Data Links Manager, Version 8
* DB2 Information Center, 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 Data Links Manager, Version 8
* DB2 Information Center, 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 Information Center, 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 Personal Edition, Version 8
Linux(TM) (iSeries and pSeries, 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 Information Center, 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 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 Information Center, 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 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) (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 Information Center, 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 Information Center, 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
If you add new components after you install DB2 Version 8.2, you need to
reinstall DB2 Version 8.2 to ensure that the newly added components are
updated.
6.0 Notices
IBM may not offer the products, services, or features discussed in this
document in all countries. Consult your local IBM representative for
information on the products and services currently available in your
area. Any reference to an IBM product, program, or service is not
intended to state or imply that only that IBM product, program, or
service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate
and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document does
not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact
the IBM Intellectual Property Department in your country/region or send
inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any
other country/region where such provisions are inconsistent with local
law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in
certain transactions; therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of
those Web sites. The materials at those Web sites are not part of the
materials for this IBM product, and use of those Web sites is at your
own risk.
IBM may use or distribute any of the information you supply in any way
it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one)
and (ii) the mutual use of the information that has been exchanged,
should contact:
IBM Canada Limited
Office of the Lab Director
8200 Warden Avenue
Markham, Ontario
L6G 1C7
CANADA
Such information may be available, subject to appropriate terms and
conditions, including in some cases payment of a fee.
The licensed program described in this document and all licensed
material available for it are provided by IBM under terms of the IBM
Customer Agreement, IBM International Program License Agreement, or any
equivalent agreement between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating
environments may vary significantly. Some measurements may have been
made on development-level systems, and there is no guarantee that these
measurements will be the same on generally available systems.
Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should
verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers
of those products, their published announcements, or other publicly
available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility, or any other claims related
to non-IBM products. Questions on the capabilities of non-IBM products
should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to
change or withdrawal without notice, and represent goals and objectives
only.
This information may contain examples of data and reports used in daily
business operations. To illustrate them as completely as possible, the
examples include the names of individuals, companies, brands, and
products. All of these names are fictitious, and any similarity to the
names and addresses used by an actual business enterprise is entirely
coincidental.
COPYRIGHT LICENSE:
This information may contain sample application programs, in source
language, which illustrate programming techniques on various operating
platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM for the purposes of developing, using,
marketing, or distributing application programs conforming to the
application programming interface for the operating platform for which
the sample programs are written. These examples have not been thoroughly
tested under all conditions. IBM, therefore, cannot guarantee or imply
reliability, serviceability, or function of these programs.
Each copy or any portion of these sample programs or any derivative work
must include a copyright notice as follows:
(C) (your company name) (year). Portions of this code are derived from
IBM Corp. Sample Programs. (C) Copyright IBM Corp. _enter the year or
years_. All rights reserved.
IBM, DB2, Universal Database, and S/390 are trademarks of International
Business Machines Corporation in the United States, other countries, or
both.
Windows is a registered trademark of Microsoft Corporation in the United
States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
Sleepycat and the names of Sleepycat Software products referenced herein
are trademarks, registered trademarks or service marks of Sleepycat
Software, Inc.
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.
**
*******************************************************************************