Hi,
After changing the hostname of all servers (CUCM 7.1.5), I ended up with database replication issue.
Database status report shows that the subscriber still refers to the old publisher hostname although ip addresses are updated.
I ran utils dbreplication stop, utils dbreplication reset all, then restarted the subscriber.
RTMT database summary shows publisher replication status 2.
But subscriber replication all attributes are blank. As if there is no subscriber.
What is the quickest and best way to fix this replication issue? All licences etc are installed, but the subscriber server is not in production yet. I am happy to rebuild the subscriber server if this is the best option. I appreciate your advice.
SUBSCRIBER:
admin:utils dbreplication status
-------------------- utils dbreplication status --------------------
connect to auhodccm01_ccm7_1_5_30000_1 failed <<<<<===== This is the subscriber itself
Enterprise Replication not active (62)
command failed -- unable to connect to server specified (5)
Replication status check is now running in background.
Use command 'utils dbreplication runtimestate' to check its progress
The final output will be in file cm/trace/dbl/sdi/ReplicationStatus.2011_06_30_12_38_56.out
Please use "file view activelog cm/trace/dbl/sdi/ReplicationStatus.2011_06_30_12_38_56.out " command to see the output
admin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.2011_06_30_12_38_56.out
connect to auhodccm01_ccm7_1_5_30000_1 failed
Enterprise Replication not active (62)
command failed -- unable to connect to server specified (5)
-------------------------------------------------
No Errors or Mismatches found.
Replication status is good on all available servers.
utils dbreplication status output
To determine if replication is suspect, look for the following:
(1) Number of rows in a table do not match on all nodes.
(2) Non-zero values occur in any of the other output columns for a table
connect to syscdr@auhodccm01_ccm7_1_5_30000_1 failed
Enterprise Replication not active (62)
command failed -- unable to connect to server specified (5)
Error Details:
I copied the database summary report that shows the mismatch on subscriber.
| 10.1.6.130 | #This file was generated by the /etc/hosts cluster manager. #It is automatically updated as nodes are added, changed, removed from the cluster. 127.0.0.1 localhost ::1 localhost 10.1.6.130 AUOPDCCM01 10.23.34.10 AUHODCCM01 |
|---|---|
| 10.23.34.10 | #This file was generated by the /etc/hosts cluster manager.
#It is automatically updated as nodes are added, changed, removed from the cluster.
127.0.0.1 localhost
::1 localhost
10.1.6.130 AUDCHOMCCM01
10.23.34.10 AUHODCCM01
|
| Server | rhosts File |
|---|---|
| 10.1.6.130 | localhost AUHODCCM01 AUOPDCCM01 |
| 10.23.34.10 | localhost
AUDCHOMCCM01
AUHODCCM01
|
| Checks the contents of the sqlhosts file on each installed server and returns a summary checking to see if they are equivalent. |
 | The sqlhosts file on 10.23.34.10 does not match the publisher. |
View Details| Server | sqlhosts File |
|---|---|
| 10.1.6.130 | g_hdr group - - i=1 g_auopdccm01_ccm7_1_5_30000_1 group - - i=2 auopdccm01_ccm7_1_5_30000_1 onsoctcp 10.1.6.130 auopdccm01_ccm7_1_5_30000_1 g=g_auopdccm01_ccm7_1_5_30000_1 b=32767,rto=300 g_auhodccm01_ccm7_1_5_30000_1 group - - i=4 auhodccm01_ccm7_1_5_30000_1 onsoctcp 10.23.34.10 auhodccm01_ccm7_1_5_30000_1 g=g_auhodccm01_ccm7_1_5_30000_1 b=32767,rto=300 |
| 10.23.34.10 | g_hdr group - - i=1
g_audchomccm01_ccm7_1_5_30000_1 group - - i=2
audchomccm01_ccm7_1_5_30000_1 onsoctcp 10.1.6.130 audchomccm01_ccm7_1_5_30000_1 g=g_audchomccm01_ccm7_1_5_30000_1 b=32767,rto=300
g_auhodccm01_ccm7_1_5_30000_1 group - - i=4
auhodccm01_ccm7_1_5_30000_1 onsoctcp 10.23.34.10 auhodccm01_ccm7_1_5_30000_1 g=g_auhodccm01_ccm7 |
Regards,
Alp
