Configuring the database with the Configuration Tool

To configure a database for the directory server instance:

1. Stop the server if it is running.
2. In the task list on the left navigational pane of the Configuration Tool, click Configure database.
3. Do one of the following:
   • If you are configuring the database for a new directory instance:
     1. Type a user ID in the Database user name field. This user ID owns the database that is used by the directory instance, and the directory server instance uses this user ID to connect to the database. The user ID must already exist before you can configure the database. (See Appendix D. Setting up users and groups: directory server instance owner, database instance owner, and database owner for more information about requirements for the user ID.)
     2. Type a password for the user in the Password field. Passwords are case-sensitive.
     3. In the Database name field, type the name you want to give the DB2® database that is used by the directory server instance to store directory data. The name can be from 1 to 8 characters long.
     4. Select the Show advanced tablespace options check box if either of the following is true:
        • You want this database to use System Managed Storage (SMS) data storage for the DB2 tablespaces.
        • You want this database to use Database Managed Storage (DMS) data storage for the DB2 tablespaces and you want to configure sizes and locations for the USERSPACE1 and LDAPSPACE tablespaces for the database.

        If you clear the check box, the USERSPACE1 and LDAPSPACE tablespaces will be created using DMS with default sizes and locations.

        If you are configuring a directory server instance with an existing database, this check box is disabled when you type the name of the existing database in the Database name field.

        DB2 can use one of two types of data storage when it creates table spaces. These are System Managed Storage (SMS) and Database Managed Storage (DMS).

        When SMS is used, the operating system's file system manager allocates and manages the space where DB2 tables are stored (the tablespace).

        When DMS is used, the tablespaces are managed by the database manager. The database administrator decides which devices and files to use, and DB2 manages the space on those devices and files.

        The default for Tivoli Directory Server 6.3 is DMS. Versions of Tivoli Directory Server earlier than 6.2 use SMS for all databases.

        Note:
        The default minimum disk space requirement for a DMS database is 1 GB. If you have limited disk space and do not plan to have a large directory, configure an SMS database. An SMS database requires a minimum of 150 MB of disk space. These requirements are for an empty database. When you store data in the database, more disk space is required.
   • If you are reconfiguring the database options for an existing directory server instance:
     1. To change the database password, select the Reset password check box, and then do the following:
        1. In the Password field, type the new database password.
        2. In the Confirm password field, type the database password again for confirmation.
     2. To disable online backup support for the database, select the Disable support for online backup check box. (If you select this check box, the administration server will be restarted after the database is successfully reconfigured).

   Click Next.

4. If the database installation location is requested:
   1. Type the location for the database in the Database install location field. For Windows systems, this location must be a drive letter. For AIX®, Linux, and Solaris systems, the location must be a directory name, such as /home/ldapdb, and you can click Browse to locate the directory.

      Be sure that you have at least 1 GB (for a DMS database) or 150 MB (for an SMS database) of free hard disk space in the location you specify and that additional disk space is available to accommodate growth as new entries are added to the directory.

   2. If you plan to perform online backups of the database:
      1. Select the Configure for online backup check box.
      2. In the Database backup location field, type the location where you want the backed-up information to be stored. Click Browse to search for the location.
      Note:
      If you do not specify a database backup location, the database will not be configured for online backup.

      Clear the Configure for online backup check box if you do not want to perform online backups of the database.

      If you configure the database for online backup and you specify a backup location, the initial, offline backup of the database will be performed, and then the Administration Server will be restarted after the database is successfully configured.

      Notes:
      1. Do not exit the Configuration Tool while the backup operation is running.
      2. You can also configure online backup for a directory server instance using the command line. However, if you do this, you cannot unconfigure online backup through the command line (using the idscfgdb command with the -c flag).

         If you configure online backup for a directory server instance using either the Instance Administration Tool or the Configuration Tool, you can unconfigure it through the Configuration Tool or the command line.

         For the most reliable results, use the Instance Administration Tool or the Configuration Tool to administer online backup.

   3. Click the type of database you want to create. You can create a UCS Transformation Format (UTF-8) database, in which LDAP clients can store UTF-8 character data, or a local code page database, which is a database in the local code page.

      Create a universal database if you plan to store data in multiple languages in the directory. A universal database is also most efficient because less data translation is needed. If you want to use language tags, the database must be a UTF-8 database. For more information about UTF-8, see Appendix O. UTF-8 support.

   4. Click Next.
