In a Master / Subordinate UVMS Architecture, the UVMS Master pushes updates for the Logins or Groups every 15 minutes for ALL defined Logins or Groups which is not normal as objects have not changed.
This creates thousands of records in the UVMS Subordinate table UNI_UV_AUDIT_TRAIL until eventually breaking the Synchronization as it hits a Primary Key error in the UVMS Subordinate table UNI_UV_AUDIT_TRAIL as below:
|ERROR| Master synhro thread pool-1-Perform UVMS synchro-1 | com.orsyp.central.synchro.MasterSynchroPoolFeeder | Error while synchronizing the node: uvms_subordinate
com.orsyp.UniverseException: An error occurred while synchronizing (true) the security object GROUP for subordinate : uvms_subordinate
Caused by: java.sql.BatchUpdateException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'PK_UNI_UV_AUDIT_TRAIL' defined on 'UNI_UV_AUDIT_TRAIL'.
Release : 6.x
Component : Univiewer Management Server
Problem in the UVMS Master Synchronization process, some Deleted Objects were not properly pushed to the Subordinate causing this continous update of the Objects during each Synchronization.
Update to a fix version listed below or a newer version if available.
Dollar Universe 6.10.101 - Planned Release Second Half May 2022
If the UVMS Subordinate stops working due to this problem, please raise a case with Technical Support to perform the truncate of the Table UNI_UV_AUDIT_TRAIL to workaround the issue.