Configure database load utility

A large component of an Optimize session is reading data from the PCT and writing data to the OCT. Configuring a database load utility improves the performance of your Optimize sessions.

Optimize uses the same configuration settings as Campaign for implementing a database load utility. If you configure Campaign to work with a database load utility, you configure Optimize to use the same commands. Similarly, if you configure Optimize to work with a database load utility, you are configuring Campaign to work with a database load utility. Each assumes a different root directory, /Campaign for Campaign or /Optimize for Optimize, so you can specify different commands in the loader command and template files.

A database load utility also improves performance when populating PCT tables with an Campaign flowchart.

When you configure a database load utility to work with Optimize, it behaves as described for the following Optimize tables:

PCT table-If the number of unique customers is greater than or equal to the MinReqForLoaderCommand or MinReqForLoaderCommandForAppend, Optimize uses the database load utility.

POA table-Optimize uses the database load utility irrespective of the values for MinReqForLoaderCommand or MinReqForLoaderCommandForAppend.

OCT table-Optimize uses the database load utility irrespective of the values for MinReqForLoaderCommand or MinReqForLoaderCommandForAppend.

RC table-Optimize uses the database load utility irrespective of the values for MinReqForLoaderCommand or MinReqForLoaderCommandForAppend.

To configure a database load utility for Optimize complete the following steps.

Complete the database load utility configuration in the Campaign partitions as described in the Campaign documentation.

Confirm that the Optimize installation has the database load utility command in the same location as Campaign.

For example, if LoaderCommand is /app/Unica/Campaign/partitions/partition1/scripts/load.sh, you must copy load.sh to /app/Unica/Optimize/partitions/partition1/scripts on your Optimize server, creating the directories if necessary.

Confirm that the Optimize installation has the control file template for the database load utility in the same location as Campaign.

The file defined by Campaign | Partitions | PartitionN | DataSources | DataSourceName | LoaderControlFileTemplate must exist on both the Campaign and Optimize servers. The control file template must be located in the same relative directory. On the Campaign server, the file must be relative to /Campaign, for example, /Campaign/partitions/partition1/scripts. On the Optimize server, the files must be relative to /Optimize for example /Optimize/partitions/partition1/scripts.

On UNIX™ systems, use soft or symbolic links to create the control file templates in the Optimize directories. For example, from the /Optimize/partitions/partition1/scripts directory, run the following command: