Pre-installing the metadata repository database in a Db2 database system by using scripts (AIX Linux®)

You can use an existing installation of a Db2® database to create a metadata repository for InfoSphere® Information Server.

About this task

The scripts run the following commands when configuring the Db2 database system. These changes affect all databases in the Db2 instance:
db2set Db2.INLIST_TO_NLJN=YES
db2set Db2.USE_ALTERNATE_PAGE_CLEANING=ON
db2set Db2.REDUCED_OPTIMIZATION=YES

Procedure

  1. Navigate to the install_dir\DatabaseSupport directory of the InfoSphere Information Server installation media, where install_dir is the directory where you extracted the InfoSphere Information Server installation media.
    Database version Directory
    Db2 11.1 install_dir\DatabaseSupport\UNIX_Linux\MetadataRepository\DB2_LUW_11_1
  2. Open the create_xmeta_db.sql script file in a text editor and make the following changes to the file:
    Important: IBM certifies and validates InfoSphere Information Server using the provided database creation scripts. If you modify the scripts beyond the changes that are specified here, IBM will not support software failures that might result from the modifications. Modifications to these scripts that do not have a functional impact might require that you make similar changes in the future to scripts that are generated by other administrative tools that depend on the information in the scripts here. You are responsible for making those changes.
    1. Replace all occurrences of @DATABASE_NAME@ (including the @ symbols) with the name of the database that you want to create.
      For example, replace @DATABASE_NAME@ with your database name:
      xmeta
    2. Replace all occurrences of @INSTALL_ROOT@ (including the @ symbols) with the path to the root directory where your Db2 database is installed.
      For example, replace @INSTALL_ROOT@ with the path to the root directory for your Db2 database:
      /home/db2inst1/db/xmeta
    3. Replace all occurrences of @DATABASE_ALIAS@ (including the @ symbols) with the name of the database that you want to create.
      For example, replace @DATABASE_ALIAS@ with your database name:
      xmeta
    4. Replace all occurrences of @DATABASE_USERNAME@ (including the @ symbols) with the name of the operating system user that you want to have access to the database.
      For example, replace @DATABASE_USERNAME@ with the operating system user name:
      xmeta
  3. Run the operating system script to invoke the SQL script:
    1. Log on as the Db2 instance owner.
    2. Change to the directory where the edited script is located, and run the following command:
      create_xmeta_db.sh [logfile]
      logfile is the name of the file where you want to save the results of running the command. This argument is optional.
  4. Open the db2_grant_Permissions.sql file in a text editor and make the following changes:
    1. Replace all occurrences of @DATABASE_NAME@ (including the @ symbols) with the name of the database that you created.
      For example, replace @DATABASE_NAME@ with your database name:
      xmeta
    2. Replace all occurrences of @DATABASE_USERNAME@ (including the @ symbols) with the name of the user that you want to grant access to the staging area schema. This user must be different from the operating system user that you specified in the create scripts.
      For example, replace @DATABASE_USERNAME@ with the user name for the staging area schema:
      xmetasr
  5. Run the operating system script to invoke the SQL script:
    1. Log on as the Db2 instance owner.
    2. Change to the directory where the edited script is located, and run the following command:
      configure_staging_area.sh [logfile]

      logfile is the name of the file where you want to save the results of running the command. This argument is optional.

  6. If you use Db2 diagnostics, run the following command to set the Db2 Database Monitor Heap size to 192 or greater:
    Note: The Db2 Database Monitor Heap is used for various database event monitors and snapshots. These monitoring tools do not work under the default size setting. See https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.config.doc/doc/r0000306.html.
    db2 update dbm cfg using MON_HEAP_SZ 192 immediate
  7. If you are using IBM® DataStage® Flow Designer, you must create the user preference table to store the user settings. For information on creating the user preference table, see the README document in the directory install_dir\DatabaseSupport\UNIX_Linux\CognitiveDesignerRepository\DB2_LUW_11_1.