UCCX DB replication is not setup properly, Backup Completed

[Ravi Saggu]

UCCX Version: 11.6su2

UCCX cluster not able to backup because of uccx dbreplication issue

admin:utils uccx dbreplication status
Replication server status :
Error: Error returned from cdr_adjust_INFORMIXSERVER: database syscdr
SQLCODE -27001 ISAM 0

Error Details:
27001: Read error occurred during connection attempt.

Current Connection: None
command failed -- SQL failure (195)
Can not switch to syscdr sqlcode:-27001 isamcode:0

Command successful.

admin:utils dbreplication runtimestate

Server Time: Sat Mar 4 22:42:32 EST 2023

Cluster Replication State: BROADCAST SYNC ended at: 2023-02-28-00-30
Sync Result: SYNC COMPLETED on 834 tables out of 834
Sync Status: All Tables are in sync
Use CLI to see detail: 'file view activelog cm/trace/dbl/20230228_002552_dbl_repl_output_Broadcast.log'

DB Version: ccm11_6_2_10000_38

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

Cluster Detailed View from UCCX-PUB (2 Servers):

PING DB/RPC/ REPL. Replication REPLICATION SETUP
SERVER-NAME IP ADDRESS (msec) DbMon? QUEUE Group ID (RTMT) & Details
----------- ---------- ------ ------- ----- ----------- ------------------
UCCX-PUB 10.X.X.X 0.013 Y/Y/Y 0 (g_2) (2) Setup Completed
uccx-sub 192.X.X.X 1.340 Y/Y/Y 0 (g_4) (2) Setup Completed

Step taken but still no success with bac:

UCCX Serviceability -> Tools -> Datastore Control Center -> Replication Servers -> disable CDS/HDS -> click on Reset Replication -> then Enable CDS/HDS

utils dbreplication reset all

utils service stop Cisco DRF Local

utils service stop Cisco DRF Master

utils service start Cisco DRF Local

utils service start Cisco DRF Master

utils service restart Cisco Unified CCX Database (on both nodes)

[Thomas G. Johannesen]

Has it ever worked. ?

Are the 2 servers same version ?

[Ravi Saggu]

Hi Thomas,

Yes last backup was done Feb27.

Before I have seen this same error but after performing uccx dbreplication fixed I was able to get backup but this time I'm not able too.

Yes version are same

PUB:admin:show version active
Active Master Version: 11.6.2.10000-38
Active Version Installed Software Options:
ciscouccx.1162.ES.Rollback.cop
ciscouccx.1162.1251SU2PREUPGRADE.41.cop
ciscouccx.1162.ES06.19.cop
ucos.keymanagement.v01.cop

SUB:admin:show version active
Active Master Version: 11.6.2.10000-38
Active Version Installed Software Options:
ciscouccx.1162.ES06.19.cop
ciscouccx.1162.1251SU2PREUPGRADE.41.cop
ucos.keymanagement.v01.cop

admin:utils uccx dbreplication reset all

Version mis-match detected

First node's version is

Second node's version is 11.6.2.10000-38.i386

Replication can be setup only when the nodes in the cluster have the same version

Replication teardown failed. This should generally not be a problem.

Refer to the replication log for detailed information.

Replication definition failed.

Refer to the replication log for detailed information.

[Ravi Saggu]

admin:utils uccx dbreplication reset all

Version mis-match detected

First node's version is

Second node's version is 11.6.2.10000-38.i386

Replication can be setup only when the nodes in the cluster have the same version

Replication teardown failed. This should generally not be a problem.

Refer to the replication log for detailed information.

Replication definition failed.

Refer to the replication log for detailed information.

[Ravi Saggu]

I was able to successfully backup

Step Taken:

Reset the database
utils dbreplication stop all (Only on the publisher)
utils dbreplication dropadmindb (First on all the subscribers one by one then the publisher)
utils dbreplication reset all ( Only on the publisher )

----waited database to sync -----

Restarted the UCCX cluster

UCCX Serviceability -> Tools -> Datastore Control Center -> Replication Servers -> disable CDS/HDS -> click on Reset Replication -> then Enable CDS/HDS
Also check the datastore where you see all nodes are at running replication status
(This Step was done multiple times and also cross check connective status via on Subscriber UCCX Serviceability)

After this backup was success.

Please rate helpful posts.