tpcolson

Real-time Geodatabase Replication? Part 4

Blog Post created by tpcolson on Jan 1, 2015

Making Sure the Agent is Working 

 

Before we dive into testing replicated CRUD operations on either SDE instance we need to make sure the Agent(s) are working.

 

In Replication Monitor select the Agent tab and right-click on Snapshot Agent and select Start Agent. It should report "Running".

 

When it reports "Completed" double-click on it. You should see something like this:

 

r3452.JPG

This indicates that the Agent is successfully reading the local (source) table TEST and any changes and publishing change articles to the server share.

 

Select the All Subscriptions tab and double-click on the subscription. You should see something like this:

 

r3e243.JPG

Now create lots of new points in the TEST feature class on the local (publication) SDE instance. Wait a few minutes and refresh the Subscription status in Monitor.

 

You should see something like this:

 

453432.JPG

This indicates that inserts on the FISH database are being replicated to the FEMPFISH database. Success! Try some updates and deletes.

 

However it is very likely you'll see some errors like this, which is related to our previous issue of the Geography column being converted to text. While we did update the properties of the Publication Agent to correctly merge the spatial column we need to reinitialize the subscription agent to recognize this change.

 

re432423.JPG

 

To resolve this:

 

Restart the Publication Agent:

 

qwer4325432.JPG

 

After is has completed its job with 100% success stop, and restart, the sync agent:

 

r3254232.JPG

aws4r3432.JPG

 

Real-time Geodatabase Replication? Part 1

Real-time Geodatabase Replication? Part 2

Real-time Geodatabase Replication? Part 3

Real-time Geodatabase Replication? Part 4

Real-time Geodatabase Replication? Part 5

Real-time Geodatabase Replication? Part 6

 

 

This is a personal blog and does not recommend, endorse, or support the methods described above. Alteration of data using SQL outside of the ESRI software stack, of course, is not supported and should not be applied to a production database without a thorough understanding and disaster recovery plan.

Outcomes