Syncing P6 On-Premises Data to Cloud Using Only Incremental Sync

If you chose to only run incremental sync and skip the initial sync with database restoration:

  1. Update the database exported timestamp in the sync_control table of T_SYNCUSER schema and post the config.

    Data is loaded into sync_config, sync_control, sync_whitelist, and sync_transfer_data tables.

  2. Ensure data is loaded to the sync_control table in T_SYNCUSER schema.
  3. Check for rows with ENTRY_NAME = next.timestamp and safe.timestamp.
  4. After data loaded to sync_control table, stop the Jetty server: ./stopserver.sh
  5. Execute the following query to update the next timestamp value and commit.

    update sync_control set entry_value=<DATA BASE EXPORTED TIMESTAMP> where entry_name='next.timestamp';

    Note: Timestamp format should be in 'YYYY-MM-DD HH:MM:SS'

  6. Restart the Jetty server: ./startserver.sh -u

    This process will fetch only those records from the paudit table in the source schema which are updated after the database exported timestamp.

Related Topics

Syncing P6 Data from On-Premises to Cloud

Prerequisites

Configuring the Sync Environment for P6 EPPM On-Premises to Cloud



Legal Notices | Your Privacy Rights
Copyright © 2016, 2020

Last Published Wednesday, October 20, 2021