Using the database wizard for DB2®

Use the database wizard to create databases for the IBM® Connections applications that you plan to install.

Before you begin

Before using the wizard for the first time, you must complete the steps described in the Preparing the database wizard for DB2® topic.

When you are creating a database either with the database wizard or SQL scripts, you must log into the system where the database is hosted with the database administrator account. The default values for DB2® are db2admin on Microsoft Windows, and db2inst1 on Linux and AIX®.

If you use only one database instance and if that instance includes other databases besides IBM® Connections, configure the numdb parameter to match the total number of databases on the instance. For more information, go to the numdb webpage in the DB2® information center.
Note: Before removing (or dropping) a database, stop Connections first to ensure that no database connection is in use; otherwise you will not drop the user and the database removal will not occur.

DB2® uses a user account called lcuser. If you are creating a DB2® database with SQL scripts, you must manually create the lcuser account on your operating system and then run the appGrants.sql script to grant the appropriate privileges to the lcuser account. When you use the database wizard, this script runs automatically. For more information, see the Creating a dedicated DB2® user topic.

  • If you are using Linux on IBM® System z® with the DASD driver, the SQL scripts are located in the connections.s390.sql/application_subdirectory directory of the IBM® Connections setup directory or installation media.
  • If you are using Linux on IBM® System z® with the SCSI driver, back up the connections.s390.sql directory and rename the connections.sql directory to connections.s390.sql.
  • (AIX® only) Download and install the following packages from the AIX® Toolbox for Linux Applications webpage:

    gtk2-2.10.6, pango-1.14.5, fontconfig-2.4.2, pkg-config-0.19, libjpeg-6b, freetype2-2.3.9, expat-2.0.1, zlib-1.2.3, xft-2.1.6, xcursor-1.1.7, glib-1.2.10, glib2-2.12.4, atk-1.12.3, gettext-0.10.40, libpng-1.2.32, and libtiff-3.8.2

    Note: Some of these packages have dependencies on other packages. The AIX® package installer alerts you to any additional packages that might be required.

About this task

Use the IBM® Connections database wizard to create, update, and remove databases.

You can review the scripts that the wizard executes by looking in the connections.sql directory in the installation media. On DB2®, the commands are shown in the log that the wizard creates.

To create databases with the wizard, complete the following steps:


  1. On Windows, you must perform DB2® administration tasks with full administrator privileges.
    1. Logged in as the instance owner, open a command prompt and change to the DB2® bin directory. For example: C:\Program Files\IBM\SQLLIB\BIN.
    2. Enter the following command: db2cwadmin.bat. This command opens the DB2® command line processor while also setting your DB2® privileges.
  2. From the IBM® Connections Wizards directory in a command line, enter the following command to launch the wizard:
    • AIX®: ./
    • Linux: ./
    • Microsoft Windows: dbWizard.bat
  3. Click Next to continue.
  4. Select the option to Create a database and click Next.
    Note: On the option selection panel, you can choose Export SQL commands list only. This option exports the create command list for you. It does not validate database connectivity or perform any create tasks.
  5. Enter the details of the database you wish to create and then click Next:
    1. Select a database type.
    2. Select the location of the database.
    3. Specify a database instance.
  6. Select an application and click Next.
    • If you are creating databases in this task, only applications that have not already been installed to a database instance are available. If you are updating databases, you can only choose applications that are already installed.
    • The News and Search databases are contained in the Home page database.
    • The Metrics application has some additional requirements:
      • If you select the Metrics application, you must also select the IBM® Cognos® application.
      • If you have already deployed Cognos® components and have a Cognos® Content Store available, you do not need to create another.
      • If you do create a Cognos® Content Store, only the container is created now; the tables are created when you start the Cognos® BI Server for the first time.
      • You do not need a dedicated database server for Cognos® or for the Metrics application; you can host the Metrics database and the Cognos® Content Store on the same database server as the other Connections databases.
      • Even if you do not plan to deploy Cognos® yet, you should create the Metrics database and the Cognos® Content Store now so that IBM® Connections can begin collecting event data immediately.
    • IBM Connections Content Manager requires two databases: Global Configuration Database and Object Store.
  7. Review the Pre Configuration Task Summary to ensure that the values you entered on previous pages in the wizard are correct. If you want to make a change, click Back to edit the value. Click Create to begin creating databases.

    The Show detailed database commands is enabled by default. It previews each SQL command before it is executed by the wizard. If you choose to save the commands, you must have write-access to the folder you choose to save them in.

    1. Click Next to see all the database scripts that are ready to be executed.
    2. Click Save As to save the commands.
    3. To run the commands listed, click Execute.
  8. Review the Post Configuration Task Summary panel and, if necessary, click View Log to open the log file. Click Finish to exit the wizard.
    Note: If the wizard returns an error indicating that it failed to create the Metrics database or encountered errors while creating it, see the following IBM® technote for assistance: Metrics database creation with error message and Cognos® cube build failed.

What to do next

(DB2® for Linux on System z® only.) To improve database performance, enable the NO FILE SYSTEM CACHING option. For more information, see the Enabling NO FILE SYSTEM CACHING for DB2 on System z topic.