Activity for Michael Drouard
-
Michael Drouard posted a comment on discussion Open Discussion
I'm glad to see that you were able to find a work around. If you upgrade to the latest 3.16.8 you will be able to use Symmetric transforms along with a host of other new features and bug fixes.
-
This error indicates that there may be an issue with DB permissions. It is pointing to an inability to select from the sym_parameter table. Could you please verify that the DB account for SymmetricDS is allowed to SELECT, UPDATE, DELETE from newly created table(s)? Also, could you verify that your JDBC driver version matches the server version? The meta data surrounding table structure is not being returned to SymmetricDS.
-
Yes, node group pushing to itself will work. It is like a multi primary.
-
Can you provide steps to reproduce this situation? Also we have opened a ticket for this issue that can be found here: https://issues.symmetricds.org/view.php?id=6997 You can add steps to reproduce this issue there.
-
This issue is fixed in 3.16.3. A link to the issue in the tracker can be found here: https://issues.symmetricds.org/view.php?id=6910 Alternatively you can flip the following parameter from true: sync.use.ready.queues=false
-
This issue is fixed in 3.16.3. A link to the issue in the tracker can be found here: https://issues.symmetricds.org/view.php?id=6910 Alternatively you an flip the following parameter from true: sync.use.ready.queues=false
-
Was this set on the correct database? This would need to be on the database for node 004. The error is occurring on the client side node. Symmetric pools its connections, you may need to restart it to pick up the setting change.
-
"thread_id is 0." Thread ID being 0 is correct. Is the batch not being loaded on the target? Are you seeing the data from the source node loaded on the target node? Are you resetting the test with a different table? There was a batch 14 on 4-30, and in the above log snippet there was also a batch 14 on 5-02. In addition the message is not an error, but rather just an info statement saying the extract has been running for more than 60 seconds. Would you be able to attach a SymmetricDS support snapshot?...
-
There is currently no limit in SymmetricDS 3.16 and earlier
-
This is a bug and we added an issue to our tracker. To work around this do not use the auto create table feature. Instead, you can create the table manually. You can also set the parameter initial.load.before.sql to add your sql script to create tables. https://issues.symmetricds.org/view.php?id=6812
-
This is the parameter: trigger.capture.ddl.changes=true This will need to be set to true in your engine file. **This only works for supported database platforms SQL Server, Postgres, and Oracle. You will need to restart the service after changing the engine file Execute this command to rebuild triggers on demand: symadmin sync-triggers
-
There are details on the main differences between Symmetric Pro and Symmetric core here - https://symmetricds.org/about/. There is also commercial support included with Symmetric Pro. You can reach out to sales@jumpmind.com if you would like a demo.
-
On Node 1 look in the table sym_node_security for a registration time of node 2, and check to see if the registration flag is now off. A batch with "node -1" indicates that the target may not be registered.
-
Make the jump from 3.14.5 to 3.15.9. These versions do have different system requirements, Java 17 is required. Either upgrade option works, there were no significant structural changes.
-
In your conf/log4j2.xml if the configuration element is using the packages element it is no longer supported. You can remove the packages attribute.
-
There are deployments that are handling 20M+ rows per hour, which is well beyond the rate you stated. A rule of thumb for servers is one server-class CPU with 2 GB of memory for every 500 MB/hour of data transfer and 350 clients.
-
In the upgrade from 3.8 -> 3.15 there is a new conflict manager. There is a parameter that you can change to use the older version. Change conflict.default.pk.with.fallback=true. This may help with duplicates.
1
