DB2(R) Version 8.1.2  Readme

Contents

1)  Readme for IBM(R) DB2 Universal Database(TM) Version 8.1.2 for 
    AIX(R), Solaris Operating Environments, HP-UX 11i, Linux (Intel) and
    Linux (S/390(R), zSeries(TM))
    1a)  About this readme
    1b)  Who should read this readme file
    1c)  How to get help
         1c.i)  IBM FTP server
    1d)  PTF and VRMF information
    1e)  Supported products and components by platform
    1f)  Prerequisites
    1g)  Before installation
         1g.i)  Setting up DB2 Version 8.1.2 on Solaris Operating 
                Environments, AIX 4.3.3, and AIX 5L
         1g.ii)  Data Warehouse functionality on Linux, AIX, and Solaris
                 Operating Environments
    1h)  Installing DB2 Version 8.1.2
    1i)  After installation
         1i.i)  Updating instances to use the new level of DB2
         1i.ii)  Restart the instances
         1i.iii)  Re-binding bind files
         1i.iv)  Uninstalling FixPaks or modification levels on UNIX
    1j)  Installing DB2 Version 8.1.2 to an alternate path
    1k)  Known problems and workarounds
         1k.i)  DB2 Data Links Manager install
         1k.ii)  Loss of Control Center functionality
         1k.iii)  Installation of a FixPak or a modification level from 
                  a directory path
         1k.iv)  Applying a FixPak or a modification level for Data 
                 Links Manager on AIX
         1k.v)  Applying a FixPak or a modification level for Data Links
                Manager on Solaris Operating Environments
         1k.vi)  Controlling login restrictions of a connecting user on 
                 an AIX server
         1k.vii)  Updates to RESTORE DATABASE Command
2)  Notices

1)  Readme for IBM(R) DB2 Universal Database(TM) Version 8.1.2 for 
          AIX(R), Solaris Operating Environments, HP-UX 11i, Linux 
          (Intel) and Linux (S/390(R), zSeries(TM))

1a)  About this readme

DB2 Version 8.1.2 is a modification level, not a FixPak.

Set the font to monospace to better view this file.

Note: If you have received special fixes from IBM support since
      05/08/2003, then you must contact IBM support to request an
      updated version of the special fixes instead of installing DB2
      Version 8.1.2. By doing this, you are assured that your system is
      in a consistent state and no special fixes are lost.

1b)  Who should read this readme file

The information in this readme file should be read by database
administrators who plan to upgrade their earlier level of DB2 Version 8
to DB2 Version 8.1.2. This readme file contains platform specific
information about the latest changes and known problems and workarounds
for DB2.

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

1c)  How to get help

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

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

To contact DB2 Customer Service by phone:
*  In the United States, call 1-800-237-5511.
*  In Canada, call 1-800-IBM-SERV (426-7378).
*  Worldwide, call 1-404-238-1234 (charges may apply). For information
   on IBM offices in your country or region, consult the IBM Directory
   of Worldwide Contacts at http://www.ibm.com/planetwide.

For additional information on changes to the product, review the product
Release Notes after you've installed DB2 Version 8.1.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.

You can also view the latest product Release Notes without installing
DB2 Version 8.1.2 by going to the DB2 Support Web site:
*  http://www.ibm.com/software/data/db2/udb/winos2unix/support

Note: You can review the Release Notes directly from the DB2 Version
      8.1.2 CD-ROM without either first installing them or without
      having to go to the IBM web site. The Release Notes can be found
      at /doc/%L/db2ir/index.htm, where %L represents the locale name.

1c.i)  IBM FTP server

DB2 Version 8.1.2 can also be downloaded from IBM's anonymous FTP server
at ftp.software.ibm.com.  Go to ps/products/db2/fixes/%L/%P/  where: 
*  %L represents the appropriate locale, for example, english-us,
   spanish, german.
*  %P represents the supported platform name/version.

The DB2 Version 8.1.2 installation image can be found in the fixpak
directory. The mfp directory contains a version of DB2 Version 8.1.2
that can be installed to an alternate path. The client directory holds
client refresh images on the related level.

The directory names for each specific UNIX operating system are:

+----------------------------------+----------------------------------+
| AIX 4.3.3 (32-bit)               | db2aix433v8                      |
+----------------------------------+----------------------------------+
| AIX 5L(TM) (32- & 64-bit)        | db2aix5v8                        |
+----------------------------------+----------------------------------+
| HP-UX 11i (32- & 64-bit)         | db2hpv8                          |
+----------------------------------+----------------------------------+
| Linux (Intel 32-bit)             | db2linuxIA32v8                   |
+----------------------------------+----------------------------------+
| Linux (S/390 and zSeries)        | db2linux390v8                    |
+----------------------------------+----------------------------------+
| Solaris Operating Environment    | db2sunv8                         |
| (32- & 64-bit)                   |                                  |
+----------------------------------+----------------------------------+

Supported languages for DB2 clients available from the FTP site

The following table details the supported languages for DB2 clients that
are available from the FTP site:

+---------+----------------------+-------------------------+---------+
| Operati | DB2 Administration   | DB2 Application         | DB2     |
| ng      | Client               | Development Client      | Run-Tim |
| System  |                      |                         | e       |
|         |                      |                         | Client  |
+---------+----------------------+-------------------------+---------+
| AIX     |  * SBCS1 (English,   |  * SBCS1 (English,      | All     |
| 4.3.3   | French, German, and  | French, German, and     | support |
| (32-bit | Italian)             | Italian)                | ed      |
| )       |  * SBCS2 (English,   |  * SBCS2 (English,      | languag |
|         | Brazilian            | Brazilian Portuguese,   | es are  |
|         | Portuguese, and      | and Spanish)            | in one  |
|         | Spanish)             |  * NORDIC (English,     | tarred  |
|         |  * NORDIC (English,  | Danish, Finnish,        | file    |
|         | Danish, Finnish,     | Norwegian, and Swedish) |         |
|         | Norwegian, and       |  * DBCS (English,       |         |
|         | Swedish)             | Japanese, Korean,       |         |
|         |  * DBCS (English,    | Simplified Chinese, and |         |
|         | Japanese, Korean,    | Traditional Chinese)    |         |
|         | Simplified Chinese,  |                         |         |
|         | and Traditional      |                         |         |
|         | Chinese)             |                         |         |
+---------+----------------------+-------------------------+---------+
| AIX 5L  |  * SBCS (English,    |  * SBCS (English,       | All     |
|         | Brazilian            | Brazilian Portuguese,   | support |
|         | Portuguese, Danish,  | Danish, Finnish,        | ed      |
|         | Finnish, French,     | French, German,         | languag |
|         | German, Italian,     | Italian, Norwegian,     | es are  |
|         | Norwegian, Spanish,  | Spanish, and Swedish)   | in one  |
|         | and Swedish)         |  * DBCS (English,       | tarred  |
|         |  * DBCS (English,    | Japanese, Korean,       | file    |
|         | Japanese, Korean,    | Simplified Chinese, and |         |
|         | Simplified Chinese,  | Traditional Chinese)    |         |
|         | and Traditional      |                         |         |
|         | Chinese)             |                         |         |
+---------+----------------------+-------------------------+---------+
| HP-UX   | All supported        | All supported languages | All     |
|         | languages are in one | are in one tarred file  | support |
|         | tarred file          |                         | ed      |
|         |                      |                         | languag |
|         |                      |                         | es are  |
|         |                      |                         | in one  |
|         |                      |                         | tarred  |
|         |                      |                         | file    |
+---------+----------------------+-------------------------+---------+
| Linux   | All supported        | All supported languages | All     |
| on      | languages are in one | are in one tarred file  | support |
| Intel   | tarred file          |                         | ed      |
| (32-bit |                      |                         | languag |
| )       |                      |                         | es are  |
|         |                      |                         | in one  |
|         |                      |                         | tarred  |
|         |                      |                         | file    |
+---------+----------------------+-------------------------+---------+
| Linux   | All supported        | All supported languages | All     |
| for     | languages are in one | are in one tarred file  | support |
| S/390   | tarred file          |                         | ed      |
|         |                      |                         | languag |
|         |                      |                         | es are  |
|         |                      |                         | in one  |
|         |                      |                         | tarred  |
|         |                      |                         | file    |
+---------+----------------------+-------------------------+---------+
| Solaris | All supported        | All supported languages | All     |
| Operati | languages are in one | are in one tarred file  | support |
| ng      | tarred file          |                         | ed      |
| Environ |                      |                         | languag |
| ments   |                      |                         | es are  |
|         |                      |                         | in one  |
|         |                      |                         | tarred  |
|         |                      |                         | file    |
+---------+----------------------+-------------------------+---------+
| Windows | All supported        | All supported languages | All     |
| (R)     | languages are in one | are in one zip file     | support |
|         | zip file             |                         | ed      |
|         |                      |                         | languag |
|         |                      |                         | es are  |
|         |                      |                         | in one  |
|         |                      |                         | zip     |
|         |                      |                         | file    |
+---------+----------------------+-------------------------+---------+

