Running Incremental Sync
If you are skipping the initial sync with data base restoration and running only the incremental sync, you must update the the data base exported timestamp in the sync control table of T_SYNCUSER schema (source.db.syncuser). After posting the config, data gets loaded to sync_config, sync_control, sync_whitelist and sync_transfer_data tables.
- Check that data is loaded to the sync_control table in T_SYNCUSER schema (source.db.syncuser).
- Check for rows with ENTRY_NAME = next.timestamp and safe.timestamp.
- After the data is loaded to sync_control table, stop the Jetty server.
./stopserver.sh
- 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: The timestamp should be in the format, YYYY-MM-DD HH:MM:SS.
- Restart the Jetty server.
./startserver.sh -u
Note: This process will fetch only those records from paudit table in the source schema which are updated after the database exported timestamp.
Related Topics
Synchronizing P6 Data Between On-Premises and Cloud
Setting Up the Sync Client Application
P6 EPPM On-Premises System Architecture for CIC
Sync Client Installation Prerequisites
Importing Security Certificates to Java Environment
Option 1: Installing Sync Client in the User Interface Mode
Option 2: Installing Sync Client in the Command Mode
Last Published Thursday, December 7, 2023