CUIC users not Replicating in Member node in Version:10.5(1) build 1 (10_5_1_10000_7

[Ramamoorthy Shanmugam]

Dear All,

  We installed CUIC 10.5.1 Publisher and communicating with UCCE data source . Recently I installed one member and sync with CUIC first node .After sync we were able to get the real time reports from both the nodes . But I have created one user from PUBLISHER node that name is not replicating in Member node .

I have restarted both the nodes and Synchronize Cluster from PUB to Member node using the below commands .

commands in sequence from publisher node CLI:

-          utils dbreplication stop all

-          utils dbreplication reset all

Member Node :

-------------------- utils dbreplication status --------------------

connect to reccuic2_ccm10_5_1_10000_7 failed

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

admin:utils dbreplication runtimestate

DB and Replication Services: ALL RUNNING

Cluster Replication State: Only available on the PUB

DB Version: ccm10_5_1_10000_7

Number of replicated tables: 0

Cluster Detailed View from SUB (2 Servers):

                                PING            REPLICATION     REPL.   DBver&  REPL.   REPLICATION SETUP

SERVER-NAME     IP ADDRESS      (msec)  RPC?    STATUS          QUEUE   TABLES  LOOP?   (RTMT)

-----------     ------------    ------  ----    -----------     -----   ------- -----   -----------------

CUIC1       172.25.6.85     0.721   Yes     Off-Line        N/A     631     N/A     (2)

CUIC2        172.25.26.85    0.022   Yes     Off-Line        N/A     match   N/A     (0)

First Node :

admin:utils dbreplication runtimestate

DB and Replication Services: ALL RUNNING

Cluster Replication State: Replication status command started at: 2016-01-04-16-24

     Replication status command COMPLETED 583 tables checked out of 631

     Processing Table:

     No Errors or Mismatches found.

     Use 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2016_01_04_16_24_20.out' to see the details

DB Version: ccm10_5_1_10000_7

Number of replicated tables: 631

Cluster Detailed View from PUB (2 Servers):

                                PING            REPLICATION     REPL.   DBver&  REPL.   REPLICATION SETUP

SERVER-NAME     IP ADDRESS      (msec)  RPC?    STATUS          QUEUE   TABLES  LOOP?   (RTMT) & details

-----------     ------------    ------  ----    -----------     -----   ------- -----   -----------------

CUIC1       172.25.6.85     0.024   Yes     Connected       0       match   Yes     (2) PUB Setup Completed

CUIC2        172.25.26.85    0.436   Yes     Off-Line        N/A     0       N/A     (0) Not Setup

admin:

Please help me to fix this issues .

Ramamoorthy 

[Gergely Szabo]

Hi,

could you please attach the log file to this post?

Also, make sure both forward and reverse DNS and NTP work (set up correctly).

G.

[Ramamoorthy Shanmugam]

Hi Gergely,

Please find attached cuic db replication status, I have verified all the steps and i could not find any Network issues. Please help us to solve this problem.

Real time report is working fin on both the Nodes , But replication is not happening from PUB to SUB .

Ram. 

[Gergely Szabo]

Hi,

did you ever use the security password recovery procedure?

G.

[Ramamoorthy Shanmugam]

No, During Installation we used PUB Security Password and the time of  installation no error / warnings occurred.  

[Gergely Szabo]

Hi,

did it ever work?

Also, this is what I got from TAC when trying to solve a similar CUIC replication issue:

1.       Please follow below steps:
*         utils dbreplication stop on Sub - wait till it finishes
*         utils dbreplication stop on Pub - wait till it finishes
*         utils dbreplication dropadmindb - on both nodes, can be run the same time
*         utils dbreplication reset all - from Pub
*         wait till is done and then verify replication status via: utils dbreplication runtimestate
2.       If possible restart Sub and then Pub after they are back verify replication again utils dbreplication runtimestate

Did/can you try the above?

G.

[Ramamoorthy Shanmugam]

Hi Gergely,

 Thank for your reply, I tried your steps but no luck . I have restarted CUIC SUB node , PUB not yet restarted .Please find attached files .

[Gergely Szabo]

OK, try restarting the Pub as well and then wait for at least 10 minutes and then take a look at the replication runtimestate.

G.

[Ramamoorthy Shanmugam · Accepted solution]

Hi All,

TAC has identified cam password is invalid from PUB to Node . After reset the password replication is happening from Primary node to Secondary node. 

Ramamoorthy Shanmugam 

[Gergely Szabo]

Hi, OK, I am glad it worked out. Thanks for letting us know. G.