Synchronization Process

You always initiate the synchronization process from the target server, which is the server that contains the mirror cubes. You must have administrator authority for this server to initiate the synchronization process.

You can synchronize on demand or schedule the synchronization process to be automatic.

TM1® updates the data in all the mirror cubes that are part of the same replication connection. You cannot specify individual cubes to update.
TM1 also updates the replicated dimensions if you made changes to their definitions and rules.
TM1 always writes updates from the source cubes to the mirror cubes.
TM1 does the following with updates you make to the mirror cube:
- Writes the updates back to the source cube, if the updates were made by users with Reserve access to the source cube.
- Does not write the updates back to the source cube, if the updates were made by users with Read or Write access to the source cube.
TM1 uses the transaction log files to keep track of the changes made to the source and mirror cubes. During the synchronization process, TM1 uses the log files to determine which updates to make.
- If you are performing a synchronization process, transaction logging must be enabled for the mirror cubes on the target server that are part of the replication and synchronization process.
- If you are performing a bi-directional synchronization, transaction logging must be enabled for all the related cubes on both the source and target servers.
To verify that transaction logging is enabled, see Enabling and Disabling Transaction Logging in the IBM® Cognos® TM1 Operation Guide.

If there is an update conflict for a particular cell, TM1 uses the most recent update, no matter where this update was made (that is, in the source cube or the mirror cube).

When a synchronization occurs, either as the result of a scheduled chore or manual execution, a log file that records all the actions that occur during the synchronization is created in the logfiles directory on the target TM1 server. The synchronization log file is named TM1ReplicationLog_<time stamp>_<source server>.log. For example, TM1ReplicationLog_20140308035140_SData.log.

The synchronization log records the time at which each action within the synchronization occurs, the name of the user who established the synchronization, and a brief description of the action.

20140308041525 [Admin] => Synchronization to "Planning Sample" started.
20140308041525 [Admin] => Current R&S values: LastSyncTime=20140308041233 
LastSyncTimeMaster=20140308041233 LastSyncStarRecord=20140308040749.  
20140308041525 [Admin] => Start: Replication of objects not yet copied.  
20140308041525 [Admin] => End: Replication of objects not yet copied.  
20140308041526 [Admin] => Replicating dimension "plan_version".
20140308041526 [Admin] => Synchronizing cube: (P)"plan_BudgetPlan" => (S)"plan_BudgetPlan" 
20140308041526 [Admin] => WARNING: No changes found in Planet server.
20140308041526 [Admin] => Synchronization of cube "plan_BudgetPlan" completed: Star <= 0
20140308041526 [Admin] => Synchronizing cube: (P)"promotions" => (S)"promotions" 
20140308041526 [Admin] => Synchronization of cube "promotions" completed: Star <= 12
20140308041528 [Admin] => Synchronizing cube: (S)"plan_BudgetPlan" => (P)"plan_BudgetPlan" 
20140308041528 [Admin] => WARNING: No changes found in Star server.
20140308041528 [Admin] => Synchronization of cube "plan_BudgetPlan" completed: Planet <= 0  
20140308041528 [Admin] => Synchronizing cube: (S)"promotions" => (P)"promotions" 
20140308041528 [Admin] => Synchronization of cube "promotions" completed: Planet <= 30  
20140308041530 [Admin] => Synchronization to "Planning Sample" completed. 
LastSyncTime=20140308041527 LastSyncTimeMaster=20140308041526 
LastSyncStarRecord=20140308041234.