Pro2 offers the following types of scheduled jobs that help manage and facilitate data replication:
  • Applied Queue Record Purge—Removes previously applied records from the replication queue. This is necessary to maintain the efficiency and performance of the replication system.
  • CDC Purge—Removes records from the CDC tracking table that have already been processed and applied to the target database.
    Note: The CDC_PURGE_DAYS property on the Properties tab of the Pro2 Administration Utility determines how many days the purge will skip. By default, it is set to 10 and skips records created within the last 10 days. Set the CDC_PURGE_DAYS property to 0 to delete all CDC records associated with Pro2 that have already been marked as applied.

  • CDC Threads—Schedules the start of the CDC Thread. The CDC thread monitors the change tracking table in the source database and transfers those records into replqueue records, ensuring data is up-to-date and consistent.

  • Enterprise Push—Data does not automatically transfer between the Enterprise View instance and the other Pro2 instances after you establish the connection. You must schedule an Enterprise Push job. The Pro2 instance has the ability to push data, metrics, and reports from one instance to the Enterprise View instance.

    For more information on how to schedule an Enterprise Push job, see Set Up Pro2 Enterprise View.

  • File Purge—Removes unnecessary or older log files from the Pro2 install directory. The job runs automatically at specified times, freeing up the disk space. It is recommended to schedule the job regularly, back up purged records, monitor job performance, and periodically adjust purge parameters based on data growth and system performance.
    Note: All entries for current changes that have not yet been applied to the target are lost when the replication queue is purged. A bulk load may be necessary for the affected tables.

  • Replication Log Check—Scans all the log files for any errors and reports them through an email. If you are running this functionality for the first time, a ErrorTrigger.lst file is created (available in the bprepl/repl_tmpl directory with an empty skeleton.). Add the error list that needs to be scanned or excluded in ErrorTrigger.lst, separated by commas. This feature scans all the log files, excluding the unwanted errors, and then sends an error report in an email.

  • Replication Threads—Schedules the start of the Replication Thread. The Replication Thread monitors the replqueue table in the repl database and transfers corresponding source records into the target database, ensuring data integrity and consistency.

  • Replication-CDC Threads—Schedules the start of the Replication-CDC Thread. The Replication-CDC thread monitors the change tracking table in the source database and directly transfers corresponding source records into the target database, bypassing the replqueue table in theinterim.

  • Status Check—Provides the queue count per thread and sends an email notification with the achieved results. This job uses the STATUS_CHECK_MAXQUEUECNT property to limit the total number of records. However, it lacks the functionality to indicate whether a thread exceeds a specific threshold of records.

For more information on how to schedule a job in Pro2, see How to schedule jobs in Pro2.