Installation, migration, upgrade, and configuration information

Hardware and software requirements

Hardware and software requirements can be viewed at the following Web site:

http://www.ibm.com/software/data/db2/udb/sysreqs.html

Installation notes

On UNIX and Linux platforms, these Installation notes apply to installation of new products only. To apply a FixPak, see the FixPak's Readme.

On Windows platforms, these Installation notes apply to both the installation of new products and the application of FixPaks. If you are applying a FixPak, these Installation notes should be used in conjunction with the FixPak Readme.

Review this entire section before installing DB2 UDB.

Directory path cannot contain blanks (Linux and UNIX)

If the db2setup program is run from a directory whose path includes a blank, 3the setup will fail with the following error:

<file>: not found  

Place the installable image in a directory whose path does not include 3spaces.

2JDK levels for DB2 UDB (Linux on IA64 and Linux on PowerPC)2

2When you install version 8.2 of DB2 Universal Database on Linux, 2the RPM-based installation attempts to install the IBM Java RPM (IBMJava2-SDK-1.4.1.-2.0.i386.rpm).

2If a later level of the RPM (such as IBMJava2-SDK-1.5.0.-2.0.i386.rpm) 2already exists, the back-level RPM is not installed.

2However, in this case, the installation leaves the JDK_PATH database 2configuration parameter pointing to the Java 1.4 path, /opt/IBMJava2-14/. As a result, none of the Java-dependant functionality, 2including the installation of the DB2 Tools Catalog, will work.

7

7
1. To point DB2 UDB to the correct IBM Developer Kit, run the following command: 7

   db2 update dbm cfg using JDK_PATH path

   where path the 1.5 install path, such as /opt/IBMJava2-15.

Uncompressing installation images (Linux and UNIX)

Some installation images are delivered in compressed or gzipped format 7on the product CDs. Before you can install DB2 UDB from these formats, you 7need to copy the installation image to a temporary directory and uncompress 7or gunzip the installation image.

The compressed or gzipped installation images on the CD have the file name PRODUCT.tar.Z or PRODUCT.tar.gz, where PRODUCT is the DB2 product you are 7installing. For example, if you are installing DB2 Enterprise Server Edition, 7the compressed image on the relevant CD might be called either ese.tar.Z or ese.tar.gz.

In addition to the software disk requirements, you must have a filesystem 7with 2 gigabytes of free space to contain the tar.Z or tar.gz file and the 7uncompressed installation image.

DB2 UDB does not allow non-English installation path (Windows)

During DB2 UDB installation on Windows, you can enter the directory path 2for DB2 UDB. However, the directory path name you enter can contain only English 2characters.

Downloading and uncompressing FixPaks for multiple products (Windows)

Starting with DB2 Version 8 for Windows Fixpak 3, IBM is providing product-specific 6FixPaks instead of one general FixPak. This change affects only DB2 Version 68 products on Windows platforms.

For example, if you have DB2 UDB Enterprise Server Edition Version 8 and 6DB2 Spatial Extender Version 8 installed on the same Windows system, you must 6download the DB2 UDB Enterprise Server Edition FixPak image and the Spatial 6Extender FixPak image. You must uncompress each image under a common parent 6directory. All images must be uncompressed for the GUI installation or silent 6installation to proceed.

For complete FixPak installation instructions, see the latest DB2 UDB FixPak 6Readme.

Installing DB2 UDB from installation images (Linux and UNIX)

If the installation images are delivered in compressed or gzipped format 7on the product CDs, you must uncompress or gunzip the installation image before 7you can install DB2 UDB. See the Uncompressing installation 7images (Linux and UNIX) section for details.

To perform the installation using the DB2 Setup wizard, enter the following 7command:

    ./PRODUCT/db2setup

where PRODUCT is the DB2 product you are installing. For 7example, if you are installing DB2 Enterprise Server Edition, enter ./ese/db2setup.

The installation Launchpad opens. Proceed through the installation panels.

Installing DB2 UDB from installation images (Windows)

To perform the installation using the DB2 Setup wizard, insert the CD into 7the drive. If enabled, the auto-run feature automatically starts the DB2 Setup 7launchpad.

Disk space required for a DB2 UDB response file installation

When you install a DB2 UDB product using a response file, 1 MB of free 7disk space is required in the etc directory.

If you receive error message DBI1191I during a response file installation, 7the message indicates there is not enough free disk space in the root directory. 7This message is misleading. Check the amount of free disk space in the etc directory. A minimum of 1 MB of free disk space 7is required before re-running the installation.

