cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
251
Views
2
Helpful
1
Replies

11.6.2 Database Replication Errors

Kamil G
Level 1
Level 1

When I try to set the process to '40' , it tells me that I need to do it on the primary node (which I am):

admin:utils dbreplication setprocess 40
This CLI can be run only on the publisher node

 

After running the "utils dbreplication status" command, I noticed errors... (see attached log file) 

admin:utils dbreplication runtimestate

Server Time: Mon Aug 19 00:25:07 EDT 2024

Cluster Replication State: Errors or data mismatches were found in utils dbreplication status at: 2024-08-19-00-21
Use CLI to see detail: 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2024_08_18_23_45_46_ccmdbtemplate.out'

DB Version: ccm11_6_2_10000_38

Repltimeout set to: 300s
PROCESS option set to: 1


Cluster Detailed View from hh-tx11-ucw030 (2 Servers):

PING DB/RPC/ REPL. Replication REPLICATION SETUP
SERVER-NAME IP ADDRESS (msec) DbMon? QUEUE Group ID (RTMT) & Details
----------- ---------- ------ ------- ----- ----------- ------------------
hh-tx11-ucw030 10.91.4.99 0.021 Y/Y/Y 0 (g_2) (2) Setup Completed
hh-nh11-ucw030 10.91.0.98 45.267 Y/Y/Y 0 (g_3) (2) Setup Completed

admin:
admin:
admin:utils dbreplication repair all
-------------------- utils dbreplication repair --------------------
chmod: changing permissions of `/var/log/active/cm/trace/dbl/sdi/replication_scripts_output.log': Operation not permitted
sh: /usr/local/cm/db/REPL_STATE_RPC: Permission denied
sh: /usr/local/cm/db/REPL_STATE_RPC: Permission denied
sh: /usr/local/cm/db/REPL_STATE_RPC: Permission denied

Replication Repair is now running in the background.
Use command 'utils dbreplication runtimestate' to check its progress

Output for ccmdbtemplate Database will be in file cm/trace/dbl/sdi/ReplicationRepair.2024_08_19_00_26_55_ccmdbtemplate.out
Please use "file view activelog cm/trace/dbl/sdi/ReplicationRepair.2024_08_19_00_26_55_ccmdbtemplate.out " command to see the output

Output for template_db_phx_config Database will be in file cm/trace/dbl/sdi/ReplicationRepair.2024_08_19_00_26_55_template_db_phx_config.out
Please use "file view activelog cm/trace/dbl/sdi/ReplicationRepair.2024_08_19_00_26_55_template_db_phx_config.out " command to see the output

Output for cuic_db_template Database will be in file cm/trace/dbl/sdi/ReplicationRepair.2024_08_19_00_26_55_cuic_db_template.out
Please use "file view activelog cm/trace/dbl/sdi/ReplicationRepair.2024_08_19_00_26_55_cuic_db_template.out " command to see the output
admin:
admin:

 

1 Reply 1

You have tried Step 7 in the attached guide, which says that after running Utils dbreplication repair all, you should proceed to Step 8 if the status does not change. Step 8 involves resetting the database replication from scratch, which should solve your problem. I have faced this issue a couple of times where Utils dbreplication repair all didn’t fix my problems.

 

 

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200396-Steps-to-Troubleshoot-Database-Replicati.html

NithinEluvathingal_0-1724306413875.png

 



Response Signature