5. If you selected the Show advanced tablespace options check box, the Select database tablespace type window is displayed. In the window:
   1. In the Select database tablespace type field, DMS is selected. DMS tablespace support is used only for the USERSPACE1 and LDAPSPACE tablespaces. All other tablespaces, such as catalog and temporary tablespace, are of type SMS.

      If you select SMS instead, all other fields are disabled.

   2. In the USERSPACE1 tablespace details section of the window:
      1. In the Tablespace container field, click File if you want the USERSPACE1 tablespace to be located in a file system or Raw device if you want the USERSPACE1 tablespace created in a raw device. (A raw device is a device where no file system is installed, such as a hard disk that has no file system.)

         If the database tablespace container location is in a file system, a DMS cooked tablespace will be created. In this case, you can specify the initial size for the tablespace and an extendable unit size, and the tablespace will be automatically expanded if needed.

         If the database tablespace container location is in a raw device, a DMS raw tablespace will be created. In this case, the size of the database tablespace container is fixed and cannot be expanded. If you do this, specify the size along with the container location instead of accepting the default values.

      2. Do one of the following:
         • If you selected File in the Tablespace container field:
           1. In the Directory path field, specify the path where you want the USERSPACE1 tablespace created. You can click Browse to select the path.
           2. In the File field, type the file name where you want the tablespace created or accept the default file name, USPACE. (By default, the path and file name is: database_location/instance name/NODE0000/SQL00001/USPACE on AIX, Linux, and Solaris systems, or database_location\instance name\NODE0000\SQL00001\USPACE on Windows systems.)
         • If you selected Raw device in the Tablespace container field, type the location of the raw device in the Device path field. On Windows systems, this path must start with \\.\ (for example, \\.\device_name); on AIX, Linux, and Solaris systems, this must be a valid path.
         Note:
         in the Tablespace container field:

         • If you select File, the USERSPACE1 tablespace container will be the auto-incremental type, where you can provide the initial size (in the Initial size (Pages) field) and an extendable unit size (in the Extendable size (Pages) field). If you do not change these fields, the initial size defaults to 16K pages, and the extendable unit size defaults to 8K pages. (The page size for the USERSPACE1 tablespace is 4 KB per page.)
         • If you select Raw Device, the size of the USERSPACE1 tablespace container is fixed. The default size is 16K pages, but for best results, specify the size you want.
      3. In the Initial size (Pages) field, type the initial size for the USERSPACE1 tablespace or accept the default.
   3. In the LDAPSPACE tablespace details section of the window:
      1. In the Tablespace container field, click File if you want the LDAPSPACE tablespace to be located in a file system or Raw device if you want the LDAPSPACE tablespace created in a raw device. (A raw device is a device where no file system is installed, such as a hard disk having no file system.)
      2. Do one of the following:
         • If you selected File in the Tablespace container field:
           1. In the Directory path field, specify the path where you want the LDAPSPACE tablespace created. You can click Browse to select the path.
           2. In the File field, type the file name where you want the tablespace created or accept the default file name, which is database location/ldap32kcont_instance name/ldapspace.
         • If you selected Raw device in the Tablespace container field, type the location of the raw device in the Device path field. On Windows systems, this path must start with \\.\ (for example, \\.\device_name); on AIX, Linux, and Solaris systems, this must be a valid path.
         Note:
         in the Tablespace container field:

         • If you select File, the LDAPSPACE tablespace container will be the auto-incremental type, where you can provide the initial size (in the Initial size (Pages) field) and an extendable unit size (in the Extendable size (Pages) field). If you do not change these fields, the initial size defaults to 16K pages, and the extendable unit size defaults to 8K pages. (The page size for the LDAPSPACE tablespace is 32 KB per page.)
         • If you select Raw Device, the size of the LDAPSPACE tablespace container is fixed. The default size is 16K pages, but for best results, specify the size you want.
      3. In the Initial size (Pages) field, type the initial size for the LDAPSPACE tablespace or accept the default.
   4. In the Other properties section of the window, if you selected File in one or both of the Tablespace container fields, use the Extendable size (Pages) field to specify the number of pages by which the tablespace containers that are of type File will be expanded if needed.
   5. Click Finish.
6. Messages are displayed while the database is being configured. Click Close when database configuration is complete.

[ Top of Page | Previous Page | Next Page ]