Creating and populating reporting tables for Campaign
You can use SQL scripts to create and populate reporting tables for Campaign. Reports uses reporting tables to extract reportable data.
1.
2.
3.
4.
5.
For Campaign with a DB2® database, increase the DB2® heap size to 10240 or higher. The default heap size is 2048. Use the following command to increase the heap size:
db2 update db cfg for databasename using stmtheap 10240
where databasename is the name of the Campaign database.
Increasing the heap size ensures that IBM® Cognos® does not display SQL error messages if a user selects all the campaigns when running a report such as the Financial Summary report.
6.
Locate the db/calendar subdirectory in the Marketing Platform installation directory and find the ReportsCalendarPopulate script that is appropriate for the database type.
The ReportsCalendarPopulate script creates the following tables:
*
*
7.
Run the ReportsCalendarPopulate script on the new database that you created with the table creation script.
8.
For DB2® only, complete one of the following tasks:
*
db2 -td@ -vf ReportsCalendarPopulate_DB2.sql
*
If you use the DB2® client interface, change the termination character to the @ character in the Statement termination character field.
9.
*
Setting up data synchronization
Make sure that you use scheduled Extraction, Transformation, and Load (ETL) method, or any custom method to schedule regular data synchronization between the production databases of the IBM® EMM application and the new reporting tables.