1d)  PTF and VRMF information

+-----------------------+----------------------+----------------------+
| Operating system      | PTF                  | VRMF                 |
+-----------------------+----------------------+----------------------+
| AIX 4.3.3             | U486565              | 8.1.0.16             |
+-----------------------+----------------------+----------------------+
| AIX 5                 | U486566              | 8.1.1.16             |
+-----------------------+----------------------+----------------------+
| Solaris Operating     | U486567              | 8.1.0.16             |
| Environment           |                      |                      |
+-----------------------+----------------------+----------------------+
| HP-UX 11i             | U486568              | 8.1.0.16             |
+-----------------------+----------------------+----------------------+
| LINUX (Intel 32-bit)  | MI00048              | 8.1.0.16             |
+-----------------------+----------------------+----------------------+
| LINUX (S/390,         | MI00049              | 8.1.0.16             |
| zSeries)              |                      |                      |
+-----------------------+----------------------+----------------------+
| Documentation         | U486569              | n/a                  |
+-----------------------+----------------------+----------------------+

1e)  Supported products and components by platform

This readme file contains information for the following products and
components for each UNIX operating system:

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


AIX(R) 5L (32-bit and 64-bit)
         Product list:
         *  DB2 Administration Client, Version 8
         *  DB2 Application Development Client, Version 8
         *  DB2 Connect Application Server Edition, Version 8
         *  DB2 Connect Enterprise Edition, Version 8
         *  DB2 Connect Enterprise Unlimited Edition, Version 8
         *  DB2 HTML Documentation, Version 8
         *  DB2 PDF Documentation, Version 8
         *  DB2 Run-Time Client, Version 8
         *  DB2 Spatial Extender, Version 8
         *  DB2 UDB Enterprise Server Edition, Version 8


