That whole blog post should probably be added to the SymmetricDS user guide though ;)
Hi Eric, Thank you for your reply. You were absolutely correct! I was not aware of this requirement. Switching to SymmetricDS Pro also helped a lot, as I could see when the transform became active in the GUI.
I put it everywhere. Sadly it did not work. I have created the tables manually at the target database instead. This worked :)
I want to synchronize a few tables from SQL Anywhere to Azure SQL. The tables may have a lot of foreign key references, but I don't care about referential integrity in the Azure SQL database. I tried defining create.table.without.foreign.keys=true in all engines, but the foreign key constraints are still created when I send a table reload request to the Azure database. I have tried completely cleaning both databases, but when the tables are synchronized, the constraints are created. Is there something...
I want to synchronise a few tables from SQL Anywhere to Azure SQL. The tables may have a lot of foreignkey references, but I don't care about referential integrity in the Azure SQL database. I tried defining create.table.without.foreign.keys=true in all engines, but the foreign key constraints are still created when I send a table reload request to the Azure database. I have tried completely cleaning both databases, but when the tables are synchronized, the constraints are created. Is there something...
Hi Evan, I have attempted to create a column transform, however I could not get it to generate a new column at the target node. The following is what I have tried: insert into "dbo"."sym_transform_table" ( transform_id, source_node_group_id, target_node_group_id, transform_point, source_schema_name, source_table_name, target_table_name, update_action, delete_action, transform_order, column_policy, update_first, last_update_by, last_update_time, create_time ) values ( 'Ledger', 'local', 'stage', 'EXTRACT',...
I had this issue as well. After trying a lot of different combinations for schema_name and catalog_name in sym_trigger, I was finally able to find something where SymmetricDS was able to find the table, both for trigger creation and deletion. In my case, I used a SQL Anywhere database, but I don't know which DBMS you are using.
Hello everyone, Almost finished with setting up SymmetricDS, but still one thing I cannot figure out. I need to add an extra column to the target database which tells what node the data comes from. I have 4 "cannot change" SQL Anywhere databases, from which I wish to sync a few tables to a central Azure SQL database. The connection is working fine, and when running with a single SQL Anywhere database, the table synchronizes to Azure without problems. What I wish to accomplish is adding an extra column...
After furter testing I now discovered that entries in symmetric-server.properties are forwarded to Spring! After adding the following to symmetric-server.properties, the error is now gone :D spring.jdbc.getParameterType.ignore=true Happy debugging!
After furter testing I now discovered that entries in symmetric-server.properties are forwarded to Spring! After adding the following to symmetric-server.properties, the error is now gone :D spring.jdbc.getParameterType.ignore=true Happy debugging!
EDIT: double-post
After more research it seems that the Sybase JDBC driver does not support "getParameterMetaData()", and will always return null. Spring Framework does not account for this, as they only catch SQLException, and not NullPointerException. Instead, they assume you configure the property "spring.jdbc.getParameterType.ignore" if you have a driver that does not support this. Perhaps this should be registered as a bug in SymmetricDS? Otherwise, an option to send propertyflags to Spring Framework would be...
After more research it seems that the Sybase JDBC driver does not support "getParameterMetaData()", and will always return null. Spring Framework does not account for this, as they only catch SQLException, and not NullPointerException. Instead, they assume you configure the property "spring.jdbc.getParameterType.ignore" if you have a driver that does not support this. Perhaps this should be registered as a bug in SymmetricDS? Otherwise, an option to send propertyflags to Spring Framework would be...
Hi Evan, I tried switching to Java 8, but I seem to be getting the same error, except the detail-level of the error is less now. I tried looking up the setNull function in Spring, and found this: https://github.com/spring-projects/spring-framework/blob/3c2dfebf4ec5e9d791c1f3c9fa0ad35a5a9fcd6b/spring-jdbc/src/main/java/org/springframework/jdbc/core/StatementCreatorUtils.java#L239 snippet: if (sqlType == SqlTypeValue.TYPE_UNKNOWN || (sqlType == Types.OTHER && typeName == null)) { boolean useSetObject...
Hi Evan, I tried switching to Java 8, but I seem to be getting the same error, except the detail-level of the error is less now. I tried looking up the setNull function in Spring, and found this: https://github.com/spring-projects/spring-framework/blob/3c2dfebf4ec5e9d791c1f3c9fa0ad35a5a9fcd6b/spring-jdbc/src/main/java/org/springframework/jdbc/core/StatementCreatorUtils.java#L239 snippet: if (sqlType == SqlTypeValue.TYPE_UNKNOWN || (sqlType == Types.OTHER && typeName == null)) { boolean useSetObject...
After removing the ojdbc driver from the lib directory, it now got much much further! The symadmin --engine test create-sym-tables command almost succeeded. It managed to create all the symlink tables [ ... lots of successful creations before this ...] [test] - SqlAnywhereSymmetricDialect - DDL applied: ALTER TABLE "sym_trigger_router_grouplet" ADD CONSTRAINT "sym_fk_trgplt_2_gplt" FOREIGN KEY ("grouplet_id") REFERENCES "sym_grouplet" ("grouplet_id") [test] - SqlAnywhereSymmetricDialect - DDL applied:...
It now got much much further! The symadmin --engine test create-sym-tables command almost succeeded. It managed to create all the symlink tables [ ... lots of successful creations before this ...] [test] - SqlAnywhereSymmetricDialect - DDL applied: ALTER TABLE "sym_trigger_router_grouplet" ADD CONSTRAINT "sym_fk_trgplt_2_gplt" FOREIGN KEY ("grouplet_id") REFERENCES "sym_grouplet" ("grouplet_id") [test] - SqlAnywhereSymmetricDialect - DDL applied: ALTER TABLE "sym_trigger_router_grouplet" ADD CONSTRAINT...
It now got much much further! The symadmin --engine test create-sym-tables command almost succeeded. It managed to create all the symlink tables [ ... lots of successful creations before this ...] [test] - SqlAnywhereSymmetricDialect - DDL applied: ALTER TABLE "sym_trigger_router_grouplet" ADD CONSTRAINT "sym_fk_trgplt_2_gplt" FOREIGN KEY ("grouplet_id") REFERENCES "sym_grouplet" ("grouplet_id") [test] - SqlAnywhereSymmetricDialect - DDL applied: ALTER TABLE "sym_trigger_router_grouplet" ADD CONSTRAINT...
Hello everyone, I recently discovered SymmetricDS, and decided it would be a great soluition for synchronising our databases. We are currently using Sybase 16 SQL Anywhere databases, and want to sync them with an Azure SQL database. However, I am stuck getting to connection from SymmetricDS to the Sybase database to work. The following is what I have tried: Download fresh installation of SymmetricDS Update http.port in conf/symmetric-server.properties Run symadmin module install sybase to get the...