Creating and populating the eMessage system tables manually
For eMessage, you must create additional system tables in the Campaign schema and then populate the tables with initial data. The Campaign installer automatically creates and populates the eMessage system tables in the Campaign schema if you select the option to create system tables automatically. However, if you do not select the option, you must create and populate the eMessage system tables manually.
Use your database client to run the appropriate script against the Campaign database.
Scripts for creating eMessage tables
HCL® provides the ace_op_systab scripts for creating eMessage tables in your local environment.
If your Campaign system tables are configured for Unicode, find the appropriate script in the ddl/unicode directory under your eMessage installation.
If your Campaign system tables are not configured for Unicode, use the non-Unicode scripts in the ddl directory under your eMessage installation. Use the following table to see the scripts that you must use:
Data source type | Script name |
---|---|
IBM DB2® |
ace_op_systab_db2.sql The user tablespace and system temporary tablespace where the system tables reside must each have a page size of 16K or greater. |
Microsoft™ SQL Server |
ace_op_systab_sqlsvr.sql |
Oracle |
ace_op_systab_ora.sql |
Scripts for populating eMessage tables
HCL provides the ace_op_populate_systab scripts for populating the eMessage tables in your local environment.
Use the following table to see the scripts that you must use:
Data source type | Script name |
---|---|
IBM DB2 |
ace_op_populate_systab_db2.sql |
Microsoft SQL Server |
ace_op_populate_systab_sqlsvr.sql |
Oracle |
ace_op_populate_systab_ora.sql |