Before installing DB2 Universal Database(TM) (UDB) Version 8.2 FixPak 4 and later, read the appropriate sections of this readme that apply to your installation. Version 8.2 FixPak 4 and later is equivalent to Version 8.1 FixPak 11 and later.
All FixPaks are cumulative in nature. For example, the current FixPak can be applied on top of Version 8.2 FixPak 1 without having to apply the FixPaks in between.
If you migrate from DB2 UDB Version 8.1 to DB2 UDB Version 8.2, and then need to move back to DB2 UDB Version 8.1, there are important considerations you need to know. For instructions on how to move back to DB2 UDB Version 8.1, see the "Migrating database directory files from Version 8.2 back to Version 8.1" section.
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(R) UDB.
Consult the following Web sites for the latest software, hardware, operating system and product fix information:
If you are applying the FixPak on AIX(R), HP-UX, or Solaris Operating Environments, ensure you have the space required before applying the FixPak. The space required to install the FixPak is equal to the space required for the DB2 UDB, Version 8 general availability (GA) installation. (On AIX, this only applies if you use the -a option, for "apply" as opposed to "commit".) Linux(TM) does not require additional space to apply a FixPak.
To see the space used by the DB2 UDB, Version 8 GA installation, enter the following command:
du -k -s <install directory>
where install directory represents the installation directory:
Before applying the FixPak, ensure the space required (provided by the previous command) is available in the following directory:
If you have received special fixes from IBM(R) support, you must contact IBM support before you install DB2 Version 8.2 FixPak 4 and later 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 Version 8 product installed at a lower VRMF (version, release, modification/maintenance level, and fix) level than this FixPak before you install Version 8.2 FixPak 4 and later.
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(R) operating system:
| Operating System | Command | Output to look for |
|---|---|---|
| AIX | lslpp -al "db2_08_01.client*" |
db2_08_01.client 8.1.0.0 or 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 "*DB2*" |
DB2V8CAE 8.1.0.x [product name] 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 Operating Environment | pkginfo -l db2cliv81 | grep VERSION |
VERSION: 8.1.0.x where x must be smaller than the current level (the 4th digit in VRMF). |
For a list of all product fixes (APARs) and support news, see Web site
Read the Known problems and workarounds sections before installing DB2 Version 8.2 FixPak 4 and later.
Before installing DB2 Version 8.2 FixPak 4 and later, 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.
Before starting the installation, ensure all DB2 processes are stopped.
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.
su - aname
. $HOME/das/dasprofile
db2admin stop
exit
where aname represents the DAS owner name./usr/sbin/slibclean
ps -efFor example, on AIX the db2fmcu command is run from /usr/opt/db2_08_01/bin.
db2fmcu -d
db2fm -D
$HOME/sqllib/bin/ipclean
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/FP11/ ...
It should not resemble the following:
/home/DB2 FixPak/FP11/ ...
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.
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 FP11_$PTF.tar.Z or FP11_$PTF.tar.gz, where FP11_$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.
To uncompress the FixPak installation images, perform the following steps:
zcat <filename>.tar.Z | tar -xvf -where <filename> is the DB2 FixPak you are applying.
gunzip -c <filename>.tar.gz | tar -xvf -where <filename> is the DB2 FixPak you are applying.
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:
where $PTF represents:
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.
To uncompress the FixPak installation images, perform the following steps:
zcat <filename>.tar.Z | tar -xvf -where <filename> is the DB2 Alternate FixPak you are applying.
gunzip -c <filename>.tar.gz | tar -xvf -where <filename> is the DB2 Alternate FixPak you are applying.
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 FixPak 4 and later.
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).
This section details Installing DB2 Version 8.2 FixPak 4 and later and installing an Alternate FixPak.
Ensure that your system has met all of the installation prerequisites including operating system patches prior to the installation of DB2 Version 8.2 FixPak 4 and later 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 FixPak 4 and later.
The following restrictions apply to installing DB2 Version 8.2 FixPak 4 and later:
To install DB2 Version 8.2 FixPak 4 and later:
./installFixPak -ywhere the -y option indicates your agreement to the license terms and conditions. The -y option must be specified for installation to continue.
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
DB2 UDB Enterprise Server Edition (ESE) operating on Linux or UNIX 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:
Prerequisites:
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 want to update the instance to run at the code level delivered in this fixpak, you can perform one of the following:
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 this DB2 Version 8 Alternate FixPak for Enterprise Server Edition (ESE) on a Linux or UNIX operating system:
After installing DB2 Version 8.2 FixPak 4 and later, do the following:
If you have DB2 Relational Connect installed, you must run the djxlink command after installing DB2 Version 8.2 FixPak 4 and later and before running db2iupdt. Perform the following steps:
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.
INSTHOME/instance/db2iupdt inamewhere iname represents the instance name and INSTHOME represents the installation directory appropriate to your operating system.
INSTHOME/instance/dasupdt dasnamewhere 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.
This task is strongly recommended if you want to use capabilities specific to the latest FixPak. If you are not planning to use capabilities specific to the latest FixPak and might possibly decide to return to an earlier FixPak, you should not use db2updv8.
After installing DB2 Universal Database (UDB) Version 8.2 FixPak 4 and later, run the db2updv8 command to update the system catalogs to support the current level by enabling several built-in routines. Running the db2updv8 command is not required, but some functionality in DB2 UDB Version 8.2 will not work if this command is not run.
After you have run the db2updv8 command to update the system catalogs to the current Version 8 level, falling back to Version 8.1 is not supported.
For more information on the db2updv8 command, run this command with the -h option. For technical information, search the Information Center for Update Database to Version 8 Current Level Command.
To restart an instance:
To restart the administration server, log in as the DAS owner and run the db2admin start command.
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.
After applying fixes, you must issue 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 ACTION ADD
db2 terminate
or
At the DB2 command line, enter:
TERMINATE
CONNECT TO <dbname>
BIND <path>/@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
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. Packages that are already bound will return an SQL0719 error. This is expected.
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 ACTION ADD SQLERROR CONTINUE VM BIND <path>/@ddcsvm.lst BLOCKING ALL GRANT PUBLIC ACTION ADD SQLERROR CONTINUE VSE BIND <path>/@ddcsvse.lst BLOCKING ALL GRANT PUBLIC ACTION ADD SQLERROR CONTINUE OS400 BIND <path>/@ddcs400.lst BLOCKING ALL GRANT PUBLIC ACTION ADD 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.
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.
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.
After installation on the server, an additional bind file needs to be bound to existing databases. This requirement does not apply to clients.
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.
If you have existing spatial-enabled databases, you must bind 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.
To bind the db2gse.lst file, you must have one of the following authorities:
To bind the db2gse.lst file:
cd $HOME/sqllib/bndwhere $HOME is the instance owner's home directory.
db2 connect to dbname db2 bind /home/instance/sqllib/bnd/@db2gse.lst db2 terminate
For syntax and options for the BIND command, refer to the DB2 Command Reference.
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.
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.
The following table summarizes the db2setup combinations:
| DB2 fixpak level | Additional product fixpak level | Is this combination permitted? |
|---|---|---|
| Version 8 FixPak 3 | Version 8 FixPak 3 | Yes. This is recommended. |
| Version 8 FixPak 3 | Version 8 GA | Yes, but Version 8 FixPak 3 must be reapplied. See the appropriate FixPak Readme for instructions to reapply the fixpak by going to the DB2 Support Web site. |
| Version 8 FixPak 3 | Version 8 FixPak 5 | No. DB2 must first be brought to the 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
In DB2 UDB Version 8.2. two new fields were added to the database entry structure, therefore the database directory file structure has changed. When migrating from Version 8.1 to Version 8.2 the database directory files will be migrated automatically. However, to demigrate the database directory files from Version 8.2 to Version 8.1, db2demigdbd is required to convert the current database directory files to the Version 8.1 format.
The db2demigdb tool is available as part of the Linux and UNIX FixPak install. It can also be located directly on the Linux and UNIX FixPak CD, without installing the FixPak. On Windows, Linux, and UNIX, the db2demigdb tool is downloadable from the IBM anonymous FTP server at ftp.software.ibm.com/ps/products/db2/tools/db2demigdbd.
You can find documentation for the db2demigdb tool at http://publib.boulder.ibm.com/infocenter/db2help/topic/com.ibm.db2.udb.doc/core/r0011770.htm. For more information and how to download the db2demigdb tool, search the Technotes database at http://www.ibm.com/software/data/db2/udb/support.html using the keywords "db2demigdb tool".
Before uninstalling DB2 Version 8.2 FixPak 4 and later, ensure that you:
If the file sets were committed when DB2 Version 8.2 FixPak 4 and later was installed, which is the default, DB2 Version 8.2 FixPak 4 and later 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.
If you have the Trusted Computing Base (TCB) enabled on the system, before uninstalling DB2 Version 8.2 FixPak 4 and later you need to ensure that the TCB is in a consistent state. See the Known problems and workarounds section in this readme for details.
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 FixPak 4 and later, or the latest version plus the second last, and so on. You can also select them all.
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 and the DAS.
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.
Before you remove DB2 products from your Linux or UNIX system:
To remove an Alternate FixPak from your system:
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.
The following sections detail problems and workarounds you must be aware of prior to installing DB2 UDB Version 8.2 FixPak 4 and later.
After installing a FixPak, to use the new level of DB2, you must update instances. However, running the db2iupdt command overwrites the following scripts: db2profile and db2cshrc. If you previously edited either of these scripts, your changes will be lost after running the db2iupdt command.
If you have more than one DB2 product installed on the same computer, you need to update all existing DB2 products to the same fixpak level.
If you have installed Alternate FixPaks (AFPs), this restriction also applies. Since each AFP has its own unique installation path, all products installed in that installation path must be at the same fixpak level.
For details, see the "Compatibility issues" section of the Version 8.2 FixPak 3 (equivalent to Version 8.1 Fixpak 10) Release Notes.
The following requirements must be met before installing 64-bit DB2 for Linux on iSeries and pSeries:
www.ibm.com/support/docview.wss?uid=swg24007906or follow these steps:
Despite the previous ability to connect to host systems from DB2 Universal Database Workgroup Server Edition and DB2 Universal Database Express Edition, beginning with Version 8.2 (Version 8.1 FixPak 7), this connection is no longer permitted.
Prior to Version 8.2 (Version 8.1 FixPak 7), when DB2 Workgroup Server Edition or DB2 Express Edition was installed, the JCC Universal Driver file, db2jcc_license_cisuz.jar, was included in \sqllib\java. The JCC Universal Driver did not check user licenses before initiating a host connection.
Beginning with Version 8.2 (Version 8.1 FixPak 7), the ability to initiating a host connection is disabled by removing file db2jcc_license_cisuz.jar. This change affects the following Version 8.2 products:
On AIX, if you have the Trusted Computing Base (TCB) enabled on the system, before installing or uninstalling DB2 Version 8.2 FixPak 4 and later you need to ensure that the TCB is in a consistent state for any file or directory related to a DB2 instance, DAS, and installed DB2 files. The TCB can be in an inconsistent state if, for example, DB2 instances were removed without using the db2idrop command.
You can check the TCB state by entering the following command as root:
tcbck -n ALL
If the TCB is not in a consistent state, installing, uninstalling, or rejecting DB2 Version 8.2 FixPak 4 and later can fail and leave some DB2 filesets in a broken state. See the AIX Security Guide for details regarding the Trusted Computing Base.
You must clean up all DB2 interprocess communications (IPCs) for the instance to be updated. Otherwise, the instance update might have errors or the db2start command might fail after the instance is updated. All DB2 IPCs must be cleaned on all nodes for the instance.
See the Stop all DB2 processes section for details.
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.
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.
Consult the Client/Server Compatibility and Migration Considerations white paper, which is available from your IBM representative at the Xtreme Leverage Portal.
To contact DB2 Customer Service by phone:
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 FixPak 4 and later 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 FixPak 4 and later 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 FixPak 4 and later:
| AIX | /usr/opt/db2_08_01/Readme/%L/Release.Notes |
| HP-UX, Linux, and Solaris Operating Environment | /opt/IBM/db2/V8.1/Readme/%L/Release.Notes |
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.
DB2 Version 8.2 FixPak 4 and later can be downloaded from:
| AIX 4.3.3 (32-bit) | db2aix433v8 |
| AIX 5L (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 pSeries(R), 32-bit) | db2linuxPPCv8 |
| Linux (S/390(R) and zSeries(R), 31-bit) | db2linux390v8 |
| Linux (S/390 and zSeries, 64-bit) | db2linux39064v8 |
| Linux (AMD64, 32-bit & 64-bit) | db2linuxAMD64v8 |
| Solaris Operating Environment (32-bit & 64-bit) | db2sunv8 |
The following reference information is available:
The following table details the PTF information.
| Operating system | PTF |
|---|---|
| AIX 4.3.3 | U805923 |
| AIX 5 | U805924 |
| Solaris Operating Environment | U805925 |
| HP-UX 11i | U805926 |
| HP-UX 11i v2 (IA64) | U805927 |
| LINUX (x86, 32-bit) | MI00146 |
| LINUX (x86, 32-bit kernel 2.6) | MI00152 |
| LINUX (IA64, 64-bit) | MI00147 |
| LINUX (iSeries and pSeries) | MI00148 |
| LINUX (AMD64, 64-bit) | MI00149 |
| LINUX (AMD64, 64-bit kernel 2.6) | MI00153 |
| LINUX (S/390, zSeries 31-bit) | MI00150 |
| LINUX (S/390, zSeries 64-bit) | MI00151 |
The following table details the supported languages for DB2 clients that are available from the FTP site.
| Operating System | DB2 Administration Client | DB2 Application Development Client | DB2 Run-Time Client |
|---|---|---|---|
| AIX 4.3.3 (32-bit) |
|
|
All supported languages are in one tarred file |
| AIX 5L (32-bit and 64-bit) |
|
|
All supported languages are in one tarred file |
| HP-UX 11i (PA-RISC) and HP-UX 11i v2 (IA64) (32-bit and 64-bit) | All supported languages are in one tarred file | All supported languages are in one tarred file | All supported languages are in one tarred file |
| Linux | All supported languages are in one tarred file | All supported languages are in one tarred file | All supported languages are in one tarred file |
| Solaris Operating Environments | All supported languages are in one tarred file | All supported languages are in one tarred file | All supported languages are in one tarred file |
| Windows(R) | All supported languages are in one self-extracting zip file | All supported languages are in one self-extracting zip file | All supported languages are in one self-extracting zip file |
DB2 products continue to be supported on AIX 4.3.3 and Solaris 7 until DB2 Version 8.1 goes out of service. Existing installs of DB2 as well as new installs of DB2 products are recommended to upgrade to a more current version of AIX, such as AIX 5.3, because AIX 4.3.3 is now out of service, and to a more current version of Solaris, such as Solaris 9.
The following lists show the supported products and components for each Linux and UNIX operating system:
If you add new components after you install DB2 Version 8.2 FixPak 4 and later, you need to reinstall DB2 Version 8.2 FixPak 4 and later to ensure that the newly added components are updated.
IBM may not offer the products, services, or features discussed in this document in all countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country/region or send inquiries, in writing, to:
IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other country/region where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product, and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information that has been exchanged, should contact:
IBM Canada Limited Office of the Lab Director 8200 Warden Avenue Markham, Ontario L6G 1C7 CANADA
Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems, and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements, or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
This information may contain examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious, and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information may contain sample application programs, in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows:
(C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. _enter the year or years_. All rights reserved.
IBM, DB2, Universal Database, and S/390 are trademarks of International Business Machines Corporation in the United States, other countries, or both.
Windows is a registered trademark of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, or service names may be trademarks or service marks of others.
------------------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. ------------------------------------------------------------------------------- ******************************************************************************* ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1999, 2006. ** ALL RIGHTS RESERVED. ** *******************************************************************************