View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003354SymmetricDSBugpublic2018-01-05 12:572019-02-27 13:57
Reporterpgsql Assigned Toadmin  
Prioritynormal 
Status closedResolutionno change required 
Product Version3.9.1 
Summary0003354: Data is Not replicating in Community Edition
DescriptionI am doing MS-SQL to postgresql replication, for that I have configured symmetricds on both nodes but data is not replicating. I have given the steps in Steps to reproduce which I have performed. Also providing logs here:

Logs:
2018-01-05 17:40:41,738 INFO [store-001] [DataGapFastDetector] [store-001-job-1] Full gap analysis is running
2018-01-05 17:40:41,744 INFO [store-001] [DataGapFastDetector] [store-001-job-1] Querying data in gaps from database took 5 ms
2018-01-05 17:40:41,744 INFO [store-001] [DataGapFastDetector] [store-001-job-1] Full gap analysis is done after 6 ms
2018-01-05 17:40:41,868 INFO [store-001] [NodeCommunicationService] [store-001-job-3] pull will use 10 threads
2018-01-05 17:40:46,786 INFO [store-001] [RouterService] [store-001-job-8] The 'heartbeat' channel is NOT in common batch mode
2018-01-05 17:40:46,929 INFO [store-001] [RouterService] [store-001-job-8] Routed 1 data events in 176 ms
2018-01-05 17:41:05,638 INFO [store-001] [PullUriHandler] [qtp319977154-11] 1 data and 1 batches sent during pull request from corp:000:000
2018-01-05 17:41:15,903 INFO [store-001] [ConfigurationChangedDatabaseWriterFilter] [qtp319977154-15] About to syncTriggers because new configuration came through the data loader
2018-01-05 17:41:15,904 INFO [store-001] [TriggerRouterService] [qtp319977154-15] Synchronizing triggers
2018-01-05 17:41:16,987 INFO [store-001] [RouterService] [store-001-job-17] The 'config' channel is NOT in common batch mode
2018-01-05 17:41:17,248 INFO [store-001] [RouterService] [store-001-job-17] Routed 6 data events in 279 ms
2018-01-05 17:41:17,509 INFO [store-001] [TriggerRouterService] [qtp319977154-15] Done synchronizing triggers
2018-01-05 17:41:17,510 INFO [store-001] [DataLoaderService] [qtp319977154-15] 6 data and 2 batches loaded during push request from corp:000:000.
2018-01-05 17:55:43,131 INFO [store-001] [RouterService] [store-001-job-13] Routed 1 data events in 117 ms
2018-01-05 17:55:45,048 INFO [store-001] [PullUriHandler] [qtp319977154-15] 1 data and 1 batches sent during pull request from corp:000:000
2018-01-05 17:56:16,265 INFO [store-001] [DataLoaderService] [qtp319977154-14] 1 data and 1 batches loaded during push request from corp:000:000.
2018-01-05 17:56:18,180 INFO [store-001] [RouterService] [store-001-job-10] Routed 1 data events in 18 ms
2018-01-05 18:10:43,977 INFO [store-001] [RouterService] [store-001-job-4] Routed 1 data events in 88 ms
2018-01-05 18:10:45,353 INFO [store-001] [PullUriHandler] [qtp319977154-14] 1 data and 1 batches sent during pull request from corp:000:000
2018-01-05 18:11:15,939 INFO [store-001] [DataLoaderService] [qtp319977154-13] 1 data and 1 batches loaded during push request from corp:000:000.
2018-01-05 18:11:19,043 INFO [store-001] [RouterService] [store-001-job-16] Routed 1 data events in 34 ms

Kindly give me solution as soon as possible.
Steps To ReproduceSteps:

1. Firstly Download the SymmetricDS Community edition from www.jumpmind.com website. Unzip the file symmetric-server-3.9.1zip on both Master Node(MS-SQL server) and Slave Node(Postgresql server).

2. On master node Copy the corp-000.properties file from symmetric-server-3.9.1\samples path and paste this file to symmetric-server-3.9.1\engines path. Follow same procedure on target node but copy store-001.properties file.

3. Now do the changes in the parameter of the corp-000.properties and store-001.properties files.