HP-UX(TM) 11i (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 HTML Documentation, Version 8
         *  DB2 PDF Documentation, Version 8
         *  DB2 Run-Time Client, Version 8
         *  DB2 Spatial Extender, Version 8
         *  DB2 UDB Enterprise Server Edition, Version 8
         *  DB2 UDB Workgroup Server Edition, Version 8
         *  DB2 UDB Workgroup Server Unlimited Edition, Version 8


Linux(TM) (Intel(R) 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 HTML Documentation, Version 8
         *  DB2 PDF Documentation, Version 8
         *  DB2 Run-Time Client, Version 8
         *  DB2 Spatial Extender, Version 8
         *  DB2 UDB Enterprise Server Edition, Version 8
         *  DB2 UDB Personal Edition, Version 8
         *  DB2 UDB Workgroup Server Edition, Version 8
         *  DB2 UDB Workgroup Server Unlimited Edition, Version 8
         *  DB2 Warehouse Manager, Version 8


Linux(TM) (S/390(R) and zSeries(R))
         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 HTML Documentation, Version 8
         *  DB2 PDF Documentation, Version 8
         *  DB2 Run-Time Client, Version 8
         *  DB2 Spatial Extender, Version 8
         *  DB2 UDB Enterprise Server Edition, Version 8


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 Data Links Manager, Version 8
         *  DB2 HTML Documentation, Version 8
         *  DB2 PDF Documentation, Version 8
         *  DB2 Run-Time Client, Version 8
         *  DB2 Spatial Extender, Version 8
         *  DB2 UDB Enterprise Server Edition, Version 8
         *  DB2 UDB Workgroup Server Edition, Version 8
         *  DB2 UDB Workgroup Server Unlimited Edition, Version 8
         *  DB2 Warehouse Manager, Version 8
         *  DB2 Warehouse Manager Connectors, Version 8

If you add new components after you have installed DB2 Version 8.1.2,
then you need to reinstall DB2 Version 8.1.2 to ensure that the newly
added components are updated.

1f)  Prerequisites


*  You must have DB2 Version 8 installed at the VRMF level that is lower
   than DB2 Version 8.1.2 before installation.
*  Ensure that you have read the entire contents of this readme.

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

+--------+-------------------------+----------------------------------+
| Operat | Command                 | Output to look for               |
| ing    |                         |                                  |
| System |                         |                                  |
+--------+-------------------------+----------------------------------+
| AIX    | 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]  |
| 11i    | "*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                |
| (Intel |                         |                                  |
| or     |                         | where x must be smaller than the |
| S/390) |                         | current                          |
|        |                         | level (the 4th digit in VRMF).   |
+--------+-------------------------+----------------------------------+
| Solari | pkginfo -l db2cliv81 |  | VERSION: 8.1.0.x                 |
| s      | grep VERSION            |                                  |
| Operat |                         | where x must be smaller than the |
| ing    |                         | current                          |
| Enviro |                         | level (the 4th digit in VRMF).   |
| nment  |                         |                                  |
+--------+-------------------------+----------------------------------+

1g)  Before installation
1. Switch to root authority by running 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.
3. Run the following commands:
       su - aname
       . $HOME/sqllib/db2profile
       db2admin stop
       exit

   where aname represents the administration server instance name.
4. On AIX, you should also run, as root, 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.

1g.i)  Setting up DB2 Version 8.1.2 on Solaris Operating Environments, 
          AIX 4.3.3, and AIX 5L

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



Downloading the DB2 Version 8.1.2 that will be installed to an alternate
path from IBM's anonymous FTP server

If you are downloading the DB2 Version 8.1.2 that will be installed to
an alternate path from IBM's anonymous FTP server at
ftp.software.ibm.com:
1. Untar and uncompress the following compressed .tar files:
   *  FP2_$PTF_ESE_MFP.tar.Z for AIX 4.3.3 and Solaris Operating
      Environments
   *  FP2_$PTF_ESE_MFP_SBCS.tar.Z or FP2_$PTF_ESE_MFP_DBCS.tar.Z for AIX
      5

   where $PTF represents:
   *  U486565 on AIX 4.3.3
   *  U486566 on AIX 5
   *  U486567 on Solaris Operating Environments

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

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



Installing the DB2 Version 8.1.2 that will be installed to an alternate
path from the CD-ROM

If you have the DB2 Version 8.1.2 that will be installed to an alternate
path CD-ROM:
1. Copy the ese.mfp.tar(.Z) to the tempspace that you set aside for this
   installation. For AIX 5L, the file that you copy will be
   ese.mfp.sbcs.tar.Z or ese.mfp.dbcs.tar.Z. See the above section for
   the supported languages in each file.
2. Untar and uncompress the ese.mfp.tar(.Z) file (for AIX 5L, untar
   ese.mfp.sbcs.tar.Z or ese.mfp.dbcs.tar.Z).
3. See the FixpakReadme.txt for information on installing DB2 Version
   8.1.2 to an alternate path, from the tempspace directory where you
   untarred the installation image.



Installing DB2 Version 8.1.2 from the CD-ROM (AIX 4.3.3 and Solaris
Operating Environment)

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

Note: In steps 1 and 2 $PTF represents:
      *  U486565 for AIX 4.3.3
      *  U486567 for Solaris Operating Environment

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



