Step: Create and populate the Campaign system tables manually, if necessary

By default, the Campaign installer automatically creates and populates the necessary system tables for operation. However, if your database policies do not allow the installer to automatically perform this step, or if for some other reason you chose during installation to perform this step manually, you must complete the instructions here before you can use Campaign.

If you plan to enable eMessage, you must also manually create and populate the eMessage system tables if the installer did not do so automatically. For details, see Create and populate the eMessage system tables manually, if necessary.

If you selected the Campaign System Table DDL Files option on the Campaign Components page during installation, the IBM® installer installs a collection of SQL scripts that you can use to create and populate the Campaign system tables. The SQL scripts are installed in the ddl directory under your installation of the Campaign server. If your system tables are configured for Unicode, the appropriate scripts are in the ddl/unicode directory under your Campaign installation.

To use the SQL scripts, run your database client to apply the scripts to the database or schema that holds the Campaign system tables. See the documentation for your database software for instructions on running SQL scripts.

The following tables list the SQL scripts that are provided for you to use to create and populate the Campaign system tables manually.

Scripts for creating Campaign system tables
Data source type	Script name
IBM® DB2®	ac_systab_db2.sql
Microsoft™ SQL Server	ac_systab_sqlsvr.sql
Oracle	ac_systab_ora.sql

Scripts for populating Campaign system tables
Data source type	Script name
IBM® DB2®	ac_populate_tables_ db2.sql
Microsoft™ SQL Server	ac_populate_tables_ sqlsvr.sql
Oracle	ac_populate_tables_ ora.sql

Create and populate the eMessage system tables manually, if necessary