Initialize the Centralized Log Database
ImportantIf you are setting up the Log Database for use in a multi-language environment, refer to the Framework Database Connectivity Reference Guide for additional information.
- A DBMS is installed, and a blank database has been created.
- Message Server is installed and running.
Start of procedure
- In your DBMS interface, go to the directory in which Message Server is installed and open the scripts folder.
- Open the folder that matches your database type.
- Load and execute the scripts that correspond to your DBMS, as provided in the following table.
- Note: Starting in release 8.5.1, the initialization scripts init_<DBMS>.sql and init_multilang_<DBMS>.sql no longer drop existing tables and procedures as part of initializing the Log Database. If you have to re-run an initialization script against an existing Log Database, make sure that you first run the script drop_tables_<DBMS>.sql.
DBMS Drop Tables Script
Initialization Script Multi-language Initialization Script a DB2 drop_tables_db2.sql init_db2.sql init_multilang_db2.sql Microsoft SQL drop_tables_mssql.sql init_mssql.sql init_multilang_mssql.sql b Oracle drop_tables_oracle.sql init_oracle.sql init_multilang_oracle.sql PostgreSQL drop_tables_postgre.sql init_postgre.sql Not required Notes:
a. Use the multi-language scripts if you are setting up your Centralized Log system in multi-language mode. Make sure that the Log Database is created with settings that allow for use in multi-language environments. Refer to the Framework Database Connectivity Reference Guide for recommented settings for your database.
b. A multi-language MS SQL database uses UCS-2 encoding instead of UTF-8 encoding. You must set utf8-ucs2=true in the [dbclient] section in the annex of the corresponding Database Access Point. Refer to the Framework Configuration Options Reference Manual for more information about this option.
This page was last modified on November 4, 2016, at 12:38.