SymmetricDS/Lobby

joshahicks

@joshahicks

You may want to try the pro version 30 day trial to help with setup.

It sounds like your current setup has two Symmetric nodes pointing to the same database but not clustered. Add the cluster.lock.enabled=true to your engines and see if the error goes away

https://www.jumpmind.com/products/symmetricds/try

veripolis-ms

@veripolis-ms

That actually helped. I successfully synced 2 nodes in a master-master setup in the trial version, and following the same logic, I was able to sync 2 nodes in the open source version.

However, I redid the setup in the opensource version, and when I restart the .\syn in the open source version, node 2 "failed to authenticate. It had the wrong password" and then "It had too many login attempts". Any tips on resolving this?

Also, it mysteriously remembers the old database name db2: "Could not find the target table 'db2.table' although I dropped the sym table and created it fresh on both nodes before redoing the setup.. Does it save the previously synced schema name on node 2 somewhere else than in the sym table?

veripolis-ms

@veripolis-ms

I fixed the password problem by updating it in sym_node_security. It is unknown to me why it changed.
I fixed the old database memory by deleting all the symmetricds files and re-unzipping it. It is unknown to me where & why it stored the previously synced schema.

Tony Dobbs

@TonyDobbs

Hey everyone, I'm having an interesting issue and was curious if anyone had any ideas. Last night my sync stopped. I restarted mysql and symmetric and the system was able to re-sync. Since then I have noticed intermittent errors in the log stating Communications link failure. The batch does get loaded on the next retry, but I don't recall seeing these errors before. In addition to this, when I was running some queries to check the sync status I noticed that occasionally I would receive the error 2006 MySQL server has gone away which I have never seen before. Does anyone have any ideas on what could cause these errors?

Tony Dobbs

@TonyDobbs

Found the issue!

The server was running out of memory and was killing processes

Tony Dobbs

@TonyDobbs

Hey me again! I have an interesting issue. I noticed that foreign characters are not transferring correctly between databases. I edited a row to contain the word "Gdańsk" and this correctly was stored in the database as well as in the sym_data table, but when I look in the database receiving the changes the ń is replaced with a '?' character. The same thing happens in reverse. Any ideas?

Tony Dobbs

@TonyDobbs

I tested again with the character 'á' and it worked as expected.. puzzling

joshahicks

@joshahicks

What are the source and target database types

Tony Dobbs

@TonyDobbs

@joshahicks Both are MySQL databases

I did another test last night with the character á and this transferred correctly to my surprise

joshahicks

@joshahicks

@TonyDobbs what are the charsets used by each source and target database

Tony Dobbs

@TonyDobbs

@joshahicks The charset is utf8mb4_unicode_ci for both the source and target databases

The charset of my sym_data table columns is utf8_general_ci is that matters

joshahicks

@joshahicks

@TonyDobbs I wonder if making all of them the same would help

Tony Dobbs

@TonyDobbs

Ok thank you I will try that

Zalman Lew

@zalmanlew

Anybody here ever setup a replication from Sybase to MSSQL?

dikum

@dikum

@joshahicks Syncing is currently not working on my end. I've checked the SYM_TABLE_RELOAD_REQUEST table, the records have load ids. I've checked the sym_outgoing_batch, there records have status of 'OK'. The changed data is not reflecting on the server. I have this on the log: Batch --- is not ready for delivery. It is currently scheduled for extraction. Also this: the public.update status channel for node group has only default routers.... Please help take a look. Thanks.

joshahicks

@joshahicks

@zalmanlew we have had groups replicate from Sybase to MSSQL it should not be different than any other vendors

@dikum do you see triggers physically in place on the source tables? Do you see entries in sym_data for capture

dikum

@dikum

@joshahicks There are records in sym_data table on the source DB. Regarding the Triggers, do you mean the records in SYM_TRIGGER table?

joshahicks

@joshahicks

@dikum in sym_data though are there entries for your tables

are changes for your tables being captured

dikum

@dikum

@joshahicks I see there are new records in the table but I don't know how to verify if changes are being captured. Please can you tell me the what to check so I revert? Thanks for your help.

joshahicks

@joshahicks

sym_data has a table_name column and a create_time

you should see new changes coming in here if capture is working

If you see records in here that are new you may want to take the data_id of one of them and query sym_data_event where data_id = ?

Then take the batch_id in sym_data_event that is returned and use that to query sym_outgoing_batch where batch_id = ?

This will tell you if batches are being constructed (as part of the routing process job) and being sent to the target. The status column on the sym_outgoing_batch will tell you if this batch is pending or has been committed on target

dikum

@dikum

@joshahicks I've executed the queries and the status says 'OK' on the sym_outgoing_batch table

joshahicks

@joshahicks

then it should of replicated and committed that change to the target

dikum

@dikum

@joshahicks The issue I'm currently facing is it isn't replicating. The number of rows in my tables are different.

dikum

@dikum

@joshahicks The channel id column is reload, summary has the name of the table. I don't know if this information would be of help.

joshahicks

@joshahicks

thats for initial load but doesnt line up with your queries in sym_data

do you see changes in sym_data for “deafault” channel

dikum

@dikum

@joshahicks If you mean having "default" as a value in the channel_id column, then No, I don't have records for that in the sym_data table.

joshahicks

@joshahicks

default is the main change capture channel unless you setup your own

This would mean you are not capturing changes on the source

if changes are occurring

dikum

@dikum

@joshahicks How can I capture the changes. I'm sorry, these weren't created by me. I just took over the system. So it's a bit confusing at the moment.

joshahicks

@joshahicks

You need to make sure you have valid configuration in sym_trigger, sym_router, and sym_trigger_router.

There is also a professional version that provides a web console for maintenance like this and full support. If that is something you might be interested in we can start a direct chat to discuss those options

dikum

@dikum

@joshahicks Thanks for your time. I'll look into what you've mentioned and get back.

Zalman Lew

@zalmanlew

What is the db.driver for MS SQL Server? Would it be com.microsoft.sqlserver?

Zalman Lew

@zalmanlew

I'm trying out the demo, trying to run

../bin/symadmin --engine corp-000 create-sym-tables

I'm getting an error

Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class oracle.jdbc.OracleDriver

(corp-000 is using sybase drivers )

joshahicks

@joshahicks

@zalmanlew you need to install the Oracle module

symadmin module install oracle

Zalman Lew

@zalmanlew

@joshahicks thanks, I tried that but got an error

ERROR: Invalid module specified

joshahicks

@joshahicks

@zalmanlew the demo uses H2 by default you may need to remove your engines files and start clean. What database types are you trying to replicate

There is a pro free trial for 30 days that might help you walk through the connection setup if you are having issues creating the engine files on your own

joshahicks

@joshahicks

@zalmanlew also are you running Java 8 or higher

Where communities thrive

People

Repo info

Activity