Skip to main content

Cleaning the Paid Media master table on successful migration

Suggest edit
Updated on December 20, 2021

This content applies only to On-premises and Client-managed cloud environments

After a successful migration of customer audience sync data, clean the Paid Media master table and associated artifacts to remove unnecessary data and free up space. By cleaning up the Paid Media master table, you ensure that your system runs smoothly.

Note: This instruction applies only if you use Paid Media Manager.
Pega Customer Decision Hub Update Guide
  1. Log on as an operator with access to Dev Studio.
  2. In the header of Dev Studio, click ConfigureSystemOperationsLogs.
  3. Confirm that the migration was successful:
    1. Click Log files and open the PegaRULES.log.
      The log contains the following lines:
      • CDH Data Upgrade - Number of records to be migrated from mkt_paidmedia_master RDBMS:XYZ
      • CDH Data Upgrade - Number of records migrated to PaidMediaMasterDDS:ABC
    2. Compare the XYZ and ABC values.
      If XYZ is equal to ABC, the migration was successful and you can now trigger the CleanUpPMMMasterAfterUpgrade activity to clean the master table and associated artifacts.
      Note: XYZ and ABC represent the number of records processed or migrated.
  4. In the header of Dev Studio, in the search box, enter and search for the CleanUpPMMMasterAfterUpgrade activity.
  5. Clean the master table and associated artifacts:
    1. Open the CleanUpPMMMasterAfterUpgrade activity, and then click ActionRun.
    2. The activity is complete if you see the following message: Success. The operation completed successfully.
  • Previous topic Enabling the Paid channel in Next-Best-Action Designer
  • Next topic Configuring the PaidMediaSync queue processor to optimize performance
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us