Installing DB2 Version 8.1.2 from the CD-ROM (AIX 5L)

To install IBM DB2 Version 8.1.2 from the CD-ROMs on AIX 5L, you will be
required to manually copy filesets from two CD-ROMs: REGULAR FIXPAK 2
(vol 1 of 3) and REGULAR FIXPAK 2 (vol 2 of 3). The filesets on the
REGULAR FIXPAK 2 (vol 2 of 4) are only required if you have installed
IBM DB2 Spatial Extender or IBM DB2 Data Links Manager. If you don't
have either of these products installed, you can skip steps #2 and #4.
1. Copy the compressed tar file (FP2_U486566.tar.Z), located on REGULAR
   FIXPAK 2 (vol 1 of 4), into a temporary directory on your system.
   This directory must have 2GB of free space.
2. Copy the tar file (extra.tar), located on REGULAR FIXPAK 2 (vol 2 of
   4), into the same temporary directory on your system that you used in
   step #1.
3. Uncompress and untar the file (FP2_U486566.tar.Z).
4. Untar the extra.tar file.
5. Follow the instructions 1h,  "Installing DB2 Version 8.1.2".

Note: These steps (except step 2 and 4) also apply if you download the
      .tar.Z file from IBM's anonymous FTP server. Download the file and
      follow steps 1- 3.

1g.ii)  Data Warehouse functionality on Linux, AIX, and Solaris 
          Operating Environments

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

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

1h)  Installing DB2 Version 8.1.2



Restrictions

The following restrictions apply when installing:
*  DB2 Version 8.1.2 for AIX 4.3.3 can only be applied on AIX 4.3.3 and
   DB2 Version 8.1.2 for AIX 5 can only be applied on AIX 5.
*  On AIX, the installFixPak script provides installation prerequisite
   checking that is not provided when you install DB2 Version 8.1.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, please see your AIX manuals. It is
   strongly recommended that you use the installFixPak script to install
   DB2 Version 8.1.2.
*  On Linux (Intel or S/390), once you have installed DB2 Version 8.1.2,
   you cannot back it out and go back to the previous level.



Prerequisites
*  Ensure that you've reviewed your software, hardware, and operating
   system requirements. See the Release Notes for the latest
   information.



Procedure

To install the DB2 Version 8.1.2:
1. Change to the directory in which the installation image is located.
2. Type the ./installFixPak command to launch the installation.

Note: By default, installFixPak will commit all of the updated filesets
      on AIX.

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

   ./installFixPak -a

1i)  After installation

1i.i)  Updating instances to use the new level of DB2

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

   INSTHOME/instance/db2iupdt iname

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

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

    INSTHOME/instance/dasupdt dasname 

 where dasname represents the DAS and INSTHOME represents the install
directory appropriate to your operating system.

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

1i.ii)  Restart the instances

To restart an instance:
1. Type su <instance_name>.
2. Type the db2start command.

Repeat for each instance.

To restart the administration server, login the DAS owner ID and run the
db2admin start command.

1i.iii)  Re-binding bind files

Due to the new bind (.bnd) files that have been shipped with DB2 Version
8.1.2, you will need to bind your DB2 utilities against all your
databases after installation.  This step is necessary for the fixes in
DB2 Version 8.1.2 to become effective.  The procedure of binding, which
follows, only needs to be performed once per database.

Re-binding to DB2 UDB databases

After applying fixes, you must do the following:

At a command prompt:
       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:
       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.

Re-binding host databases

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


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

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

Re-binding specific packages

If you want to bind only a specific .bnd file to the database, issue the
following commands for each database.

At a command prompt:
       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:
       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.

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 are at
different versions or service levels of DB2, you must bind the utilities
once for each operating system and DB2 client-version combination.

Bind db2schema.bnd to existing databases

After DB2 Version 8.1.2 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 these commands: 

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.

1i.iv)  Uninstalling FixPaks or modification levels on UNIX

Note: If you have received special fixes from IBM Support that you have
      applied to the DB2 Version 8.1.2 level, you will lose all of the
      special fixes when you uninstall DB2 Version 8.1.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.1.2.

