Installing the DB2® database client for Cognos® Transformer

Install the IBM® DB2® database client on the computer where you will host IBM® Cognos® Business Intelligence.

Before you begin

Before you install the database client, the database server must be installed and running, and you must have created the Metrics database and the Cognos® Content Store database.

About this task

To install the DB2® database client for Cognos® Transformer, complete the appropriate steps for your operating system:

Installing the DB2® database client for Cognos® Transformer on AIX and Linux

Procedure

  1. Install the database client on the server where you will deploy Cognos® Business Intelligence, using the instructions provided with your database product.
    For instructions on installing the IBM® DB2® client, see the Installation methods for IBM® data server clients in the DB2® information center.
  2. Linux™ only: Ensure that the DB2® client library is properly sourced:
    1. Open the /etc/ld.so.conf file for editing.
    2. Add the following library DB2_installation_directory/lib32 to the file.
      Use the path where DB2® is installed; for example: .
      /usr/X11R6/lib64/Xaw3d
/usr/X11R6/lib64
/usr/lib64/Xaw3d
/usr/X11R6/lib/Xaw3d
/usr/X11R6/lib
/usr/lib/Xaw3d
/usr/x86_64-suse-linux/lib
/usr/local/lib
/opt/kde3/lib
/lib64
/lib
/usr/lib64
/usr/lib
/usr/local/lib64
/opt/kde3/lib64
/opt/ibm/db2/V10.1/lib32
include /etc/ld.so.conf.d/*.conf
    3. Save and close the file.
    4. Run the ldconfig command to regenerate dynamic link libraries (DLLs).
  3. Create a connection between the client and the database. To do so, follow these steps:
    1. Connect the client to the node (the DB2® server) where the database is hosted.
      1. Log on to the client computer as a user with at least DB2® SYSADM authority. You cannot catalog a node as a root authority.
      2. Change to the home directory of instance. The following steps refer to this directory as INSTHOME.
      3. Set up the instance environment by running the startup script. Note that INSTHOME indicates the home directory of the instance.

        bash, Bourne, or Korn shell: . INSTHOME/sqllib/db2profile

        C shell: source INSTHOME/sqllib/db2cshrc

      4. Open the DB2® command line processor: db2
      5. Catalog the DB2® server. To do so, enter the following commands:
        db2 => catalog tcpip node node_name remote Host_name|IP_address
       server Service_name|DB2_Instance_Port

db2 => terminate
        Where:
        • node_name indicates a local nickname (for example, the short host name) that you can set for the DB2® server.
        • Host_name|IP_address indicates the host name or IP address of the server instance where the database resides (both IPv4 and IPv6 addresses are accepted).
        • Service_name|DB2_Instance_Port indicates the service name or DB2® instance port used for the connection (typically port 50000 for DB2®).
        For example, catalog the server as node "db2node" with the IP address "2001:DB8:0:0:0:0:0:0" on port 50000 as follows: 
        db2 => catalog tcpip node db2node remote 2001:DB8:0:0:0:0:0:0 server 50000
DB20000I  The CATALOG TCPIP NODE command completed successfully.
DB21056W  Directory changes may not be effective until the directory cache is refreshed.

db2 => terminate
DB20000I  The TERMINATE command completed successfully.
    2. Connect the client to the DB2® database itself. To do so, run the following commands in the DB2® command line processor:
      db2 => catalog database Database_name as Database_alias at node node_name

db2 => connect to Database_alias user Metrics_db_user

db2 => terminate
      Where node_name is the same local nickname that you used to connect to the DB2 server earlier in step 3.a.v, and the database information matches the values specified in the cognos-setup.properties file that is used during installation:
      • Database_name indicates the name of the Metrics database. The name should be "Metrics" when it is created by Connection database install wizard (the metrics.db.name setting; the default value is METRICS).
      • Database_alias indicates the alias for the Metrics database (the metrics.db.local setting; the default value is METRICS).
      • Metrics_db_user indicates the user name that will be used to access the database (the metrics.db.user setting; the default value is LCUSER).
      For example, catalog the METRICS database as "METRICS" on the server "db2node" as the user "LCUSER" and then test the connection with the following commands:
      db2 => catalog database METRICS as METRICS at node db2node
DB20000I  The CATALOG DATABASE command completed successfully.
DB21056W  Directory changes may not be effective until the directory cache is refreshed.

db2 => connect to METRICS user LCUSER
Database Connection Information     
Database server = DB2 10.1.0     
SQL authorization ID = LCUSER     
Local database alias = METRICS

db2 => terminate
DB20000I  The TERMINATE command completed successfully.

    For more information on connecting the DB2® client to the DB2® server and database (including optional arguments), see Configuring client-to-server connections using the command line processor in the DB2® information center.

Installing the DB2® database client for Cognos® Transformer on Windows

Procedure

  1. Install the database client on the server where you will deploy Cognos® Business Intelligence, using the instructions provided with your database product.
    For instructions on installing the IBM® DB2® client, see the Installation methods for IBM® data server clients in the DB2® information center.
  2. To create a connection between the client and the database, follow these steps:
    1. Connect the client to the node (the DB2® server) where the database is hosted.
      1. Log on to the client computer as a user with at least DB2® SYSADM authority. You cannot catalog a node as a root authority.
      2. Change to the home directory of instance. The following steps refer to this directory as INSTHOME.
      3. Open the DB2® command line processor: 
        db2cmd
db2
      4. Catalog the DB2® server. To do so, enter the following commands:
        db2 => catalog tcpip node node_name remote Host_name|IP_address
       server Service_name|DB2_Instance_Port

db2 => terminate
        Where:
        • node_name indicates a local nickname (for example, the short host name) that you can set for the DB2® server.
        • Host_name|IP_address indicates the host name or IP address of the server instance where the database resides (both IPv4 and IPv6 addresses are accepted).
        • Service_name|DB2_Instance_Port indicates the service name or DB2® instance port used for the connection (typically port 50000 for DB2®).
        For example, catalog the server as node "db2node" with the IP address "2001:DB8:0:0:0:0:0:0" on port 50000 as follows: 
        db2 => catalog tcpip node db2node remote 2001:DB8:0:0:0:0:0:0 server 50000
DB20000I  The CATALOG TCPIP NODE command completed successfully.
DB21056W  Directory changes may not be effective until the directory cache is refreshed.

db2 => terminate
DB20000I  The TERMINATE command completed successfully.
    2. Connect the client to the DB2® database itself. To do so, run the following commands in the DB2® command line processor:
      db2 => catalog database Database_name as Database_alias at node node_name

db2 => connect to Database_alias user Metrics_db_user

db2 => terminate
      Where node_name is the same local nickname that you used to connect to the DB2 server in step 2.a.iv, and the database information matches the values specified in the cognos-setup.properties file that is used during installation:
      • Database_name indicates the name of the Metrics database. The name should be "Metrics" when it is created by Connection database install wizard (the metrics.db.name setting; the default value is METRICS).
      • Database_alias indicates the alias for the Metrics database (the metrics.db.local setting; the default value is METRICS).
      • Metrics_db_user indicates the user name that will be used to access the database (the metrics.db.user setting; the default value is LCUSER).
      For example, catalog the METRICS database as "METRICS" on the server "db2node" as the user "LCUSER" and then test the connection with the following commands:
      db2 => catalog database METRICS as METRICS at node db2node
DB20000I  The CATALOG DATABASE command completed successfully.
DB21056W  Directory changes may not be effective until the directory cache is refreshed.

db2 => connect to METRICS user LCUSER
Database Connection Information     
Database server = DB2 10.1.3     
SQL authorization ID = LCUSER     
Local database alias = METRICS

db2 => terminate
DB20000I  The TERMINATE command completed successfully.

    For more information on connecting the DB2® client to the DB2® server and database (including optional arguments), see Configuring client-to-server connections using the command line processor in the DB2® information center.