Scaling out DB2 UDB on Windows Server 2003 procedure

Published 16 December 2003

Authors: Whei-Jen Chen


This is a high level procedure for scaing out DB2 UDB on Windows Server 2003


Scaling out DB2 UDB on Windows Server 2003 procedure

Scaling out DB2 UDB is the ability to add more servers to the DB2 system. This is the way to improve scalability when a single system will not meet the needs in memory, processor, and storage for your business. Windows Server 2003 can be considered a powerful and safe option when implementing very large databases. The DB2 UDB ESE Partitioning feature is a product that takes advantage of the shared-nothing architecture.

Following is a high-level procedure for scaling out DB2 UDB on a Windows Server 2003. The details can be found in the IBM Redbook Scaling DB2 UDB onWindows Server 2003, SG24-7019.

1. Preparing the Windows environment
Before you install DB2 UDB, you must prepare your Windows environment for installation. To prepare your environment, you will:

    • Verify that each computer meets the necessary operating system, memory, and disk requirements.
    • Ensure that all computers belong to the same Windows domain.
    • Ensure that all computers have consistent time and date settings.
    • Verify that all computers can communicate with each other via TCP/IP.
    • Add a domain user account to the local Administrator group on each computer.
    • Optionally create DB2 user accounts for setup.

2. Setting up Windows Server 2003 Domain Controller
    If your primary server and participating servers are not under a domain or the domain does not exist, then you must create a Domain Controller server in order to install DB2 UDB as a partitioned database server.

3. Installing a DB2 partitioned environment
    • Before configuring DB2 UDB on a physical cluster environment, use the same installation considerations as for installing DB2 UDB in a single server. There are additional considerations regarding users, security, and the coordinator node in a server cluster for a partitioned database environment.
    • Install the DB2 Instance Owning Node.
    • Install a physical database partition.
    • Verify DB2 partitioning configuration.
    • Create partitioned databases.
    • Create additional partitions and redistribute data.

Special Notices

This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.

Follow IBM Redbooks

Follow IBM Redbooks