A metric store is a database that contains content for metric packages. A metric store also contains scorecarding application settings, such as user preferences. You must create a metric store database using Oracle, Microsoft SQL Server, or DB2.
If you installed Cognos Content Database, it cannot be used as a metric store database.
Your database administrator must back up Cognos 8 databases regularly because they contain the Cognos data. To ensure the security and integrity of databases, it is also important to protect them from unauthorized or inappropriate access.
In the c8_location/configuration/schemas/cmm/sqlserver directory, run the cmm_create_db.cmd script by typing the following command:
path_to_script cmm_create_db host_namedatabase_nameuser_namepassword [user_to_create]
Use the following values in your command.
| Value | Setting |
| host_name | The name of the computer where the database will be created. |
| database_name | The name of the database that will be created. |
| user_name | The user ID with permissions to create the database. The user ID must have permission to create the database, such as the sa user. |
| password | The password for the username. |
| user_to_create | The user created by the script and given database owner permissions. This value is optional. |
Determine which user account Metric Studio will use to access the database.
The user account must be the database owner (dbo) or aliased to the database owner.
Ensure that you are logged into the Oracle server as a user that is a member of the ORA_DBA user group on Windows or the dba group on UNIX.
Set the NLS_LANG (National Language Support) environment variable to the UTF-8 character set on the metric store computer by typing the following command:
NLS_LANG = language_territory.character_set
NLS_LANG = AMERICAN_AMERICA.UTF8
NLS_LANG = JAPANESE_JAPAN.UTF8
The value of the variable determines the locale-dependent behavior of Cognos 8. Error messages, sort order, date, time, monetary, numeric, and calendar conventions automatically adapt to the native language and locale.
From the c8_location/configuration/schemas/cmm/oracle directory, run the cmm_create_db.cmd script by typing the following command:
path_to_script cmm_create_db sidpathdatabase_version [user_to_create]
Use the following values in your command.
| Value | Setting |
| path_to_script | The path to the script. For example, c8_location/configuration/schemas/cmm/oracle/ |
| sid | The SID for the new database that will be created. |
| path | The path where the data files will be created. |
| database_version | The version of Oracle software that is installed. For example, oracle9 or oracle10. |
| user_to_create | The user created by the script and given database owner permissions. This value is optional. |
Determine which user account Metric Studio will use to access the database.
If you included the optional user in the previous step, this is the user you will use to access the database. If you did not include a user, then you must use a valid Oracle database username with the following permissions granted:
CREATE TABLE, CREATE VIEW, CREATE PROCEDURE, CREATE TRIGGER, CREATE TYPE, CREATE SEQUENCE, and CREATE SESSION
EXECUTE on DBMS_LOCK and DBMS_UTILITY packages.
The CREATE TABLE and CREATE TRIGGER permissions must be granted directly to the user account rather than to a role.
Ensure that you are logged into the Oracle server as a user that is a member of the ORA_DBA user group on Windows or the dba group on UNIX.
Set the NLS_LANG (National Language Support) environment variable to the UTF-8 character set on the metric store computer by typing the following command:
NLS_LANG = language_territory.character_set
Examples are:
NLS_LANG = AMERICAN_AMERICA.UTF8
NLS_LANG = JAPANESE_JAPAN.UTF8
The value of the variable determines the locale-dependent behavior of Cognos 8. Error messages, sort order, date, time, monetary, numeric, and calendar conventions automatically adapt to the native language and locale.
Determine which user account Metric Studio will use to access the database. You must use a valid Oracle database username with the following permissions granted:
CREATE TABLE, CREATE VIEW, CREATE PROCEDURE, CREATE TRIGGER, CREATE TYPE, CREATE SEQUENCE, and CREATE SESSION
EXECUTE on DBMS_LOCK and DBMS_UTILITY packages.
The CREATE TABLE and CREATE TRIGGER permissions must be granted directly to the user account rather than to a role.
In the c8_location/configuration/schemas/cmm/db2 directory, run the cmm_create_db.cmd script by typing the following command:
On Windows, type
cmm_create_db dbinstanceuser_namepassworddbname drivedbalias
On UNIX, type
cmm_create_db.sh dbinstanceuser_namepassworddbname drivedbalias
Use the following values in your command.
| Value | Setting |
| dbinstance | The DB2 instance name where the database will be created. |
| user_name | The user ID with permissions to create the database. The user ID must have SYSADM or SYSCTRL privileges, and must have DBADM privileges to create the schema. |
| password | The password for the username. |
| dbname | The name of the database that will be created. The name must have a maximum of 8 characters, and it cannot start with a number. |
| drive/path | On Windows, the drive on which the database objects will be created. On UNIX, the path where the database objects will be created. |
| dbalias | The database alias name. This value is optional. |
Note: Your database administrator can review the scripts to ensure they suit your environment. The initializedb.db2 script is invoked by the cmm_create_db.cmd script and defines the buffer pools and tablespaces.
Determine which user account Metric Studio will use to access the database.
The user account must have DBADM privileges.
Note: If your DB2 server is an earlier version than 8.2, and compiles stored procedures using a platform-specific, third party C compiler, the compiler must be installed on each DB2 server computer used to the metric store.