Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...

Chapter 4Managing your network database59cdr_er_cleanup.shThis script:• Removes a subhost from Enterprise Replication when run on the subhost.• Removes ER completely when run on the nethost with no arguments.• Removes a subhost when run from the nethost using the -s argument accompanied by thename of the server to be removed. If the server name provided is the nethost, the result is thesame as if the script was run from the nethost with no arguments.The script must be run on every subhost or from the nethost to perform a complete ER removalbefore the system can be brought up again.The cdr_er_cleanup.sh script can be run from the command line or from ercmd.sh. The usermust be root or ppadmin.Enterprise Replication conflict resolution and spoolingWhen conflicting data is encountered during ER between source and target servers, Picture Perfectapplies the following rules for conflict resolution:• Time stamp The row or transaction with the most recent time stamp is applied. This rule is used for bi-directional replicate tables (person/base).• Always-apply ER does not attempt to resolve conflicts, but always applies source datato the target. This rule is used for uni-directional replicate tables(host_time).To implement conflict resolution, two types of shadow objects are used in ER: shadow columns andshadow tables.Enterprise Replication backup/restoreEnterprise Replication does not impact the current database backup functionality. However, thedatabase recovery/restore functionality has some new constraints:• The Recovery option is no longer available from the client GUI. Recovery must be performedusing the restore.sh command line option.• Recovery cannot be performed while TPS is running.• The cbr command may be used on a running system only when history restoring data fromarchives for reporting purposes (see Picture Perfect 4.6 User Manual, Chapter 15).• When restoring from backups on an Enterprise system, replication is stopped, triggers aredisabled, data is restored, replication is restarted, and triggers are re-enabled.• Enterprise Replication is turned off when modifying the database during a restore operation.- Restore is normally done during installation. After installation all the hosts are resynchronizedusing hostconfig.- Restore is also done via dropreloaddb, in which case hostconfig also resynchronizesthe hosts.- If Restore is called outside of these two scenarios, the ercmd.sh (restore table)command should be used to manually synchronize the database tables.