Before you install
a database product on Windows operating
systems, ensure that the system you choose meets the necessary operating
system, hardware, and software requirements.
For
the most up-to-date installation requirements for database products,
see System requirements for IBM® DB2® for Linux, UNIX, and Windows.
This techdoc uses IBM Software
Product Compatibility Reports (SPCR). With the SPCR tool, you
can locate and find complete lists of supported operating systems,
system requirements, prerequisites, and optional supported software
for these database products.
In
addition to system requirements, installing a data server product
on supported Windows operating
systems has these additional considerations.
- In DB2 Version
10.5 Fix Pack 5 and
later fix packs, BLU Acceleration is supported on all Windows operating
systems that are supported by DB2 Advanced Enterprise Server Edition
and Advanced Workgroup Server Edition. Only
a single processor group is supported. BLU
Acceleration for Windows has the same recommended minimums as all
other platforms, specifically 8 cores, and 64 GB RAM. In addition,
a maximum of four sockets is supported. If
you are running more than one socket, set performance variable DB2_RESOURCE_POLICY to AUTOMATIC.
- Windows Installer 3.0
is required. It is 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 or later framework runtime. In an x64 environment,
32-bit IBM data
server provider for .NET applications runs in the WOW64 emulation
mode.
- If you plan to use LDAP (Lightweight Directory Access Protocol),
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 the database products). Before installation of the Microsoft Active Directory,
you must 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.
- The
computer name of the Windows workstation
on which the DB2 installation
files are located, must be 15 characters or less in length.
- DB2 must be installed on a drive with short names enabled or a
directory with no spaces such as E:\DB2\SQLLIB. To check the current 8.3 file
name settings for a drive, in a command window with administrator privileges,
enter
fsutil.exe behavior query disable8dot3
The following possible values are
returned when you run the command: - 0: Create 8.3 short file names (default)
- 1: Do not create 8.3 file names
- 2: Set 8.3 file names on a per volume basis
- 3: Disable 8.3 file names on all volumes, except the system volume
The registry state of
NtfsDisable8dot3NameCreation is 0, which means
that 8.3 file names are enabled on all volumes. To enable 8.3 file names on a global basis, enter
fsutil.exe behavior set disable8dot3 0
If DB2 is installed on a drive without 8.3 name support andin a directory without
spaces, it must be reinstalled on a drive with 8.3 name support. If the folder you are trying to
install DB2 is already created when 8.3 name support is
disabled, then the short name is not created if you try a reinstall onto the same directory. Windows
short names are created during the directory creation, hence you must install it into a new
directory or if the directory is empty delete the directory and allow recreation.
Note: Data server products support the hardware-enforced Data
Execution Prevention (DEP) feature that is built into some Windows operating systems.