The commands are what TAC had sent to me. Ask your engineer if they recommend them as well. Have them verify in the Install/Switch Version Logs. Have them check for the most recent COP file is installed. Both had led my engineer to determine it was a replication issue in my case. If the Subscriber is not pulling the information from the Publisher then I would guess they will come to the same conclusion. I hope this helps resolve your issue.
... View more
We had the same issue. We were also on the Unrestricted version of Unity Connection. After weeks and weeks of working with TAC we finally figured out that it is a replication issue. Replication showed as a "2" but when switching versions it became out of sync. I am not sure about your cluster set up but I would bring up this on your TAC case. Below are the commands that I used to fix the issue with replication. After replication was repaired the switch version via CLI worked. I hope this helps. On Subscriber run – utils dbreplication stop (here you have to wait some time once is finish wait for like 10 min.) On Publisher run – utils dbreplication stop (here you have to wait some time once is finish wait for like 10 min.) On Publisher run – utils dbreplication reset all Reboot both servers using: utils system restart On the Subscriber utils cuc cluster overwritedb (here you also need to give it time)
... View more