Notes and restrictions

Notes

Distributed connection is interrupted

If there is a interruption to the distributed connection during the synchronization, the synchronization can not be completed. In this case, a "FAILED" message will be sent to the master system. The clients won't get this message. As soon as the connection is reestablished, the master system can initiate a new synchronization.

No distributed connection to the master system and the client configuration is deleted on the client system

In this case (if the client is still assigned to the master) the configuration will be sent again to the client as soon as the connection is reestablished. The deletion of the client configuration will be canceled!

Redundancy

If there is a redundancy changeover during the synchronization, the synchronization will be restarted after the changeover.

Logfile

The synchronization history is saved on the internal data point _DistSync.Historical as well as in the "distsync_Log.txt" logfile under "<WinCC_OA_Proj>\log" on the master system.

Control script is not running

In case that the control script distSyncMan.ctl nis not running but a comparison or synchronization is triggered, the following warning is displayed:

One Way Dist

If there is a One Way Dist connection between master and client (the client cannot see the master), the handshake is automatically disabled for this client. Therefore, no confirmation is necessary for this synchronization and the synchronization result panel is displayed on the client. The handshake cannot be enabled for this client. If you click on the handshake checkbox the following warning is displayed:

Distsync DP Types

DP types required for Distsync must be already defined on the client system of a Dist system in order for the synchronization to work.

Restrictions

  • A master system contains its own clients but cannot share them with other masters.

  • Alert colors must be synchronized manually.

  • Alert classes: for synchronizing CTRL functions you have to synchronize the libs manually.

  • Alert screen table config: for synchronizing UserDef functions, the files must be synchronized as well.

  • RDB Compression and statistical compression steps are not synchronized.

  • Changing the comments and alias in the Oracle database is only possible with a running RDB manager.

  • The data is only sent from the server to the client. There is no merging (client data is overwritten).

  • If the master or a client is in split mode, the synchronization is not possible.

  • Alert classes are only synchronized if they are from the data point type _AlertClass.