Database replication mismatch on CUCM cluster after upgrade

Unanswered Question
Oct 22nd, 2008

Dear all,

After Upgrading the CUCM from 5.1.2.3000 to 5.1.3.4000 the cluster database is not same on both servers. One more thing when trying to insert new phone or update any phone on the SUB node i got the following error:

"Reset Failed. java.sql.SQLException: No UPDATE permission"

Please what can i do in this situation?

kindly advice

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Loading.
Jaime Valencia Wed, 10/22/2008 - 11:52

make sure all nodes are running the same version and there is no component mismatch, use the utils dbreplication commands to restore the replication between nodes

HTH

java

if this helps, please rate

eemara949 Thu, 10/23/2008 - 02:25

Thank you my dear, i downgraded the CUCM and everything back to noraml.

allan.thomas Thu, 10/23/2008 - 11:48

When you attempt the upgrade again, make sure that you verify the dbreplication status before you begin.

That way you can be sure that at least this shouldn't be a problem following the switchover.

Also, always switch the inactive partition on the Publisher following the upgrade before you switch the inactive partitions on the subscribers.

The show tech dbstateinfo cli command available in 5.1(3) should give a good indication of the dbstates, or alternative verify same through the RTMT database summary. Anything other than a status of 2 is cause for concern..

Rgds

Allan.

Actions

This Discussion