Before uninstalling DB2 Version 8.1.2, ensure that you:
*  Stop all instances, including the DAS instance
*  Backup your data

AIX      If DB2 Version 8.1.2 was installed and the filesets were just
         applied but not committed, then DB2 Version 8.1.2 can be
         uninstalled using smit. See the smit documentation for more
         details.

         If the filesets were committed when DB2 Version 8.1.2 was
         installed, which is the default, then DB2 Version 8.1.2 cannot
         be uninstalled. The only course of action available is to
         uninstall DB2 from your system, reinstall DB2 Version 8, and
         then bring DB2 on the system to the desired level by applying
         the corresponding level of DB2 .


HP-UX    DB2 Version 8.1.2 filesets can be uninstalled using the sam
         utility. If you use swlist or sam, you can list all filesets
         for DB2 Version 8.1.2 and receive output similar to the
         following:
            PDB2_810100010 8.1.0.8
            PDB2_810100011 8.1.0.8
            PDB2_810200011 8.1.0.16
            PDB2_810200010 8.1.0.16 

         The installation signature is combined with the name of the
         fileset. You should uninstall the group of PDB2_* filesets with
         the same signature starting with the largest number. You can
         remove DB2 Version 8.1.2, or the latest version plus the second
         last, etc. You can also select them all.

Linux (Intel and s/390)
         You cannot uninstall DB2 Version 8.1.2 on Linux (Intel and
         s/390). The only course of action available is to uninstall DB2
         from your system, reinstall DB2 Version 8, and then bring DB2
         on the system to the desired level by applying the
         corresponding level of DB2. A db2_deinstall script is provided
         with DB2 Version 8.1.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.1.2 and leave the
         system in the state that it was before installing DB2 Version
         8.1.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.1.2.  You must uninstall from the
         highest to the lowest level until you've uninstalled the
         version that you want to remove. For example if you're at
         FixPak 7, you wouldn't be able to uninstall FixPak 5 unless
         you've uninstalled modification level 6 and FixPak 7.

Update all instances, including the DAS instance.

1j)  Installing DB2 Version 8.1.2 to an alternate path

DB2 UDB Enterprise Server Edition (ESE) operating on UNIX-based
operating systems now supports FixPaks or modification levels that have
been installed in an alternate path in a production environment.
Essentially, this enables you to have another FixPak or modification
level of DB2 installed in a different path from your current DB2 level. 
 For DB2 Version 8, it is possible to have multiple code levels
simultaneously existing on your system.

For more information about installing DB2 Version 8.1.2 to an alternate
path, see the DB2 Version 8.1.2 Release Notes.

To install DB2 Version 8.1.2 to an alternate path, ensure that:
*  You have root authority.
*  You have a copy of the DB2 Version 8.1.2 image that will be installed
   to an alternate path. This can be downloaded from IBM's 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.

The following restrictions apply:
*  Response file installations of DB2 Version 8.1.2 to be installed to
   an alternate path are not supported at this time.
*  The DB2 Version 8.1.2 to be installed to an alternate path is always
   installed to a predetermined path, meaning that you cannot select a
   different path for installation.
*  If you install the DB2 Version 8.1.2 to be installed to a alternate
   path without an installed copy of DB2 Version 8, you will need to
   obtain the license key from the Version 8 release level media. You
   can then install the license by using the db2licm command.

If you want to update an instance running against a 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 FixPak 1 that has been
installed to an alternate path. If you wish to update the instance to
run at the V8.1.2 code level,  you can perform one of the following:
1. Install DB2 Version 8.1.2 to an alternate path, then update your
   instance. For example:
   a. Install V8.1.2 to an alternate path.
   b. Stop db2inst1.
   c. Run V8.1.2_alternate_installation_path/instance/db2iupdt db2inst1
      	where V8.1.2_alternate_installation_path refers to the alternate
      installation path for V8.1.2.

2. Install DB2 Version 8.1.2 against the Version 8.1 code, then update
   your instance. For example:
   a. Install DB2 Version 8.1.2 on top of the Version 8.1 GA (General
      Availability) 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 V8.1.2.

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