Restrictions to adding products using the db2setup command (Linux, 6UNIX)

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

The following table summarizes the db2setup combinations:

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

DB2 Web Tools

The application servers supported by DB2 Web Tools for the following languages are required to be compliant with the Servlet 2.3 specification:

• Japanese
• Korean
• Simplified Chinese
• Traditional Chinese
• Russian
• Polish

Binding Query Patroller packages after applying fixpaks

If you have Query Patroller installed, after applying a fixpak and performing 6all post-fixpak installation tasks, perform the following steps:

6
1. Log in as a user with DBADM authority.
6
2. Change to the proper directory: 6
   6
   • INSTPATH/bnd (Linux and UNIX)
   6
   • INSTPATH\bnd (Windows)
   where INSTPATH is the DB2 UDB instance path.
6
3. Run the following commands: 6

     db2 connect to dbname
   6  db2 bind @qpserver.lst blocking all grant public

Query Patroller installation at FixPak 3 level or later

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

If you have DB2 UDB Version 8 FixPak 3 or later installed and you install 6the DB2 Query Patroller^(TM) base or GA version, you must reapply DB2 UDB FixPak 63 or later. Otherwise, the Query Patroller changes are not applied to the 6DB2 UDB FixPak level you are at.

If you are installing the Query Patroller server, you must also update 6the DB2 UDB instances after reapplying the DB2 UDB FixPak level. The instances 6must be restarted after they are updated.

Query Patroller server installation

When you are installing Query Patroller server note the following:

2
• If you select Computer usage based from 2the Select the installation type window using 2the DB2 Setup wizard, and you select Server from 2the Select how this computer will be used window, 2the Query Patroller Center will not be installed. If you want to install the 2Query Patroller Center, select either the Complete or the Custom installation types from 2the Select the installation type window.
2
• The DB2 Query Patroller Guide uses installation 2panels from the Computer usage based installation type to illustrate how to 2install Query Patroller server using the DB2 Setup wizard. You do not have 2to use the Computer usage based installation type to install Query Patroller 2server. You can use either the Complete or the Custom installation types to 2install Query Patroller server.
2
• DB2 Clients which have Query Patroller Client Tools installed must connect 2to a partition that has the Query Patroller server installed. In a typical 2partitioned database environment, the Query Patroller server is installed 2on all partitions, so you can choose any partition to be the coordinator partition 2and still be able to use the Query Patroller client tools.

Defining a new database partition group in Query Patroller

When you define a new table space during Query Patroller installation in 7a partitioned environment, you can select an existing database partition 7group. Alternatively, you can set up a new database partition group for the 7new table space. If you choose to set up a new database partition group, 7you can select only one database partition from the list box on the install 7panel for that new database partition group. If you want to add additional 7partitions into the new database partition group, you must add them manually 7after the installation is complete.

Query Patroller client tools installation

DB2 clients do not require the Query Patroller client tools to be installed 2on them in order to submit queries to the Query Patroller server.

Recreating beta versions of spatial databases

If you created spatial databases in a beta version of DB2 Geodetic Extender 7Version 8.2, you must recreate them in the official version of Geodetic Extender 7Version 8.2.

Installing MDAC files for national language versions of DB2 UDB

If you do not install the national language version of Microsoft Data Access Components (MDAC) 2.7 prior to installing the national language version of DB2 UDB Version 8.2, DB2 Universal Database installs English MDAC files by default. This installation causes the Windows ODBC Data Source Administrator panels to appear untranslated if your operating system is in a language other than English. To fix this problem, install the "MDAC 2.7 RTM - Refresh" bundle from the Microsoft Web site at http://msdn.microsoft.com/data/downloads/updates/default.aspx. Choose the language that you want to install, download the required executable file, and run it. This procedure installs the translated ODBC Data Source Administrator files.

DB2 license policy for DB2 Universal Database Workgroup Server Edition

The Internet license policy is not valid for DB2 Universal Database Workgroup Server Edition. If you require a license for Internet users, you need to purchase DB2 Universal Database Workgroup Server Unlimited Edition.

5Installing additional Asian fonts (Linux)5

5IBM offers additional font packages for Linux that contain additional 5double-byte character set (DBCS) support for Asian characters. These font 5packages are necessary with some versions of Linux that install only the fonts 5required to display the country-specific or region-specific characters.

