DB2 10.5 for Linux, UNIX, and Windows

Installing DB2 database servers using the DB2 Setup wizard (Windows)

This task describes how to start the DB2 Setup wizard on Windows. 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 to register the DB2 server in Windows operating systems Active Directory, extend the directory schema before you install, otherwise you must manually register the node and catalog the databases. For more information, see the "Extending the Active Directory Schema for LDAP directory services (Windows)" topic.
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.
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, 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:

Log on to the system with the local Administrator account that you have defined for the DB2 installation.
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 the setup icon to start the DB2 Setup Launchpad.
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. On Windows 2008 and Windows Vista or later versions of Windows operating system, you must right-click on setup.exe and select Run as administrator or start setup.exe from command prompt from "Command Window: Administrator".

Attention: You must never start the installation package(".msi" file) present in the DB2 installation media directly. Installation must always be started by setup.exe with full administrative privileges.

From the DB2 Setup launchpad, you can view installation prerequisites and the release notes, or you can proceed directly to the installation. You might want to review the installation prerequisites and release notes for late-breaking information. On Windows 2008 and Windows Vista or later versions of Windows operating system, you must right-click on setup.exe and select Run as administrator or start setup.exe from command prompt from "Command Window: Administrator".
Click Install a Product and the Install a Product window displays 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 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 9.7, Version 9.8, or Version 10.1 copy, or to install an add-on product.
The DB2 Setup wizard determines 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.
1. When you're at the Select the installation type step, when you click View Features... , some features are unchecked.
  1. The Connect support feature option does not affect your system’s ability to connect to DB2 for z/OS®. If you select this option, two extra trace utilities are installed. These utilities are ddcstrcn and ddcspkgn. The DDCSTRCN utility implements detailed DRDA traces and usually IBM support might request you use this utility when they need more diagnostic data to resolve a problem. For more information about the ddcspkgn tool, see Binding applications and utilities (DB2 Connect server).
Sample panels when using the DB2 setup wizard lead you to the installation process. See the related links.

Results

Your DB2 database product is 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 has _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 about 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 2012.log.

If this is a new DB2 product installation on Windows 64−bit, and you 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 is accessed from the web if the DB2 Information Center is not locally installed.

IBM Data Studio can be installed by running the the DB2 Setup wizard

DB2 Express® Server Edition and DB2 Workgroup Server Edition memory limits

If you are installing DB2 Express Server 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 64 GB.

The amount of memory allocated to the instance is determined by the INSTANCE_MEMORY database manager configuration parameter.

Important notes when upgrading from V9.7, V9.8, or V10.1:

The self tuning memory manager does not increase your overall instance memory limit beyond the license limits.