Installing DB2 Version 9.7 Contents 1.0 Edition Notice 2.0 Installing DB2 Servers 2.1 Before you install 2.1.1 DB2 servers and IBM data server clients 2.1.2 DB2 installation methods 2.1.3 Supported DB2 interface languages 2.2 Installation requirements for DB2 database products 2.2.1 Disk and memory requirements 2.2.2 Java software support for DB2 products 2.2.3 Installation requirements for DB2 servers and IBM data server clients (Windows) 2.2.4 Installation requirements for DB2 servers and IBM data server clients (AIX) 2.2.5 Installation requirements for DB2 servers and IBM data server clients (HP-UX) 2.2.6 Installation requirements for DB2 servers and IBM data server clients (Linux) 2.2.7 Installation requirements for DB2 servers and IBM data server clients (Solaris) 2.2.8 Password rules 2.3 Additional Windows requirements 2.3.1 DB2 services running on your system (Windows) 2.3.2 Required user accounts for installation of DB2 server products (Windows) 2.3.3 Setting up Windows elevated privileges before installing a DB2 product (Windows) 2.3.4 Granting user rights (Windows) 2.3.5 Extending the Active Directory Schema for LDAP directory services (Windows) 2.3.6 Verifying port range availability on participating computers (Windows) 2.4 Additional Linux and UNIX requirements 2.4.1 Multiple DB2 copies on the same computer (Linux and UNIX) 2.4.2 DB2 users and groups (Linux and UNIX) 2.4.3 Centralized user-management considerations (Linux and UNIX) 2.4.4 Preparing to install DB2 for Linux on zSeries 2.4.5 Creating group and user IDs for a DB2 database installation (Linux and UNIX) 2.4.6 OS user limit requirements (Linux and UNIX) 2.4.7 Kernel parameters (Linux and UNIX) 2.5 Installing on Windows 2.5.1 An overview of installing your DB2 server product (Windows) 2.5.2 Installing DB2 servers (Windows) 2.5.3 Multiple DB2 copies on the same computer (Windows) 2.6 Installing on Linux and UNIX 2.6.1 An overview of installing your DB2 server product (Linux and UNIX) 2.6.2 Installing as a root user 2.6.3 Installing as a non-root user 3.0 IBM data server clients and drivers overview 3.1 IBM data server client types 3.2 IBM Data Server Drivers 3.2.1 IBM Data Server Driver restrictions 3.2.2 Installing IBM Data Server Driver Package (Windows) 3.2.3 Installing IBM Data Server Driver Package (Linux and UNIX) 3.3 Installation methods for IBM data server clients 3.3.1 Options for connecting to DB2 databases 3.3.2 Installing IBM data server clients (Windows) 3.3.3 Installing IBM data server clients (Linux and UNIX) 4.0 Overview of the DB2 technical information 4.1 Terms and Conditions 5.0 Notices 1.0 Edition Notice This document contains proprietary information of IBM®. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such. You can order IBM publications online or through your local IBM representative. * To order publications online, go to the IBM Publications Center at www.ibm.com/shop/publications/order * To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at www.ibm.com/planetwide To order DB2® publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU (426-4968). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. 2.0 Installing DB2 Servers 2.1 Before you install 2.1.1 DB2 servers and IBM data server clients A DB2 database system consists of a DB2 server and IBM data server clients. A DB2 server is a relational database management system (RDBMS) that delivers data to its IBM data server clients. If you plan to use a database that resides on this computer, install a DB2 server. For more information about DB2 servers, go to http://www-306.ibm.com/software/data/db2/9/editions.html An IBM data server client is an application that allows you to run commands and SQL statements against a DB2 server, connect to a remote DB2 server, and access its databases. 2.1.2 DB2 installation methods This topic provides information about DB2 installation methods. The following table shows the installation methods that are available by operating system. Table 1. Installation method by operating system. +-----------------------+----------------------+----------------------+ | Installation method | Windows® | Linux® or UNIX® | +-----------------------+----------------------+----------------------+ | DB2 Setup wizard | Yes | Yes | +-----------------------+----------------------+----------------------+ | Response file | Yes | Yes | | installation | | | +-----------------------+----------------------+----------------------+ | db2_install command | No | Yes | +-----------------------+----------------------+----------------------+ | Payload file | No | Yes | | deployment | | | +-----------------------+----------------------+----------------------+ The following list describes DB2 installation methods. DB2 Setup wizard The DB2 Setup wizard is a GUI installer available on Linux, UNIX, and Windows operating systems. The DB2 Setup wizard provides an easy-to-use interface for installing DB2 products and for performing initial setup and configuration tasks. The DB2 Setup wizard can also create DB2 instances and response files that can be used to duplicate this installation on other machines. Note: For non-root installations on Linux and UNIX platforms, only one DB2 instance can exist. The DB2 Setup wizard automatically creates the non-root instance. On Linux and UNIX platforms, an X server is required to display the DB2 Setup wizard. Response file installation A response file is a text file that contains setup and configuration values. The file is read by the DB2 setup program and the installation is performed according to the values that have been specified. A response file installation is also referred to as a silent installation. Another advantage to response files is that they provide access to parameters that cannot be set using the DB2 Setup wizard. On Linux and UNIX operating systems, if you embed the DB2 installation image in your own application, it is possible for your application to receive installation progress information and prompts from the installer in computer-readable form. This behavior is controlled by the INTERACTIVE response file keyword. There are a number of ways to create a response file: Using the response file generator You can use the response file generator to create a response file that replicates an existing installation. For example, you might install an IBM data server client, fully configure the client, then generate a response file to replicate the installation and configuration of the client to other computers. Using the DB2 Setup wizard The DB2 Setup wizard can create a response file based on the selections you make as you proceed through the DB2 Setup wizard. Your selections are recorded in a response file that you can save to a location on your system. If you select a partitioned database installation, two response files will be generated, one for the instance-owning computer and one for participating computers. One benefit of this installation method is that you can create a response file without performing an installation. This feature can be useful to capture the options required to install the DB2 product. The response file can be used at a later time to install the DB2 product according to the exact options you specified. You can export a client or server profile with the db2cfexp command to save your client or server configuration, and then easily import the profile using the db2cfimp command. A client or server profile exported with the db2cfexp command can also be imported during a response file installation using the CLIENT_IMPORT_PROFILE keyword. You should export the client or server profile after performing the installation and cataloging any data sources. Customizing the sample response files that are provided for each DB2 product An alternative to using the response file generator or the DB2 Setup wizard to create a response file is to manually modify a sample response file. Sample response files are provided on the DB2 product DVD. The sample response files provide details about all the valid keywords for each product. db2_install command (Linux and UNIX platforms only) The db2_install command installs all components for the DB2 product you specify with the English interface support. You can select additional languages to support with the -L parameter. You cannot select or deselect components. Although the db2_install command installs all components for the DB2 product you specify, it does not perform user and group creation, instance creation, or configuration. This method of installation might be preferred in cases where configuration is to be done after installation. To configure your DB2 product while installing it, consider using the DB2 Setup wizard. On Linux and UNIX operating systems, if you embed the DB2 installation image in your own application, it is possible for your application to receive installation progress information and prompts from the installer in computer-readable form. This installation methods requires manual configuration after the product files are deployed. Payload file deployment (Linux and UNIX only) This method is an advanced installation method that is not recommended for most users. It requires the user to physically install payload files. A payload file is a compressed tarball that contains all of the files and metadata for an installable component. This installation methods requires manual configuration after the product files are deployed. Note: DB2 product installations are no longer operating system packages on Linux and UNIX platforms. As a result, you can no longer use operating system commands for installation. Any existing scripts that you use to interface and query with DB2 installations must change. 2.1.3 Supported DB2 interface languages DB2 language support for DB2 interfaces can be categorized into server group languages and client group languages. Server group languages will translate most messages, help, and DB2 graphical interface elements. Client group languages will translate the IBM Data Server Runtime Client component, which will include most messages and certain help documentation. Server group languages include: Brazilian Portuguese, Czech, Danish, Finnish, French, German, Italian, Japanese, Korean, Norwegian, Polish, Russian, Simplified Chinese, Spanish, Swedish, and Traditional Chinese. Client group languages include: Arabic, Bulgarian, Croatian, Dutch, Greek, Hebrew, Hungarian, Portuguese, Romanian, Slovak, Slovenian, and Turkish. Do not confuse languages supported by the DB2 product with languages supported by the DB2 interface. Languages supported by the DB2 product means the languages in which data can exist. These languages are a superset of languages supported by the DB2 interface. 2.1.3.1 Displaying the DB2 Setup wizard in your national language (Linux and UNIX) The db2setup command queries the operating system to determine the existing language settings. If the language setting of your operating system is supported by db2setup, then that language will be used when displaying the DB2 Setup wizard. If your system uses the same code pages but different locale names than those supported by the DB2 interface, you can still see the translated db2setup by setting your LANG environment variable to the appropriate value by entering the following command: bourne (sh), korn (ksh), and bash shells: LANG= export LANG C shell: setenv LANG where locale is a locale supported by the DB2 interface. 2.1.3.2 Language identifiers for running the DB2 Setup wizard in another language If you want to run the DB2 Setup wizard in a language different from the default language on your computer, you can start the DB2 Setup wizard manually, specifying a language identifier. The language must be available on the platform where you are running the installation. On Windows operating systems, you can run setup.exe with the -i parameter to specify the two-letter language code of the language the installation is to use. On Linux and UNIX operating systems, it is recommended that you set the LANG environment variable to display the DB2 Setup wizard in your national language. Table 2. Language identifiers +----------------------------------+----------------------------------+ | Language | Language identifier | +----------------------------------+----------------------------------+ | Arabic (available on Windows | ar | | platforms only) | | +----------------------------------+----------------------------------+ | Brazilian Portuguese | br | +----------------------------------+----------------------------------+ | Bulgarian | bg | +----------------------------------+----------------------------------+ | Chinese, Simplified | cn | +----------------------------------+----------------------------------+ | Chinese, Traditional | tw | +----------------------------------+----------------------------------+ | Croatian | hr | +----------------------------------+----------------------------------+ | Czech | cz | +----------------------------------+----------------------------------+ | Danish | dk | +----------------------------------+----------------------------------+ | Dutch | nl | +----------------------------------+----------------------------------+ | English | en | +----------------------------------+----------------------------------+ | Finnish | fi | +----------------------------------+----------------------------------+ | French | fr | +----------------------------------+----------------------------------+ | German | de | +----------------------------------+----------------------------------+ | Greek | el | +----------------------------------+----------------------------------+ | Hungarian | hu | +----------------------------------+----------------------------------+ | Italian | it | +----------------------------------+----------------------------------+ | Japanese | jp | +----------------------------------+----------------------------------+ | Korean | kr | +----------------------------------+----------------------------------+ | Norwegian | no | +----------------------------------+----------------------------------+ | Polish | pl | +----------------------------------+----------------------------------+ | Portuguese | pt | +----------------------------------+----------------------------------+ | Romanian | ro | +----------------------------------+----------------------------------+ | Russian | ru | +----------------------------------+----------------------------------+ | Slovak | sk | +----------------------------------+----------------------------------+ | Slovenian | sl | +----------------------------------+----------------------------------+ | Spanish | es | +----------------------------------+----------------------------------+ | Swedish | se | +----------------------------------+----------------------------------+ | Turkish | tr | +----------------------------------+----------------------------------+ 2.1.3.3 Changing the DB2 product interface language (Windows) The DB2 interface language is the language that appears in messages, help, and graphical tool interfaces. When installing your DB2 product, you have the option of installing support for one or more languages. After installation, you can change the DB2 interface language to one of the other installed interface languages. Do not confuse languages supported by a DB2 product with languages supported by the DB2 interface. Languages supported by a DB2 product means the languages in which data can exist. These languages are a superset of languages supported by the DB2 interface. The DB2 interface language you want to use must be installed on your system. The DB2 product interface languages are selected and installed when you install a DB2 product using the DB2 Setup wizard. If you change the interface language of a DB2 product to a supported interface language that has not been installed, the DB2 product interface language will default to the operating system language first, and if that is not supported, English. Changing the interface language for a DB2 product on Windows requires that you change the default language setting for your Windows operating system. To change the DB2 product interface language on Windows operating systems: 1. Through the Control Panel, select Regional and Language Options. 2. On the Regional Options tab under Standards and formats, select the appropriate language. On Windows 2008 and Windows Vista or higher, use the Formats tab for this step. 3. On the Regional Options tab under Location, select the location that corresponds to the appropriate language. 4. On the Advanced tab under Language for non-Unicode programs select the appropriate language. On Windows 2008 and Windows Vista or higher, on the Administrative tab, under Language for non-unicode programs, click Change system locale and select the appropriate language. You will then be asked to reboot, click Cancel. 5. On the Advanced tab under Default user account settings, check the Apply all settings to the current user account and to the default user profile box. On Windows 2008 and Windows Vista or higher, on the Administrative tab under reserved accounts, click Copy to reserved accounts and check the accounts that you want to copy the language settings to. 6. You will be asked to reboot before these changes come into effect. Refer to your operating system help for additional information about changing the default system language. 2.1.3.4 Changing the DB2 interface language (Linux and UNIX) The interface language of the DB2 product is the language that appears in messages, help, and graphical tool interfaces. When installing your DB2 product, you have the option of installing support for one or more languages. If, at some time after installation, you want to change the interface language to one of the other installed interface languages, use the steps outlined in this task. Do not confuse languages supported by the DB2 product with languages supported by the DB2 interface. Languages supported by the DB2 product, that is, languages that data can exist in, are a superset of languages supported by the DB2 interface. Support for the DB2 interface language you want to use must be installed on your system. DB2 interface language support is selected and installed when you install DB2 using the DB2 Setup wizard. If you change the interface language of the DB2 product to a supported interface language that has not been installed, the DB2 interface language will default to the operating system language. If the operating system language is not supported, English is used as the DB2 interface language. DB2 interface language support is selected and installed when you install your DB2 product using the DB2 Setup wizard or by using the National Language Package. To check which public locales are available in your system, run the $ locale -a command. To change the DB2 interface language, set the LANG environment variable to the locale you want. For bourne (sh), korn (ksh), and bash shells: LANG= export LANG For C shell: setenv LANG For example, to interface with the DB2 product in French, you must have the French language support installed and you must set the LANG environment variable to a French locale, for example, fr_FR. 2.2 Installation requirements for DB2 database products Before you install your DB2 product, ensure that the system you choose meets the necessary operating system, hardware, software, communications, disk and memory requirements. 2.2.1, "Disk and memory requirements" The disk space required for your product depends on the type of installation you choose and the type of file system you have. Likewise, memory requirements are affected by the size and complexity of your database system. DB2 database and IBM data server client products There is a list of operating system, software, and hardware prerequisites that must be met for each operating system, as follows: * 2.2.4, "Installation requirements for DB2 servers and IBM data server clients (AIX)" * 2.2.5, "Installation requirements for DB2 servers and IBM data server clients (HP-UX)" * 2.2.6, "Installation requirements for DB2 servers and IBM data server clients (Linux)" * 2.2.7, "Installation requirements for DB2 servers and IBM data server clients (Solaris)" * 2.2.3, "Installation requirements for DB2 servers and IBM data server clients (Windows)" Installation requirements for DB2® Connect(TM) products There is a list of operating system, software, and hardware prerequisites that must be met for each operating system, as follows: * "Installation requirements for DB2 Connect Personal Edition (Windows)" in Installing and Configuring DB2 Connect Personal Edition * "Installation requirements for DB2 Connect Personal Edition (Linux)" in Installing and Configuring DB2 Connect Personal Edition * "Installation requirements for DB2 Connect products (Solaris Operating System)" in Installing and Configuring DB2 Connect Servers * "Installation requirements for DB2 Connect server products (Windows)" in Installing and Configuring DB2 Connect Servers * "Installation requirements for DB2 Connect server products (Linux)" in Installing and Configuring DB2 Connect Servers * "Installation requirements for DB2 Connect server products (AIX®)" in Installing and Configuring DB2 Connect Servers * "Installation requirements for DB2 Connect server products (HP-UX)" in Installing and Configuring DB2 Connect Servers 2.2.2, "Java software support for DB2 products" You require the appropriate level of IBM Software Development Kit (SDK) for Java(TM) to use Java-based tools and to create and run Java applications, including stored procedures and user-defined functions. Virtualization support For details about virtualization technology supported by DB2 products, see http://www.ibm.com/developerworks/wikis/display/im/DB2+Virtualization+Support. Installation requirements for DB2 Query Patroller products * "Installing Query Patroller server using the DB2 Setup wizard ( Windows )" in Query Patroller Administration and User's Guide * "Installing Query Patroller server using the DB2 Setup wizard ( Linux and UNIX )" in Query Patroller Administration and User's Guide Installation requirements for DB2 Spatial Extender * "System requirements for installing Spatial Extender" in Spatial Extender and Geodetic Data Management Feature User's Guide and Reference Installation requirements for InfoSphere(TM) Federation Server products * http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.swg.im.iis.prod.install.core.doc/topics/iiypisrq-sys.html * http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.swg.im.iis.prod.install.core.doc/topics/iiypirrq-sys.html 2.2.1 Disk and memory requirements Disk requirements The disk space required for your product depends on the type of installation you choose and the type of file system you have. The DB2 Setup wizard provides dynamic size estimates based on the components selected during a typical, compact, or custom installation. Remember to include disk space for required databases, software and communication products. On Linux and UNIX operating systems, 2 GB of free space in the /tmp directory is recommended. Memory requirements At a minimum, a DB2 database system requires 256 MB of RAM. For a system running just a DB2 product and the DB2 GUI tools, a minimum of 512 MB of RAM is required. However, 1 GB of RAM is recommended for improved performance. These requirements do not include any additional memory requirements for other software that is running on your system. When determining memory requirements, be aware of the following: * DB2 products that run on HP-UX Version 11i for Itanium-based systems require 512 MB of RAM at a minimum. * For IBM data server client support, these memory requirements are for a base of five concurrent client connections. You will need an additional 16 MB of RAM per five client connections. * Memory requirements are affected by the size and complexity of your database system, and the extent of database activity and the number of clients accessing your system. For DB2 server products, the self-tuning memory feature simplifies the task of memory configuration by automatically setting values for several memory configuration parameters. When enabled, the memory tuner dynamically distributes available memory resources among several memory consumers including sort, the package cache, the lock list and buffer pools. * On Linux and UNIX operating systems, SWAP space at least twice as large as RAM is recommended. 2.2.2 Java software support for DB2 products You require the appropriate level of IBM Software Development Kit (SDK) for Java, listed later in this section, to use Java-based tools and to create and run Java applications, including stored procedures and user-defined functions. If the IBM SDK for Java is required by a component being installed and the SDK for Java is not already installed in that path, the SDK for Java will be installed if you use either the DB2 Setup wizard or a response file to install the product. The SDK for Java is not installed with IBM Data Server Runtime Client or IBM Data Server Driver Package. The following table lists the installed SDK for Java levels for DB2 products according to operating system platform: +-----------------------+---------------------------------------------+ | Operating System | SDK for Java level | | Platform | | +-----------------------+---------------------------------------------+ | AIX | SDK 6 Service Release 3 | +-----------------------+---------------------------------------------+ | HP-UX for | HP SDK for J2SE HP-UX 11i platform, adapted | | Itanium-based systems | by IBM for IBM Software, Version 6 Service | | | Release 3 | +-----------------------+---------------------------------------------+ | Linux on x86 | SDK 6 Service Release 3 | +-----------------------+---------------------------------------------+ | Linux on AMD64/EM64T | SDK 6 Service Release 3 | +-----------------------+---------------------------------------------+ | Linux on zSeries® | SDK 6 Service Release 3 | +-----------------------+---------------------------------------------+ | Linux on POWER(TM) | SDK 6 Service Release 3 | +-----------------------+---------------------------------------------+ | Solaris Operating | SDK 6 Service Release 3 | | System | | +-----------------------+---------------------------------------------+ | Windows x86 | SDK 6 Service Release 3 | +-----------------------+---------------------------------------------+ | Windows x64 | SDK 6 Service Release 3 | +-----------------------+---------------------------------------------+ Note: 1. The SDK for Java software can be downloaded from the developerWorks® Web page at: http://www.ibm.com/developerworks/java/jdk/index.html . For a list of the supported levels of the SDK for Java, see the table later in this section entitled DB2 Database for Linux, UNIX, and Windows support for SDKs for Java. Note: For Windows operating system platforms, use the IBM Development Package for Eclipse downloads. 2. DB2 GUI tools only run on Linux on x86, Linux on AMD64/EM64T, Windows x86, and Windows x64. 3. On Windows x86 and Linux on x86: * the 32-bit SDK is installed * 32-bit applications and Java external routines are supported 4. On all supported platforms (except Windows x86, and Linux on x86): * 32-bit applications are supported * 32-bit Java external routines are not supported * 64-bit applications and Java external routines are supported Supported Java application development software The following table lists the supported levels of the SDK for Java. The listed levels and forward-compatible later versions of the same levels are supported. Because there are frequent SDK for Java fixes and updates, not all levels and versions have been tested. If your database application has problems that are related to the SDK for Java, try the next available version of your SDK for Java at the given level. Non-IBM versions of the SDK for Java are supported only for building and running stand-alone Java applications. For building and running Java stored procedures and user-defined functions, only the IBM SDK for Java that is included with the DB2 Database for Linux, UNIX, and Windows product is supported. Table 3. DB2 Database for Linux, UNIX, and Windows supported levels of SDKs for Java +-------------+-------------+-------------+-------------+-------------+ | Java Java Java Stored DB2 | | application application Procedures Graphical | | s using s using and User Tools | | JDBC driver JDBC driver Defined | | db2java.zip db2jcc4.jar Functions | | or | | db2jcc.jar | +-------------+-------------+-------------+-------------+-------------+ | AIX 1.4.2 to 6 6 1.4.2 to 65 N/A | +-------------+-------------+-------------+-------------+-------------+ | HP-UX for 1.4.2 to 61 61 1.4.2 to 6 N/A | | Itanium-bas | | ed systems | +-------------+-------------+-------------+-------------+-------------+ | Linux on 1.4.2 to 63,4 1.4.2 to 6 N/A | | POWER 63,4 | +-------------+-------------+-------------+-------------+-------------+ | Linux on 1.4.2 to 62,3,4 1.4.2 to 6 5 to 6 | | x86 62,3,4 | +-------------+-------------+-------------+-------------+-------------+ | Linux on 1.4.2 to 62,3,4 1.4.2 to 6 N/A | | AMD64 and 62,3,4 | | Intel® | | EM64T | | processors | +-------------+-------------+-------------+-------------+-------------+ | Linux on 1.4.2 to 63,4 1.4.2 to 6 N/A | | zSeries 63,4 | +-------------+-------------+-------------+-------------+-------------+ | Solaris 1.4.2 to 62 62 1.4.2 to 6 N/A | | operating | | system | +-------------+-------------+-------------+-------------+-------------+ | Windows on 1.4.2 to 62 62 1.4.2 to 6 5 to 6 | | x86 | +-------------+-------------+-------------+-------------+-------------+ | Windows on 1.4.2 to 62 62 1.4.2 to 6 5 to 6 | | x64, for | | AMD64 and | | Intel EM64T | | processors | +-------------+-------------+-------------+-------------+-------------+ Note: 1. The same levels of the SDK for Java that are available from Hewlett-Packard are supported for building and running stand-alone client applications that run under the IBM Data Server Driver for JDBC and SQLJ. 2. The same levels of the SDK for Java that are available from Sun Microsystems are supported for building and running stand-alone client applications that run under the IBM Data Server Driver for JDBC and SQLJ. 3. A minimum level of SDK for Java 1.4.2 SR6 is required for SUSE Linux Enterprise Server (SLES) 10. A minimum level of SDK for Java 1.4.2 SR7 is required for Red Hat Enterprise Linux (RHEL) 5. 4. SDK for Java 6 support on Linux requires SDK for Java 6 SR3 or later. 5. If SDK for Java 6 SR2 or later is used, set DB2LIBPATH=java_home/jre/lib/ppc64. The following table lists the versions of the IBM Data Server Driver for JDBC and SQLJ that are available with DB2 database products. Table 4. Versions of IBM Data Server Driver for JDBC and SQLJ and DB2 Database for Linux, UNIX, and Windows fix pack levels +----------------------------------+----------------------------------+ | DB2 version and fix pack level IBM Data Server Driver for JDBC | | and SQLJ version1 | +----------------------------------+----------------------------------+ | DB2 Version 9.1 3.1.xx | +----------------------------------+----------------------------------+ | DB2 Version 9.1 Fix Pack 1 3.2.xx | +----------------------------------+----------------------------------+ | DB2 Version 9.1 Fix Pack 2 3.3.xx | +----------------------------------+----------------------------------+ | DB2 Version 9.1 Fix Pack 3 3.4.xx | +----------------------------------+----------------------------------+ | DB2 Version 9.1 Fix Pack 4 3.6.xx | +----------------------------------+----------------------------------+ | DB2 Version 9.1 Fix Pack 5 3.7.xx | +----------------------------------+----------------------------------+ | DB2 Version 9.5 3.50.xx, 4.0.xx | +----------------------------------+----------------------------------+ | DB2 Version 9.5 Fix Pack 1 3.51.xx, 4.1.xx | +----------------------------------+----------------------------------+ | DB2 Version 9.5 Fix Pack 2 3.52.xx, 4.2.xx | +----------------------------------+----------------------------------+ | DB2 Version 9.5 Fix Pack 3 3.53.xx, 4.3.xx | +----------------------------------+----------------------------------+ | DB2 Version 9.7 3.57.xx, 4.7.xx | +----------------------------------+----------------------------------+ Note: All driver versions are of the form n.m.xx. n.m stays the same within a GA level or a fix pack level. xx changes when a new version of the IBM Data Server Driver for JDBC and SQLJ is introduced through an APAR fix. 2.2.3 Installation requirements for DB2 servers and IBM data server clients (Windows) Before you install a DB2 database product on Windows operating systems, ensure that the system you choose meets the necessary operating system, hardware, and software requirements. Table 5. Windows workstation platforms +-------------------------+-----------------+-------------------------+ | Operating System | Prerequisites | Hardware | +-------------------------+-----------------+-------------------------+ | Windows XP Professional | Windows XP | All Intel and AMD | | (32-bit and 64-bit) | Service Pack 2 | processors capable of | | Windows Vista Business | or later | running the supported | | (32-bit and 64-bit) | IBM Data Server | Windows operating | | | Provider for | systems (32-bit and x64 | | Windows Vista | .NET client | based systems) | | Enterprise (32-bit and | applications | | | 64-bit) | and CLR | | | | server-side | | | Windows Vista Ultimate | procedures | | | (32-bit and 64-bit) | require .NET | | | | 2.0 framework | | | | runtime. | | | | | | | | 64-bit IBM data | | | | server provider | | | | for .NET | | | | applications | | | | are supported. | | | | | | | | All Windows | | | | Vista service | | | | packs are | | | | supported. | | +-------------------------+-----------------+-------------------------+ Table 6. Windows server platforms +-------------------------+-------------------------+-----------------+ | Operating System | Prerequisites | Hardware | +-------------------------+-------------------------+-----------------+ | Windows 2003 Datacenter | Service Pack 2 or | All Intel and | | Edition (32-bit and | later. | AMD processors | | 64-bit) | R2 is also supported | capable of | | Windows 2003 Enterprise | | running the | | Edition (32-bit and | IBM data server | supported | | 64-bit) | provider for .NET | Windows | | | client applications and | operating | | Windows 2003 Standard | CLR server-side | systems (32-bit | | Edition (32-bit and | procedures require .NET | and x64 based | | 64-bit) | 2.0 framework runtime. | systems). | | | | | | | 64-bit IBM data server | | | | provider for .NET | | | | applications are | | | | supported. | | |-------------------------|-------------------------| | | Windows Server 2008 | IBM data server | | | Datacenter Edition | provider for .NET | | | (32-bit and 64-bit) | client applications and | | | Windows Server 2008 | CLR server-side | | | Enterprise Edition | procedures require .NET | | | (32-bit and 64-bit) | 2.0 framework runtime. | | | | | | | Windows Server 2008 | 64-bit IBM data server | | | Standard Edition | provider for .NET | | | (32-bit and 64-bit) | applications are | | | | supported. | | | | | | | | All Windows Server 2008 | | | | service packs are | | | | supported. | | +-------------------------+-------------------------+-----------------+ Note: DB2 database products support the hardware-enforced Data Execution Prevention (DEP) feature that is built into some Windows operating systems. Additional software considerations * Windows Installer 3.0 is required. It will be installed by the installer if is it not detected. * IBM Data Server Provider for .NET client applications and CLR server-side procedures require .NET 2.0 framework runtime. In an x64 environment, 32-bit IBM data server provider for .NET applications will run in the WOW64 emulation mode. * MDAC 2.8 is required. The DB2 Setup wizard will install MDAC 2.8 if it is not already installed. Note: If a previous version of MDAC (for example, 2.7) is already installed, DB2 install will upgrade MDAC to 2.8. For a typical install, MDAC 2.8 is installed. For a custom install, MDAC 2.8 is installed but only if you have not deselected the default which is to install it. If you deselect MDAC as part of a custom install, it will not be installed. * If you plan to use LDAP (Lightweight Directory Access Protocol), you should use either a Microsoft® LDAP client or the IBM Tivoli® Directory Server v6 client (also known as the IBM LDAP client which is included with DB2 database products). Before installation of the Microsoft Active Directory, you will need to extend your directory schema using the db2schex utility, which can be found on the installation media under the db2\Windows\utilities directory. The Microsoft LDAP client is included with Windows operating systems. * One of the following browsers is required to view online help, run the DB2 install launchpad (setup.exe), and to run First Steps (db2fs): * Firefox 2.0 and later * Internet Explorer 6.0 and later * Mozilla-based browsers 1.7 and later * Safari 3.0 and later 2.2.4 Installation requirements for DB2 servers and IBM data server clients (AIX) Before you install DB2 database products on AIX operating systems, ensure that the system you choose meets the necessary operating system, hardware, software, and communications requirements. To install a DB2 database product, the following requirements must be met: Table 7. AIX installation requirements +----------------------------------+----------------------------------+ | Operating System | Hardware | +----------------------------------+----------------------------------+ | AIX Version 5.3 | 64-bit Common Hardware Reference | | * 64-bit AIX kernel is required | Platform (CHRP) architecture1 | | * AIX 5.3 Technology Level (TL) | | | 9and Service Pack (SP(TM)) 2 | All processors that are capable | | * Minimum C++ runtime level | of running the supported AIX | | requires the xlC.rte 9.0.0.8 and | operating systems. | | xlC.aix50.rte 9.0.0.8 (or later) | | | filesets. These filesets are | | | included in the June 2008 IBM | | | C++ Runtime Environment | | | Components for AIX package. | | | | | | AIX Version 6.12 | | | * 64-bit AIX kernel is required | | | * Minimum C++ runtime level | | | requires the xlC.rte 9.0.0.8 and | | | xlC.aix61.rte 9.0.0.8 (or later) | | | filesets. These filesets are | | | included in the June 2008 IBM | | | C++ Runtime Environment | | | Components for AIX package. | | +----------------------------------+----------------------------------+ * 1To verify that it is a CHRP architecture system, issue the command lscfg and look for the following output: Model Architecture: chrp * 2In AIX 6.1 there are two types of Workload Partitions (WPARs): system WPARs and application WPARs. DB2 installation is supported only on a system WPAR. AIX 6.1 also supports the ability to encrypt a JFS2 file system or set of files. Software considerations * For application development and runtime considerations, see the topics in Supported programming languages and compilers for database application development. * You can download the latest IBM C++ Runtime Environment Components for AIX at the IBM AIX XL C and C++ support Web site. * (Clients only) If you plan to use Kerberos Authentication, you require IBM Network Authentication Service client v1.4 or later. The NAS client can be downloaded from https://www6.software.ibm.com/dl/dm/dm-nas-p. * Use the bosboot command to switch to the 64-bit kernel. To switch to a 64-bit kernel, you require root authority and enter the following commands: ln -sf /usr/lib/boot/unix_64 /unix ln -sf /usr/lib/boot/unix_64 /usr/lib/boot/unix bosboot -a shutdown -Fr * One of the following browsers is required to view online help and to run First Steps (db2fs): * Firefox 2.0 and later * Mozilla-based browsers 1.7 and later * An X Window System software capable of rendering a graphical user interface is required if: * you want to use the DB2 Setup wizard to install a DB2 product on Linux or UNIX operating systems * For details regarding known AIX issues, see www.ibm.com/support/docview.wss?&uid=swg21165448 2.2.5 Installation requirements for DB2 servers and IBM data server clients (HP-UX) To install a DB2 product, the following operating system, hardware, and communications requirements must be met: Table 8. HP-UX installation requirements +-----------------------------------------+---------------------------+ | Operating System | Hardware | +-----------------------------------------+---------------------------+ | | Itanium® based HP | | DB2 products are supported on: | Integrity Series Systems | | * HP-UX 11iv2 (11.23.0505) with: | | | * May 2005 Base Quality (QPKBASE) | | | bundle | | | * May 2005 Applications Quality | | | (QPKAPPS) bundle | | | * HP-UX 11iv3 (11.31) | | +-----------------------------------------+---------------------------+ Kernel configuration considerations A system restart is required if you update the kernel configuration parameters. The kernel configuration parameters are set in /etc/system. Depending on the values of your kernel configuration parameters, modify some of them before you install the Version 9 client or DB2 server products. If the kernel parameter being modified is not listed as dynamic, a system reboot is required to make the changes to /etc/system take effect. Software considerations * One of the following browsers is required to view online help and to run First Steps (db2fs): * Firefox 2.0 and later * Mozilla-based browsers 1.7 and later * An X Window System software capable of rendering a graphical user interface is required if: * you want to use the DB2 Setup wizard to install a DB2 product on Linux or UNIX operating systems * For details regarding known HP-UX issues, see www.ibm.com/support/docview.wss?&uid=swg21257602 2.2.6 Installation requirements for DB2 servers and IBM data server clients (Linux) Before you install DB2 database products on Linux operating systems, ensure that the system you choose meets the necessary operating system, hardware, software, and communications requirements. For the latest information about supported Linux distributions, point your browser to http://www.ibm.com/software/data/db2/linux/validate/. DB2 database products are supported on the following hardware: * x86 (Intel Pentium®, Intel Xeon®, and AMD) 32-bit Intel and AMD processors * x64 (64-bit AMD64 and Intel EM64T processors) * POWER (IBM eServer(TM) OpenPower®, iSeries®, pSeries®, System i®, System p®, and POWER Systems that support Linux) * eServer System z® or System z9® The supported operating systems for Linux include: * Red Hat Enterprise Linux (RHEL) 5 Update 2 * SUSE Linux Enterprise Server (SLES) 10 Service Pack 2 * SUSE Linux Enterprise Server (SLES) 11 * Ubuntu 8.0.4.1 Multithreaded architecture limitations If you are installing a DB2 32-bit database product on a Linux operating system, consider upgrading to a 64-bit operating system and installing the DB2 64-bit database product instead. The multithreaded architecture generally simplifies memory configuration. However, this could affect the memory configuration of 32-bit DB2 database servers. For example: * Private memory for agent threads is allocated within a single process. The aggregate of all private memory allocations for database agents might not fit in a single process memory space. * Support for multiple databases is limited because all database shared memory segments for all databases are allocated in a single process. You might need to reduce the memory usage for some databases in order to activate all databases successfully at the same time. However, the database manager performance might be impacted. Another alternative is to create multiple instances and catalog the databases across the instances. However, sufficient system resources is required to support this configuration. Distribution Requirements You should update your kernel configuration parameters before installing a DB2 database product. The default values for particular kernel parameters might not be sufficient when running a DB2 database system. You might also have other products or applications that require Linux system resources. You should modify the kernel configuration parameters based on the needs of your Linux system working environment. The kernel configuration parameters are set in /etc/sysctl.conf. Refer to your operating system manual for information about setting and activating these parameters using the sysctl command. Package requirements The following tables list the package requirements for SLES and RHEL distributions: * libaio.so.1 is required for DB2 database servers using asynchronous i/o. * libstdc++so.6 is required for DB2 database servers and clients. However, if IBM Tivoli System Automation for Multiplatforms, or, IBM Tivoli Monitoring for Databases: DB2 Agent is used, libstdc++so.5 is needed. Package requirements for SLES and RHEL +------------------+--------------------------------------------------+ | Package name | Description | +------------------+--------------------------------------------------+ | libaio | Contains the asynchronous library required for | | | DB2 database servers. | +------------------+--------------------------------------------------+ | compat-libstdc++ | Contains libstdc++so.6 (not required for Linux | | | on POWER) | +------------------+--------------------------------------------------+ The following tables list the package requirements for SUSE Linux and Red Hat distributions for DB2 partitioned database servers. * The ksh93 Korn shell is required for SUSE10 and RHEL5 systems. The pdksh Korn Shell package is required for all other DB2 database systems. * A remote shell utility is required for partitioned database systems. DB2 database systems support the following remote shell utilities: * rsh * ssh By default, DB2 database systems use rsh when executing commands on remote DB2 nodes, for example, when starting a remote DB2 database partition. To use the DB2 database system default, the rsh-server package must be installed (see table below). More information about rsh and ssh is available in the DB2 Information Center. If you choose to use the rsh remote shell utility, inetd (or xinetd) must be installed and running as well. If you choose to use the ssh remote shell utility, you need to set the DB2RSHCMD communication variable immediately after the DB2 installation is complete. If this registry variable is not set, rsh is used. * The nfs-utils Network File System support package is required for partitioned database systems. All required packages should be installed and configured before continuing with the DB2 database system setup. For general Linux information, see your Linux distribution documentation. Package requirements for SUSE Linux +------------------+--------------------------------------------------+ | Package name | Description | +------------------+--------------------------------------------------+ | pdksh or ksh93 | Korn Shell. This package is required for | | | partitioned database environments. | +------------------+--------------------------------------------------+ | openssh | This package contains a set of server programs | | | which allow users to run commands on (and from) | | | remote computers via a secure shell. This | | | package is not required if you use the default | | | configuration of DB2 database systems with rsh. | +------------------+--------------------------------------------------+ | rsh-server | This package contains a set of server programs | | | which allow users to run commands on remote | | | computers, login in to other computers, and copy | | | files between computers (rsh, rexec, rlogin, and | | | rcp). This package is not required if you | | | configure DB2 database systems to use ssh. | +------------------+--------------------------------------------------+ | nfs-utils | Network File System support package. It allows | | | access to local files from remote computers. | +------------------+--------------------------------------------------+ Package requirements for Red Hat +-----------------------+-------------+-------------------------------+ | Directory | Package | Description | | | name | | +-----------------------+-------------+-------------------------------+ | /System | pdksh or | Korn Shell. This package is | | Environment/Shell | ksh93 | required for partitioned | | | | database environments. | +-----------------------+-------------+-------------------------------+ | /Applications/Interne | openssh | This package contains a set | | t | | of client programs which | | | | allow users to run commands | | | | on a remote computer via a | | | | secure shell. This package is | | | | not required if you use the | | | | default configuration of DB2 | | | | database systems with rsh. | +-----------------------+-------------+-------------------------------+ | /System | openssh-ser | This package contains a set | | Environment/Daemons | ver | of server programs which | | | | allow users to run commands | | | | from a remote computer via a | | | | secure shell. This package is | | | | not required if you use the | | | | default configuration of DB2 | | | | database systems with rsh. | +-----------------------+-------------+-------------------------------+ | /System | rsh-server | This package contains a set | | Environment/Daemons | | of programs which allow users | | | | to run commands on a remote | | | | computer. Required for | | | | partitioned database | | | | environments. This package is | | | | not required if you configure | | | | DB2 database systems to use | | | | ssh. | +-----------------------+-------------+-------------------------------+ | /System | nfs-utils | Network File System support | | Environment/Daemons | | package. It allows access to | | | | local files from remote | | | | computers. | +-----------------------+-------------+-------------------------------+ Software considerations * (Clients only) If you plan to use Kerberos Authentication, you require IBM Network Authentication Service client v1.4 or later. The NAS client can be downloaded from https://www6.software.ibm.com/dl/dm/dm-nas-p. * One of the following browsers is required to view online help and to run First Steps (db2fs): * Firefox 2.0 and later * Mozilla-based browsers 1.7 and later * An X Window System software capable of rendering a graphical user interface is required if: * you want to use the DB2 Setup wizard to install a DB2 database product on Linux or UNIX operating systems, or * you want to use any DB2 graphical tools on Linux for x86 and Linux on AMD 64/EM64T. * Micro Focus does not offer support for any of its COBOL compiler products on SLES 11. Security-enhanced Linux considerations On RHEL 5 systems, if Security-enhanced Linux (SELinux) is enabled and in enforcing mode, the installer might fail due to SELinux restrictions. To determine if SELinux is installed and in enforcing mode, you can do one of the following: * check the /etc/sysconfig/selinux file * run the sestatus command * check the /var/log/messages file for SELinux notices. To disable SELinux, you can do one of the following: * set it in permissive mode and run the setenforce 0 command as a superuser * modify /etc/sysconfig/selinux and reboot the machine. If your DB2 database product installs successfully on a RHEL 5 system, DB2 processes will run in the unconfined domain. To assign DB2 processes to their own domains, modify the policy. A sample SELinux policy is provided in the sqllib/samples directory. 2.2.7 Installation requirements for DB2 servers and IBM data server clients (Solaris) Before you install a DB2 database product on Solaris, ensure that your system meets the operating system, hardware and software requirements. Table 9. Solaris installation requirements +-----------------------------------------+---------------------------+ | Operating System | Hardware | +-----------------------------------------+---------------------------+ | Solaris 9 | UltraSPARC or SPARC64 | | * 64- bit kernel | processors | | * Patches 111711-12 and 111712-12 | | | * If raw devices are used, patch | | | 122300-11 | | | * 64-bit Fujitsu PRIMEPOWER and | | | Solaris 9 Kernel Update Patch 112233-01 | | | or later to get the fix for patch | | | 912041-01 | | | Solaris 10 Update 5 | | | * 64- bit kernel | | | * If raw devices are used, patch | | | 125100-07 | | +-----------------------------------------+---------------------------+ | Solaris 10 Update 5 | Solaris x64 (Intel 64 or | | * 64- bit kernel | AMD64) | | * Patch 118855-33 | | | * If raw devices are used, patch | | | 125101-07 | | +-----------------------------------------+---------------------------+ Kernel configuration considerations The kernel configuration parameters are set in /etc/system. If the kernel parameter being modified is not listed as dynamic, a system reboot is required to make the changes to /etc/system take effect. These parameters must be set before you install an IBM data server client. Software considerations * (Clients only) If you plan to use Kerberos Authentication, you require Solaris 9 or higher with IBM Network Authentication Service (NAS) client v1.4 or later. The NAS client can be downloaded from Web site: www6.software.ibm.com/dl/dm/dm-nas-p. * One of the following browsers is required to view online help and to run First Steps (db2fs): * Firefox 2.0 and later * Mozilla-based browsers 1.7 and later * An X Window System software capable of rendering a graphical user interface is required if you want to use the DB2 Setup wizard to install a DB2 database product * For details regarding known Solaris issues, see www.ibm.com/support/docview.wss?&uid=swg21257606 Security patches can be obtained from the http://sunsolve.sun.com Web site. From the SunSolve Online Web site, click Patches in the left panel. The Java2 Standard Edition (J2SE) Solaris Operating System Patch Clusters and the SUNWlibC software are also required and can be obtained from the http://sunsolve.sun.com Web site. For DB2 database products on 64-bit Fujitsu PRIMEPOWER systems, you require the following: * Solaris 9 Kernel Update Patch 112233-01 or later to get the fix for patch 912041-01. The Fujitsu PRIMEPOWER patches for the Solaris Operating System can be downloaded from FTSI at: http://download.ftsi.fujitsu.com/. 2.2.8 Password rules When choosing a password, be aware that your password length can be up to the maximum number of characters supported by your operating system. Some operating systems might have more password rules, such as minimum length and simplicity, and some operating systems can be configured to use different password encryption algorithms. See the appropriate operating system documentation for more information. Note: To enable long password support on the AIX operating system, Version 6.1, or later, install APAR IZ35001 on the DB2 client and server machines. 2.3 Additional Windows requirements 2.3.1 DB2 services running on your system (Windows) The following table lists the DB2 services that run on your system when a DB2 product is installed: Table 10. DB2 Services +-------------------+------------------------+------------------------+ | Service Display | Service Name | Description | | Name | | | +-------------------+------------------------+------------------------+ | DB2 - (DB2 copy | <instance | Allows applications to | | name) - <instance | name>[<-nodenum>] | create, update, | | name> | | control, and manage | | [<-nodenum>] | | DB2 databases. | | where <-nodenum> | | | | is added for DB2 | | | | ESE instances. | | | +-------------------+------------------------+------------------------+ | DB2 Governor (DB2 | DB2GOVERNOR | Collects statistics | | copy name) | _db2copyname | for applications | | | | connected to DB2 | | | | databases. | +-------------------+------------------------+------------------------+ | DB2 Information | DB2ICSERVER_Vxx (where | Provides documentation | | Center Server | xx is the DB2 version | for DB2 products. | | | you are running, for | | | | example, V95 is | | | | Version 9.5) | | +-------------------+------------------------+------------------------+ | DB2 License | DB2LICD _db2copyname | Monitors DB2 license | | Server (DB2 copy | | compliance. | | name) | | | +-------------------+------------------------+------------------------+ | DB2 Management | DB2MGMTSVC | Manages DB2 registry | | Service (DB2 copy | _db2copyname | entries for backward | | name) | | compatibility purposes | | | | for the DB2 copy. | +-------------------+------------------------+------------------------+ | DB2 Query | DB2QP _db2copyname | DB2 Query Patroller | | Patroller (DB2 | | | | copy name) | | | +-------------------+------------------------+------------------------+ | DB2 Remote | | Supports remote DB2 | | Command Server | DB2REMOTECMD | command execution. | | (DB2 copy name) | _db2copyname | | +-------------------+------------------------+------------------------+ | DB2DAS - DB2DASXX | DB2DASXX (where XX is | Supports local and | | | 00-99) | remote database | | | | administrative | | | | requests. | +-------------------+------------------------+------------------------+ | Monitoring Agent | kudcma_<instance name> | Monitors the DB2 | | for DB2 - | | server and database | | <instance | | for availability. | | name> | | | +-------------------+------------------------+------------------------+ 2.3.2 Required user accounts for installation of DB2 server products (Windows) If you are installing a DB2 server product on Windows, you require the following user accounts: * An installation user account and * Optional - one or more setup user accounts. You can create these accounts during the installation. * A DB2 Administration Server (DAS) user account * A DB2 instance user account. You can also use the LocalSystem account for products other than DB2 Enterprise Server Edition. The installation user account is the account of the user performing the installation. The installation user account must be defined before running the DB2 Setup wizard. The setup user accounts can be defined before installation or you can have the DB2 Setup wizard create them for you. All user account names must adhere to your system naming rules and to DB2 User, user ID and group naming rules. Extended security on Windows DB2 products offer extended Windows security. If the extended security feature is selected, you must add the users who will administer or use the DB2 product to either the DB2ADMNS or DB2USERS group as appropriate. The DB2 installer creates these two new groups. You can either specify a new name or accept the default names during installation. To enable this security feature, select the Enable operating system security check box on the Enable operating system security for DB2 objects panel during the DB2 installation. Accept the default values for the DB2 Administrators Group field, and the DB2 Users Group field. The default group names are DB2ADMNS and DB2USERS. If there is a conflict with existing group names, you will be prompted to change the group names. If required, you can specify your own values. DB2 server user accounts Installation user account A local or domain user account is required to perform the installation. Normally, the user account must belong to the Administrators group on the computer where you will perform the installation. Alternatively, a non-Administrator user account can be used. This alternative requires that a member of the Windows Administrators group first configure the Windows elevated privileges settings to allow a non-Administrator user account to perform an installation. On Windows 2008 and Windows Vista or higher, a non-administrator can perform an installation, but will be prompted for administrative credentials by the DB2 Setup wizard. The user right "Access this computer from the network" is required for the installation user account. The installation user ID must belong to the Domain Administrators group on the domain if the installation requires a domain account to be created or verified. You may also use the built-in LocalSystem account as your Service Logon account for all products, except DB2 Enterprise Server Edition User rights granted by the DB2 installer The DB2 installation program does not grant the Debug Programs user right. The DB2 installer grants the following user rights: * Act as part of the operating system * Create token object * Lock pages in memory * Log on as a service * Increase quotas * Replace a process level token DB2 Administration Server (DAS) user account A local or domain user account is required for the DB2 Administration Server (DAS). If you are performing a response file installation, you can also specify the Local System account in the response file. For more details, refer to the sample response files in the db2\windows\samples directory. The LocalSystem account is available for all products, except DB2 Enterprise Server Edition and can be selected through the DB2 Setup wizard. The DAS is a special DB2 administration service used to support the GUI tools and assist with administration tasks on local and remote DB2 servers. The DAS has an assigned user account that is used to log the DAS service on to the computer when the DAS service is started. You can create the DAS user account before installing DB2 or you can have the DB2 Setup wizard create it for you. If you want to have the DB2 Setup wizard create a new domain user account, the user account you use to perform the installation must have authority to create domain user accounts. The user account must belong to the Administrators group on the computer where you will perform the installation. This account will be granted the following user rights: * Act as part of the operating system * Debug programs * Create token object * Lock pages in memory * Log on as a service * Increase quotas (adjust memory quotas for a process on Windows XP and Windows Server 2003 operating systems) * Replace a process level token If extended security is enabled, the DB2ADMNS group will have all these privileges. You can add users to that group and you do not need to add these privileges explicitly. However, the user still needs to be a member of the Local Administrators group. The "Debug programs" privilege is only needed when DB2 group lookup is explicitly specified to use the access token. If the user account is created by the install program, the user account will be granted these privileges and if the user account already exists, this account will also be granted these privileges. If the install grants the privileges, some of them will only be effective on first log on by the account that was granted the privileges or upon reboot. It is recommended that the DAS user have SYSADM authority on each of the DB2 systems within your environment so that it can start or stop other instances if required. By default, any user that is part of the Administrators group has SYSADM authority. DB2 instance user account The user account must belong to the Administrators group on the computer where you will perform the installation. A local or domain user account is required for the DB2 instance. Every DB2 instance has one user that is assigned when the instance is created. DB2 logs on with this user name when the instance is started. An error will occur if you use a domain user account to perform a database operation (such as, creating a database) against a DB2 instance created with either a Local user account or the LocalSystem account. If you know you will be using a domain user account, you should create the instance using a domain user account. You may also use the built-in LocalSystem account to run the installation for all products, except for DB2 Enterprise Server Edition. You can create the DB2 instance user account before installing DB2 or you can have the DB2 Setup wizard create it for you. If you want to have the DB2 Setup wizard create a new domain user account, the user account you use to perform the installation must have authority to create domain user accounts. This account will be granted the following user rights: * Act as part of the operating system * Debug programs * Create token object * Increase quotas * Lock pages in memory * Log on as a service * Replace a process level token If extended security is enabled, then the DB2ADMNS group will have all these privileges. You can add users to that group and you do not need to add these privileges explicitly. However, the user still needs to be a member of the Local Administrators group. The "Debug programs" privilege is only needed when DB2 group lookup is explicitly specified to use the access token. If the user account is created by the install program, the user account will be granted these privileges and if the user account already exists, this account will also be granted these privileges. If the install grants the privileges, some of them will only be effective on first log on by the account that was granted the privileges or upon reboot. 2.3.3 Setting up Windows elevated privileges before installing a DB2 product (Windows) The usual method to install a DB2 product on Windows is to use an Administrator user account. However, DB2 products can be installed using a non-administrator account. To do so, a Windows Administrator must configure the elevated privileges feature in Windows. This task explains how a Windows Administrator can set up a computer with elevated privileges to allow installation using a non-Administrator user account. The related task of granting DB2 administration authorities to non-Administrator users is also covered. Typically a Windows Administrator would perform this task to enable another person who does not have an Administrator account to install a DB2 product. The role of this person might be only to install DB2 products or to also administer DB2 products once installed. Before initiating this procedure, note the following restrictions on non-Administrator installation using elevated privileges: * Non-Administrator users can only install fix packs, add-on products, or upgrade DB2 products if prior installations or upgrades were also performed by the same non-Administrator user. * Non-Administrator users cannot uninstall a DB2 product. Those non-Administrator users on a Windows Vista (and later) operating system can uninstall a DB2 product. This procedure uses the Windows Group Policy Editor. 1. Click Start -> Run and type gpedit.msc. The Group Policy window opens. 2. Click on Computer Configuration -> Administrative Templates -> Windows Components -> Windows Installer. 3. Enable the following Group Policy settings: * Always install with elevated privileges (mandatory) * Enable user control over installs (mandatory) * Disable Windows Installer. Then set it to Never. * Enable user to patch elevated products (optional) * Enable user to use media source while elevated (optional) * Enable user to browse for source while elevated (optional for new installations, mandatory for fix pack upgrades) 4. Enable elevated privileges for the user account that will be performing the installation. a. Click User Configuration -> Administrative Templates -> Windows Components -> Windows Installer. b. Enable the Always install with elevated privileges (mandatory) Group Policy setting. 5. Perform setup related to the user account that will install the DB2 product. * Identify the user account that will install the DB2 product. If necessary, create that account. * Give that account write permission for the drive on which an installation is planned. 6. Optional: Complete additional steps applicable to installing fix packs: * Provide read access to the sqllib\cfg directory. * Ensure that allowlockdownpatch is enabled (as described in the Windows Installer SDK documentation) because fix pack installations are considered minor upgrades to the product. 7. Refresh the computer's security policy in any one of the following ways: * Reboot the PC. * At the command line, enter gpupdate.exe. By following this procedure you will have set up the computer with elevated privileges and set up a user account that will be able to install DB2 server products, clients and fix packs. After DB2 installation is complete: * Any user in the system administrative (SYSADM) or system control (SYSCTRL) authority group defined in the database manager configuration for the instance can create and use DB2 databases within the DB2 instance. * Only a user with local Administrator authority can run DB2 instance utilities, such as db2icrt, db2idrop, db2iupdt, or db2iupgrade. * The authorization requirements for running the db2start or db2stop command is defined in the topics START DATABASE MANAGER command, and STOP DATABASE MANAGER command. Using regedit instead of the Windows Group Policy Editor An alternative to using the Windows Group Policy Editor is to use regedit. 1. In the registry branch HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows, add the key installer 2. Edit the key installer with the following values: * For AlwaysInstallElevated, enter REG_DWORD=1 * For AllowLockdownBrowse, enter REG_DWORD=1 * For AllowLockdownMedia, enter REG_DWORD=1 * For AllowLockdownPatch, enter REG_DWORD=1 * For DisableMSI, enter REG_DWORD=0 * For EnableUserControl, enter REG_DWORD=1 3. In the registry branch HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows, add the key installer 4. Edit the key installer with the following values: * For AlwaysInstallElevated, enter REG_DWORD=1 Removing elevated privileges After you have given elevated privileges, you can reverse this action. To do so, remove the registry key Installer under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows. Granting a non-administrator user DB2 administration authorities At this point, only members of the Windows Administrators group will have DB2 administration authorities. The Windows Administrator has the option to grant one or more DB2 authorities, such as SYSADM, SYSMAINT, or SYSCTRL to the non-Administrator user who installed the DB2 product. 2.3.4 Granting user rights (Windows) This topic describes the steps required to grant user rights on Windows operating systems. Specific user rights are recommended for user accounts required to install and set up DB2. To grant advanced user rights on Windows you must be logged on as a local Administrator. 1. Click Start -> Run and type secpol.msc. On Windows 2008 and Windows Vista (or higher), click Start and type secpol.msc in the search bar. Click OK. 2. Select Local Security Policy. 3. In the left window pane, expand the Local Policies object, then select User Rights Assignment. 4. In the right window pane, select the user right that you want to assign. 5. From the menu, select Action --> Security... 6. Click Add, then select a user or group to assign the right to, and click Add. 7. Click OK. If your computer belongs to a Windows domain, the domain user rights can override your local settings. In this case, your Network Administrator must make the changes to the user rights. 2.3.5 Extending the Active Directory Schema for LDAP directory services (Windows) If you plan to use the Lightweight Directory Access Protocol (LDAP) directory server feature with Windows Server 2003, you should extend the Active Directory schema to contain DB2 object classes and attribute definitions. You should perform this task before you install any DB2 products. Extending the directory schema ensures that: * The default DB2 instance, created during the installation, is cataloged as a DB2 node in Active Directory provided the installation user ID had sufficient privileges to write to Active Directory. * Any databases that the user creates after installation will automatically be cataloged into Active Directory. If you decide to install your DB2 product and create databases before you extend the directory schema, you must manually register the node and catalog the databases. Your Windows user account must have Schema Administration authority. To extend the directory schema: 1. Log onto the domain controller. 2. Run the db2schex.exe program from the installation DVD with a user account that has Schema Administration authority. You can run this program without logging off and logging on again, as follows: runas /user:MyDomain\Administrator x:\db2\Windows\utilities\db2schex.exe where x: represents the DVD drive letter. When db2schex.exe completes, you can proceed with the installation of your DB2 product. 2.3.6 Verifying port range availability on participating computers (Windows) This task describes the steps required to verify port range availability on participating computers. The port range is used by the Fast Communications Manager (FCM). FCM is a feature of DB2 that handles communications between database partition servers. When you install the instance-owning database partition server on the primary machine, DB2 reserves a port range according to the specified number of database partition servers participating in partitioned database environment. The default range is four ports. The DB2 Setup wizard must be able to reserve an identical port range when database partition servers are installed on participating computers; the port range needs to be free on each of the database partition servers. This task should be done after you install the instance-owning database partition server and before you install any participating database partition servers. To verify the port range availability on participating computers: 1. Open the services file. The default location of the services file is in the %SystemRoot%\system32\drivers\etc directory, where %SystemRoot% is your Windows root directory. 2. Locate the ports reserved for the DB2 Fast Communications Manager (FCM). The entries should appear similar to the following: DB2_DB2 60000/tcp DB2_DB2_1 60001/tcp DB2_DB2_2 60002/tcp DB2_DB2_END 60003/tcp DB2 reserves the first four available ports after 60000. 3. On each participating computer, open the services file and verify that the ports reserved for DB2 FCM in the services file of the primary computer are not being used. 4. In the event that the required ports are in use on a participating computer, identify an available port range for all computers and update each service file, including the services file on the primary computer. 2.4 Additional Linux and UNIX requirements 2.4.1 Multiple DB2 copies on the same computer (Linux and UNIX) DB2 products can be installed to an installation path of your choice. DB2 products can also be installed multiple times on a single machine. Each DB2 Copy can be at the same or different code levels. Root installations of DB2 products can be installed to an installation path of your choice. Unless specified otherwise, the default installation paths are: * for AIX, HP-UX or Solaris operating systems /opt/IBM/db2/V9.7 * for Linux operating systems /opt/ibm/db2/V9.7 If you are using the DB2 Setup wizard and choose to install a new DB2 copy when the default installation path is already in use, the default path becomes: * for AIX, HP-UX or Solaris /opt/IBM/db2/V9.7_## * for Linux /opt/ibm/db2/V9.7_## where ## is a zero-prefixed sequential number in the range 01 to 99. The first occurrence of modifying the default path is _01. For example, a DB2 product is installed using the DB2 Setup wizard without specifying an installation path, and, the default installation path /opt/ibm/db2/V9.7 is already in use, the DB2 product will be installed in the new default path /opt/ibm/db2/V9.7_01. If you install a DB2 copy using an installation method other than the DB2 Setup wizard, you must specify the installation path. Automatic sequential incrementation of the default path only occurs when the DB2 Setup wizard is used to install a DB2 copy. Regardless of the installation method, another full product cannot be installed in the path of another DB2 copy (such as /opt/ibm/db2/V9.7). A DB2 copy installed to a subdirectory of an existing DB2 copy is not supported because all copies are rendered unusable. With the ability to install multiple copies of DB2 products on your system and the flexibility to install DB2 products and features in the path of your choice, the db2ls command helps you keep track of what is installed and where it is installed. Run the db2ls command to locate DB2 products installed on your system. The following restrictions apply when installing multiple DB2 copies on one system: * Non-root installations do not support multiple DB2 copies * There can be only one DB2 Administration Server (DAS) on the system. * Instance names must be unique across DB2 copies. * A DB2 copy is not aware of any instances created in another DB2 copy. However, the db2iupdt command can switch ownership of an instance from one DB2 copy to another. * Creating links with the db2ln command for one DB2 copy renders the other copies nonfunctional. Links must not be created when multiple DB2 copies are intended to coexist. * Linux 32-bit images cannot be installed on Linux x64 operating system platforms. * The DB2 installation tools do not support multiple simultaneous invocations on the same machine by the same user. 2.4.2 DB2 users and groups (Linux and UNIX) The DB2 Setup wizard creates the users and groups automatically (if needed) during the installation of your DB2 product. Note: This topic does not apply to non-root installations. If you are using the DB2 Setup wizard, you can create the following users and groups during installation. To manually create the following users and groups, see 2.4.5, "Creating group and user IDs for a DB2 database installation (Linux and UNIX)". Three users and three groups are used to operate DB2 on Linux and UNIX platforms. Instance owner The DB2 instance is created in the instance owner home directory. This user ID controls all DB2 processes and owns all filesystems and devices used by the databases contained within the instance. The default user is db2inst1 and the default group is db2iadm1. When using the DB2 Setup wizard, the default action is to create a new user for your DB2 instance. The default name is db2inst1. If that user name already exists, the DB2 Setup wizard searches through user names (db2inst2, db2inst3, and so on). The search continues until a user name is identified that is not already an existing user on the system as the default instance owner ID. If you choose to proceed this user is created by the DB2 Setup wizard. However, you also have a choice to specify any existing user as the instance owner. This method for user name creation also applies to the creation of fenced users and DB2 administration server users. Fenced user The fenced user is used to run user defined functions (UDFs) and stored procedures outside of the address space used by the DB2 database. The default user is db2fenc1 and the default group is db2fadm1. If you do not need this level of security, for example in a test environment, you can use your instance owner as your fenced user. DB2 administration server user The user ID for the DB2 administration server user is used to run the DB2 administration server (DAS) on your system. The default user is dasusr1 and the default group is dasadm1. This user ID is also used by the DB2 GUI tools to perform administration tasks against the local server database instances and databases. There is only one DAS per computer. One DAS services one or more database instances, including database instances that belong to different installations. The DAS can service database instances whose release level is lower than the release level of the DAS. However, for database instances whose release level is higher than the release level of the DAS, the DAS must be migrated to a higher level. The DAS release level must be as high (or higher) than the release level of any of the database instances it services. User ID restrictions User IDs have the following restrictions and requirements: * Must have a primary group other than guests, admins, users, and local * Can include lowercase letters (a-z), numbers (0-9), and the underscore character ( _ ) * Cannot be longer than eight characters * Cannot begin with IBM, SYS, SQL, or a number * Cannot be a DB2 reserved word (USERS, ADMINS, GUESTS, PUBLIC, or LOCAL), or an SQL reserved word * Cannot use any User IDs with root privilege for the DB2 instance ID, DAS ID or fenced ID. * Cannot include accented characters * If existing user IDs are specified instead of creating new user IDs, make sure that the user IDs: * Are not locked * Do not have expired passwords 2.4.3 Centralized user-management considerations (Linux and UNIX) In environments that include security software, there are some installation considerations. Note: The DB2 installation cannot update or create users and groups if they are controlled outside of the operating system. For example, LDAP can be used to control users and groups outside of the operating system. Note: Network Information Services (NIS) and Network Information Services Plus (NIS+) features are deprecated starting with DB2 Version 9.1 Fix Pack 2. Support for these features might be removed in a future release. Lightweight Directory Access Protocol (LDAP) is the recommended solution for centralized user-management services. At instance creation, without a security component present, the instance owner's group list is modified to include that of the database administrative server (DAS) user's primary group, if the DAS is created. If the instance creation program is unable to modify these properties, it reports that it could not. The warning message provides the necessary information to manually make the changes. These considerations hold true for any environment in which an external security program does not allow the DB2 installation or instance creation programs to modify user characteristics. 2.4.4 Preparing to install DB2 for Linux on zSeries To install a DB2 product on an IBM zSeries that is running Linux, you must make the installation image accessible to the Linux operating system. You can use FTP to send the installation image to the operating system, or use an NFS mount to make the product DVD available to the operating system. Prerequistes You have already obtained your DB2 product installation image. Using FTP to access the installation image From the IBM zSeries computer running Linux: 1. Enter the following command: ftp yourserver.com where yourserver.com represents the FTP server where the DB2 product installation image resides. 2. Enter your user ID and password. 3. Enter the following commands: bin get product file where product file represents the appropriate product package name. Using the DB2 product DVD over NFS to access the installation image To use the product DVD on a Linux operating system: 1. Mount the appropriate product DVD. 2. Export the directory where you mounted the DVD. For example, if you mounted the DVD under /db2dvd, then export the /db2dvd directory. 3. On the IBM zSeries computer running Linux, NFS mount this directory using the following command: mount -t nfs -o ro nfsservername:/db2dvd /local_directory_name where nfsservername represents the host name of the NFS server, db2dvd represents the name of the directory being exported on the NFS server, and local_directory_name represents the name of the local directory. 4. From the IBM zSeries computer running Linux, change to the directory where the DVD is mounted. You can do this by entering the cd /local_directory_name command, where local_directory_name represents the mount point of your product DVD. 2.4.5 Creating group and user IDs for a DB2 database installation (Linux and UNIX) The DB2 Setup wizard will create these users and groups for you during the installation process. If you want, you can create them ahead of time. To perform this task, you must have root authority to create users and groups. Three users and groups are required. The user and group names used in the following instructions are documented in the following table. You can specify your own user and group names if they adhere to system naming rules and DB2 naming rules. The user IDs you create will be required to complete subsequent setup tasks. Table 11. Default users and groups +-----------------------+----------------------+----------------------+ | User | Example user name | Example group name | +-----------------------+----------------------+----------------------+ | Instance owner | db2inst1 | db2iadm1 | +-----------------------+----------------------+----------------------+ | Fenced user | db2fenc1 | db2fadm1 | +-----------------------+----------------------+----------------------+ | DB2 administration | dasusr1 | dasadm1 | | server user | | | +-----------------------+----------------------+----------------------+ * The instance owner home directory is where the DB2 instance will be created. * The fenced user is used to run user defined functions (UDFs) and stored procedures outside of the address space used by the DB2 database. * The user ID for the DB2 administration server user is used to run the DB2 administration server on your system. To create the required groups and user IDs for DB2: 1. Log in as a user with root authority. 2. Enter the appropriate commands for your operating system. Note: These command line examples do not contain passwords. They are examples only. You can use the passwd username command from the command line to set the password. AIX operating systems To create groups on AIX, enter the following commands: mkgroup id=999 db2iadm1 mkgroup id=998 db2fadm1 mkgroup id=997 dasadm1 Create users for each group: mkuser id=1004 pgrp=db2iadm1 groups=db2iadm1 home=/home/db2inst1 db2inst1 mkuser id=1003 pgrp=db2fadm1 groups=db2fadm1 home=/home/db2fenc1 db2fenc1 mkuser id=1002 pgrp=dasadm1 groups=dasadm1 home=/home/dasusr1 dasusr1 Set initial password: passwd db2inst1 passwd db2fenc1 passwd dasusr1 HP-UX operating systems To create groups on HP-UX, enter the following commands: groupadd -g 999 db2iadm1 groupadd -g 998 db2fadm1 groupadd -g 997 dasadm1 Create users for each group: useradd -g db2iadm1 -d /home/db2instl -m db2inst1 useradd -g db2fadm1 -d /home/db2fenc1 -m db2fenc1 useradd -g dbasgrp -d /home/dasusr1 -m dasusr1 Set initial password: passwd db2inst1 passwd db2fenc1 passwd dasusr1 Linux operating systems To create groups on Linux operating systems, enter the following commands: groupadd -g 999 db2iadm1 groupadd -g 998 db2fadm1 groupadd -g 997 dasadm1 Create users for each group: useradd -u 1004 -g db2iadm1 -m -d /home/db2inst1 db2inst1 useradd -u 1003 -g db2fadm1 -m -d /home/db2fenc1 db2fenc1 useradd -u 1002 -g dasadm1 -m -d /home/dasusr1 dasusr1 Set initial password: passwd db2inst1 passwd db2fenc1 passwd dasusr1 Solaris operating systems To create groups on Solaris, enter the following commands: groupadd -g 999 db2iadm1 groupadd -g 998 db2fadm1 groupadd -g 997 dasadm1 Create users for each group: useradd -g db2iadm1 -u 1004 -d /export/home/db2inst1 -m db2inst1 useradd -g db2fadm1 -u 1003 -d /export/home/db2fenc1 -m db2fenc1 useradd -g dasadm1 -u 1002 -d /export/home/dasusr1 -m dasusr1 Set initial password: passwd db2inst1 passwd db2fenc1 passwd dasusr1 2.4.6 OS user limit requirements (Linux and UNIX) This topic outlines the recommended operating system user process resource limits (ulimits) on Linux and UNIX operating systems. Depending on your installation, the DB2 engine automatically raises the ulimits to varying degrees: * For root installations, the DB2 engine automatically raises ulimits where necessary based on the needs of the DB2 database system. * For non-root installations, the DB2 engine can update only the data, nofiles, and fsize ulimits for the engine process up to the hard limits imposed by the system administrator. In either case, it might be more practical to set the resource limits permanently on your system. Especially for non-root installations, the data, nofiles, and fsize ulimit values should be set appropriately by an administrator after installing. Recommended ulimit values for non-root installations After a non-root installation is completed, the instance owner should verify the hard operating system ulimits for the data, nofiles, and fsize resources. The recommended values are outlined in the following table: Table 12. Recommended ulimit values for non-root installations +-------------+-------------+-------------+-------------+-------------+ | Hard ulimit | Description | Minimum | Recommended | Command to | | resource | | value | value | query the | | | | | | value | +-------------+-------------+-------------+-------------+-------------+ | data | Maximum | The amount | Unlimited | ulimit -Hd | | | private | of memory | | | | | memory | available | | | | | allowed for | on the | | | | | a process | computer | | | +-------------+-------------+-------------+-------------+-------------+ | nofiles | Maximum | Larger than | 65536 or | ulimit -Hn | | | number of | the sum of | unlimited | | | | open files | all | | | | | allowed for | MAXFILOP | | | | | a process | database | | | | | | configurati | | | | | | on | | | | | | parameters | | | | | | for all | | | | | | databases | | | | | | in the | | | | | | instance | | | +-------------+-------------+-------------+-------------+-------------+ | fsize | Maximum | Unlimited | Unlimited | ulimit -Hf | | | file size | | | | | | allowed | | | | +-------------+-------------+-------------+-------------+-------------+ If the minimum ulimit values are not met, the DB2 engine could encounter unexpected operating system resource shortage errors. These errors can lead to a DB2 outage. Contact a root user or a System Administrator if the ulimit values need to be updated for your non-root installation. Values for ulimits must be set manually, except on AIX operating systems, where you also have the option to set ulimits by running the db2rfe command. 2.4.7 Kernel parameters (Linux and UNIX) 2.4.7.1 Modifying kernel parameters (HP-UX) For your DB2 product to perform properly on HP-UX, you might need to update your system's kernel configuration parameters. If you update your kernel configuration parameter values, you must restart your computer. You must have root authority to modify kernel parameters. To modify kernel parameters: 1. Enter the sam command to start the System Administration Manager (SAM) program. 2. Double-click the Kernel Configuration icon. 3. Double-click the Configurable Parameters icon. 4. Double-click the parameter that you want to change and type the new value in the Formula/Value field. 5. Click OK. 6. Repeat these steps for all of the kernel configuration parameters that you want to change. 7. When you are finished setting all of the kernel configuration parameters, select Action --> Process New Kernel from the action menu bar. The HP-UX operating system automatically restarts after you change the values for the kernel configuration parameters. 2.4.7.2 Recommended kernel configuration parameters (HP-UX) For HP-UX systems running a DB2 64-bit database system, run the db2osconf command to suggest appropriate kernel configuration parameter values for your system. The db2osconf utility can only be run from $DB2DIR/bin, where $DB2DIR is the directory where you installed your DB2 product. 2.4.7.3 Modifying kernel parameters (Linux) Before installing a DB2 database system, update your Linux kernel parameters. The default values for particular kernel parameters on Linux are not sufficient when running a DB2 database system. You must have root authority to modify kernel parameters. To update kernel parameters on Red Hat and SUSE Linux: 1. Run the ipcs -l command 2. Analyze the output to determine if there are any necessary changes required for your system. Comments have been added following the // to show what the parameter names are. # ipcs -l ------ Shared Memory Limits -------- max number of segments = 4096 // SHMMNI max seg size (kbytes) = 32768 // SHMMAX max total shared memory (kbytes) = 8388608 // SHMALL min seg size (bytes) = 1 ------ Semaphore Limits -------- max number of arrays = 1024 // SEMMNI max semaphores per array = 250 // SEMMSL max semaphores system wide = 256000 // SEMMNS max ops per semop call = 32 // SEMOPM semaphore max value = 32767 ------ Messages: Limits -------- max queues system wide = 1024 // MSGMNI max size of message (bytes) = 65536 // MSGMAX default max size of queue (bytes) = 65536 // MSGMNB * Beginning with the first section on Shared Memory Limits, SHMMAX and SHMALL are the parameters that need to be looked at. SHMMAX is the maximum size of a shared memory segment on a Linux system whereas SHMALL is the maximum allocation of shared memory pages on a system. * It is recommended to set the SHMMAX value to be equal to the amount of physical memory on your system. However, the minimum required on x86 systems is 268435456 (256 MB) and for 64-bit systems, it is 1073741824 (1 GB). * SHMALL is set to 8 GB by default (8388608 KB = 8 GB). If you have more physical memory than this, and it is to be used for DB2, then this parameter increases to approximately 90% of your computer's physical memory For instance, if you have a computer system with 16 GB of memory to be used primarily for DB2, then SHMALL should be set to 3774873 (90% of 16 GB is 14.4 GB; 14.4 GB is then divided by 4 KB, which is the base page size). The ipcs output has converted SHMALL into kilobytes. The kernel requires this value as a number of pages. If you are upgrading to DB2 Version 9.7 and you are not using the default SHMALL setting, you must increase the SHMALL setting by an additional 4 GB. This increase in memory is required by the fast communication manager (FCM) for additional buffers or channels. * The next section covers the amount of semaphores available to the operating system. The kernel parameter sem consists of 4 tokens, SEMMSL, SEMMNS, SEMOPM and SEMMNI. SEMMNS is the result of SEMMSL multiplied by SEMMNI. The database manager requires that the number of arrays (SEMMNI) be increased as necessary. Typically, SEMMNI should be twice the maximum number of agents expected on the system multiplied by the number of logical partitions on the database server computer plus the number of local application connections on the database server computer. * The third section covers messages on the system. * MSGMNI affects the number of agents that can be started, MSGMAX affects the size of the message that can be sent in a queue, and MSGMNB affects the size of the queue. * MSGMAX should be change to 64 KB (that is, 65535 bytes), and MSGMNB should be increased to 65535. 3. To modify these kernel parameters, edit the /etc/sysctl.conf file. If this file does not exist, create it. The following lines are examples of what should be placed into the file: kernel.sem=250 256000 32 1024 #Example shmmax for a 64-bit system kernel.shmmax=1073741824 #Example shmall for 90 percent of 16 GB memory kernel.shmall=3774873 kernel.msgmax=65535 kernel.msgmnb=65535 4. Run sysctl with -p parameter to load in sysctl settings from the default file /etc/sysctl.conf: sysctl -p 5. To make the changes effective after every reboot: * (SUSE Linux) Make boot.sysctl active * (Red Hat) The rc.sysinit initialization script will read the /etc/sysctl.conf file automatically 2.4.7.4 Modifying kernel parameters (Solaris Operating System) For the DB2 database system to operate properly, it is recommended that you update your system's kernel configuration parameters. You can use the db2osconf utility to suggest recommended kernel parameters. If you want to take advantage of project resource controls (/etc/project), consult your Solaris documentation. You must have root authority to modify kernel parameters. To use the db2osconf command, you must first install the DB2 database system. The db2osconf utility can only be run from $DB2DIR/bin, where $DB2DIR is the directory where you installed your DB2 product. You must restart your system after modifying kernel parameters. To set a kernel parameter, add a line at the end of the /etc/system file as follows: set parameter_name = value For example, to set the value of the msgsys:msginfo_msgmax parameter, add the following line to the end of the /etc/system file: set msgsys:msginfo_msgmax = 65535 After updating the /etc/system file, restart the system. 2.5 Installing on Windows 2.5.1 An overview of installing your DB2 server product (Windows) This topic outlines the steps for installing your DB2 server product on Windows. To install your DB2 server product: 1. Review your DB2 product prerequisites. 2. Review DB2 upgrade information if applicable. 3. Prepare the installation media: Product DVD Insert the DB2 product DVD into your DVD-ROM drive. Installation image If you downloaded an installation image, extract the file. 4. Install your DB2 product using: * the DB2 Setup wizard. * a silent installation with a response file. You can use the DB2 Setup wizard to perform installation and configuration tasks, such as: * Selecting DB2 installation type (typical, compact, or custom). * Selecting DB2 product installation location. * Installing the languages that you can specify later as the default language for the product interface and messages. * Setting up DB2 Extended Security. * Setting up a DB2 instance (including instance user setup. By default, it is same as the DAS user). * Setting up the DB2 Administration Server (including DAS user setup). * Setting up the DB2 Text Search server. * Setting up Administration contact and health monitor notification. * Setting up and configuring your instance setup and configuration (including instance user setup). * Preparing the DB2 tools catalog. * Specifying the DB2 Information Center port. * Creating response files. * Installing additional products. 2.5.2 Installing DB2 servers (Windows) This task describes how to start the DB2 Setup wizard on Windows. You will use the DB2 Setup wizard to define your installation and install your DB2 database product on your system. Before you begin Before you start the DB2 Setup wizard: * If you are planning on setting up a partitioned database environment, refer to "Setting up a partitioned database environment". * Ensure that your system meets installation, memory, and disk requirements. * If you are planning to use LDAP on Windows to register the DB2 server in Active Directory, you should extend the directory schema before you install. * If you are planning to use the IBM Tivoli Monitoring for Databases: DB2 Agent, before installing your DB2 product see topic "Installing IBM Tivoli Monitoring for Databases: DB2 Agent with the DB2 installer" for details, limitations and restrictions. * You must have a local Administrator user account with the recommended user rights to perform the installation. In DB2 database servers where LocalSystem can be used as the DAS and DB2 instance user and you are not using the database partitioning feature, a non-administrator user with elevated privileges can perform the installation. Note: If a non-Administrator user account is going to do the product installation, then the VS2005 runtime library must be installed before attempting to install a DB2 database product. The VS2005 runtime library is needed on the operating system before the DB2 database product can be installed. The VS2005 runtime library is available from the Microsoft runtime library download web site. There are two choices: choose vcredist_x86.exe for 32-bit systems or vcredist_x64.exe for 64-bit systems. * Although not mandatory, it is recommended that you close all programs so that the installation program can update any files on the computer without requiring a reboot. * Installing DB2 products from a virtual drive or an unmapped network drive (such as \\hostname\sharename in Windows Explorer) is not supported. Before attempting to install DB2 products, you must map the network drive to a Windows drive letter (for example, Z:). Restrictions * You cannot have more than one instance of the DB2 Setup wizard running in any user account. * The DB2 copy name and the instance name cannot start with a numeric value.The DB2 copy name is limited to 64 English characters consisting of the characters A-Z, a-z and 0-9. * The DB2 copy name and the instance name must be unique among all DB2 copies. * The use of XML features is restricted to a database that has only one database partition. * No other DB2 database product can be installed in the same path if one of the following is already installed: * IBM Data Server Runtime Client * IBM Data Server Driver Package * DB2 Information Center * The DB2 Setup wizard fields do not accept non-English characters. * If you enable extended security on Windows Vista or Windows 2008, or higher, users must belong to the DB2ADMNS or DB2USERS group to run local DB2 commands and applications because of an extra security feature (User Access Control) that limits the privileges that local administrators have by default. If users do not belong to one of these groups, they will not have read access to local DB2 configuration or application data. Procedure To start the DB2 Setup wizard: 1. Log on to the system with the local Administrator account that you have defined for the DB2 installation. 2. If you have the DB2 database product DVD, insert it into the drive. If enabled, the autorun feature automatically starts the DB2 Setup Launchpad. If the autorun does not work, use Windows Explorer to browse the DB2 database product DVD and double-click on the setup icon to start the DB2 Setup Launchpad. 3. If you downloaded the DB2 database product from passport advantage, run the executable file to extract the DB2 database product installation files. Use Windows Explorer to browse the DB2 installation files and double-click on the setup icon to start the DB2 Setup Launchpad. 4. From the DB2 Setup launchpad, you can view installation prerequisites and the release notes, or you can proceed directly to the installation. You may want to review the installation prerequisites and release notes for late-breaking information. 5. Click Install a Product and the Install a Product window will display the products available for installation. If you have no existing DB2 database products installed on your computer, launch the installation by clicking Install New. Proceed through the installation following the DB2 Setup wizard's prompts. If you have at least one existing DB2 database product installed on your computer, you can: * Click Install New to create a new DB2 copy. * Click Work with Existing to update an existing DB2 copy, to add function to an existing DB2 copy, upgrade an existing DB2 Version 8, Version 9.1, or Version 9.5 copy, or to install an add-on product. 6. The DB2 Setup wizard will determine the system language, and launch the setup program for that language. Online help is available to guide you through the remaining steps. To invoke the online help, click Help or press F1. You can click Cancel at any time to end the installation. Results Your DB2 database product will be installed, by default, in the Program_Files\IBM\sqllib directory, where Program_Files represents the location of the Program Files directory. If you are installing on a system where this directory is already being used, the DB2 database product installation path will have _xx added to it, where xx are digits, starting at 01 and increasing depending on how many DB2 copies you have installed. You can also specify your own DB2 database product installation path. What to do next * Verify your installation. * Perform the necessary post-installation tasks. For information on errors encountered during installation, review the installation log file located in the My Documents\DB2LOG\ directory. The log file uses the following format: DB2-ProductAbrrev-DateTime.log, for example, DB2-ESE-Tue Apr 04 17_04_45 2008.log. If this is a new DB2 product installation on Vista 64-bit, and you will use a 32-bit OLE DB provider, you must manually register the IBMDADB2 DLL. To register this DLL, run the following command: c:\windows\SysWOW64\regsvr32 /s c:\Program_Files\IBM\SQLLIB\bin\ibmdadb2.dll where Program_Files represents the location of the Program Files directory. If you want your DB2 database product to have access to DB2 documentation either on your local computer or on another computer on your network, then you must install the DB2 Information Center. The DB2 Information Center contains documentation for the DB2 database system and DB2 related products. By default, DB2 information will be accessed from the web if the DB2 Information Center is not locally installed. DB2 Express Edition and DB2 Workgroup Server Edition memory limits If you are installing DB2 Express Edition, the maximum allowed memory for the instance is 4 GB. If you are installing DB2 Workgroup Server Edition, the maximum allowed memory for the instance is 16 GB. The amount of memory allocated to the instance is determined by the INSTANCE_MEMORY database manager configuration parameter. Important notes when upgrading from Versions 9.1 or 9.5: * If the memory configuration for your Version 9.1 DB2 database product exceeds the allowed limit, the DB2 database product might not start after upgrading to the current version. * The self tuning memory manager will not increase your overall instance memory limit beyond the license limits. 2.5.3 Multiple DB2 copies on the same computer (Windows) You can use multiple DB2 copies on the same computer. Each DB2 copy can be at the same or different code levels. The benefits of doing this include: * The ability to run applications that require different DB2 versions on the same machine at the same time. * The ability to run independent copies of DB2 products for different functions. * The ability to test on the same computer before moving the production database to the latter version of the DB2 product. * For independent software vendors, the ability to embed a DB2 server product into your product and hide the DB2 database from your users. A DB2 copy can contain one or more different DB2 products. This refers to the group of DB2 products that are installed at the same location. Differences when only one DB2 copy is installed * During installation, a unique Default DB2 copy name is generated. You can only change the name of the default DB2 copy as you go through the DB2 Setup wizard. You cannot change the DB2 copy name after the installation is completed. * Applications use the Default DB2 copy in an environment similar to the DB2 Version 8 environment. Differences when multiple DB2 copies are installed on the same computer * DB2 Version 8 can coexist with DB2 Version 9.1 and DB2 Version 9.5, with restrictions described below. * The DB2 Version 8 copy must be the default copy even though you may have multiple copies of DB2 Version 9.1 or Version 9.5. This default copy cannot be changed. After DB2 Version 8 is uninstalled, you can use the Global Switcher to set the default copy to any the DB2 Version 9.1 or Version 9.5 copies. * Optional: You can configure each DB2 copy to use a different DB2 Information Center. Note: You can have only one copy of the DB2 Information Center installed on the same system at the same Release level. Specifically, you can have a Version 8, a Version 9.1, and a Version 9.5 (or higher) DB2 Information Center on the same system, but you cannot have one DB2 Information Center at Version 9 fix pack 1 and another at Version 9 fix pack 2 on the same machine. You can however configure the DB2 database server to access these DB2 Information Centers remotely. * Only the IBM Data Server Provider for .NET from the default IBM database client interface copy is registered in the Global Assembly Cache. If Version 8 is installed with Version 9, the IBM Data Server Provider for .NET 2.0 Provider from Version 9 is also registered in the Global Assembly Cache. Version 8 does not have a 2.0 .NET provider. * Each instance name must be unique. For a response file installation with NO_CONFIG=YES, the default instance will not be created. However, when you create the instance after the installation, it must be unique. The name of the default instance will be "DB2". If an instance of the "DB2" name already exists, a unique name for the instance is generated to ensure uniqueness. This is done by using the "DB2" name and adding an underscore and generating the last 2 characters in numerical sequence. The subsequent instance names generated are "DB2_01", "DB2_02", and so on. For performance reasons, the DB2 Control Center should only be used from one DB2 copy at a single time on a machine. For Microsoft COM+ applications, it is recommended that you use and distribute the IBM Data Server Driver Package (installer) or IBM Data Server Driver for ODBC and CLI (zip) with your application instead of the IBM Data Server Runtime Client as only one Data Server Runtime Client can be used for COM+ applications at a time. The IBM Data Server Driver Package (installer) or IBM Data Server Driver for ODBC and CLI (zip) does not have this restriction. Microsoft COM+ applications accessing DB2 data sources are only supported with the default DB2 copy. Concurrent support of COM+ applications accessing different DB2 copies is not supported. If you have DB2 Universal Database (UDB) Version 8 installed, you can only use DB2 UDB Version 8 to run these applications. If you have DB2 Version 9 or higher installed, you can change the default DB2 copy using the Default DB2 Copy Selection Wizard, but you can not use them concurrently. Choosing a default when installing a new DB2 copy Your system environment includes several DB2 copies one which is the default DB2 copy. In Version 9.1, you can have a scenario where you have installed multiple DB2 copies. (In this example, DB2COPY1, DB2COPY2, and on to DB2COPYn.) One of the DB2 copies is selected by you as the default DB2 copy. In this case, DB2COPY1 is selected as the default DB2 copy. Beginning with Version 9.5, image a scenario where you install one DB2 copy (DB2COPY1). It is the default DB2 copy and the default IBM database client interface copy. As you are installing a new DB2 copy, you decide not to make the new DB2 copy the default DB2 copy. Then you install a DB2 product in a new DB2 copy (DB2COPY2). During the installation of the new DB2 copy (DB2COPY2) you are asked if you want to make the new DB2 copy the default DB2 copy. If you respond "No", then DB2COPY1 remains the default DB2 copy. (It is also the default IBM database client interface copy.) However, consider the same scenario but you respond "Yes" when asked if you want to make the new DB2 copy the default DB2 copy. As you are installing a new DB2 copy, you decide to make the new DB2 copy the default DB2 copy. In this case, DB2COPY2 becomes the new default DB2 copy (and the default IBM database client interface copy). Version 8 coexistence DB2 Version 8 and DB2 Version 9 can coexist with the restriction that DB2 Version 8 is set as the Default DB2 copy. To no longer have DB2 Version 8 as the Default DB2 copy, you can upgrade that DB2 copy to DB2 Version 9 and then change the Default DB2 copy. On the server, there can be only one DAS version and it administers instances as follows: * If the DAS is on Version 9, then it can administer Version 8 and Version 9 instances. * If the DAS is on Version 8, then it can administer only Version 8 instances. You can upgrade your Version 8 DAS, or drop it and create a new Version 9 DAS to administer the Version 8 and Version 9 instances. This is required only if you want to use the Control Center to administer the instances. Version 8 and Version 9 coexistence and the DB2 .NET Data Provider In DB2 Version 9, the DB2 .NET Data Provider has System.Transaction support. However, this is only available for the default DB2 copy and is therefore not supported in a coexistence environment. If Version 8 is installed, the 1.1 .NET Data Provider registered in the Global Assembly Cache will be from Version 8. The 2.0 provider, that is registered, will be from Version 9. The 2.0 provider cannot be used in the same process that uses the 1.1 provider, OLE DB, or ODBC to connect to DB2. 3rd party applications that run as a service By default, 3rd party applications that dynamically bind DB2 DLLs, for example, that are linked with db2api.lib, will find the DB2 DLLs in the current PATH. This means that existing applications that are not enabled for multi-version support will use the Default DB2 copy. To work around this, the application can use the db2SelectDB2Copy API before loading any DB2 libraries. For more information, see the Call Level Interface Guide and Reference, Volume 1. 32- and 64-bit versions on Win x64 DB2 does not support multiple DB2 32- and 64-bit versions installed on Windows. If you install the DB2 64-bit version, the 32-bit version will be removed from the system. This is because the DB2 32- and 64-bit registries reside in different locations. LDAP and CLI configuration With DB2 Version 8, if an application needs different LDAP settings, it needs to use a different LDAP user. Otherwise, the CLI configuration will affect all DB2 copies that the LDAP user might potentially use. Performance counters Performance counters can be registered for only one DB2 copy at a time and they can monitor only the instances in the DB2 copy in which they are registered. When you switch the Default DB2 copy, the DB2 Selection Wizard de-registers and reregisters the performance counters so that they are active for the Default DB2 copy. Windows Management Instrumentation (WMI) Only one version of the WMI provider can be registered at any given time. Client Connectivity You can use only one DB2 copy in the same process. Applications that dynamically link DB2 DLLs Applications that link to DB2 DLLs directly or that use LoadLibrary instead of LoadLibraryEx with the LOAD_WITH_ALTERED_SEARCH_PATH parameter will need to ensure that the initial dependent library is loaded properly. You can use your own coding technique to do this, or you can call the db2envar.bat file to setup the environment before running the application, or you can call the db2SelectDB2Copy API, which can be statically linked into the application. Visual Studio 2003 plugins If the default DB2 copy is a Version 9.5, a Version 9.1, or a Version 8 copy, there can be only one version of the plugins registered on the same computer at the same time. The version of the plugins that is active will be the version that is shipped with the default DB2 copy. Licensing Licenses need to be registered for each DB2 copy. They are not system-wide. This allows different licenses for different paths and provides the ability for both restricted versions of DB2 copies of the product and full versions of DB2 copies on the same machine. NT Services DB2 NT services will use the . For example, DB2NETSECSERVER_MYCOPY1. The display name also contains the Copy Name appended to it in brackets, for example, DB2 Security Server (MYCOPY1). Instances also include the DB2--- in the display name, which is shown in the services control panel applet. The actual service name remains as is. API to select the DB2 copy to use You can use the db2SelectDB2Copy API to select the DB2 copy that you want your application to use. This API does not require any DLLs. It is statically linked into your application. You can delay the loading of DB2 libraries and call this API first before calling any other DB2 APIs. Note that the function cannot be called more than once for any given process; that is, you cannot switch a process from one DB2 copy to another. The db2SelectDB2Copy API sets the environment required by your application to use the DB2 copy name or the location specified. If your environment is already set up for the copy of DB2 that you want to use, then you do not need to call this API. If, however, you need to use a different DB2 copy, you must call this API before loading any DB2 DLLs within your process. This call can be made only once per process. Database Partitioning with multiple physical nodes Each physical partition must use the same DB2 copy name on all computers. Using MSCS and Multiple DB2 Copies Each DB2 resource must be configured to run in a separate resource monitor. 2.6 Installing on Linux and UNIX 2.6.1 An overview of installing your DB2 server product (Linux and UNIX) This topic outlines the steps for installing your DB2 server product on AIX, HP-UX, Linux, and Solaris. To install your DB2 server product: 1. Review your DB2 product prerequisites. 2. Review DB2 upgrade information if applicable. 3. Modify kernel parameters on HP-UX, Linux, and Solaris. On all platforms, except for Linux on x86_32, you must install a 64-bit kernel before proceeding with the installation, otherwise the installation will fail. 4. Prepare the installation media: Product DVD If the DB2 product DVD does not automount, mount your DB2 product DVD. Installation image If you downloaded an installation image, untar the file. 5. Install your DB2 product using one of the available methods: * The DB2 Setup wizard * The db2_install command * A silent installation using a response file * Payload file deployment For DB2 servers, you can use the DB2 Setup wizard to perform installation and configuration tasks, such as: * Selecting DB2 installation type (typical, compact, or custom). * Selecting DB2 product installation location. * Install the languages that you can specify later as the default language for the product interface and messages. * Install or upgrade the IBM Tivoli System Automation for Multiplatforms (Linux and AIX). * Setting up a DB2 instance. * Setting up the DB2 Administration Server (including DAS user setup). * Setting up the DB2 Text Search server. * Setting up Administration contact and health monitor notification. * Setting up and configuring your instance setup and configuration (including instance user setup). * Setting up Informix® data source support. * Preparing the DB2 tools catalog. * Specify the DB2 Information Center port. * Creating response files. 6. If you installed a DB2 server using a method other than the DB2 Setup wizard, post-installation configuration steps are required. 2.6.2 Installing as a root user 2.6.2.1 Installing DB2 servers using the DB2 Setup wizard (Linux and UNIX) This task describes how to start the DB2 Setup wizard on Linux and UNIX operating systems. The DB2 Setup wizard is used to define your installation preferences and to install your DB2 database product on your system. Before you begin Before you start the DB2 Setup wizard: * If you are planning on setting up a partitioned database environment, see how to do this by following the related link at the bottom of this topic. * Ensure that your system meets installation, memory, and disk requirements. * Ensure you have a supported browser installed (Firefox 2.0+, Mozilla 1.7+, or SeaMonkey 1.1.4). * You can install a DB2 server using either root or non-root authority. For more information on non-root installation, see the related links. * The DB2 database product image must be available. You can obtain a DB2 installation image either by purchasing a physical DB2 database product DVD, or by downloading an installation image from Passport Advantage®. * If you are installing a non-English version of a DB2 database product, you must have the appropriate National Language Packages. * The DB2 Setup wizard is a graphical installer. You must have X windows software capable of rendering a graphical user interface for the DB2 Setup wizard to run on your machine. Ensure that the X windows server is running. Ensure that you have properly exported your display. For example, export DISPLAY=9.26.163.144:0. * If you are using security software in your environment, you must manually create required DB2 users before you start the DB2 Setup wizard. * If you are planning to use the IBM Tivoli Monitoring for Databases: DB2 Agent, before installing your DB2 product see topic "Installing IBM Tivoli Monitoring for Databases: DB2 Agent with the DB2 installer" for details, limitations and restrictions. Restrictions * You cannot have more than one instance of the DB2 Setup wizard running in any user account. * The use of XML features is restricted to a database that is defined with the code set UTF-8 and has only one database partition. * The DB2 Setup wizard fields do not accept non-English characters. Procedure To start the DB2 Setup wizard: 1. If you have a physical DB2 database product DVD, change to the directory where the DB2 database product DVD is mounted by entering the following command: cd /dvdrom where /dvdrom represents the mount point of the DB2 database product DVD. 2. If you downloaded the DB2 database product image, you must extract and untar the product file. a. Extract the product file: gzip -d product.tar.gz where product is the name of the product that you downloaded. b. Untar the product file: On Linux operating systems tar -xvf product.tar On AIX, HP-UX, and Solaris operating systems gnutar -xvf product.tar where product is the name of the product that you downloaded. c. Change directory: cd ./product where product is the name of the product that you downloaded. Note: If you downloaded a National Language Package, untar it into the same directory. This will create the subdirectories (for example ./nlpack/disk1) in the same directory, and allows the installer to automatically find the installation images without prompting. 3. Enter the ./db2setup command from the directory where the database product image resides to start the DB2 Setup wizard. 4. The IBM DB2 Setup Launchpad opens. From this window, you can view installation prerequisites and the release notes, or you can proceed directly to the installation. You can also review the installation prerequisites and release notes for late-breaking information. 5. Click Install a Product and the Install a Product window will display the products available for installation. Launch the installation by clicking Install New. Proceed through the installation following the DB2 Setup wizard's prompts. Once you have initiated the installation, proceed through the DB2 Setup wizard installation panels and make your selections. Installation help is available to guide you through the remaining steps. To invoke the installation help, click Help or press F1. You can click Cancel at any time to end the installation. Results For non-root installations, DB2 database products are always installed in the $HOME/sqllib directory, where $HOME represents the non-root user's home directory. For root installations, DB2 database products are installed, by default, in one of the following directories: AIX, HP-UX, and Solaris /opt/IBM/db2/V9.7 Linux /opt/ibm/db2/V9.7 If you are installing on a system where this directory is already being used, the DB2 database product installation path will have _xx added to it, where _xx are digits, starting at 01 and increasing depending on how many DB2 copies you have installed. You can also specify your own DB2 database product installation path. DB2 installation paths have the following rules: * Can include lowercase letters (a-z), uppercase letters (A-Z), and the underscore character ( _ ) * Cannot exceed 128 characters * Cannot contain spaces * Cannot contain non-English characters The installation log files are: * The DB2 setup log file. This file captures all DB2 installation information including errors. * For root installations, the DB2 setup log file name is db2setup.log. * For non-root installations, the DB2 setup log file name is db2setup_username.log, where username is the non-root user ID under which the installation was performed. * The DB2 error log file. This file captures any error output that is returned by Java (for example, exceptions and trap information). * For root installations, the DB2 error log file name is db2setup.err. * For non-root installations, the DB2 error log file name is db2setup_username.err, where username is the non-root user ID under which the installation was performed. By default, these log files are located in the /tmp directory. You can specify the location of the log files. There is no longer a db2setup.his file. Instead, the DB2 installer saves a copy of the DB2 setup log file in the DB2_DIR/install/logs/ directory, and renames it db2install.history. If the name already exists, then the DB2 installer renames it db2install.history.xxxx, where xxxx is 0000-9999, depending on the number of installations you have on that machine. Each installation copy has a separate list of history files. If an installation copy is removed, the history files under this install path will be removed as well. This copying action is done near the end of the installation and if the program is stopped or aborted before completion, then the history file will not be created. What to do next * Verify your installation. * Perform the necessary post-installation tasks. National Language Packs can also be installed by running the ./db2setup command from the directory where the National Language Pack resides, after a DB2 database product has been installed. On Linux x86, if you want your DB2 database product to have access to DB2 documentation either on your local computer or on another computer on your network, then you must install the DB2 Information Center. The DB2 Information Center contains documentation for the DB2 database system and DB2 related products. DB2 Express Edition and DB2 Workgroup Server Edition memory limits If you are installing DB2 Express Edition, the maximum allowed memory for the instance is 4 GB. If you are installing DB2 Workgroup Server Edition, the maximum allowed memory for the instance is 16 GB. The amount of memory allocated to the instance is determined by the INSTANCE_MEMORY database manager configuration parameter. Important notes when upgrading from Versions 9.1 or 9.5: * If the memory configuration for your Versions 9.1 or 9.5 DB2 database product exceeds the allowed limit, the DB2 database product might not start after upgrading to the current version. * The self tuning memory manager will not increase your overall instance memory limit beyond the license limits. 2.6.3 Installing as a non-root user 2.6.3.1 Non-root installation overview (Linux and UNIX) Before Version 9.5, you could install products, apply and roll back fix packs, configure instances, add features, or uninstall products only if you had root privileges. Now, if you are a non-root user, you can perform these tasks on Linux and UNIX platforms. The DB2 installer automatically creates and configures a non-root instance during a non-root installation. As a non-root user, you can customize the configuration of the non-root instance during the installation. You can also use and maintain the installed DB2 product without root privileges. The non-root installation of a DB2 product has one DB2 instance with most features enabled by default. A non-root installation can be attractive for many groups, such as the following ones: * Enterprises that have thousands of workstations and users who want to install a DB2 product without consuming a system administrator's time * Application developers who are not typically system administrators but use DB2 products to develop applications * Independent Software Vendors (ISVs) who develop software that does not require root authority yet embeds a DB2 product Although non-root installations have most of the function of root installations, there are some differences and limitations. You can lift some of the limitations by having a root user run the db2rfe command. 2.6.3.2 Differences between root installations and non-root installations In addition to a few limitations, the directory structure of a non-root installation is slightly different than the directory structure of a root installation. During a root installation, subdirectories and files for the DB2 product are created in a directory of the root user's choosing. Unlike root users, non-root users cannot choose where DB2 products are installed. Non-root installations are always placed in the $HOME/sqllib directory, where $HOME represents the non-root user's home directory. The layout of the subdirectories within the sqllib directory of a non-root is similar to that of a root installation. For root installations, multiple instances can be created. Instance ownership is associated with the user ID under which the instance was created. Non-root installations can have only one DB2 instance. The non-root installation directory contains all of the DB2 product files and instance files with no soft links. The following table summarizes the differences between root installations and non-root installations. Table 13. Differences between root installations and non-root installations +-----------------------+----------------------+----------------------+ | Criteria | Root installations | Non-root | | | | installations | +-----------------------+----------------------+----------------------+ | User can select | Yes | No. DB2 products are | | installation | | installed under the | | directory | | user's home | | | | directory. | +-----------------------+----------------------+----------------------+ | Number of DB2 | Multiple | One | | instances allowed | | | +-----------------------+----------------------+----------------------+ | Files deployed during | Program files only. | Program files and | | installation | Instances must be | instance files. The | | | created after | DB2 product is ready | | | installation. | for use immediately | | | | after installation. | +-----------------------+----------------------+----------------------+ 2.6.3.3 Limitations of non-root installations In addition to the differences between root installations and non-root installations, there are several limitations on non-root installations. This topic discusses the limitations to help you decide if you want to use a non-root installation. Product limitations Some DB2 products are not supported in non-root installations: * IBM Data Studio * DB2 Query Patroller * DB2 Net Search Extender * Locally installed DB2 Information Center Note: The locally installed DB2 Information Center is not supported in non-root installations because it requires root authority to start the daemon. However, a non-root-installation DB2 instance can be configured to use a locally installed DB2 Information Center if it is installed on the same computer. Features and tools limitations The following features and tools are not available in non-root installations: * The DB2 Administration Server (DAS) and its associated commands: dascrt, dasdrop, daslist, dasmigr, and dasupdt * The Configuration Assistant * The Control Center * The ability for the db2governor to increase priority is not supported * In the Work Load Manager (WLM), attempts to set agent priority in a DB2 service class in a non-root DB2 instance are allowed. However, the agent priority will not be respected, and no SQLCODE error is returned. * Automatic starting of non-root DB2 instances at system reboot is not supported Health monitor limitations The following health monitor features are not supported in non-root installations: * Running script or task actions on alert occurrences * Sending alert notifications Partitioned database limitation Only single-partition databases are supported in non-root installations. You cannot add additional database partitions. Listing DB2 products The output produced by the db2ls command, when run as a non-root user, is different than the output produced when run as a root user. For details, refer to the db2ls command topic. DB2 copies Each non-root user can have only one copy of a DB2 product installed. DB2 instance limitation In non-root installations, one DB2 instance is created during installation. Additional instances cannot be created. DB2 instance actions can be performed only by the instance owner Root installations and non-root installations can coexist on the same computer in different installation paths. However, a non-root instance can be updated, or dropped (using the db2_deinstall command), only by the non-root user who owns the non-root instance. A DB2 instance created by a user with root privilege can be updated or dropped only by a user with root privilege. DB2 instance commands The following DB2 instance commands are unavailable in non-root installations: db2icrt When installing a DB2 product as a non-root user, a single instance is automatically created and configured. Further instances cannot be created in non-root installations. However, if the automatically created instance needs to be configured, you can use the non-root install configuration command, db2nrcfg. db2iupdt The db2iupdt command cannot be used for non-root instances. Instead, use the non-root install configuration command (db2nrcfg) to update the non-root DB2 instance. However, updating the non-root instance is normally not required because it gets updated automatically when updating your DB2 product. db2idrop The instance that gets automatically created during non-root installations cannot be dropped. The DB2 product must be uninstalled to drop the DB2 instance. db2iupgrade Upgrading is not supported for non-root installations. Upgrading limitation Root instances cannot be upgraded to a non-root instance. Post-installation actions can be performed only by the DB2 instance owner Root installations and non-root installations can coexist on the same computer. However, only the original non-root user who installed the DB2 product can perform subsequent actions such as: * Applying fix packs * Adding features * Installing add-on products Adjusting ulimit values The ulimit command on UNIX and Linux sets or reports user resource limits, such as data and stack limits. For root instances, the database server dynamically updates required ulimit settings without changing the permanent settings. However, for non-root instances, the ulimit settings can only be checked during installation. A warning message is displayed if the settings are inadequate. Root authority is required to change the ulimit settings. Limitations that can be overcome by running db2rfe There are further limitations on non-root installations which can be overcome by running the db2rfe command. The following features and abilities are initially unavailable in non-root installations: * Operating system-based authentication * High Availability (HA) feature * The ability to reserve service names in the /etc/services file * The ability to increase user data limits (ulimits). This ability applies only to AIX. On other platforms, user data limits must be increased manually. Run the Enable root features for non-root install command (db2rfe) to enable these features and abilities. Running the db2rfe command is optional, and must be run by a user with root authority. Authentication type in non-root installations Operating system-based authentication is the default authentication type for DB2 products. Since non-root installations do not support operating system-based authentication, if you choose not to run the db2rfe command after installing your DB2 product as a non-root user, then you must manually set the authentication type. You can do so by updating the following parameters in the database manager configuration (dbm cfg) file: * clnt_pw_plugin (Client userid-password plug-in configuration parameter) * group_plugin (Group plug-in configuration parameter) * srvcon_pw_plugin (Userid-password plug-in for incoming connections at the server configuration parameter) 2.6.3.4 Installing a DB2 product as a non-root user Most DB2 products can be installed as a non-root user. Before you install any DB2 product as a non-root user, be aware of the differences between root installations and non-root installations, and the limitations of non-root installations. Refer to the Related Links at the end of this topic for details. Prerequisites for installing a DB2 product as a non-root user are: * You must be able to mount the installation DVD, or have it mounted for you. * You must have a valid user ID that can be used as the owner of a DB2 instance. User IDs have the following restrictions and requirements: * Must have a primary group other than guests, admins, users, and local * Can include lowercase letters (a-z), numbers (0-9), and the underscore character ( _ ) * Cannot be longer than eight characters * Cannot begin with IBM, SYS, SQL, or a number * Cannot be a DB2 reserved word (USERS, ADMINS, GUESTS, PUBLIC, or LOCAL), or an SQL reserved word * Cannot use any User IDs with root privilege for the DB2 instance ID, DAS ID or fenced ID. * Cannot include accented characters * If existing user IDs are specified instead of creating new user IDs, make sure that the user IDs: * Are not locked * Do not have expired passwords * The hardware and software prerequisites that exist for the product you are installing apply to the non-root user just as they do for root users. * On AIX Version 5.3, Asynchronous I/O (AIO) must be enabled. * Your home directory must be a valid DB2 path. DB2 installation paths have the following rules: * Can include lowercase letters (a-z), uppercase letters (A-Z), and the underscore character ( _ ) * Cannot exceed 128 characters * Cannot contain spaces * Cannot contain non-English characters Installing DB2 products as a non-root user is transparent to the non-root user. In other words, there is nothing special a non-root user needs to do to install a DB2 product, other than being logged in as a non-root user. To perform a non-root installation: 1. Log in as a non-root user 2. Install your DB2 product using any of the methods available to you. Options include: * The DB2 Setup wizard (GUI install) * The db2_install command * The db2setup command with a response file (silent install) Note: Since non-root users cannot choose the directory where DB2 products are installed, any FILE keyword in your response file is ignored. Refer to the Related Links at the end of this topic for details. 3. After the DB2 product is installed, you must open a new login session to use the non-root DB2 instance. Alternatively, you can use the same login session if you source the DB2 instance environment with $HOME/sqllib/db2profile (for Bourne shell and Korn shell users) or $HOME/sqllib/db2chsrc (for C shell users), where $HOME is the non-root user's home directory. After the DB2 product is installed, verify your operating system user process resource limits (ulimits). If the minimum ulimit values are not met, the DB2 engine can encounter unexpected operating resource shortage errors. These errors can lead to a DB2 outage. 2.6.3.5 Enabling root-based features in non-root installations with db2rfe There are several features and abilities in non-root installations that are initially unavailable but can be enabled by running a the db2rfe command This task requires root authority. To enable the features and abilities that are initially unavailable in non-root installations: 1. Locate the sample configuration files. Two sample configuration files are provided: * $HOME/sqllib/instance/db2rfe.cfg is pre-configured with default values for the non-root DB2 instance * $HOME/sqllib/cfg/db2rfe.cfg.sample is not configured where $HOME is the non-root user's home directory. 2. Copy one of the sample configuration files to a different location so the original file remains unaltered. 3. Update the copied configuration file as needed. This configuration file is input to the db2rfe command. An example of a configuration file is: INSTANCENAME=db2inst2 SET_ULIMIT=NO ENABLE_HA=NO ENABLE_OS_AUTHENTICATION=NO RESERVE_REMOTE_CONNECTION=NO **SVCENAME=db2c_db2inst2 **SVCEPORT=48000 RESERVE_TEXT_SEARCH_CONNECTION=NO **SVCENAME_TEXT_SEARCH=db2j_db2inst2 **SVCEPORT_TEXT_SEARCH=55000 Note: * The value for the INSTANCENAME parameter is filled in automatically by DB2 installer * The SET_ULIMIT parameter is available only on AIX. On other operating systems, a user with root authority needs to set ulimit values manually. * The default value for the other keywords is NO * Child parameters (such as SVCENAME) are commented out by default. Comments are denoted with ** * If you set a parameter to YES, and if it has any child parameters, it is recommended that you uncomment the child parameters and provide appropriate values. Any port values that are provided are examples. Ensure the port values you assign are free. An example is provided below to show an edited configuration file that will enable the following features and abilities: * High availability * Operating system-based authentication * DB2 Text Search, with a service name of db2j_db2inst2 and a port value of 55000 To enable these features and abilities, edit the configuration file as follows: INSTANCENAME=db2inst2 SET_ULIMIT=NO ENABLE_HA=YES ENABLE_OS_AUTHENTICATION=YES RESERVE_REMOTE_CONNECTION=NO **SVCENAME=db2c_db2inst2 **SVCEPORT=48000 RESERVE_TEXT_SEARCH_CONNECTION=YES SVCENAME_TEXT_SEARCH=db2j_db2inst2 SVCEPORT_TEXT_SEARCH=55000 4. Log in as a user with root authority 5. Navigate to the $HOME/sqllib/instance directory, where $HOME represent's the non-root user's home directory. 6. Run the db2rfe command using the following syntax: db2rfe -f config_file where config_file is the configuration file created in Step 3. You must rerun the db2rfe command after applying fix packs to keep root-based features enabled on non-root installations. 3.0 IBM data server clients and drivers overview This topic outlines information available about clients and drivers, and provides links to further details. This topic will help you to perform the following tasks: 1. Choose the appropriate IBM data server client or driver to enable connections between your system and remote databases. 2. Choose the most suitable method for installing your client or driver. 3. Complete the steps and address the considerations needed to set up a client or driver. Connection options Options for connecting a system to a remote database include various IBM data server clients and drivers. The options available depend on whether the system connecting to the remote database is: * An application located on a business user's machine or an application server * An application development workstation * A database administrator workstation There are additional options to consider if you need to also connect to midrange or mainframe databases. IBM data server client and driver types The following lists the IBM data server clients and drivers: * IBM Data Server Client * IBM Data Server Runtime Client * IBM Data Server Driver Package * IBM Data Server Driver for ODBC and CLI * IBM Data Server Driver for JDBC and SQLJ. In addition, a separate product, DB2 Connect Personal Edition, includes all the functionality of IBM Data Server Client plus the capability to connect to midrange and mainframe databases. DB2 Connect capability can be added to any client or driver. Installation methods The common method for installing a client or driver is to run the installation program provided on a product DVD. There is no installation program for IBM Data Server Driver for ODBC and CLI or for IBM Data Server Driver Package on Linux and UNIX. You must install the driver manually. Other installation methods are also available. Some methods are designed to automate the deployment of large numbers of clients. Other methods use various Windows operating system capabilities. For example, on Windows operating systems, you can use merge modules to embed the functionality of Data Server Runtime Client or IBM Data Server Driver Package in your application. Setting up a client or driver After you decide which client to use, set up the client by performing the following steps: 1. Ensure that system prerequisites are satisfied. 2. Perform the installation. 3. Catalog databases and configure connections to remote servers. For systems where a Version 8 client or a DB2 Version 9 client already exists, consider whether to upgrade the existing client to a Version 9.7 Data Server Client, or, keep the pre-Version 9.7 client and install the Version 9.7 Data Server Client as an additional client. It is strongly recommended that installing additional clients is for advanced users. Note: The option to upgrade and replace the existing client applies to Data Server Client only. 3.1 IBM data server client types There are several types of IBM data server clients and drivers available. Each provides a particular type of support. The following lists the IBM data server client and driver types available to you: * IBM Data Server Driver for JDBC and SQLJ * IBM Data Server Driver for ODBC and CLI * IBM Data Server Driver Package * IBM Data Server Runtime Client * IBM Data Server Client Each IBM data server client and driver provides a particular type of support: * For Java applications only, use IBM Data Server Driver for JDBC and SQLJ. * For applications using ODBC or CLI only, use IBM Data Server Driver for ODBC and CLI. (Also referred to as cli driver.) * For applications using ODBC, CLI, .NET, OLE DB, PHP, Ruby, JDBC, or SQLJ, use IBM Data Server Driver Package. * If you need DB2 Command Line Processor Plus (CLPPlus) support, use IBM Data Server Driver Package. * If you need DB2 command line processor (CLP) support and basic client support for running and deploying applications, use IBM Data Server Runtime Client. * If you need support for database administration, and application development using an application programming interface (API), such as ODBC, CLI, .NET, or JDBC, use IBM Data Server Client. IBM Data Server Driver for JDBC and SQLJ IBM Data Server Driver for JDBC and SQLJ is the default driver for Java stored procedures and user-defined functions. This driver provides support for client applications and applets that are written in Java using JDBC to access local or remote servers, and SQLJ for embedded static SQL in Java applications. IBM Data Server Driver for ODBC and CLI Data Server Driver for ODBC and CLI is a lightweight deployment solution designed for independent software vendors (ISV) deployments. This driver, also referred to as cli driver, provides runtime support for applications using ODBC API, or CLI API without need of installing the Data Server Client or the Data Server Runtime Client. This driver is available only as a tar file, not as an installable image. Messages are reported only in English. The IBM Data Server Driver for ODBC and CLI provides: * runtime support for the CLI API; * runtime support for the ODBC API; * runtime support for the XA API; * database connectivity; * support for DB2 Interactive Call Level Interface (db2cli); * LDAP Database Directory support; and * tracing, logging, and diagnostic support. Register Data Server Driver for ODBC and CLI with the Microsoft ODBC driver manager using the db2oreg1.exe utility. IBM Data Server Driver Package, IBM Data Server Driver Package is a lightweight deployment solution that provides runtime support for applications using ODBC, CLI, .NET, OLE DB, PHP, Ruby, JDBC, or SQLJ without the need of installing Data Server Runtime Client or Data Server Client. This driver has a small footprint and is designed to be redistributed by independent software vendors (ISVs), and to be used for application distribution in mass deployment scenarios typical of large enterprises. The IBM Data Server Driver Package capabilities include: * The DB2 Command Line Processor Plus (CLPPlus) for dynamically creating, editing, and running SQL statements and scripts. * Support for applications that use ODBC, CLI, PHP, or Ruby to access databases. * Support for client applications and applets that are written in Java using JDBC, and for embedded SQL for Java (SQLJ). * IBM Informix Dynamic Server support for .NET, PHP, and Ruby. * Support for running embedded SQL applications. No precompiler or bind capabilities are provided. * Application header files to rebuild the PHP and Ruby drivers. * Support for DB2 Interactive Call Level Interface (db2cli). * Support for the for DRDA® traces (db2drdat). * On Windows operating systems, IBM Data Server Driver Package also provides support for applications that use .NET or OLE DB to access databases. In addition, this is available as an installable image, and merge modules are available to allow you to easily embed the driver in a Windows Installer-based installation. IBM Data Server Runtime Client The IBM Data Server Runtime Client provides a way to run applications on remote databases. GUI tools are not shipped with the IBM Data Server Runtime Client. Capabilities include: * The DB2 command line processor (CLP) for issuing commands. The CLP also provides a basic way to perform remote administration of servers. * Base client support to handle database connections, SQL statements, XQuery statements, and commands. * Support for common database access interfaces: JDBC, ADO.NET, OLE DB, ODBC, Command Line Interface (CLI), PHP, and Ruby. This support includes drivers and capabilities to define data sources. For example, for ODBC, installing an IBM data server client installs the ODBC driver and registers the driver. Application developers and other users can use the Windows ODBC Data Source Administrator tool to define data sources. * Lightweight Directory Access Protocol (LDAP) exploitation. * Support for common network communication protocols: TCP/IP, and Named Pipe. * Support for installing multiple copies of a client on the same computer. These copies can be the same or different versions. * License terms that allow free redistribution of IBM Data Server Runtime Client with your application. * smaller deployment footprint compared to that of the full IBM Data Server Client in terms of installation image size and disk space required. * A catalog that stores information for connecting to databases and servers. * Packing advantages on Windows operating systems: You can package the client with your application to provide connectivity for that application. Also, the client is available as Windows Installer merge modules that enable you to include the RTCL DLL files in your application installation package. This approach also enables you to include only the parts of the client that you need with your application. * IBM Informix Dynamic Server support for PHP, Ruby, .NET, and JDBC IBM Data Server Client IBM Data Server Client includes all the functionality of IBM Data Server Runtime Client, plus functionality for database administration, application development, and client/server configuration. Capabilities include the following: * A larger deployment footprint compared to that of IBM Data Server Runtime Client in terms of installation image size and disk space required. However, on Windows operating systems, you can prune the IBM Data Server Client image to reduce the installation image size. * The configuration Assistant to assist with cataloging databases and configuring the database server. * Control Center and other graphical tools for database implementation and for database administration. These tools are available for versions of Windows on x86 (32-bit only), Windows on x64 (AMD64/EM64T), Linux on x86, and Linux on AMD64/EM64T (x64). * First Steps documentation for new users. * Visual Studio tools * IBM Data Studio * Application header files * Precompilers for various programming languages * Bind support * Samples and tutorials * IBM Informix Dynamic Server support for PHP, Ruby, .NET, JCC, and JDBC 3.2 IBM Data Server Drivers 3.2.1 IBM Data Server Driver restrictions The IBM Data Server Driver Package simplifies application deployment. However, certain restrictions apply. The following restrictions apply toIBM Data Server Driver Package: * No other database product can be installed in the same path if IBM Data Server Driver Package is already installed. * On Windows operating systems, you can install a maximum of 16 copies of IBM Data Server Driver Package. * To connect to a z/OS® server or a System i server, you must register a DB2 Connect license key. (Retrieve the license file from your Passport Advantage distribution, for example db2conpe.lic, then copy the license file to the license directory under the directory where the driver was installed.) * XA connections against a z/OS server are supported. However, XA connections against a System i server are not supported. * If you use the configuration file db2dsdriver.cfg to specify aliases, the following entries must contain a value: * DSN_Collection entries (alias, name, host, and port) * database entries (name, host, port). These entries must be specified and cannot be empty. * The CLI/ODBC configuration keyword DBNAME is not supported. * The CLI LOAD utility statement attribute, sql_attr_use_load_api, is not supported. Functionality supported with restrictions * There is no local database directory. Lightweight Directory Access Protocol (LDAP) is supported, but the LDAP cache is not saved to disk. Functionality not supported * DB2 Command Line Processor (CLP) * administrative APIs * installation program Known limitations For information on short term limitations, go to http://www.ibm.com/developerworks/wikis/display/DB2/IBM+Data+Server+Driver+Limitations 3.2.2 Installing IBM Data Server Driver Package (Windows) On Windows platforms, IBM Data Server Driver Package simplifies application deployment. This driver, which has a small footprint, is designed to be redistributed by independent software vendors (ISVs) and to be used for application distribution in mass deployment scenarios typical of large enterprises. IBM Data Server Driver Package is not part of IBM Data Server Client or IBM Data Server Runtime Client. IBM Data Server Driver Package must be installed separately. No other DB2 database product can be installed in the same path if IBM Data Server Driver Package is already installed. IBM Data Server Driver Package is installed by running the DB2 setup.exe from the product DVD. There are separate install images for each language. To install IBM Data Server Driver Package using a response file, or to install it from a fix pack image, you can run the DB2 setup.exe from the command line. A sample response file is located in the \samples subdirectory. For fix pack images, you can download the setup.exe command from https://www14.software.ibm.com/webapp/iwm/web/reg/pick.do?lang=en_US&source=swg-idsc11. The default installation path of IBM Data Server Driver Package is Program Files\IBM\IBM DATA SERVER DRIVER. If a second copy is installed in the same machine, the default directory name is Program Files\IBM\IBM DATA SERVER DRIVER_02. In general, the default directory name is IBM DATA SERVER DRIVER_nn where nn is the generated number to make this directory unique. If you want to install more than one copy of IBM Data Server Driver Package, you can have a maximum of 16 copies. Each copy must be installed to different directories. The default copy name of IBM Data Server Driver Package is IBMDBCL1. If there are further drivers are installed on your machine, they will receive default names: IBMDBCL2, IBMDBCL3, and so on. Note: Installation of multiple copies is an advanced installation method that is not recommended for most users. After installing IBM Data Server Driver Package, you can optionally create and populate the configuration file, db2dsdriver.cfg, with database directory information. 3.2.2.1 Installing IBM data server clients (Windows) Instructions to install any IBM data server client type, namely the IBM Data Server Client, the IBM Data Server Runtime Client, and the IBM Data Server Driver Package. The main procedure covers a simple, but common, case where there is no DB2 product already installed. If the machine already has a prior version of a client installed, you should first review topics that cover upgrading. If the machine already has a DB2 server product installed, it is not necessary to install a client because the DB2 server provides all the capability found in an IBM data server client. Prerequisites Before installing IBM data server clients or client package: * You have determined which client best suits your need. * You have located a DVD or other install image that you need. Ensure you have the appropriate 32-bit or 64-bit version, depending on your machine. * You have a Windows user account that is part of the Administrators group. Note: If a non-Administrator user account is going to do the product installation, then the VS2005 runtime library must be installed before attempting to install a DB2 product. The VS2005 runtime library is needed on the operating system before the DB2 product can be installed. The VS2005 runtime library is available from the Microsoft runtime library download web site. There are two choices: choose vcredist_x86.exe for 32-bit systems or vcredist_x64.exe for 64-bit systems. * Your system meets all memory, disk space, and installation requirements. The installation program will check disk space and basis system requirements, and notify you if there is a problem. Restrictions * No other DB2 product can be installed in the same path if one of the following products is already installed: * IBM Data Server Runtime Client * IBM Data Server Driver Package * DB2 Information Center * The DB2 Setup wizard fields do not accept non-English characters. This procedure covers the simple case. Information for other cases is covered elsewhere in this topic. To install any IBM data server client on Windows: 1. Log on to the system with the user account that you want to use to perform the installation. 2. Optional: Shut down any other programs. 3. Insert the DVD into the drive. The auto-run feature starts the DB2 Setup wizard which determines the system language and starts the setup program for that language. For the Data Server Client, you can run the DB2 Setup wizard in a language other than the default system language by manually invoking the DB2 Setup wizard and specifying a language code. For example, the setup -i fr command runs the DB2 Setup wizard in French. For the Data Server Runtime Client or Data Server Driver Package, there are separate install images for each language. 4. To install an IBM data server client or client package: * If you are installing a Data Server Client, launch the DB2 Setup wizard, when the DB2 Launchpad opens, choose Install a Product. Follow the DB2 Setup wizard's prompts. * If you are installing a Data Server Runtime Client, it does not have a launchpad. See the Related Links for setup command parameters. If you are installing a second copy of the Data Server Runtime Client, the command is: setup /v" TRANSFORMS=:InstanceId1.mst MSINEWINSTANCE=1" To install each subsequent copy of the Data Server Runtime Client (up to a maximum of 16 copies), modify the command by incrementing InstanceIdn, for example: setup /v" TRANSFORMS=:InstanceId2.mst MSINEWINSTANCE=1" Note: It is strongly recommended that installing multiple copies is for advanced users. * If you are installing Data Server Driver Package, run the setup command from the product DVD. If you are installing a fix pack image, see the Related Links for the installation command options of the setup command. If you are installing a second copy of Data Server Driver Package, the following methods can be used: * To perform a new copy installation with a generated default copy name: setup /o * If the copy name already exists, perform a maintenance (or upgrade) installation on that copy. Otherwise, perform the new installation by using the specified copy name. setup /n copyname After installing Data Server Driver Package, you can optionally create and populate the configuration file, db2dsdriver.cfg, with database directory information. 5. If you are installing a Data Server Client on a machine that already has a DB2® Universal Database(TM) (UDB) Version 8 copy installed, you will be presented with the option to install a new copy or to upgrade the DB2 UDB Version 8 copy. Installing a new copy preserves the DB2 UDB Version 8 copy and installs an additional DB2 Version 9 copy. Choosing to upgrade will copy the DB2 UDB Version 8 client instance settings to the DB2 Version 9 copy then remove the DB2 UDB Version 8 copy. Note: If a machine already has a DB2 UDB Version 8 copy installed, the Version 9 copies cannot be set to default. If you are installing a Data Server Runtime Client, the installation program always installs a new copy. To upgrade a DB2 UDB Version 8 client instance as a subsequent step, see topics on migration. After completing this procedure, the product is now installed at the location you specified during the installation. As part of the IBM Data Server Client installation procedure, an instance of the DB2 database manager is created. The instance is called "DB2" if there is no other instance called "DB2". If you already have a copy of DB2 Version 8 or DB2 Version 9.1 installed, the default instance is DB2_01. The default installation path of Data Server Client and Data Server Runtime Client is Program Files\IBM\sqllib. If a second copy is installed in the same machine, the default directory name is Program Files\IBM\sqllib_01. In general, the default directory name is sqllib_nn where nn is the number of copies installed in that machine minus one. The default installation path of Data Server Driver Package is Program Files\IBM\IBM DATA SERVER DRIVER. If a second copy is installed in the same machine, the default directory name is Program Files\IBM\IBM DATA SERVER DRIVER_02. In general, the default directory name is IBM DATA SERVER DRIVER_nn where nn is the generated number to make this directory unique. If you want to install more than one copy of the Data Server Driver Package, you can have a maximum of 16 copies. Each copy must be installed to different directories. The default copy name of the Data Server Client or Data Server Runtime Client is DB2COPY1 The default copy name of the Data Server Driver Package is IBMDBCL1 This installation does not include product documentation. See the related links for options for installing or accessing the DB2 Information Center. After installing your IBM data server client, the next step is to configure it to access remote DB2 servers. Notes on installing using a user account that is not a member of the Administrators group Members of the Power Users group can install an IBM data server client. Members of the Users group can also install an IBM data server client after they have been enabled to do so. To enable members of the Users group to install an IBM data server client, a member of the Administrators group must ensure the installing user has write permission for the following: * HKEY_LOCAL_MACHINE\SOFTWARE registry branch. * the system directory (for example, c:\WINNT). * the default install path (c:\Program Files) or another install path. Of related interest, a non-administrator can also install fix packs if a non-administrator performed the original installation. However, a non-administrator cannot install fix packs if the original installation was performed by an Administrator user account. 3.2.2.2 Command line options to install IBM Data Server Driver Package (Windows) The IBM Data Server Driver Package can be installed by running the DB2 setup.exe from the command line. For fix pack images, you can download the setup.exe command from https://www14.software.ibm.com/webapp/iwm/web/reg/pick.do?lang=en_US&source=swg-idsc11. The following list describes command-line options available for the setup command. For more information about the available Windows Installer options, see http://www.msdn.microsoft.com/. /n [copy name] Specifies the copy name that you want the installation to use. Specifying this option overrides the installation path that is specified in the response file. If the copy exists, a maintenance installation is performed on that copy. Otherwise, a new installation is performed by using the specified copy name. /o Specifies that a new copy installation with a generated default copy name is to be performed. /u [response file] Specifies the full path and file name of the response file. /m Shows the progress dialog during the installation. However, you are not prompted for any input. Use this option with the /u option. /l [log file] Specifies the full path and file name of the log file. /p [install-directory] Changes the installation path of the product. Specifying this option overrides the installation path that is specified in the response file. /i language Specifies the two-letter language code of the language in which to perform the installation. /? Generates usage information. After installing IBM Data Server Driver Package, you can optionally create and populate the configuration file, db2dsdriver.cfg, with database directory information. The following are some examples of how to use the command-line parameters: * To install a new copy with a generated default copy name, use the following command: setup /o * To install a second copy use the following command: setup /n "COPY_NAME" * To perform a response file installation, use the following command: setup /u "[Full path to the response file]" A sample response file is located in the \samples subdirectory. 3.2.3 Installing IBM Data Server Driver Package (Linux and UNIX) On Linux and UNIX operating systems, IBM Data Server Driver Package simplifies application deployment. This driver, which has a small footprint, is designed to be redistributed by independent software vendors (ISVs) and to be used for application distribution in mass deployment scenarios typical of large enterprises. To install IBM Data Server Driver Package, you need to obtain the compressed file that contains this driver package. Download this file from the Fix Pack and client download Web site: http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21288110. On Linux and UNIX operating systems, there is no installation program for IBM Data Server Driver Package. This driver package includes database drivers for Java, ODBC/CLI, PHP, and Ruby on Rails, each of which is stored in its own subdirectory. The Java and ODBC/CLI drivers are compressed. The basic extraction steps for each driver are the same: 1. Uncompress the Data Server Driver Package archive. 2. Find the files for the driver you need and copy them onto the target machine. 3. For the Java and ODBC/CLI drivers, uncompress the driver file into your chosen install directory on the target machine. 4. Optional: remove the compressed driver file. Java Path: jdbc_sqlj_driver/ Filename: db2_db2driver_for_jdbc_sqlj.zip For installation instructions, see: Installing the IBM Data Server Driver for JDBC and SQLJ. ODBC/CLI Path: odbc_cli_driver/ Filename: ibm_data_server_driver_for_odbc_cli.tar.Z For installation instructions, see: Installing the IBM Data Server Driver for ODBC and CLI. PHP Path: php_driver//php32 or php_driver//php64 Files: ibm_db2_4.4.6.so, ibm_db2_5.2.1.so, pdo_ibm_5.2.1.so Prerequisite: The PHP drivers require the ODBC/CLI driver also included in this driver package to be installed. For installation instructions, see: Setting up the PHP environment on Linux or UNIX. Ruby on Rails Path: ruby_driver/ File: ibm_db-0.10.0.gem Prerequisite: The Ruby on Rails driver requires the ODBC/CLI driver also included in this driver package to be installed. To install the Ruby on Rails driver, from the location of the gem file, run the following command: gem install ibm_db-0.10.0.gem. To validate the installation, see: Verifying installation with IBM Data Servers on Rails applications. After installing Data Server Driver Package, you can optionally create and populate the configuration file, db2dsdriver.cfg, with database directory information. 3.3 Installation methods for IBM data server clients This section outlines common and alternative methods for installing an IBM data server client or driver. Clients are commonly installed on machines where there is no server present. You do not need to install a client if you already installed a server product is already installed because the server includes all the functionality present in an IBM data server client. Common situations The common method for installing an IBM data server client or driver is to run the installation program provided on a product DVD (setup command on Windows operating systems and db2setup command on Linux and UNIX operating systems). The IBM Data Server Client installation image is included in the database server installation image. Automation of large-scale deployments One group of methods automates the deployment of large numbers of clients: * Response file. You can automate client installation by using the response file installation method. A response file installation lets you install database products without any user interaction. * Third-party deployment tools. You can install clients using deployment tools or methods such as Windows Active Directory, Windows Systems Management Server (SMS), or Tivoli products. Use of Windows operating system capabilities Another group of options uses Windows operating system capabilities: * Windows thin client topology. This option is supported for the IBM Data Server Client and DB2 Connect Personal Edition. A thin client topology is where client code is installed in a shared Windows directory on a single code server rather than on the local hard disk of each client workstation. Individual client workstations connect to the shared Windows directory on the code server to run the Data Server Client code. * A Windows non-administrator ID. The common installation method uses a Windows administrator user ID: that is, a user ID in the Administrators group. However, you can also install an IBM data server client using a user ID that is part of the Windows Power Users group or Users group. This method is suitable when the user ID performing the installation does not have administrator privileges. The DB2 product also supports the Windows Elevated Privileges mechanism. It is recommended to use Windows Elevated Privileges to allow a non-administrator to install an IBM data server client. Linux and UNIX alternatives On Linux and UNIX operating systems, an alternative installation method provided for database servers is also applicable to clients: the db2_install script. Also, IBM Data Server Driver for ODBC and CLI is available as a tar file. Separate client instances If a database server product is installed, you can use a separate client instance instead of using a server instance that also serves as a client instance. To create a separate client instance, use the db2icrt command with the -s option, as shown in the following example: db2icrt -s client 3.3.1 Options for connecting to DB2 databases This section outlines the options for what you can install on a machine (the local system) to enable it to connect to a database on a different machine (the remote system). To select a suitable option, you first need to consider whether the local system is: * a system that runs business applications on a business user's system or on an application server. * an application development workstation. * a database administrator workstation. You also need to determine where the databases reside that you want to connect to. The databases could be located: * on same machine, that is, on the local system. This includes databases located in a single DB2 instance or in various DB2 instances. * on different machines, that is, on remote systems. * on different machines that are midrange or mainframe servers. Options for business user systems or application servers Typically, when a business application connects to a database, one of the following topologies is involved: * An application connects to a DB2 database where both are located on the same machine. An example is an application used by a single user on their personal workstation. * An application connects to a DB2 database on another machine. * An application client connects to an application server which, in turn, connects to one or more DB2 databases located: * on the same machine only. * on one or more other machines only. * a combination of the above. If a DB2 server is installed on the same machine as the application, there is no need to install a separate client. The DB2 server product includes functionality to enable applications to connect to local databases and to connect to databases on remote machines, as well. If the machine with the application does not also have a DB2 server, you have the following options to enable applications to connect to remote DB2 databases: * DB2 application driver. With a DB2 application driver, the information needed to connect to a database is included in the application or the application prompts the user to provide it. This approach differs from an IBM data server client which maintains this information in its catalog. The application driver is deployed as a file in the application directory so no separate DB2-specific installation or setup is required. Typically, an application driver is packaged with an application in a manner that provides connectivity only for that application. A DB2 application driver can coexist on the same machine with other DB2 application drivers or with an IBM data server client. DB2 products provide drivers for Java (JDBC and SQLJ) and for ODBC, CLI, .NET, OLE DB, or open source applications. Drivers can be obtained by copying driver files from an IBM Data Server Driver Package installation image or by downloading the driver files from developerWorks. * IBM data server client. This option involves installing and configuring one of the clients included with the DB2 product. The IBM data server client is installed on any machine that connects directly to the DB2 database. Depending on the application topology, the client is installed on each business user workstation or on an application server. A single IBM data server client can enable all applications on the machine to connect to one or more DB2 databases on other machines. * DB2 instance merge modules. These merge modules create a DB2 instance environment. This approach provides a way to deploy the IBM Data Server Runtime Client by including the files in the corresponding modules. This approach is targeted for use with Windows Installer and other install tools that support Windows Installer merge modules. With this approach, a single installation program installs both the application and the Data Server Runtime Client. If you do not require an instance environment or a Command Line Processor (CLP) you should use the non-DB2 instance merge modules to avoid instance management. * Non-DB2 instance merge modules. These merge modules create a non-DB2 instance environment. This approach provides a way to deploy the IBM Data Server Driver Package by including the client DLL files in the application deployment package. This approach is targeted for use with Windows Installer and other install tools that support Windows Installer merge modules. With this approach, a single installation program installs both the application and the IBM Data Server Driver Package. Options for application development workstations The IBM Data Server Client provides all the functionality of the IBM Data Server Runtime Client plus tools used for client-server configuration, database administration and application development. The points below describe the role and setup of the Data Server Client in light of the other tools and products used by application developers. There are several tools and products typically used by application developers who write code to access a DB2 database. Each developer workstation typically includes the following components: * An integrated development environment (IDE) such as Rational® Application Developer or Microsoft Visual Studio. * A DB2-specific development tool related to the IDE such as: * IBM Database Developer Add-ins for Visual Studio .NET * IBM Data Studio * Access to a database server to host the database they are developing. This database server can reside in one or both of the following locations: * On each developer's workstation, so each developer has their own local copy of the database. * On a workgroup server, so multiple developers work on the same copy of the database. With the foregoing as context, the value of the Data Server Client is that it provides headers and libraries required to compile applications and provides tools for database administration. However, it is not always necessary to install the Data Server Client to obtain these tools. Any time a DB2 server is installed on a machine, there is no need to install a separate IBM data server client. The DB2 server product includes all functionality available in a standalone Data Server Client. Options for administrator workstations A database administrator can perform administration tasks on remote databases in one of two major ways. They use a tool, such as telnet, to connect to an individual database server machine and run DB2 administrator commands locally. Alternatively, they can run tools and commands from their workstation that make connections to the remote databases. This section focuses on the second case which involves choices about which IBM data server client to use and where to install it. DB2 provides various means to perform administration activities on one or more DB2 servers remotely from an administrator workstation. The options and considerations are the following: * Install the IBM Data Server Runtime Client. This option is suitable if you only use the Command Line Processor (CLP) for administration. * Install the IBM Data Server Client. This client includes all the functionality of the Data Server Runtime Client plus tools used for client-server configuration, database administration and application development. Functionality includes the graphical administration tools such as the Configuration Assistant and Control Center (available on supported platforms). These tools use the DB2 Administration Server (DAS) on the DB2 server, which is setup by default during DB2 server installation. * Install a DB2 server product. Any time a DB2 server is installed on a machine, there is no need to install a separate IBM data server client. The DB2 server product includes all the functionality available in any standalone IBM data server client. Options for connecting to midrange and mainframe databases With DB2 Connect products, you can connect to DB2 databases on mainframe and midrange platforms, namely OS/390® and z/OS, System i, VSE, and VM. You can also connect to non-IBM databases that comply with the Distributed Relational Database Architecture(TM) (DRDA). With DB2 Connect, you can connect from a user's workstation or from a DB2 for Linux, UNIX, or Windows server. The options and considerations are the following: * IBM Data Server Driver Package. This lightweight deployment solution that provides runtime support for applications using ODBC, CLI, .NET, OLE DB, PHP, Ruby, JDBC, or SQLJ without the need of installing Data Server Runtime Client or Data Server Client. To connect to a z/OS server or a System i server, you must register a DB2 Connect license key. (Retrieve the license file from your Passport Advantage distribution, for example db2conpe.lic, then copy the license file to the license directory under the directory where the driver was installed.) * DB2 Connect Personal Edition. This product is installed on a workstation and provides connectivity from that workstation. This option is targeted for situations where there is a need to connect from a workstation directly to one or more hosts. This product is available for Linux, Solaris and Windows operating systems. * DB2 Connect Server Editions. A server edition of the DB2 Connect product is usually installed on a connectivity server and serves as a gateway to supported mainframe or midrange database servers. A server edition of the DB2 Connect product enables workstations with IBM data server clients to setup access to host systems via the DB2 Connect gateway as if they were databases on DB2 on Windows, Linux and UNIX. Both options can be used concurrently. For example, a workstation can connect to a midrange or mainframe database in the following ways: * Install DB2 Connect Personal Edition locally and use it to connect directly to a host. * Connect to the same or different host through an intermediate DB2 Connect server gateway. 3.3.2 Installing IBM data server clients (Windows) Instructions to install any IBM data server client type, namely the IBM Data Server Client, the IBM Data Server Runtime Client, and the IBM Data Server Driver Package. The main procedure covers a simple, but common, case where there is no DB2 product already installed. If the machine already has a prior version of a client installed, you should first review topics that cover upgrading. If the machine already has a DB2 server product installed, it is not necessary to install a client because the DB2 server provides all the capability found in an IBM data server client. Prerequisites Before installing IBM data server clients or client package: * You have determined which client best suits your need. * You have located a DVD or other install image that you need. Ensure you have the appropriate 32-bit or 64-bit version, depending on your machine. * You have a Windows user account that is part of the Administrators group. Note: If a non-Administrator user account is going to do the product installation, then the VS2005 runtime library must be installed before attempting to install a DB2 product. The VS2005 runtime library is needed on the operating system before the DB2 product can be installed. The VS2005 runtime library is available from the Microsoft runtime library download web site. There are two choices: choose vcredist_x86.exe for 32-bit systems or vcredist_x64.exe for 64-bit systems. * Your system meets all memory, disk space, and installation requirements. The installation program will check disk space and basis system requirements, and notify you if there is a problem. Restrictions * No other DB2 product can be installed in the same path if one of the following products is already installed: * IBM Data Server Runtime Client * IBM Data Server Driver Package * DB2 Information Center * The DB2 Setup wizard fields do not accept non-English characters. This procedure covers the simple case. Information for other cases is covered elsewhere in this topic. To install any IBM data server client on Windows: 1. Log on to the system with the user account that you want to use to perform the installation. 2. Optional: Shut down any other programs. 3. Insert the DVD into the drive. The auto-run feature starts the DB2 Setup wizard which determines the system language and starts the setup program for that language. For the Data Server Client, you can run the DB2 Setup wizard in a language other than the default system language by manually invoking the DB2 Setup wizard and specifying a language code. For example, the setup -i fr command runs the DB2 Setup wizard in French. For the Data Server Runtime Client or Data Server Driver Package, there are separate install images for each language. 4. To install an IBM data server client or client package: * If you are installing a Data Server Client, launch the DB2 Setup wizard, when the DB2 Launchpad opens, choose Install a Product. Follow the DB2 Setup wizard's prompts. * If you are installing a Data Server Runtime Client, it does not have a launchpad. See the Related Links for setup command parameters. If you are installing a second copy of the Data Server Runtime Client, the command is: setup /v" TRANSFORMS=:InstanceId1.mst MSINEWINSTANCE=1" To install each subsequent copy of the Data Server Runtime Client (up to a maximum of 16 copies), modify the command by incrementing InstanceIdn, for example: setup /v" TRANSFORMS=:InstanceId2.mst MSINEWINSTANCE=1" Note: It is strongly recommended that installing multiple copies is for advanced users. * If you are installing Data Server Driver Package, run the setup command from the product DVD. If you are installing a fix pack image, see the Related Links for the installation command options of the setup command. If you are installing a second copy of Data Server Driver Package, the following methods can be used: * To perform a new copy installation with a generated default copy name: setup /o * If the copy name already exists, perform a maintenance (or upgrade) installation on that copy. Otherwise, perform the new installation by using the specified copy name. setup /n copyname After installing Data Server Driver Package, you can optionally create and populate the configuration file, db2dsdriver.cfg, with database directory information. 5. If you are installing a Data Server Client on a machine that already has a DB2 Universal Database (UDB) Version 8 copy installed, you will be presented with the option to install a new copy or to upgrade the DB2 UDB Version 8 copy. Installing a new copy preserves the DB2 UDB Version 8 copy and installs an additional DB2 Version 9 copy. Choosing to upgrade will copy the DB2 UDB Version 8 client instance settings to the DB2 Version 9 copy then remove the DB2 UDB Version 8 copy. Note: If a machine already has a DB2 UDB Version 8 copy installed, the Version 9 copies cannot be set to default. If you are installing a Data Server Runtime Client, the installation program always installs a new copy. To upgrade a DB2 UDB Version 8 client instance as a subsequent step, see topics on migration. After completing this procedure, the product is now installed at the location you specified during the installation. As part of the IBM Data Server Client installation procedure, an instance of the DB2 database manager is created. The instance is called "DB2" if there is no other instance called "DB2". If you already have a copy of DB2 Version 8 or DB2 Version 9.1 installed, the default instance is DB2_01. The default installation path of Data Server Client and Data Server Runtime Client is Program Files\IBM\sqllib. If a second copy is installed in the same machine, the default directory name is Program Files\IBM\sqllib_01. In general, the default directory name is sqllib_nn where nn is the number of copies installed in that machine minus one. The default installation path of Data Server Driver Package is Program Files\IBM\IBM DATA SERVER DRIVER. If a second copy is installed in the same machine, the default directory name is Program Files\IBM\IBM DATA SERVER DRIVER_02. In general, the default directory name is IBM DATA SERVER DRIVER_nn where nn is the generated number to make this directory unique. If you want to install more than one copy of the Data Server Driver Package, you can have a maximum of 16 copies. Each copy must be installed to different directories. The default copy name of the Data Server Client or Data Server Runtime Client is DB2COPY1 The default copy name of the Data Server Driver Package is IBMDBCL1 This installation does not include product documentation. See the related links for options for installing or accessing the DB2 Information Center. After installing your IBM data server client, the next step is to configure it to access remote DB2 servers. Notes on installing using a user account that is not a member of the Administrators group Members of the Power Users group can install an IBM data server client. Members of the Users group can also install an IBM data server client after they have been enabled to do so. To enable members of the Users group to install an IBM data server client, a member of the Administrators group must ensure the installing user has write permission for the following: * HKEY_LOCAL_MACHINE\SOFTWARE registry branch. * the system directory (for example, c:\WINNT). * the default install path (c:\Program Files) or another install path. Of related interest, a non-administrator can also install fix packs if a non-administrator performed the original installation. However, a non-administrator cannot install fix packs if the original installation was performed by an Administrator user account. 3.3.3 Installing IBM data server clients (Linux and UNIX) This task describes how to install an IBM data server client on Linux or UNIX. The instructions apply to the IBM Data Server Client and the IBM Data Server Runtime Client. The main procedure covers a simple, but common, case where no DB2 product is already installed. A summary of the prerequisites is presented below. If you need more detailed information, see the related links at the end of this section. If the machine already has a prior version of a client installed, you should first review topics that cover upgrading. If the machine already has a DB2 server product installed, it is not necessary to install a client because the DB2 server provides all the capability found in IBM Data Server Client. * You have determined which client best suits your needs: the Data Server Client or the Data Server Runtime Client. * You have located a DVD or other install image that you need. * Your system meets all memory, disk space, and installation requirements. The installation program will check disk space and basis system requirements, and notify you if there is a problem. * Installing an IBM data server client on the Solaris operating system or on HP-UX requires that you update your kernel configuration parameters. This is also recommended for Linux. To install any IBM data server client on Linux or UNIX: 1. Insert and mount the appropriate DVD. 2. Change to the directory where the DVD is mounted. 3. Enter the ./db2setup command to start the DB2 Setup wizard. 4. Choose Install a Product when the DB2 Launchpad opens. 5. Select the client you want to install. 6. Follow the DB2 Setup wizard's prompts. Help is available in the wizard to guide you through the remaining steps. When installation is complete, the IBM data server client is installed by default in the following directories: Linux /opt/ibm/db2/V9.7 UNIX /opt/IBM/db2/V9.7 This installation does not include product documentation. See the related links for options for installing or accessing the DB2 Information Center. After installing your IBM data server client, the next step is to configure it to access a remote DB2 server. Notes on national language installations You can run the DB2 Setup wizard in a language other than the default system language by manually invoking the DB2 Setup wizard and specifying a language code. For example, the ./db2setup -i fr command runs the DB2 Setup wizard in French. However, the DB2 Setup wizard fields do not accept non-English characters. Notes on installing on a machine that has an existing DB2 Version 9.5 client The default directory name for the first copy is V9.7. If a copy is already installed, the second installation shows a default directory name of V9.7_01. In general, the default directory name is V9.7_nn where nn refers to the number of copies installed minus one. Notes on installing on a machine that has an existing pre-DB2 Version 9.5 client Installing a Data Server Client or Data Server Runtime Client on a system that already has either a DB2 Universal Database (UDB) Version 8 or DB2 Version 9 client preserves previous copy and installs an additional DB2 Version 9.5 (or higher) copy. For information on upgrading client instances to DB2 Version 9.5 (or higher), see the upgrading topics. 4.0 Overview of the DB2 technical information DB2 technical information is available through the following tools and methods: * DB2 Information Center * Topics (Task, concept and reference topics) * Help for DB2 tools * Sample programs * Tutorials * DB2 books * PDF files (downloadable) * PDF files (from the DB2 PDF DVD) * printed books * Command line help * Command help * Message help Note: The DB2 Information Center topics are updated more frequently than either the PDF or the hardcopy books. To get the most current information, install the documentation updates as they become available, or refer to the DB2 Information Center at ibm.com. You can access additional DB2 technical information such as technotes, white papers, and IBM Redbooks® publications online at ibm.com. Access the DB2 Information Management software library site at http://www.ibm.com/software/data/sw-library/. Documentation feedback We value your feedback on the DB2 documentation. If you have suggestions for how to improve the DB2 documentation, send an e-mail to db2docs@ca.ibm.com. The DB2 documentation team reads all of your feedback, but cannot respond to you directly. Provide specific examples wherever possible so that we can better understand your concerns. If you are providing feedback on a specific topic or help file, include the topic title and URL. Do not use this e-mail address to contact DB2 Customer Support. If you have a DB2 technical issue that the documentation does not resolve, contact your local IBM service center for assistance. 4.1 Terms and Conditions Permissions for the use of these publications is granted subject to the following terms and conditions. Personal use: You may reproduce these Publications for your personal, non commercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these Publications, or any portion thereof, without the express consent of IBM. Commercial use: You may reproduce, distribute and display these Publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these Publications, or reproduce, distribute or display these Publications or any portion thereof outside your enterprise, without the express consent of IBM. Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the Publications or any information, data, software or other intellectual property contained therein. IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the Publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed. You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations. IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE. 5.0 Notices This information was developed for products and services offered in the U.S.A. Information about non-IBM products is based on information available at the time of first publication of this document and is subject to change. IBM may not offer the products, services, or features discussed in this document in other 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 grant 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 character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, 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 contains 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: © (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. The following terms are trademarks or registered trademarks of other companies * Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. * Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. * UNIX is a registered trademark of The Open Group in the United States and other countries. * Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. * Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.