3.18.3 released
3.18.2 released
3.18.2 released
3.17.10 released
SymmetricDS 3.16.20 released
Hi Jainish, This is expected when running PostgreSQL in a cloud provider, such as GCP, AWS, and Azure. In 3.18 support for these cloud platforms moved to Symmetric-Pro. Please reach out to our sales team to discuss commercial options. https://www.jumpmind.com/symmetricds/trial/ Thank you, Andy Webb
https://symmetricds.sourceforge.net/doc/3.18/html/user-guide.html#_features
Also, the documentation mentions that Azure PostgreSQL is supported in the Community Edition. In that case, why are we getting this error? Could this be some kind of bug or compatibility issue?
Hello SymmetricDS Support, We are evaluating SymmetricDS Community Edition 3.18.1 for bidirectional synchronization between an HQ database on Azure Database for PostgreSQL and multiple child sites, each with its own standalone PostgreSQL database. The child sites are on separate networks. They can connect to HQ over the internet, but we do not have a shared network or VPN. We plan to use GUIDs for row IDs. When starting the HQ engine against Azure PostgreSQL, we receive: The detected database platform...
3.18.1 released
3.17.9 released
SymmetricDS 3.16.19 released
SymmetricDS 3.16.19 released
SymmetricDS 3.18.0 released
Hi Pavel, thank you for your response. Regarding the two possibilities you mentioned, we have already ruled both of them out: Duplicate transform setup Our setup is as simple as it gets: 2 nodes, both Oracle 1 source table, captured by exactly 1 trigger 1 trigger_router entry, routing to exactly 1 target node 1 transform_table entry (LOAD, SOURCE to TARGET) 1 transform_column entry with the BSH script No other BSH transforms exist anywhere in the configuration There is no way a duplicate transform...
Hi Vincent, Has the issue been resolved? Are there any learning to share with the community? Thanks, Pavel
SymmetricDS 3.18.0 released
SymmetricDS 3.17.8 released
3.16.18 released
Hi Vincent, I can think of two possibilities leading to BSH called twice: Duplicate transform set up. Data Conflicts (multiple CDC events from different nodes get reconciled). Either way the BSH script does not look right. Instead of "context.put" the script should return the NewAndOldValue object: return new org.jumpmind.symmetric.io.data.transform.NewAndOldValue(newValue, oldValue); There are some examples floating around with a single value return, but they are outdated and do not apply to versions...
Hi, I have a BSH column transform script that runs twice per row. I have investigated this extensively and cannot find the cause. Here is a full summary of what I found. Setup: SymmetricDS Pro 3.17.7 (Trial) One source table (SOURCE) mapped to one target table (TARGET) via one transform transform_point: LOAD update_action: UPD_ROW delete_action: DEL_ROW Only one BSH column in sym_transform_column include_on: ALL (also tested with UPDATE only, same result) One trigger, one router, one trigger_router...
Thanks for reporting this bug. We have added it to our issue tracker. You can use the following link to track its progress: https://jumpmind.atlassian.net/browse/SYM-7908
Product version: 3.14.5 (code verified identical in 3.15 branch) Component: symmetric-wrapper OS: Windows Server (issue is specific to Windows commit accounting) Summary Each SymmetricDS Windows service runs two java.exe processes: the wrapper (monitor) and the actual server engine. The heap settings wrapper.java.initmemory / wrapper.java.maxmemory from sym_service.conf are applied only to the server process. The wrapper JVM itself is launched with no -Xms/-Xmx at all, and there is no configuration...
3.17.7 released
3.16.17 released
3.16.16 released
3.16.16 released
Yes, we always carry fixes and enhancements forward to a newer release! The fix for SYM-7061 was merged in and released with 3.17.6 Feel free to give us steps to reproduce your issue and a support snapshot. You can find instructions for capturing a Support Snapshot here: https://support.jumpmind.com/kb/article/30-How-To-Take-A-Support-Snapshot https://support.jumpmind.com/kb/article/34-Take-a-Support-Snapshot-from-Commandline And you have a code fix you want to contribute back to the community, feel...
Yes, we always carry fixes and enhancements forward to a newer release! The fix for SYM-7061 was merged in and released with 3.17.6 Feel free to give us steps to reproduce your issue and a support snapshot. You can find instructions for capturing a Support Snapshot here: https://support.jumpmind.com/kb/article/30-How-To-Take-A-Support-Snapshot https://support.jumpmind.com/kb/article/34-Take-a-Support-Snapshot-from-Commandline And you have a code fix you want to contrribute back to the community,...
Which 3.17.x release includes the fix for issue 0007061? Issue 0007061 ("The (sourceExternalId) and $(targetExternalId) variables don't get replaced when included in a router's target catalog/schema") is listed as fixed in 3.16.7. I'm running 3.17.6 (community) with MySQL/MariaDB and the variables are still not being substituted in target_catalog_name, neither in sym_router nor in sym_transformtable — I get "Unknown database ' (sourceExternalId)$(sourceCatalogName)'". Is this fix included in the...
3.17.6 released
3.16.15 released
3.17.5 released
3.17.4 released
3.16.14 released
Hi Shan, This is pretty strange! Do you have the WatchDog job enabled and configured time-to-live per User guide? Feel free to share a support snapshot for both central and the store with this issue. KB article: https://support.jumpmind.com/kb/article/34-Take-a-Support-Snapshot-from-Commandline Warm regards, Pavel
3.17.3 released
Hello, this fix is included in the latest release of 3.17.2! You can see release details here: https://symmetricds.org/news/symmetricds-3-17-2-released/
Hi Team, I'm using SymmetricDS Version: 3.16.6 (Central and Store) Central Node: auto.registration=true and auto.reload=true. Scenario: Store nodes are in production. They are powered off after business hours and powered on every morning. Typically, a new store node registers once, receives a full initial load, and completes successfully (we have verified that initial_load_time and initial_load_end_time are updated in the sym_node and sym_node_security tables on both sides). Issue: Recently observed...
3.17.2 released
3.16.13 released
SymmetricDS doesn't automatically delete from sym_trigger_router. Do you think this is a SymmetricDS issue that you can reproduce in a lower environment?
Hi folks, I have faced an issue in SymmetricDS version 3.15.11. I have a 3 tier setup with a central, master and register. The sync flows from central to master and then from master to register. The reverse is also applicable for the particular table In the initial state, all the triggers for the mentioned flow was enabled. Then due to some issue we had to disable few triggers Disabled register to master and master to central flow by making sync on update and insert as 0 for the respective triggers...
Great, thank you! Would it be possible to include the fix also in 3.16.x version?
Thank you for the snapshots and the detailed write up. We were able to reproduce the issue on our end and we will include a fix in the next release of 3.17! You can see a Jira card for this issue here: https://jumpmind.atlassian.net/browse/SYM-7537 Please let us know if you have any more questions
I cannot test the bug in 3.17.1 community edition because Oracle DB is not supported anymore and install fails. So I made a new test environment for 3.16.12 and reproduced the bug. Support snapshots are attached.
Summary Replication fails with IndexOutOfBoundsException when an Oracle TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE column contains a NULL value. Regular TIMESTAMP columns with NULL values replicate correctly. SymmetricDS Version 3.14.19 (community edition) 3.15.22 (community edition) 3.16.12 (community edition) Database Oracle 19c (source and target) Steps to Reproduce Create a test table on the source database: CREATE TABLE ORA_TIMESTAMP_TEST ( ID NUMBER(12) NOT NULL, TIMESTAMP3...
Would you be able to upload a Symmetric Support Snapshot from the 3.17.1 install? Details to take a support snapshot can be found here: https://support.jumpmind.com/kb/article/34-Take-a-Support-Snapshot-from-Commandline
Summary Replication fails with IndexOutOfBoundsException when an Oracle TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE column contains a NULL value. Regular TIMESTAMP columns with NULL values replicate correctly. SymmetricDS Version 3.14.19 (community edition) 3.15.22 (community edition) 3.16.12 (community edition) 3.17.1 (community edition) Database Oracle 19c (source and target) Steps to Reproduce Create a test table on the source database: CREATE TABLE ORA_TIMESTAMP_TEST ( ID NUMBER(12)...
Summary Replication fails with IndexOutOfBoundsException when an Oracle TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE column contains a NULL value. Regular TIMESTAMP columns with NULL values replicate correctly. SymmetricDS Version 3.14.19 (community edition) 3.15.22 (community edition) 3.16.12 (community edition) 3.17.1 (community edition) Database Oracle 19c (source and target) Steps to Reproduce Create a test table on the source database: CREATE TABLE ORA_TIMESTAMP_TEST ( ID NUMBER(12)...
Hi Susant, This an unusual issue! Could you share a support snapshot or logs from the node that has this problem, please? You can find instructions for capturing a Support Snapshot here: Command line: https://support.jumpmind.com/kb/article/34-Take-a-Support-Snapshot-from-Commandline PRO edition's web UI: https://support.jumpmind.com/kb/article/30-How-To-Take-A-Support-Snapshot Warm regards, Pavel
Hi, I recently upgraded SymmetricDS from version 3.11.11 to 3.15.11. My setup includes one central node, multiple store nodes, and their respective register nodes. So far, I have upgraded the central node, one store node, and two register nodes to 3.15.11. The remaining store and register nodes are still on version 3.11.11. After the upgrade, I’m facing an issue with data synchronization from the central node to the store node. Batches for master data (employee table) are being created repeatedly...
3.17.1 released
3.16.12 released
SymmetricDS Discord Server
SymmetricDS Discord Server
SymmetricDS Discord Server
SymmetricDS uses encryption which is part of the HTTPS protocol.
3.17.0 released
3.17.0 released
3.16.11 released
3.16.11 released
3.16.11 released
Hi Shan, Please refer to Symmetric DS User Guide MySQL section: https://symmetricds.sourceforge.net/doc/3.16/html/user-guide.html#_mysql. You will want to use the instructions and grants outlined there and in the MariaDB section as well.
Hi Dwi, If you don't have any foreign keys across tables you could move them into separate channels and queues to achieve parallel processing. You could move all the tables with foreign keys into a channel and queue as well. Here's a related article: https://medium.com/data-weekly/channel-ing-your-symmetricds-configuration-706b6c19cb.
Hi Team, currently configured SymmetricDS version 3.16.6 with MariaDB 10.x. After upgrading to MariaDb 11.8, during Symds startup, getting the below error message in the Symds log: 1) Failed to get metadata - Access denied: you need (atleast one of) the process privilege( s) for this operation. 2) Failed to retrive node group links. i.e Accessing any tables from information schema, getting Access denied error. This issue is observed after upgrading Mariadb. Team is having concern to give grant PROCESS...
i have a question right now im running mariadb to postgresql using symmetricds i have 30 tables and 2 of them can cause the outgoing batches stuck on LD for too long for example table A is update heavy table which every 1 minutes it gives 5 batches and each batches contain 3k - 6k rows of data. and the target table on postgresql is also 1:1 with mariadb same indexes same PKs, it has 72 column and 22 indexes how do i do a parallel so it doesnt affect to another table, because when LD this table, another...
Thanks, Pavel for answering. I tried db.delimited.identifier.mode=true, and it made no difference. I will probably rename the columns, but if I have time I will create a test project demonstrating the problem.