5If you run the db2setup command and 5find missing characters in the DB2 setup wizard interface, it is likely that 5your Linux system does not have all the necessary fonts installed. To enable 5the db2setup command to properly refer to the 5fonts embedded in the installation CD, perform the following task:

5
1. Enter the following command: 5

   export JAVA_FONTS=/<cdrom>/db2/<linux_platform>/java/jre/lib/fonts

   5

   where <cdrom> is the location of the install image and <linux_platform> 3is a directory name with a Linux prefix.5

5
2. Re-run the db2setup command.

5If you notice missing characters when using the DB2 GUI tools 5after installation, install the necessary fonts provided with the DB2 product. 5These fonts can be found in the fonts directory on any of the following 5CDs:

7 7
• 7IBM Developer Kit, Java Technology Edition 7(64-bit) for AIX 5L 7
7
• 7DB2 Embedded Application Server and applications 7(XML registry, Web Administration tools and Java distributed debugger) for 7your operating system7

5In the fonts directory, there are two typefaces available: 5Times New Roman WorldType and Monotype Sans Duospace WorldType. For each typeface, 5there is a country-specific or region-specific font. The following table lists 5the eight fonts provided in compressed format in the fonts directory.

Configuring the Development Center to use Java Development Kits (Linux)

In some cases, DB2 UDB does not install a Java Development Kit on the client operating system. To use the Development Center to develop Java stored procedures on these clients, you must point the Development Center to the location of an installed Java Development Kit .

7Follow these steps to identify the location of a Java Development 7Kit:

7
1. In Development Center, select the Project -> Environment Settings menu item.
7
2. In the Environment Settings notebook, select the Process node.
7
3. In the Java Home section of the Process 7page, select the JDK level that will be used 7to build and run Java stored procedures.
7
4. In the Directory field, specify a directory 7path that exists or is accessible on the client where the selected JDK is 7installed.
7
5. If the client computer is used to develop Java stored procedures on multiple 7DB2 servers, you might need to select additional JDK levels and specify their 7installed locations, depending on which JDK levels are used by these servers.

On the DB2 server, the Java Development Kit installation might not have 7linked some Java libraries into the system /usr/lib subdirectory. 7 These links are needed to build and run Java stored procedures.

The following example shows how to create the links to a Java Development Kit on a Linux client:

 # Setup the links to the .so files 
cd /usr/lib
ln -s /opt/IBMJava2-131/jre/bin/libhpi.so 
ln -s /opt/IBMJava2-131/jre/bin/libjava.so
ln -s /opt/IBMJava2-131/jre/bin/libjitc.so
ln -s /opt/IBMJava2-131/jre/bin/libxhpi.so
ln -s /opt/IBMJava2-131/jre/bin/libzip.so
ln -s /opt/IBMJava2-131/jre/bin/classic/libjvm.so 

Creating group and user IDs on United Linux 1.0 and SuSE Linux distributions

To create group and user IDs for a DB2 UDB Version 8.2 installation on 7United Linux 1.0 and SuSE Linux distributions, use the groupadd and useradd commands, respectively. The version 8.2 Installation and Configuration Supplement incorrectly documents the mkgroup and mkuser commands to create group and user IDs, 7respectively.

Help system daemon does not start after installing with the db2_install 7command (UNIX)

If you are installing the DB2 Information Center on UNIX platforms using 7the db2_install command, the help system daemon (db2icd) does not start following 7the installation. You need to manually start the help system daemon or restart 7your computer to access the documentation.

See the topic titled "DB2 Information Center daemon" in the Documentation updates | Installation and configuration section of the Version 8.2 Release Notes.

Ready for Tivoli enablement (UNIX)

When you purchase an IBM software product that carries the Ready for Tivoli^(R) logo, you can manage your IBM software products through various Tivoli offerings. The Tivoli products allow you to automatically discover, monitor, and inventory one or more Ready for Tivoli applications.

IBM software products that are Ready for Tivoli can be managed through products such as IBM Tivoli Configuration Manager. IBM Tivoli Monitoring for Databases provides support for all leading databases including DB2 UDB, Oracle, and Informix^(R).

For additional information, point your browser to the IBM Web site at http://www.tivoli.com/products/tivoli_ready/

Installation image reduction tool (Windows)

The db2iprune command line utility can reduce the size of your DB2 UDB 7Windows product installation image. The tool is particularly useful for large 7scale deployments of DB2 UDB. The tool is also useful for embedding DB2 UDB 7within an application.

