How to do a SYNC of CA Directory Manually when the EEM Cluster Setup fails and give you a 846 Network Error

Document ID : KB000019252
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

This document take you step by step on synchronizing the CA Directory DB manually what the SYNC command does not work for the customer.

Solution:

During the EEM Failover Cluster setup (provided in the EEM Implementation Guide title "How to Setup a failover environment?") you get a 846 Network error when trying to run the java setup in the secondary server you get the 846 error every time; Which will not let you run the sync command.

The following is the java command that is needed to run the cluster setup

java -jar eiam-clustersetup.jar -p <FQDN_PrimaryServerName>

In this ClusterSetup command CA Directory is able to sycy all the database entries from the primary server to the secondary. We will be running through the same steps manually.

EEM1 and EEM2
We can do that last step manually so the database sync up and the information can be copied over to the secondary server. Once the information is copiedall updates are sent successfully.

on EEM1 (Primary)

Open up the command prompt and type: "telnet localhost 10510"

This will return with a screen that says "dsa>"

At the dsa prompt type

dump dxgrid-db; (it will give you a message that dump is being created)

Then type "logout;" to exit the program.

Open up you window explorer and navigate to DXHOME/data/iTechPoz-EEM1/

You will find a itechpoz-ServerName.zdb You will need to copy this over to EEM2.

On EEM2 (Secondary)

On the Command prompt type "dxsever stop itechpoz-eem2"

Open Windows explorer and navigate to: DXHOME/data/itechpoz-eem2

Delete the itechpoz-eem2.tx file

Rename the itechpoz-eem2.db to itechpoz-eem2.old

Copy the itechpoz-eem1.zdb from EEM1 to this EEM2 under this same folder.

Rename the itechpoz-eem1.zdb to itechpoz-eem2.db

dxserver start all

Star will create a "new" itechpoz-eem2.tx

Now you can test the replication by creating a test policy on primary and check the secondary, then delete on secondary and check the delete come over to the primary.