Quick Beginnings EEE for Windows**

Before You Begin

Before you begin the installation, be sure that you have the following items and information:

  1. Ensure that all of the machines that will participate in this partitioned database system:
    1. Meet all the requirements outlined in Planning for Installation.
    2. Belong to the same Windows domain.
    3. Have consistent time and date settings.

      Figure 00002674 not displayed.

      To be considered consistent, the difference in GMT time between all machines that participate in a partitioned database system must be within 1 hour. You can use the max_time_diff configuration parameter to change this restriction. For more information, refer to the Administration Guide.
    4. Have a TCP/IP port range free that spans 4 port numbers. This port range will be used by the Fast Communications Manager (FCM). FCM is a feature of DB2 that handles communications between database partition servers. The port range you select must be available on every machine that will participate in the partitioned database system. By default, the setup program will generate a range for you, use this port range or provide your own.

      To review the TCP/IP ports that are already in use, open the services file located in the x:\winnt\system32\drivers\etc directory, where x: represents the drive where you installed Windows.

      Make note of this port range here: ______ to ______.

      Figure 00002674 not displayed.

      If you plan to run multiple logical nodes (MLNs) on any of the machines that will participate in your partitioned database system, then you must specify a port range that spans the number of MLNs on the machine running the most MLNs.

      For example, if you had a database partition server that was running 6 database managers (by installing a database partition server and then adding 5 logical nodes) you would need to specify 6 consecutive ports as your port range for the installation. For more information, refer to the Administration Guide.

    5. Have a TCP/IP port free for use by the DB2 Performance Monitor. The port you select must be available on every machine that will participate in the partitioned database system. By default, the setup program will generate a value for you. You can use this port or provide your own.

      To review the TCP/IP ports that are already in use on a machine, open the services file located in the x:\winnt\system32\drivers\etc directory, where x: represents the drive where you installed Windows.

      Make note of this port here: ______.

    6. Can communicate with each other using TCP/IP. To ensure that two machines can communicate with each other using TCP/IP, perform the following steps:

      Step  1)

      On a machine that will participate in this partitioned database system, enter the following command:

         hostname
      

      This command will return the hostname of this machine

      Step  2)

      On another machine that will participate in this partitioned database system, enter the following command:

         ping hostname
      

      You will receive output similar to the following:

      Pinging myserver.com [9.21.27.230] with 32 bytes of data:
       
      Reply from 9.21.27.230: bytes=32 time<10ms TTL=128
      Reply from 9.21.27.230: bytes=32 time<10ms TTL=128
      

      This output verifies that both machines can communicate with each other.



      Figure 00002674 not displayed.

      If you are planning to use multiple network adapters, you must use the db2nchg command to specify the TCP/IP address for the netname field in the db2nodes.cfg file. For more information, you can refer to the Administration Guide, or to Changing the Database Partition Server Configuration.

  2. A domain user account that belongs to the Local Administrators group on the machine where you are going to perform the installation. The domain user account you specify must be defined as a Local Administrator on every machine that will participate in the partitioned database system.

    This user account must also have the "Act as part of the operating system" advanced user right. For more information on granting advanced user rights, refer to Granting Advanced User Rights on Windows.

  3. A domain user account to be associated with the DB2 instance. This domain user account does not need to be given Administrator or Domain Administration authority.
  4. During installation, you will be asked to provide a user account that will be used by the Administration Server to log on to the system and to start itself as a service.

    By default, the setup program will create a user account with the user name db2admin and the password you supply. You can accept the default user account, create your own user account by modifying the default value, or provide your own user account. If this account already exists on your system, you must use the password that was previously set for this user account. If you provide your own user account, you must ensure that it conforms to DB2's naming rules. For more information, see Appendix C, Naming Rules.

  5. To verify that DB2 installed correctly, you will need to have a user account that belongs to the DB2 System Administrative (SYSADM) group. The account name must comply with DB2's naming rules, as described in Username, User ID, Group Name, and Instance Name Rules.

    By default, any local user account that belongs to the Local Administrators group, on the local machine where the account is defined, has SYSADM authority on the instance. For more information, see Working with the System Administrative Group. For more information on valid DB2 usernames, see Appendix C, Naming Rules.

  6. During the installation, you may also be prompted for user names and passwords for the products and services that you install.
  7. If you want to use LDAP with Windows 2000, you must extend the directory schema to contain DB2 object classes and attribute definitions. You must do this once, before you install any DB2 product.

    To extend the directory schema, execute the db2schex.exe program from the installation CD with Schema Admins authority. You can execute this program with Schema Admins authority, without logging off and logging on again, as follows:

       runas /user:MyDomain\Administrator x:\db2\common\db2schex.exe
    

    where x: represents the CD-ROM letter. When db2schex.exe completes, you can continue with the installation.


[ Top of Page | Previous Page | Next Page ]