144 Deployment Guide Series: IBM Tivoli Configuration Manager
After running the admin scripts, you can run the schema scripts, as described in
the following section.
4.4.2 Running the schema scripts
The schema scripts create the tables and views in the allocated tablespaces and
they must be run with the user owner of the database and not with the user
owner of the instance. The following list describes the schema scripts:
mdist_db2_schema.sql
Installs the mdist2 repository schema and defines its
tables and views.
inv_db2_schema.sql
Installs the inv_db repository schema and defines its
tables and views.
h_inv_db2_schema.sql
Installs the Inventory history tables for the configuration
repository. (This script is optional. It must be run after the
inv_db2_schema.sql script.)
plans_db2_schema.sql
Installs the planner repository schema and defines its
tables and views.
Important: If you are creating one database for each product, you must
change the admin script ccm_db2_admin.sql, because there is an error
on it. If you create the database ccm_db, you must change the
database name ccm to ccm_db in the update lines ccm_db:
Original file:
-- logfile size in in 4k pages. Total log space is 16MB
UPDATE DATABASE CONFIGURATION FOR ccm USING LOGFILSIZ 1024;
UPDATE DATABASE CONFIGURATION FOR ccm USING LOGPRIMARY 2;
UPDATE DATABASE CONFIGURATION FOR ccm USING LOGSECOND 2;
Changed file:
-- logfile size in in 4k pages. Total log space is 16MB
UPDATE DATABASE CONFIGURATION FOR ccm_db USING LOGFILSIZ 1024;
UPDATE DATABASE CONFIGURATION FOR ccm_db USING LOGPRIMARY 2;
UPDATE DATABASE CONFIGURATION FOR ccm_db USING LOGSECOND 2;
This change is not necessary if you selected the integrated database
named cm_db.
Chapter 4. Installation of IBM Tivoli Configuration Manager in a large enterprise 145
pristine_db2_schema.sql
Installs the pristine repository schema and defines its
tables and views.
ccm_db2_schema.sql
Installs the ccm repository schema and defines its tables
and views.
The preceding schema scripts are in the following directories after the Tivoli
Configuration Manager V4.2.2 installation:
򐂰 Distribution Status:
$BINDIR/TME/MDIST2/sql/mdist_db2_schema.sql
򐂰 Inventory:
$BINDIR/../generic/inv/SCRIPTS/RDBMS/inv_db2_schema.sql
$BINDIR/../generic/inv/SCRIPTS/RDBMS/h_inv_db2_schema.sql
򐂰 Activity Planner:
$BINDIR/TME/APM/SCRIPTS/plans_db2_schema.sql
򐂰 Change Manager:
$BINDIR/TME/CCM/SCRIPTS/ccm_db2_schema.sql
򐂰 Pristine:
$BINDIR/TME/PM/SCRIPTS/pristine_db2_schema.sql
The next step is to run the schema scripts. To do that, copy all the schema scripts
to the home directory of the database owner user and perform the following
steps.
1. Log in to AIX 5L where the DB2 client is installed as the instance owner user.
2. Start DB2 by running the db2start command, if necessary.
3. Run the following for each database:
a. Connect to the database with the owner of the database and not with the
owner of the instance:
db2 connect to <db_name> user remote_db_user using remote_db_password
b. Run the script according to the database connected:
db2 -f <script_name> -o -t -z <script_name>.log
At this point, your RDBMS is configured.
Note: The database owner user must be the same one used in 4.3.2, “The
server installation” on page 114 when the RIM objects were defined.

Get Deployment Guide Series: IBM Tivoli Configuration Manager now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.