In corp-000.properties
engine.name = corp-000
db.driver=net.sourceforge.jtds.jdbc.Driver
db.url=jdbc:jtds:sqlserver://hostip:port/databasename;useCursors=true;bufferMaxMemory=10240;lobBuffer=5242880
db.user=put the database user here
db.password=put the database password here
sync.url=http://hostip:31415/sync/corp-000
group.id=corp
external.id=000
In store-001.properties
engine.name=store-001
sync.url = http://hostip:31415/sync/store-001
db.driver=org.postgresql.Driver
db.url=jdbc:postgresql://hostip:port/databasename?protocolVersion=2&stringtyp e=unspecified
db.user=put the database user here
db.password=put the database password here
registration.url=http://masternodeip:31415/sync/corp-000
group.id=store
external.id=001
4. Create system tables on master node by running following command on master node:
symmetric-server-3.9.1/bin/symadmin --engine corp-000 create-sym-tables

5. Now Insert the values in the system tales:

         insert into SYM_NODE_GROUP
        (node_group_id)values(‘store’);

         insert into SYM_NODE_GROUP_LINK
        (source_node_group_id, target_node_group_id, data_event_action)values ('corp', 'store', 'P');
             
          Where P = Push

           insert into SYM_NODE_GROUP_LINK
(source_node_group_id, target_node_group_id, data_event_action)
      values ('store', 'corp', 'W');
    
          Where W = Wait for pull

          insert into SYM_ROUTER (router_id,
        source_node_group_id, target_node_group_id, create_time,
        last_update_time) values ('corp-2-store','corp', 'store',current_timestamp, current_timestamp);


        insert into SYM_CHANNEL (channel_id, processing_order, max_batch_size, max_batch_to_send,extract_period_millis, batch_algorithm, enabled, description)values ('patient_dtl', 10, 1000, 10, 0, 'default', 1, ‘Patient Details');

        insert into SYM_TRIGGER (trigger_id, source_table_name,
          channel_id, last_update_time, create_time)values ('patient_dtl', 'patient_dtl', 'patient_dtl', current_timestamp, current_timestamp);

        insert into SYM_TRIGGER_ROUTER(trigger_id, router_id, initial_load_order, create_time,last_update_time)values ('patient_dtl', 'corp-2-store', 1, current_timestamp,
current_timestamp);

The Setup and configuration is now completed.




6. We will now start both SymmetricDS nodes

On master node:
symmetric-server-3.9.1/bin/sym

On Slave Node:
symmetric-server-3.9.1/bin/
and run ./sym
This command on slave node system tables automatically. It begins polling the server node in order to register.


7. Registering a Node
Open registration for the slave node server by executing the below command on master node cmd:

symmetric-server-3.9.1/bin/symadmin –-engine corp-000 open-registration store 001

 The registration is now opened for a node group called “store” with an external identifier of “001”.

8. Sending an Initial Load
               Next, we will send an initial load of data to our store (that is, the slave node)

     Send an initial load of data to the client node server by executing following command on master node cmd:
          symmetric-server-3.9.1/bin/symadmin –-engine corp-000 reload-node 001
TagsNo tags attached.

Relationships

has duplicate 0003353 closed Data not replicating in community edition 
has duplicate 0003351 closed SymmetricDS Community Edition replication not happening 
has duplicate 0003350 closed Regarding SymmetricDS Community Edition 
has duplicate 0003352 closed Replication not happening in Community Edition 3.9.1 

Activities

hanes

2018-10-03 12:43

developer   ~0001248

Unable to recreate your issue in 3.9.13 based on the information provided. A couple of thoughts:
1. Did your patient_dtl table exist on both corp and store-001 databases? SymmetricDS will not automatically create the table by default if it doesn't already exist.
2. Was there any errors in either log file?

admin

2019-02-27 13:57

administrator   ~0001396

Closing, nothing to fix. Use forums for support.

Issue History

Date Modified Username Field Change
2018-01-05 12:57 pgsql New Issue
2018-10-03 12:43 hanes Status new => feedback
2018-10-03 12:43 hanes Note Added: 0001248
2018-10-03 12:46 hanes Relationship added has duplicate 0003353
2018-10-03 12:48 hanes Relationship added has duplicate 0003351
2018-10-03 12:48 hanes Relationship added has duplicate 0003350
2018-10-03 12:48 hanes Relationship added has duplicate 0003352
2018-10-03 16:39 hanes Priority urgent => normal
2019-02-27 13:57 admin Assigned To => admin
2019-02-27 13:57 admin Status feedback => closed
2019-02-27 13:57 admin Resolution open => no change required
2019-02-27 13:57 admin Note Added: 0001396