Forum,
I have been reviewing previous posted in respect to UCM Database Communication Error. I am running into the same issue for Unity Connection. I recently tried to upgrade my UCN v11.0.1.21900-11 to v11.5. I followed the typical published documentation by Cisco. I performed the upgrades via application GUI.
For the UCN publisher, the upgrade failed twice with radial button selection 'Manually restart' after. However...about 1.5hrs the application seems to be finished...the log showing 'release_upgrade_lock'...but sits there and does nothing further for several hours (like 3+ hours) on both occasions. Keep in mind...this is a lab...a few mailboxes tied to the application with 12 active ports, no application traffic.
So the third attempt on the upgrade, I selected the 'switch versions and reboot after upgrade' radial button and the log indicated a successful upgrade. I proceeded to do the same with the UCN subscriber and the log indicated a successful upgrade and would proceed with reboot.
Now...observations...the UCN application never switched over when selecting the 2nd radial button 'switch versions and reboot after upgrade' so the application still runs v11.0.1.21900-11 for both UCN pub and sub servers. I can log into the GUI of my UCN publisher...however, the cluster is not running as indicated on the GUI. The UCN Sub has the 'Database Communication Error' when logging into the app.
In the UCN Sub CLI, run
admin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.2016_07_11_09_48_01.out
Mon Jul 11 09:48:01 2016 main() DEBUG: -->
Mon Jul 11 09:48:08 2016 main() DEBUG: Replication cluster summary:
SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_2_ccm11_0_1_21900_11 2 Active Connected 0 Jul 11 08:37:22
g_3_ccm11_0_1_21900_11 3 Active Local 0
Mon Jul 11 09:48:23 2016 main() DEBUG: <--
This seems to be good...I get the same type of response with the UCN publisher. I also ran 'utils dbreplication repair all' with the following output
SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_2_ccm11_0_1_21900_11 2 Active Connected 0 Jul 11 08:37:22
g_3_ccm11_0_1_21900_11 3 Active Local 0
Mon Jul 11 09:50:16 2016 dbllib.getReplServerName DEBUG: -->
Mon Jul 11 09:50:26 2016 dbllib.getReplServerName DEBUG: replservername: g_2_ccm11_0_1_21900_11
Mon Jul 11 09:50:26 2016 dbllib.getReplServerName DEBUG: <--
I am lost...any takers...open for suggestions.
