To use IBM Cognos product documentation, you must enable JavaScript in your browser.

Change the Notification Database

By default, the notification server uses the same database that Content Manager uses for the content store. You can use a separate database for notification in situations where you run large volumes of batch reports and email.

Using a separate database for notification involves the following tasks:

      

Create a notification database.

For DB2, Oracle, Microsoft SQL Server, or Sybase, use the same procedure that was used to create the content store database, Guidelines for Creating the Content Store.

For DB2 on z/OS, use the instructions in Suggested Settings for Creating a DB2 Notification Database on z/OS.

      

Set up the database connectivity. You can use the same procedure as to set the connectivity for the content store database, Set Up Database Connectivity for the Content Store Database.

      

Change the connection properties for the notification database.

Suggested Settings for Creating a DB2 Notification Database on z/OS

The database you create for the notification database must contain some recommended configuration settings.

To ensure a successful installation, use the following guidelines when creating the notification database.

Use the following checklist to help you help you set up the notifications database in DB2 on z/OS.

      

Create a database instance, storage group, and a user account for the notification database.

A user must have permissions to create and delete tables in the database.

IBM Cognos 8 uses the credentials of the user account to communicate with database server.

      

Ensure you reserve a buffer pool with a page size of 32 k, and a second one with a page size of 4 k for the database instance.

      Administrators must run a script to create tablespaces to hold Large Objects and other data for the notification database to use the tablespaces. For information about running the script, see Create Tablespaces for the DB2 Notification Database on z/OS.
      

Your database administrator must back up IBM Cognos 8 databases regularly because they contain the IBM Cognos data. To ensure the security and integrity of databases, protect them from unauthorized or inappropriate access.

Create Tablespaces for the DB2 Notification Database on z/OS

A database administrator must run a script to create a set of tablespaces required for the notification database. The script must be modified to replace the placeholder parameters with ones that are appropriate for your environment.

Ensure that you use the naming conventions for DB2 on z/OS. For example, all names of parameters must start with a letter and the length must not exceed eight characters. For more information, see the IBM DB2 Information Center.

Steps
  1. Connect to the database as a user with privileges to create and drop tablespaces and to allow execution of SQL statements.

  2. Open the NC_TABLESPACES.sql script file and use the following table to help you to replace the placeholder parameters with ones appropriate for your environment.

    Not all of the parameters listed are in the script, but may be added in the future.

    Parameter Name

    Description

    NCCOG

    Specifies the name of the notification database.

    DSN8G810

    Specifies the name of the storage group.

    BP32K

    Specifies the name of the buffer pool.

  3. Save and run the script.

The notification database is created. You can now change the notification database in IBM Cognos Configuration, .

Change the Connection Properties for the Notification Database

After you create a separate database for notification, you must configure IBM Cognos 8 to use the new database.

You must configure all Content Managers and Application Tier Components to use the same notification database.

Steps
  1. In each location where Content Manager or Application Tier Components is installed, start IBM Cognos Configuration.

  2. In the Explorer window, under Data Access, click Notification.

  3. Identify the database that is used for notification:

  4. In the Properties window, enter the values for the notification database resource.

  5. From the File menu, click Save.

  6. Test the notification. In the Explorer window right-click Notification and click Test.

    IBM Cognos 8 tests the database connection and tests the mail server connection.

    If you have been using the content store database for notification, the schedules will be replicated in the tables of the new notification database.

Important: Ensure that the values used to identify the notification database resource are the same on all Content Manager and Application Tier Components computers. To use the default notification database, you do not have to edit the values in the Properties window.