The db2iprune tool consists of an input file and an executable file. The 7input file (.prn), contains a full list of removable components and is used 7to indicate which features and languages you would like to remove from the 7installation image. The db2iprune executable file (db2iprune.exe) then removes 7the cabinet files associated with those features and languages. The result 7is a new, smaller DB2 UDB image that can be installed using the regular installation 7methods. Fixpaks are also applied using the regular methods. When the fixpak 7is installed it detects and updates only the components that were installed 7using db2iprune.

The db2iprune tool is located in the \db2\windows\utilities\db2iprune directory on your DB2 UDB product installation CD. This directory also 7contains a Readme file. Refer to the db2iprune Readme for detailed instructions 7on how to use db2iprune.

DB2 Universal Database, Version 8 HTML documentation installation restriction (Windows)

On Windows, do not install the DB2 Universal Database, Version 8 HTML documentation on a workstation or server where a DB2 Universal Database, Version 7 (or earlier) product is already installed. The installer detects the earlier version and removes the earlier product.

Previous installations updated to the latest level (Windows)

If you have a DB2 product that is installed at an earlier Version 8 level, 3the installation image detects this and updates the product to the latest 3level.

System requirements for the DB2 .NET Data Provider (Windows)

Before using the DB2 UDB installation program to install the DB2 .NET Data 3Provider, you must have the .NET Framework already installed on the computer. 3If the .NET Framework is not installed, the DB2 UDB installation program will 3not register the DB2 .NET Data Provider.

If DB2 UDB is installed and the .NET Framework is not installed, the DB2 3.NET Data Provider is not registered. If the .NET Framework is installed 3at a later date, you can run the db2nmpreg executable to register the provider. 3 This executable resides in the sqllib\bin directory. There are no parameters.

To register DB2 .NET Data Provider, enter db2nmpreg from any command window.

Installing DB2 Version 8 Clients and DB2 Connect PE as a non-Administrator (Windows)

When installing a DB2 Administration client, DB2 Application Development client, or DB2 Connect Personal Edition, you must update your Windows TCP/IP services file if the following conditions apply:

• The data warehousing feature is selected in the installation setup
• The user ID performing the installation is not a member of the Administrators group on the target computer
• The product is being installed on any one of the following operating systems: Windows NT^(R), Windows 2000, Windows XP, or Windows Server 2003.

If all of the these conditions apply, the following entries need to be added to the Windows TCP/IP services file:

Without these entries, the Data Warehouse Center will not function properly.

Migration notes

Migrating DB2 UDB (Windows)

The following steps show the correct order for the migration prerequisites 7for DB2 UDB on Windows.

Migrating DB2 Universal Database when using DataJoiner or replication

If you want to migrate an instance of DataJoiner^(R) or DB2 Universal 1Database for Linux, UNIX, and Windows on which you are running the Capture 1or Apply programs for DB2 Universal Database replication, you must prepare 1to migrate your replication environment before you migrate the DB2 Universal 1Database or DataJoiner instance. Detailed instructions for carrying out the 1required preparation are included in the migration documentation for DB2 DataPropagator^(TM), 1Version 8. You can find migration documentation for DB2 DataPropagator, Version 18 at http://www.ibm.com/software/data/dpropr/.

Migrating a DB2 Version 8 Windows 32-bit database to Windows 564-bit

This topic lists the steps for migrating your 32-bit DB2 Version 58 database on a 32-bit computer to a 64-bit database on a 64-bit 5Windows operating system.

Migrating XML Extender from previous versions

If you are using an earlier version of DB2 XML Extender, you must migrate 2 each database that is enabled for XML Extender before you use an existing 2 XML-enabled database with the updated XML Extender release. Each new fix 2 pack contains all of the previous fix packs' updates.

Before running the migration program, create a backup of the database.

To migrate an XML enabled database and XML enabled columns, complete the 2following steps.

2
1. From the DB2 Command Line, enter: 2

   db2 connect to database_name
   2db2 bind dxxinstall/bnd/@dxxMigv.lst
   2db2 bind dxxinstall/bnd/@dxxbind.lst

   where dxxinstall is the directory path in which you installed DB2 Universal 2Database .
2
2. From the DB2 Command Line, enter: 2

   dxxMigv database_name

Database migration (HP-UX on IA64)

Database migration is not supported for DB2 UDB for HP-UX on IA64 throughout 4the Version 8.x releases.

Restoring a Version 7 DB2 backup image to a Version 8 instance is not 4supported on DB2 UDB for HP-UX on IA64.