To install DB2 Version 8.1.2 to be installed to an alternate path for
Enterprise Server Edition (ESE) on UNIX operating systems:
1. Run the installAltFixPak utility from the directory where you
   untarred the image for DB2 Version 8.1.2 to be installed to an
   alternate path.
2. The install program checks to see if DB2 Version 8 is installed. If
   it detects an existing DB2 Version 8 installation, it will prompt you
   to install the same filesets/packages from the DB2 Version 8.1.2 to
   be installed to an alternate path.
   *  If the answer is yes, then the installation program proceeds to
      install the same set of filesets/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.1.2 to be installed
      to an alternate path - licenses must be installed from the Version
      8 release level media.

1k)  Known problems and workarounds

1k.i)  DB2 Data Links Manager install

The DB2 Data Links Manager install 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.

1k.ii)  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/

1k.iii)  Installation of a FixPak or a modification level from a 
          directory path

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

/home/DB2FixPak/FP2/ ...

It should not resemble the following:

/home/DB2 FixPak/FP2/ ...

1k.iv)  Applying a FixPak or a modification level for Data Links Manager 
          on AIX

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

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

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

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

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

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

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

1k.v)  Applying a FixPak or a modification level for Data Links Manager 
          on Solaris Operating Environments

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

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

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

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

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

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

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

1k.vi)  Controlling login restrictions of a connecting user on an AIX 
          server

By default, when an user is authenticated on an AIX server, DB2 will
check the connecting user's local login restrictions before allowing the
connection to proceed. The DB2LOGINRESTRICTIONS registry variable will
permit DB2 to enforce alternative modes of login restrictions. If
DB2LOGINRESTRICTIONS is not set, the default value is LOCAL. The
variable may be set to the following values:

REMOTE   DB2 will only enforce remote login restrictions

SU       DB2 will only enforce su restrictions

NONE     DB2 will not enforce any particular mode of login restrictions

LOCAL    DB2 will only enforce local login restrictions

In all cases, DB2 will still check for the following error conditions:
*  expired account
*  locked account
*  invalid user

1k.vii)  Updates to RESTORE DATABASE Command

The following is an update to the RESTORE DATABASE command topic.

You can restore database backups created in DB2 Version 8 32-bit Windows
system to a DB2 Version 8 64-bit Windows system, or the reverse.

Database backups created on AIX, HP-UX, and Solaris Operating
Environments, each in either DB2 Version 8 32-bit or 64-bit, may be
restored on  AIX, HP-UX, and Solaris Operating Environments, each in
either DB2 Version 8 32-bit or 64-bit.

You can restore database backups created in DB2 Version 8 32-bit Linux
(Intel) to a DB2 Version 8 64-bit Linux (Intel) platform, or the
reverse.

2)  Notices

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

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

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

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

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

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

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

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

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

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

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

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

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

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

COPYRIGHT LICENSE:

This information may contain sample application programs, in source
language, which illustrate programming techniques on various operating
platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM for the purposes of developing, using,
marketing, or distributing application programs conforming to the
application programming interface for the operating platform for which
the sample programs are written. These examples have not been thoroughly
tested under all conditions. IBM, therefore, cannot guarantee or imply
reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work
must include a copyright notice as follows:

(C) (your company name) (year). Portions of this code are derived from
IBM Corp. Sample Programs.  (C) Copyright IBM Corp. _enter the year or
years_. All rights reserved.

IBM, DB2, Universal Database, and S/390 are trademarks of International
Business Machines Corporation in the United States, other countries, or
both.

Windows is a registered trademark of Microsoft Corporation in the United
States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Other company, product, or service names may be trademarks or service
marks of others.

-------------------------------------------------------------------------------
 *  are trademarks or registered trademarks of IBM Corporation. 
** are trademarks or registered trademarks of their respective owners.  
-------------------------------------------------------------------------------

*******************************************************************************
**
**  (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1999-2003.
**                    ALL RIGHTS RESERVED.
**
*******************************************************************************