I have replication set up for a table going from Oracle 10G to PostgreSQL 9.1.
I am having trouble getting "inline" reload to work for that table. I'm mostly using the Mx4j interface, although I have seen the same behavior with symadmin.
Some things which were not obvious, which I've learned:
1 - When you fill in the form, you put in the destination node, but the source schema and table name.
2 - Reload does not do an "upsert". It ignores primary key collisions.
3 - The only collision behavior tunable using reload is the initial.load.delete.first property.
(other than the "load filters" which I'm still trying to understand) This means that if you have a "mostly correct" table in the destination node, you first have to wipe it out (and do without it) and then reload it from scratch. Inline reload can not "fix" rows in the table.
4 - You only need to set the initial.load.delete.first=true property in the source node's property table.
What I'm observing is setting initial.load.delete.first deletes all of the rows in the destination table, but no data gets loaded. There are no particular errors or exceptions. Status gets set to 'OK' on both sides and everything looks good ... except that the table is empty on the destination node.
I can wipe the node's table out by hand, and reload - nothing goes over.
I can update, insert, and delete on the source node, and those changes replicate perfectly fine.
I can use the out-of-band tools, dbexport/dbimport to load the table. (I can even use them to do the "upsert" style data fixing without any problems.) It is just the inline reload that doesn't seem to work.
I've looked through the available properties and options and double checked things like the initial load select in the trigger_router table. I've yet to come across anything obvious that would explain why SymmetricDS thinks the reload went ok, but nothing happened.
dang, I posted in the Mobile Forum... again. Sorry about that. There doesn't appear to be a way to move this to one of the other forums.